classic V2A deprecation

Author: Ankita Dutta

articles/site-recovery/vmware-physical-azure-classic-deprecation.md

@@ -4,40 +4,41 @@ description: Details about upcoming deprecation of classic experience to protect
 services: site-recovery
 author: Sharmistha-Rai
 ms.service: site-recovery
-ms.topic: article
+ms.topic: conceptual
 ms.date: 03/02/2023
-ms.author: ankitaduttaMSFT 
+ms.author: ankitadutta
 
 ---
 
 # Deprecation of classic experience to protect VMware and Physical machines using Azure Site Recovery 
 
-This article describes the upcoming deprecation plan, the corresponding implications, and the alternative options available for the customers for the following scenario:
+This article describes the upcoming deprecation plan, corresponding implications, and the alternative options available to the customers in the following scenario:
 
 Classic experience to protect VMware and physical machines to Azure using Site Recovery
 
 > [!IMPORTANT]
-> On November 15, 2023, the support for classic experience to protect VMware and Physical machines using Azure Site Recovery will be deprecated. It is advised to move to the [modernized experience](how-to-move-from-classic-to-modernized-vmware-disaster-recovery.md) at the earliest to avoid any disruption to environment and minimize security risk. 
+> The support for the classic experience of protecting VMware and physical machines using Azure Site Recovery will be discontinued on March 15, 2026. We recommend switching to the [modernized experience](how-to-move-from-classic-to-modernized-vmware-disaster-recovery.md) at the earliest to avoid any disruption to your environment and minimize security risks. 
 
 ## What changes should you expect?
 
-- Starting November 2022, you'll receive Azure portal notifications & email communications with the upcoming deprecation of classic replication experience of VMware and physical machines. The capability will be completely deprecated and go out of support on November 2023.
+- Starting November 2022, you'll receive Azure portal notifications & email communications for the upcoming deprecation of classic replication experience of VMware and physical machines. This capability will no longer be supported after March 30, 2026.
 
-- Starting 15 November 2022, only use the new, modernized experience can be used to enable Azure Site Recovery for all newly created Recovery Services vaults.
+- Starting March 15, 2023, you can only use the modernized experience to enable Azure Site Recovery for all newly created Recovery Services vaults.
 
-- Existing VMware and physical machines can remain on the classic management experience until 15 November 2023. However, changes to any configurations of the replication on these existing VMware and physical machines will require upgrade to the new modernized experience, starting 15 April 2023. 
+- Existing VMware and physical machines can remain on the classic management experience until March 30, 2026. However, changes to any configurations of the replication on these existing VMware and physical machines will require upgrade to the new modernized experience, starting 15 April 2023. 
 
-- Any support for new features or improvements, along with mobility agent support for new Linux distros, will only be released on the new, modernized experience.
+- Support for new features or improvements, along with mobility agent support for new Linux distros, will only be available on the modernized experience.
+
+- If you do not migrate your machines by March 30, 2026, the replication health of your machines may be disrupted and you will no longer be able to view, manage, or perform any disaster recovery-related operations through the Azure Site Recovery experience in the Azure portal.
 
-- Replication health of all machines not migrated by 15 November 2023 may get disrupted. Customers won't be able to view, manage, or performs any DR-related operations via the Azure Site Recovery experience in Azure portal. 
 
 ## Alternatives 
 
-[Modernized experience](vmware-azure-architecture-modernized.md) is the alternative that the customer should choose to ensure that their DR strategy isn't impacted once the experience is deprecated. 
+The [modernized experience](vmware-azure-architecture-modernized.md) is an alternative that the customer should choose to ensure that their DR strategy isn't impacted once the experience is deprecated. 
 
 ## Remediation steps
 
-Execute the following steps to move your existing replications to the modernized experience:
+Follow these steps to move your existing replications to the modernized experience:
 
 1. [Check the required infrastructure for your setup](move-from-classic-to-modernized-vmware-disaster-recovery.md#how-to-define-required-infrastructure) and the [FAQs](move-from-classic-to-modernized-vmware-disaster-recovery.md#faqs) for all related information.
 2. [Check the architecture and minimum version of all components](move-from-classic-to-modernized-vmware-disaster-recovery.md#architecture) required for this migration.
@@ -48,4 +49,6 @@ Execute the following steps to move your existing replications to the modernized
 
 ## Next steps
 
-Plan for the deprecation and move to the modernized experience to experience the [benefits](move-from-classic-to-modernized-vmware-disaster-recovery.md#why-should-i-migrate-my-machines-to-the-modernized-architecture) and stay up-to-date. In case you have any queries regarding this deprecation, reach out to Microsoft Support.
+Plan ahead for the deprecation and move to the modernized experience to take advantage of its [benefits](move-from-classic-to-modernized-vmware-disaster-recovery.md#why-should-i-migrate-my-machines-to-the-modernized-architecture) and stay up-to-date. 
+
+In case you have any queries regarding this deprecation, reach out to Microsoft Support.