classic V2A deprecation

Ankita Dutta · Ankita Dutta · commit 1059c228d4b7 · 2023-03-02T19:17:16.000+05:30
diff --git a/articles/site-recovery/move-from-classic-to-modernized-vmware-disaster-recovery.md b/articles/site-recovery/move-from-classic-to-modernized-vmware-disaster-recovery.md
@@ -3,7 +3,7 @@ title: Move from classic to modernized VMware disaster recovery.
 description: Learn about the architecture, necessary infrastructure, and FAQs about moving your VMware replications from classic to modernized protection architecture.
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 01/13/2023
+ms.date: 03/02/2023
 author: ankitaduttaMSFT
 ms.custom: engagement-fy23
 ---
@@ -12,29 +12,30 @@ ms.custom: engagement-fy23
 
 This article provides information about the architecture, necessary infrastructure, and FAQs about moving your VMware or Physical machine replications from [classic](./vmware-azure-architecture.md) to [modernized](./vmware-azure-architecture-modernized.md) protection architecture. With this capability to migrate, you can successfully transfer your replicated items from a configuration server to an Azure Site Recovery replication appliance. This migration is guided by a smart replication mechanism, which ensures that complete initial replication isn't performed again for non-critical replicated items, and only the differential data is transferred. 
 
-> [!Note]
+> [!NOTE]
 > Recovery plans won't be migrated and will need to be created again in the modernized Recovery Services vault.  
 
 ## Architecture  
 
 The components involved in the migration of replicated items of a VMware machine are summarized in the following table:  
 
-|Component|Requirement|
+| Component |Requirement|
 |---------|-------------|
 |Replicated items in a classic Recovery Services vault| One or more replicated items that are protected using the classic architecture and a healthy configuration server.<br></br>The replicated item should be in a non-critical state and must be replicated from on-premises to Azure with the mobility agent running on version 9.50 or later.|
-|Configuration server used by the replicated items|The configuration server, used by the replicated items, should be in a non-critical state and its components should be upgraded to the latest version (9.50 or later).|  
+|Configuration server used by the replicated items|The configuration server, used by the replicated items, should be in a non-critical state and its components should be upgraded to the latest version (9.50 or later).|
 |A Recovery Services vault with modernized experience|A Recovery Services vault with modernized experience.|
 |A healthy Azure Site Recovery replication appliance|A non-critical Azure Site Recovery replication appliance, which can discover on-premises machines, with all its components upgraded to the latest version (9.50 or later). The exact required versions are as follows:<br></br>Process server: 9.50<br>Proxy server: 1.35.8419.34591<br>Recovery services agent: 2.0.9249.0<br>Replication service: 1.35.8433.24227|
 
 ## Required infrastructure  
 
 Ensure the following for a successful movement of replicated item: 
 - A Recovery Services vault using the modernized experience.   
-  >[!Note] 
-  >Any new Recovery Services vault created will have the modernized experience switched on by default. You can [switch to the classic experience](./vmware-azure-common-questions.md#how-do-i-use-the-classic-experience-in-the-recovery-services-vault-rather-than-the-modernized-experience) but once done, you can’t switch again.   
+  >[!NOTE] 
+  > Classic experience will be [deprecated](vmware-physical-azure-classic-deprecation.md) in November 2023 and its use is discouraged. Any newly created Recovery Services vaults will always have the modernized experience.
+   
 - An [Azure Site Recovery replication appliance](./deploy-vmware-azure-replication-appliance-modernized.md), which has been successfully registered to the vault, and all its components are in a non-critical state.   
 - The version of the appliance must be 9.50 or later. For a detailed version description, check [here](#architecture). 
-- The vCenter server or vSphere host’s details, where the existing replicated machines reside, are added to the appliance for the on-premises discovery to be successful.   
+- The vCenter server or vSphere host’s details, where the existing replicated machines reside, are added to the appliance for the on-premises discovery to be successful.  
 
 ## Prerequisites  
 
@@ -122,7 +123,7 @@ Ultimately, the classic architecture will be deprecated, so one must ensure that
 |Classic architecture| Modernized architecture [New]|
 |---------------------|-----------------------------|
 |Multiple setups required for discovering on-premises data.|**Central discovery** of on-premises data center using discovery service.| 
-|Extensive number of steps required for initial onboarding.|**Simplified the onboarding experience** by automating artifact creation and introduced defaults to reduce required inputs.|  
+|Extensive number of steps required for initial onboarding.|**Simplified the onboarding experience** by automating artifact creation and introduced defaults to reduce required inputs.|
 |Utilizes a manually downloaded file to obtain cloud context.|**Introduced replication key** for obtaining cloud context when setting up the appliance.|
 |Extensive number of steps required for a simple enable replication process.|**Simplified the enable replication experience** by reducing the number of required inputs and redefining each blade.|
 |Configuration server continues to be an on-premises infrastructure with extensive setup for various components.|Enhanced the appliance by converting all components into Azure hosted microservices. This **simplifies appliance scaling, monitoring, and troubleshooting.**|
@@ -189,4 +190,6 @@ All replicated items, which are a part of a replication group will be migrated t
 
 ## Next steps
 
-[How to move from classic to modernized VMware disaster recovery](how-to-move-from-classic-to-modernized-vmware-disaster-recovery.md)
+[How to move from classic to modernized VMware disaster recovery](how-to-move-from-classic-to-modernized-vmware-disaster-recovery.md).
+
+
diff --git a/articles/site-recovery/toc.yml b/articles/site-recovery/toc.yml
@@ -151,6 +151,8 @@
     href: ../availability-zones/migrate-recovery-services-vault.md
   - name: About VMware VM disaster recovery
     items:
+    - name: Deprecation of classic experience
+      href: vmware-physical-azure-classic-deprecation.md
     - name: VMware disaster recovery overview
       href: vmware-azure-about-disaster-recovery.md
     - name: Common questions
@@ -189,6 +191,8 @@
       href: exclude-disks-replication.md
   - name: About physical server disaster recovery
     items:
+    - name: Deprecation of classic experience
+      href: vmware-physical-azure-classic-deprecation.md
     - name: VMware/physical to Azure support matrix
       href: vmware-physical-azure-support-matrix.md
     - name: Physical server to Azure architecture
@@ -299,6 +303,8 @@
         href: unregister-vmm-server-script.md
   - name: VMware to Azure disaster recovery
     items:
+    - name: Deprecation of classic experience
+      href: vmware-physical-azure-classic-deprecation.md
     - name: Set up disaster recovery at scale
       href: vmware-physical-large-deployment.md
     - name: Set up networking
diff --git a/articles/site-recovery/vmware-azure-common-questions.md b/articles/site-recovery/vmware-azure-common-questions.md
@@ -1,13 +1,14 @@
 ---
 title: Common questions about VMware disaster recovery with Azure Site Recovery
 description: Get answers to common questions about disaster recovery of on-premises VMware VMs to Azure by using Azure Site Recovery.
-ms.date: 12/28/2022
+ms.date: 03/02/2023
 ms.topic: conceptual
 ms.service: site-recovery
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ms.custom: engagement-fy23
 ---
+
 # Common questions about VMware to Azure replication
 
 This article answers common questions that might come up when you deploy disaster recovery of on-premises VMware virtual machines (VMs) to Azure.
@@ -19,23 +20,7 @@ This article answers common questions that might come up when you deploy disaste
 
 ### How do I use the classic experience in the Recovery Services vault rather than the modernized experience? 
 
-A new and more reliable way to protect VMware virtual machines using the Azure Site Recovery replication appliance is now generally available. When a new Recovery Services vault is created, by default the modernized experience will be selected. 
-
-
-To change the experience - 
-
-1. Open the vault on Azure portal. 
-2. Click on **Site Recovery** in the **Getting started** section. 
-3. Click on the banner on top of this page. 
-
-    [![Modify VMware stack step 1](./media/vmware-azure-common-questions/change-stack-step-1.png)](./media/vmware-azure-common-questions/change-stack-step-1.png#lightbox)
-
-4. This will open the experience selection blade. Select the classic experience if you want to use configuration server and then click on **OK**. If not, close the pane. 
-
-    [![Modify VMware stack step 2](./media/vmware-azure-common-questions/change-stack-step-2.png)](./media/vmware-azure-common-questions/change-stack-step-2.png#lightbox)
-
-> [!NOTE]
-> Note that once the experience type has been switched to classic from modernized, it cannot be switched again in the same Recovery Services vault. Ensure that the desired experience is selected, before saving this change.
+Moving to the classic experience in a newly created Recovery Services is not possible as it will be [deprecated](vmware-physical-azure-classic-deprecation.md) in November 2023. All new Recovery Services vaults will be using the modernized experience. 
 
 ### Can I migrate to the modernized experience? 
 
diff --git a/articles/site-recovery/vmware-physical-azure-classic-deprecation.md b/articles/site-recovery/vmware-physical-azure-classic-deprecation.md
@@ -0,0 +1,51 @@
+---
+title: Deprecation of classic experience to protect VMware and Physical machines using Azure Site Recovery | Microsoft Docs
+description: Details about upcoming deprecation of classic experience to protect VMware and Physical machines to Azure and alternate options
+services: site-recovery
+author: Sharmistha-Rai
+ms.service: site-recovery
+ms.topic: article
+ms.date: 03/02/2023
+ms.author: ankitaduttaMSFT 
+
+---
+
+# 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:
+
+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. 
+
+## 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 15 November 2022, only use the new, modernized experience can be used 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. 
+
+- 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.
+
+- 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. 
+
+## Remediation steps
+
+Execute the following 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.
+3. Check all the [resources required](move-from-classic-to-modernized-vmware-disaster-recovery.md#required-infrastructure) and deploy the [Azure Site Recovery replication appliance](deploy-vmware-azure-replication-appliance-modernized.md).  
+4. [Prepare the classic Recovery Services vault](move-from-classic-to-modernized-vmware-disaster-recovery.md#prepare-classic-recovery-services-vault) used by your existing replications.
+5. [Prepare the modernized Recovery Services vault](move-from-classic-to-modernized-vmware-disaster-recovery.md#prepare-modernized-recovery-services-vault) where your appliance has been registered.
+6. [Trigger migration for your existing replications](how-to-move-from-classic-to-modernized-vmware-disaster-recovery.md).
+
+## 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.
