Skip to content

Commit df8c8ef

Browse files
committed
Correction in how to move section
1 parent 7b98dde commit df8c8ef

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ The components involved in the migration of replicated items of a VMware machine
3131
Ensure the following for a successful movement of replicated item:
3232
- A Recovery Services vault using the modernized experience.  
3333
>[!Note]
34-
>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.  
34+
>Any new Recovery Services vault created will have the modernized experience switched on by default. You can not switch to the classic experience as its deprecation has already been [announced](./vmware-physical-azure-classic-deprecation).  
3535
- 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 noncritical state.  
3636
- The version of the appliance must be 9.50 or later. For a detailed version description, check [here](#architecture).
3737
- 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.  

0 commit comments

Comments
 (0)