---
layout: Conceptual
title: Deprecation of classic experience to protect VMware and physical machines using Azure Site Recovery - Azure Site Recovery | Azure Docs
canonicalUrl: https://docs.azure.cn/en-us/site-recovery/vmware-physical-azure-classic-deprecation
breadcrumb_path: /bread/toc.json
uhfHeaderId: mooncake
recommendations: false
author: WendiZ
ms.author: v-leozhao
ms.service: azure-site-recovery
description: Details about upcoming deprecation of classic experience to protect VMware and physical machines to Azure and alternate options
ms.topic: overview
ms.date: 2025-10-13T00:00:00.0000000Z
locale: en-us
document_id: b833d498-5e62-b308-fdc5-0ef413a1fded
document_version_independent_id: 8f9ad2e5-811b-4ec4-75a6-96cc5f81a164
updated_at: 2025-10-15T06:37:00.0000000Z
original_content_git_url: https://github.com/MicrosoftDocs/mc-docs-pr/blob/live/articles/site-recovery/vmware-physical-azure-classic-deprecation.md
gitcommit: https://github.com/MicrosoftDocs/mc-docs-pr/blob/d66ddfc11e9ae70d8520e0a3a83fce6760101a8e/articles/site-recovery/vmware-physical-azure-classic-deprecation.md
git_commit_id: d66ddfc11e9ae70d8520e0a3a83fce6760101a8e
site_name: DocsAzureCN
depot_name: Azure.mooncake-docs
page_type: conceptual
toc_rel: toc.json
feedback_system: None
feedback_product_url: ''
feedback_help_link_type: ''
feedback_help_link_url: ''
word_count: 414
asset_id: site-recovery/vmware-physical-azure-classic-deprecation
moniker_range_name: 
monikers: []
item_type: Content
source_path: articles/site-recovery/vmware-physical-azure-classic-deprecation.md
cmProducts:
- https://authoring-docs-microsoft.poolparty.biz/devrel/bba62c59-6b53-4be4-8b9d-6624f9184c22
- https://authoring-docs-microsoft.poolparty.biz/devrel/68ec7f3a-2bc6-459f-b959-19beb729907d
spProducts:
- https://authoring-docs-microsoft.poolparty.biz/devrel/f3a81ffb-ee36-4ec7-b54a-01b6681aff65
- https://authoring-docs-microsoft.poolparty.biz/devrel/90370425-aca4-4a39-9533-d52e5e002a5d
platformId: a6ee1c1c-4441-da5e-b951-9790462f1450
---

# Deprecation of classic experience to protect VMware and physical machines using Azure Site Recovery - Azure Site Recovery | Azure Docs

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

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) at the earliest to avoid any disruption to your environment and minimize security risks.

## What changes should you expect?

- Starting March 15, 2023, 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 March 15, 2023, you can only use the modernized experience to enable Azure Site Recovery for all Recovery Services vaults.
- Existing VMware and physical machines can remain on the classic management experience until March 30, 2026. After 30 March 2026, changes to any configurations of the replication on these existing VMware and physical machines will require upgrade to 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.
- Enable replication for Classic Appliance from portal is blocked and PowerShell will be blocked by January 31, 2026.

## Alternatives

The [modernized experience](vmware-azure-architecture-modernized) is an alternative that the customer should choose to ensure that their DR strategy isn't impacted once the experience is deprecated.

## Remediation steps

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#how-to-define-required-infrastructure) and the [FAQs](classic-to-modernized-common-questions) for all related information.
2. [Check the architecture and minimum version of all components](move-from-classic-to-modernized-vmware-disaster-recovery#architecture) required for this migration.
3. Check all the [resources required](move-from-classic-to-modernized-vmware-disaster-recovery#required-infrastructure) and deploy the [Azure Site Recovery replication appliance](deploy-vmware-azure-replication-appliance-modernized).
4. [Prepare the classic Recovery Services vault](move-from-classic-to-modernized-vmware-disaster-recovery#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#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).