URLs for government cloud

Author: SharmisthaRai

articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md

@@ -72,9 +72,6 @@ Ensure the following URLs are allowed and reachable from the Azure Site Recovery
 
 Ensure the following URLs are allowed and reachable from the Azure Site Recovery replication appliance for continuous connectivity, when enabling replication to a government cloud:
 
-
-
-
   | **URL for Fairfax**                  | **URL for Mooncake**                             | **Details**                             |
   | ------------------------- | -------------------------------------------| -------------------------------------------|
   | `login.microsoftonline.us/*` <br> `graph.microsoftazure.us` | `login.chinacloudapi.cn/*` <br> `graph.chinacloudapi.cn` | To sign-in to your Azure subscription.  |
@@ -84,30 +81,6 @@ Ensure the following URLs are allowed and reachable from the Azure Site Recovery
   |`*.vault.usgovcloudapi.net`| `*.vault.azure.cn` |Manage secrets in the Azure Key Vault. Note: Ensure that the machines which need to be replicated have access to this. |
 
 
-Mooncake
-  =========
-https://portal.azure.cn/
-https://management.chinacloudapi.cn//.default
-https://login.chinacloudapi.cn
-https://login.chinacloudapi.cn/<tenantid>/oauth2/deviceauth
-https://graph.chinacloudapi.cn
-https://management.chinacloudapi.cn
-https://login.chinacloudapi.cn/login.srf
-https://portal.partner.microsoftonline.cn/#
-https://portal.partner.microsoftonline.cn/login?IdentityProvider=aad&ru=%2Fdefault.aspx
-https://login.chinacloudapi.cn/common
-
-  FAIRFAX
-  =======
-
-https://login.microsoftonline.us/<tenantid>/oauth2/deviceauth
-https://management.usgovcloudapi.net//.default
-https://login.microsoftonline.us/
-https://graph.microsoftazure.us
-https://management.usgovcloudapi.net
-https://login.microsoftonline.us/login.srf
-https://portal.azure.us/#
-
 ### Folder exclusions from Antivirus program
 
 #### If Antivirus Software is active on appliance
@@ -130,7 +103,7 @@ C:\Program Files\Microsoft Azure VMware Discovery Service <br>
 C:\Program Files\Microsoft On-Premise to Azure Replication agent <br>
 E:\ <br>
 
-#### If Antivirus software is active on Source machine
+#### If Antivirus software is active on source machine
 
 If source machine has an Antivirus software active, installation folder should be excluded. So, exclude folder C:\ProgramData\ASR\agent for smooth replication.
 

articles/site-recovery/move-from-classic-to-modernized-vmware-disaster-recovery.md

@@ -32,7 +32,7 @@ The components involved in the migration of replicated items of a VMware machine
 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 always have the modernized experience as classic experience will be [deprecated](vmware-physical-azure-classic-deprecation.md) in Novemebr 2023 and is not recommended to be used.
+  >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.   
 - 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.   
@@ -43,7 +43,7 @@ Ensure the following for a successful movement of replicated item:
 
 Ensure the following before you move from classic architecture to modernized architecture: 
 
-- [Create a Recovery Services vault](./azure-to-azure-tutorial-enable-replication.md#create-a-recovery-services-vault).md#how-do-i-use-the-classic-experience-in-the-recovery-services-vault-rather-than-the-modernized-experience). 
+- [Create a Recovery Services vault](./azure-to-azure-tutorial-enable-replication.md#create-a-recovery-services-vault) and ensure the experience has [not been switched to classic](./vmware-azure-common-questions.md#how-do-i-use-the-classic-experience-in-the-recovery-services-vault-rather-than-the-modernized-experience)
 - [Deploy an Azure Site Recovery replication appliance](./deploy-vmware-azure-replication-appliance-modernized.md). 
 - [Add the on-premises machine’s vCenter Server details](./deploy-vmware-azure-replication-appliance-modernized.md) to the appliance, so that it successfully performs discovery.   
 

articles/site-recovery/toc.yml

@@ -133,8 +133,6 @@
     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
@@ -173,8 +171,6 @@
       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
@@ -279,8 +275,6 @@
         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
@@ -373,8 +367,6 @@
         href: delete-vault.md
   - name: Physical 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

articles/site-recovery/vmware-azure-common-questions.md

@@ -17,7 +17,23 @@ 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? 
 
-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.  
+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.
 
 ### Can I migrate to the modernized experience?