Merge pull request #171474 from hirenshah1/patch-20

Update classic-vm-deprecation.md

Author: PRMerger16

articles/virtual-machines/classic-vm-deprecation.md

@@ -28,11 +28,12 @@ VMs created using the classic deployment model will follow the [Modern Lifecycle
 - On March 1, 2023, subscriptions that are not migrated to Azure Resource Manager will be informed regarding timelines for deleting any remaining VMs (classic).  
 
 This retirement does *not* affect the following Azure services and functionality: 
-- [Azure Cloud Services (classic)](../cloud-services/cloud-services-choose-me.md)
 - Storage accounts *not* used by VMs (classic) 
 - Virtual networks *not* used by VMs (classic) 
 - Other classic resources
 
+Azure Cloud Services (classic) retirement was announced in August 2021 [here](https://azure.microsoft.com/updates/cloud-services-retirement-announcement/)
+
 ## What resources are available for this migration?
 
 - [Microsoft Q&A](/answers/topics/azure-virtual-machines-migration.html): Microsoft and community support for migration.
@@ -65,4 +66,4 @@ Start planning your migration to Azure Resource Manager, today.
 
 1. For technical questions, issues, and help with adding subscriptions to the allowlist, [contact support](https://ms.portal.azure.com/#create/Microsoft.Support/Parameters/{"pesId":"6f16735c-b0ae-b275-ad3a-03479cfa1396","supportTopicId":"8a82f77d-c3ab-7b08-d915-776b4ff64ff4"}).
 
-1. Complete the migration as soon as possible to prevent business impact and to take advantage of the improved performance, security, and new features of Azure Resource Manager.
+1. Complete the migration as soon as possible to prevent business impact and to take advantage of the improved performance, security, and new features of Azure Resource Manager.