Proposed Pull Request Change

title	description	ms.topic	ms.date	ms.service	author	ms.author	ms.custom
Support Matrix for Azure VM Disaster Recovery with Azure Site Recovery	Summarizes support for Azure VMs disaster recovery to a secondary region with Azure Site Recovery.	concept-article	09/11/2026	azure-site-recovery	Jeronika-MS	v-gajeronika	engagement-fy23, references_regions, linux-related-content

📄 Document Links

View on GitHub

View on Microsoft Learn

⚠ Content Truncation Detected

The generated rewrite appears to be incomplete.

Original lines: -

Output lines: -

Ratio: -

Raw New Markdown

Generating updated version of doc...

Rendered New Markdown

Generating updated version of doc...

+0 -0

--- title: Support Matrix for Azure VM Disaster Recovery with Azure Site Recovery description: Summarizes support for Azure VMs disaster recovery to a secondary region with Azure Site Recovery. ms.topic: concept-article ms.date: 09/11/2026 ms.service: azure-site-recovery author: Jeronika-MS ms.author: v-gajeronika ms.custom: engagement-fy23, references_regions, linux-related-content # Customer intent: As an IT manager, I want to understand the disaster recovery support for Azure VMs by using Azure Site Recovery so that I can effectively plan my organization's resilience against data loss and ensure compliance with our recovery objectives. --- # Support matrix for Azure VM disaster recovery between Azure regions This article summarizes support and prerequisites for disaster recovery (DR) of Azure virtual machines (VMs) from one Azure region to another by using [Azure Site Recovery](site-recovery-overview.md). ## Deployment method support Deployment | Support --- | --- Azure portal | Supported. Azure PowerShell | Supported. For more information, see how to [set up DR for Azure VMs by using Azure PowerShell](azure-to-azure-powershell.md). REST API | Supported. Azure CLI | Not currently supported. ## Resource move or migrate support Resource action | Details --- | --- Move vaults across resource groups. | Not supported. Move compute, storage, or network resources across resource groups. | Not supported. For example, you move a VM or associated components, such as storage or a network, after the VM is replicating. Then you need to disable and re-enable replication for the VM. Replicate Azure VMs from one subscription to another for DR. | Supported within the same Microsoft Entra tenant. Migrate VMs across regions within supported geographical clusters (within and across subscriptions). | Supported within the same Microsoft Entra tenant. Migrate VMs within the same region. | Not supported. Azure Dedicated Host. | Not supported. Azure Virtual Desktop infrastructure VMs. | Supported if all the Azure-to-Azure replication prerequisites are fulfilled. (Zone-to-zone replication for individual servers is also supported.) ## Region support [!INCLUDE [azure-to-azure-region-limitations.md](./includes/azure-to-azure-region-limitations.md)] With Site Recovery, you can perform global disaster recovery. You can replicate and recover VMs between any two Azure regions in the world. If you have concerns around data sovereignty, you can limit replication within your specific geographic cluster. For information on the various geographic clusters that are supported, see [Products available by region](https://Azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=site-recovery&regions=all). Support for restricted regions is reserved for in-country/region disaster recovery: - Switzerland West is reserved for Switzerland North customers. - France South is reserved for France Central customers. - Norway West is reserved for Norway East customers. - JIO India Central is reserved for JIO India West customers. - Brazil Southeast is reserved for Brazil South customers. - South Africa West is reserved for South Africa North customers. - Germany North is reserved for Germany West Central customers. - UAE Central is reserved for UAE North customers. To use restricted regions as your primary or recovery region, make a request at [Products available by region](/troubleshoot/Azure/general/region-access-request-process) for both source and target subscriptions to get on the allow list: - For Brazil South, you can replicate and fail over to the following regions: Brazil Southeast, South Central US, West Central US, East US, East US 2, West US, West US 2, and North Central US. - You can use only Brazil South as a source region from which VMs can replicate by using Site Recovery. It can't act as a target region. If you fail over from Brazil South as a source region to a target, failback to Brazil South from the target region is supported. You can use only Brazil Southeast as a target region. - If the region in which you want to create a vault doesn't show, ensure that your subscription has access to create resources in that region. - If you can't see a region within a geographic cluster when you enable replication, ensure that your subscription has permissions to create VMs in that region. ## Cache storage This table summarizes support for the cache storage account that Site Recovery uses during replication. Setting | Support | Details --- | --- | --- General-purpose V2 (GPv2) storage accounts (hot and cool tiers) | Supported | Use GPv2 because GPv1 doesn't support zone-redundant storage (ZRS). Premium storage | Supported | Use Premium block blob storage accounts to get high-churn support. For more information, see [Azure VM disaster recovery: High-churn support](./concepts-azure-to-azure-high-churn-support.md). Region | Same region as VM | Cache storage account should be in the same region as the VM you're protecting. Subscription | Can be different from source VMs | Cache storage account must be in the same subscription as the source VMs. To use cache storage from the target subscription, use Azure PowerShell. Azure Storage firewalls for virtual networks | Supported | If you use a firewall-enabled cache storage account or a target storage account, ensure that you [allow trusted Microsoft services](../storage/common/storage-network-security.md#exceptions). Access must also be allowed to all subnets containing source Virtual Machines. If you use user-assigned managed identity (UAMI) created on an Azure Recovery Services vault, don't restrict virtual network access to your storage accounts that are used for Site Recovery. Allow access from all networks if you use vault UAMI. Soft delete | Not supported | Soft delete isn't supported because after soft delete is enabled on a cache storage account, it increases cost. Site Recovery performs frequently creates and deletes log files. Replicating causes costs to increase. Encryption at rest | Supported | You can configure storage account encryption with customer-managed keys (CMKs). Managed identity | Supported | Follow [Turn off key based access on cache account](/azure/site-recovery/asr-turn-off-key-authentication-cache). The following table lists the limits in terms of number of disks that can replicate to a single storage account. Storage account type | Churn = 4 MBps per disk | Churn = 8 MBps per disk --- | --- | --- V1 storage account | 300 disks | 150 disks V2 storage account | 750 disks | 375 disks As average churn on the disks increases, the number of disks that a storage account can support decreases. Use the preceding table as a guide for making decisions on the number of storage accounts that you must provision. The cache limits are specific to Azure-to-Azure and zone-to-zone DR scenarios. When you enable replication by using the VM workflow for cross-subscriptions, the portal lists only the cache storage account from the source subscription. It doesn't list any storage account created in the target subscription. To set up this scenario, use [Azure PowerShell](azure-to-azure-powershell.md). ## Replicated machine operating systems Site Recovery supports replication of Azure VMs running the operating systems listed in this section. For example, an already-replicating machine's operating system is later upgraded (or downgraded) to a different major version of the operating system, as in Red Hat Enterprise Linux (RHEL) 8 to RHEL 9. Then you must disable replication, uninstall the mobility agent, and re-enable replication after the upgrade. >[!NOTE] >- Major Linux OS upgrade without disable replication is currently in Preview. [Learn more](#upgrade-linux-major-os-version-without-disabling-replication-preview). >- Windows OS upgrade without disable replication is supported. ### Windows [!INCLUDE [end-of-support-notes-windows-server-2008-2012.md](./includes/end-of-support-notes-windows-server-2008-2012.md)] Operating system | Details --- | --- Windows Server 2025 | Supported. Windows Server 2022 | Supported. Windows Server 2019 | Supported for Server Core, Server with Desktop Experience. Windows Server 2016 | Supported for Server Core, Server with Desktop Experience. Windows Server 2012 R2 | Supported. Windows Server 2012 | Supported. Windows Server 2008 R2 with SP1/SP2 | Supported. From version [9.30](https://support.microsoft.com/help/4531426/update-rollup-42-for-Azure-site-recovery) of the Mobility service extension for Azure VMs, you need to install a Windows [servicing stack update (SSU)](https://support.microsoft.com/help/4490628) and [SHA-2 update](https://support.microsoft.com/help/4474419) on machines running Windows Server 2008 R2 SP1/SP2. SHA-1 isn't supported as of September 2019. If SHA-2 code signing isn't enabled, the agent extension won't install/upgrade as expected. For more information, see [SHA-2 code signing support requirement for Windows](https://aka.ms/SHA-2KB). Windows 11 (x64) | Supported (from the mobility agent version 9.56 and later). Windows 10 (x64) | Supported. Windows 8.1 (x64) | Supported. Windows 8 (x64) | Supported. Windows 7 (x64) with SP1 and later | From version [9.30](https://support.microsoft.com/help/4531426/update-rollup-42-for-Azure-site-recovery) of the Mobility service extension for Azure VMs, you need to install a Windows [SSU](https://support.microsoft.com/help/4490628) and [SHA-2 update](https://support.microsoft.com/help/4474419) on machines running Windows 7 with SP1. SHA-1 isn't supported as of September 2019. If SHA-2 code signing isn't enabled, the agent extension won't install/upgrade as expected. For more information, see [SHA-2 code signing support requirement for Windows](https://aka.ms/SHA-2KB). ### Linux Mobility service versions 9.58 and 9.59 aren't released for Azure to Azure Site Recovery. Operating system | Details --- | --- Red Hat Enterprise Linux | 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, [7.7](https://support.microsoft.com/help/4528026/update-rollup-41-for-azure-site-recovery), [7.8](https://support.microsoft.com/help/4564347/), [7.9](https://support.microsoft.com/help/4578241/), [8.0](https://support.microsoft.com/help/4531426/update-rollup-42-for-azure-site-recovery), 8.1, [8.2](https://support.microsoft.com/help/4570609/), [8.3](https://support.microsoft.com/help/4597409/), [8.4](https://support.microsoft.com/topic/883a93a7-57df-4b26-a1c4-847efb34a9e8) (4.18.0-305.30.1.el8_4.x86_64 or later), [8.5](https://support.microsoft.com/topic/883a93a7-57df-4b26-a1c4-847efb34a9e8) (4.18.0-348.5.1.el8_5.x86_64 or later), [8.6](https://support.microsoft.com/topic/update-rollup-62-for-azure-site-recovery-e7aff36f-b6ad-4705-901c-f662c00c402b) (4.18.0-348.5.1.el8_5.x86_64 or later), 8.7, 8.8, 8.9, 8.10, 9.0, 9.1, 9.2, 9.3, 9.4, 9.5, 9.6, 9.7, 9.8, 10.0, 10.1, 10.2 RHEL `9.x`, `10.x` is supported for the [following kernel versions](#supported-kernel-versions-for-red-hat-enterprise-linux-for-azure-vms). Ubuntu 14.04 LTS Server | Includes support for all 14.04.*x* versions. [Supported kernel versions](#supported-ubuntu-kernel-versions-for-azure-vms). Ubuntu 16.04 LTS Server | Includes support for all 16.04.*x* versions. [Supported kernel versions](#supported-ubuntu-kernel-versions-for-azure-vms). Ubuntu servers using password-based authentication and sign-in, and the `cloud-init` package to configure cloud VMs, might have password-based sign-in disabled on failover (depending on the `cloud-init` configuration). To re-enable password-based sign-in on the VM, reset the password from the **Support** > **Troubleshooting** > **Settings** menu of the failed-over VM in the Azure portal. Ubuntu 18.04 LTS Server | Includes support for all 18.04.*x* versions. [Supported kernel versions](#supported-ubuntu-kernel-versions-for-azure-vms). Ubuntu servers using password-based authentication and sign-in, and the `cloud-init` package to configure cloud VMs, might have password-based sign-in disabled on failover (depending on the `cloud-init` configuration). To re-enable password-based sign-in on the VM, reset the password from the **Support** > **Troubleshooting** > **Settings** menu of the failed-over VM in the Azure portal. Ubuntu 20.04 LTS server | Includes support for all 20.04.*x* versions. [Supported kernel versions](#supported-ubuntu-kernel-versions-for-azure-vms). Ubuntu 22.04 LTS server | Includes support for all 22.04.*x* versions. [Supported kernel versions](#supported-ubuntu-kernel-versions-for-azure-vms). Ubuntu 24.04 LTS server | Includes support for all 24.04.*x* versions. [Supported kernel versions](#supported-ubuntu-kernel-versions-for-azure-vms). Ubuntu 26.04 LTS server | Includes support for all 26.04.*x* versions. [Supported kernel versions](#supported-ubuntu-kernel-versions-for-azure-vms). Debian 7 | Includes support for all 7.*x* versions. [Supported kernel versions](#supported-debian-kernel-versions-for-azure-vms). Debian 8 | Includes support for all 8.*x* versions. [Supported kernel versions](#supported-debian-kernel-versions-for-azure-vms). Debian 9 | Includes support for 9.1 to 9.13. Debian 9.0 isn't supported. [Supported kernel versions](#supported-debian-kernel-versions-for-azure-vms). Debian 10 | [Supported kernel versions](#supported-debian-kernel-versions-for-azure-vms). Debian 11 | [Supported kernel versions](#supported-debian-kernel-versions-for-azure-vms). Debian 12 | [Supported kernel versions](#supported-debian-kernel-versions-for-azure-vms). Debian 13 | [Supported kernel versions](#supported-debian-kernel-versions-for-azure-vms). SUSE Linux Enterprise Server 12 | SP1, SP2, SP3, SP4, SP5. [(Supported kernel versions.)](#supported-suse-linux-enterprise-server-12-kernel-versions-for-azure-vms) SUSE Linux Enterprise Server 15 | 15, SP1, SP2, SP3, SP4, SP5, SP6, SP7. [(Supported kernel versions.)](#supported-suse-linux-enterprise-server-15-kernel-versions-for-azure-vms) SUSE Linux Enterprise Server 16 | [(Supported kernel versions.)](#supported-suse-linux-enterprise-server-16-kernel-versions-for-azure-vms) SUSE Linux Enterprise Server 11 | SP3. Upgrade of replicating machines from SP3 to SP4 isn't supported. If a replicated machine was upgraded, disable replication and re-enable replication after the upgrade. SUSE Linux Enterprise Server 11 | SP4. Oracle Linux | 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, [7.7](https://support.microsoft.com/help/4531426/update-rollup-42-for-azure-site-recovery), [7.8](https://support.microsoft.com/help/4573888/), [7.9](https://support.microsoft.com/help/4597409), [8.0](https://support.microsoft.com/help/4573888/), [8.1](https://support.microsoft.com/help/4573888/), [8.2](https://support.microsoft.com/topic/update-rollup-55-for-azure-site-recovery-kb5003408-b19c8190-5f88-43ea-85b1-d9e0cc5ca7e8), [8.3](https://support.microsoft.com/topic/update-rollup-55-for-azure-site-recovery-kb5003408-b19c8190-5f88-43ea-85b1-d9e0cc5ca7e8) (running the Red Hat-compatible kernel or Unbreakable Enterprise Kernel (UEK) Release 3, 4, 5, and 6 (UEK3, UEK4, UEK5, UEK6), [8.4](https://support.microsoft.com/topic/update-rollup-59-for-azure-site-recovery-kb5008707-66a65377-862b-4a4c-9882-fd74bdc7a81e), 8.5, 8.6, 8.7, 8.8, 8.9, 8.10, 9.0, 9.1, 9.2, 9.3, 9.4, 9.5, 9.6, 9.7, 10.0, 10.1). Unbreakable Enterprise Kernel Release 7 (UEK7) is supported from 8.7. 8.1 (running on all UEK kernels and the Red Hat kernel <= 3.10.0-1062.* is supported in [9.35](https://support.microsoft.com/help/4573888/). Support for the rest of the Red Hat kernels is available in [9.36](https://support.microsoft.com/help/4578241/).) Oracle Linux 9.x is supported for the [following kernel versions](#supported-red-hat-linux-kernel-versions-for-oracle-linux-on-azure-vms). Rocky Linux | [See supported versions](#supported-rocky-linux-kernel-versions-for-azure-vms). Alma Linux | [See supported versions](#supported-alma-linux-kernel-versions-for-azure-vms). For Linux versions, Site Recovery doesn't support custom OS kernels. Only the stock kernels that are part of the distribution minor version release/update are supported. ### Linux kernel support timelines > [!NOTE] > Supported Linux kernel versions are no longer updated in a support matrix. For the latest supported kernel versions, see [Azure Site Recovery supported kernels](https://github.com/Azure/Azure-SiteRecovery/blob/main/MobilityAgent/AzureToAzure/SupportedKernels/). To support newly released Linux kernels, Site Recovery provides hotfix patches of the mobility agent on top of the latest mobility agent version. These hotfixes are released on a *best-effort basis within 30 days* of the kernel release and apply only to *Azure-to-Azure disaster recovery scenarios*. >[!NOTE] >This isn't a service-level agreement. The 30-day support window on a *best-effort basis* applies only to specific scenarios as outlined in the following table. Only the scenarios mentioned in the *Scenarios covered by 30-day best-effort support* column are applicable for the best-effort basis of 30 days. Any other scenario, even if it isn't mentioned in the *Scenarios not covered by 30-day best-effort support* column, isn't applicable for this best-effort support. #### Scope of 30-day kernel support on best effort Distribution | Scenarios covered by 30-day best-effort support | Scenarios not covered by 30-day best-effort support --- | --- | --- Ubuntu | New kernel within an already supported kernel series within a supported Ubuntu version. An example is 5.15.0-1081-Azure for Ubuntu 22.04 if 5.15.0-1079-Azure is already supported for Ubuntu 22.04 because both belong to the 5.15.0-* kernel series. Applies to both Azure (`-Azure`) and generic kernels (`-generic`) only. | New major OS version released. For example, assume Ubuntu releases Ubuntu 28.04, which Site Recovery doesn't support yet. New kernel series not previously supported for the same Ubuntu version. An example is 6.5.0-18-Azure for Ubuntu 22.04 if no kernel from the 6.5.0-* series is supported. Debian | New kernel within an already supported kernel series within a supported Debian version. An example is 4.19.0-27-cloud-amd64 for Debian 10 if 4.19.0-26-cloud-amd64 is already supported for Debian 10 because both belong to the 4.19.0-* kernel series. Applies to Azure kernels (`-cloud-amd64`) and stock kernels (`-amd64`) only. | New major OS version released. For example, assume Debian releases Debian 14, which Site Recovery doesn't support yet. New kernel series not previously supported for the same Debian version. An example is 5.10.0-0.deb10.30-cloud-amd64 for Debian 10 if no kernel from the 5.10.0-* series is supported. SUSE | New kernel within an already supported kernel series within a supported service pack (SP) version. An example is 6.4.0-150600.8.8 for SUSE 15 SP6 if 6.4.0-150600.8.5 is already supported for SUSE 15 SP6 because both belong to the 6.4.0-150600.8.* kernel series. Applies to Azure kernels (`-Azure:`[service pack number]). Stock kernels (`-default`) are supported by default. | New service pack releases. For example, assume SUSE releases SUSE 16 SP1, which Site Recovery doesn't support yet. New kernel series isn't previously supported for the same SP version. RHEL, Rocky, Alma, and Oracle Linux. (All distros are based on RHEL kernels.) | A new kernel for RHEL 8.x or 9.y is supported if it meets two criteria. The minor OS version (RHEL 8.x or RHEL 9.y) is supported. The kernel series is already supported for that minor OS version. For RHEL 8.x, this support applies only if x ≥6. For Oracle Linux UEK kernels, this support applies only if new kernels are within a supported UEK kernel series within a supported OS version. | New major version released. For example, assume RHEL 11.x, Rocky Linux 11.x, Alma Linux 11.x, or Oracle Linux 11.x is released, which Site Recovery doesn't support. Minor OS version is released within a supported major OS version. For example, assume RHEL 10.3 is released, which Site Recovery doesn't support. New kernels for RHEL 8.x where x <6 (for example, RHEL 8.4) aren't supported within 30 days. Site Recovery doesn't support new kernel releases for a UEK kernel series. For Ubuntu and Debian, the Mobility service installer compares the complete kernel version with its supported-kernel list. A newly released stock kernel isn't supported until the exact version is listed or a compatible preinstalled driver is available. ## Upgrade Linux major OS version without disabling replication (preview) Azure Site Recovery now supports major version upgrades for Linux OS without disabling replication. This feature is currently available for Azure-to-Azure (A2A) disaster recovery scenario. When you upgrade Linux OS to a new major version, Azure Site Recovery detects the change and prompts to update the Mobility Agent as needed. This update ensures that replication continues seamlessly and disaster recovery setup remains protected. ### Supported Linux distributions - Red Hat Enterprise Linux (RHEL) - Upgrade from RHEL 7 to RHEL 8, Upgrade from RHEL 8 to RHEL 9.  - SUSE Linux Enterprise Server (SLES) - Upgrade from SLES 12 to SLES 15. >[!NOTE] >Support for this feature in preview is available only from Azure Site Recovery agent version 9.66.7567.1 and above. So, first update the Azure Site Recovery agent to version 9.66.7567.1 and later and then, you can do major OS upgrades. If you configure auto update of Azure Site Recovery agent, Azure Site Recovery agent gets automatically updated in the next update cycle to be compatible with the upgraded OS version. To update the Azure Site Recovery agent manually, follow these steps: 1. Upgrade Linux OS and navigate to the **Replicated Items** page of the VM in the Azure portal. 2. Select **Update Agent to support new OS version detected on VM**. :::image type="content" source="./media/azure-to-azure-support-matrix/replicated-items.png" alt-text="Screenshot of replicated items." lightbox="./media/azure-to-azure-support-matrix/replicated-items.png"::: 3. Review the details in the context pane and proceed with the agent upgrade as prompted. >[!NOTE] >If you upgrade your Linux OS without updating the Azure Site Recovery Mobility Agent to a compatible version, replication may fail. Ensure that the agent version supports your new OS version. After a major Linux OS upgrade, data resynchronization occurs when the agent is updated. #### Supported kernel versions for Red Hat Enterprise Linux for Azure VMs Enabling replication when you create a VM deployment workflow isn't supported for VMs with OS RHEL 9 and later. Release | Mobility service version | Red Hat kernel version | --- | --- | --- | RHEL 10.0 RHEL 10.1 | 9.66 | 6.12.0-55.9.1 and later 6.12.0-124.8.1 and later | RHEL 10.2 | 9.67| [Supported kernels](https://github.com/Azure/Azure-SiteRecovery/blob/main/MobilityAgent/AzureToAzure/SupportedKernels/) | RHEL 9.0 RHEL 9.1 RHEL 9.2 RHEL 9.3 RHEL 9.4 RHEL 9.5 RHEL 9.6 RHEL 9.7 RHEL 9.8 | 9.67| [Supported kernels](https://github.com/Azure/Azure-SiteRecovery/blob/main/MobilityAgent/AzureToAzure/SupportedKernels/) | RHEL 9.0 RHEL 9.1 RHEL 9.2 RHEL 9.3 RHEL 9.4 RHEL 9.5 RHEL 9.6 RHEL 9.7 | 9.66 | 5.14.0-611.5.1 and later | RHEL 9.0 RHEL 9.1 RHEL 9.2 RHEL 9.3 RHEL 9.4 RHEL 9.5 RHEL 9.6 | 9.65 | 5.14.0-503.11.1 and later 5.14.0-570.12.1 and later | RHEL 9.0 RHEL 9.1 RHEL 9.2 RHEL 9.3 RHEL 9.4 RHEL 9.5 | 9.64 | 5.14.0-503.11.1 and later | RHEL 9.0 RHEL 9.1 RHEL 9.2 RHEL 9.3 RHEL 9.4 | 9.63 | 5.14.0-284.73.1.el9_2.x86_64 5.14.0-284.75.1.el9_2.x86_64 5.14.0-284.77.1.el9_2.x86_64 5.14.0-284.79.1.el9_2.x86_64 5.14.0-284.80.1.el9_2.x86_64 5.14.0-284.82.1.el9_2.x86_64 5.14.0-284.84.1.el9_2.x86_64 5.14.0-284.85.1.el9_2.x86_64 5.14.0-284.86.1.el9_2.x86_64 5.14.0-427.24.1.el9_4.x86_64 5.14.0-427.26.1.el9_4.x86_64 5.14.0-427.28.1.el9_4.x86_64 5.14.0-427.31.1.el9_4.x86_64 5.14.0-427.33.1.el9_4.x86_64 5.14.0-427.35.1.el9_4.x86_64 5.14.0-427.37.1.el9_4.x86_64 5.14.0-427.13.1.el9_4.x86_64 and later | RHEL 9.0 RHEL 9.1 RHEL 9.2 RHEL 9.3 RHEL 9.4 | 9.62 | 5.14.0-70.97.1.el9_0.x86_64 5.14.0-70.101.1.el9_0.x86_64 5.14.0-284.62.1.el9_2.x86_64 5.14.0-284.64.1.el9_2.x86_64 5.14.0-284.66.1.el9_2.x86_64 5.14.0-284.67.1.el9_2.x86_64 5.14.0-284.69.1.el9_2.x86_64 5.14.0-284.71.1.el9_2.x86_64 5.14.0-427.13.1.el9_4.x86_64 5.14.0-427.16.1.el9_4.x86_64 5.14.0-427.18.1.el9_4.x86_64 5.14.0-427.20.1.el9_4.x86_64 5.14.0-427.22.1.el9_4.x86_64 5.14.0-427.13.1.el9_4.x86_64 and later | #### Supported Ubuntu kernel versions for Azure VMs Release | Mobility service version | Kernel version | --- | --- | --- | 14.04 LTS | 9.66| No new 14.04 LTS kernels supported in this release. | 14.04 LTS | 9.65| No new 14.04 LTS kernels supported in this release. | 14.04 LTS | 9.64| No new 14.04 LTS kernels supported in this release. | 14.04 LTS | 9.63| No new 14.04 LTS kernels supported in this release. | 14.04 LTS | 9.62| No new 14.04 LTS kernels supported in this release. | ||| 16.04 LTS | 9.66| No new 16.04 LTS kernels supported in this release. | 16.04 LTS | 9.65| No new 16.04 LTS kernels supported in this release. | 16.04 LTS | 9.64| No new 16.04 LTS kernels supported in this release. | 16.04 LTS | 9.63| No new 16.04 LTS kernels supported in this release. | 16.04 LTS | 9.62| No new 16.04 LTS kernels supported in this release. | ||| 18.04 LTS | 9.66| 4.15.0-1188-azure 4.15.0-1189-azure 4.15.0-1190-azure 4.15.0-1191-azure 4.15.0-1192-azure 4.15.0-1193-azure 4.15.0-1194-azure 4.15.0-1196-azure 4.15.0-237-generic 4.15.0-238-generic 4.15.0-239-generic 4.15.0-240-generic 4.15.0-241-generic 4.15.0-242-generic 4.15.0-243-generic 4.15.0-245-generic 4.15.0-246-generic 5.4.0-1150-azure 5.4.0-1151-azure 5.4.0-1152-azure 5.4.0-1153-azure 5.4.0-1154-azure 5.4.0-215-generic 5.4.0-216-generic 5.4.0-218-generic 5.4.0-219-generic 5.4.0-220-generic 5.4.0-221-generic 5.4.0-222-generic 5.4.0-223-generic 5.4.0-225-generic | 18.04 LTS | 9.65| 4.15.0-1186-azure 4.15.0-1187-azure 4.15.0-235-generic 4.15.0-236-generic 5.4.0-1147-azure 5.4.0-1148-azure 5.4.0-1149-azure 5.4.0-211-generic 5.4.0-212-generic 5.4.0-214-generic| 18.04 LTS | 9.64| 4.15.0-1185-azure 4.15.0-233-generic 4.15.0-234-generic 5.4.0-1142-azure 5.4.0-1143-azure 5.4.0-1145-azure 5.4.0-208-generic 4.15.0-1181-azure 4.15.0-1182-azure 4.15.0-1183-azure 4.15.0-1184-azure 4.15.0-229-generic 4.15.0-230-generic 4.15.0-231-generic 4.15.0-232-generic 5.4.0-1137-azure 5.4.0-1138-azure 5.4.0-1139-azure 5.4.0-1140-azure 5.4.0-195-generic 5.4.0-196-generic 5.4.0-198-generic 5.4.0-200-generic 5.4.0-202-generic 5.4.0-204-generic | 18.04 LTS | 9.63 | 5.4.0-1135-azure 5.4.0-192-generic 4.15.0-1180-azure 4.15.0-228-generic 5.4.0-1136-azure 5.4.0-193-generic 5.4.0-1137-azure 5.4.0-1138-azure 5.4.0-195-generic 5.4.0-196-generic 4.15.0-1181-azure 4.15.0-229-generic 4.15.0-1182-azure 4.15.0-230-generic 5.4.0-1139-azure 5.4.0-198-generic | 18.04 LTS | 9.62| 4.15.0-226-generic 5.4.0-1131-azure 5.4.0-186-generic 5.4.0-187-generic 4.15.0-1178-azure 5.4.0-1132-azure 5.4.0-1133-azure 5.4.0-1134-azure 5.4.0-190-generic 5.4.0-189-generic | ||| 20.04 LTS | 9.66| 5.15.0-1088-azure 5.15.0-1089-azure 5.15.0-1091-azure 5.15.0-1094-azure 5.15.0-1095-azure 5.15.0-1096-azure 5.15.0-1097-azure 5.15.0-1098-azure 5.15.0-1103-azure 5.15.0-139-generic 5.15.0-142-generic 5.15.0-143-generic 5.15.0-144-generic 5.15.0-145-generic 5.15.0-151-generic 5.15.0-152-generic 5.15.0-153-generic 5.15.0-156-generic 5.15.0-157-generic 5.15.0-160-generic 5.15.0-161-generic 5.15.0-168-generic 5.4.0-1150-azure 5.4.0-1151-azure 5.4.0-1152-azure 5.4.0-1153-azure 5.4.0-1154-azure 5.4.0-215-generic 5.4.0-216-generic 5.4.0-218-generic 5.4.0-219-generic 5.4.0-220-generic 5.4.0-221-generic 5.4.0-222-generic 5.4.0-223-generic 5.4.0-225-generic | 20.04 LTS | 9.65| 5.15.0-1082-azure 5.15.0-1086-azure 5.15.0-1087-azure 5.15.0-136-generic 5.15.0-138-generic 5.4.0-1147-azure 5.4.0-1148-azure 5.4.0-1149-azure 5.4.0-211-generic 5.4.0-212-generic 5.4.0-214-generic| 20.04 LTS | 9.64| 5.15.0-1079-azure 5.15.0-1081-azure 5.15.0-131-generic 5.15.0-134-generic 5.4.0-1143-azure 5.4.0-1145-azure 5.4.0-205-generic 5.4.0-208-generic 5.15.0-1072-azure 5.15.0-1073-azure 5.15.0-1074-azure 5.15.0-1075-azure 5.15.0-1078-azure 5.15.0-121-generic 5.15.0-122-generic 5.15.0-124-generic 5.15.0-125-generic 5.15.0-126-generic 5.15.0-127-generic 5.15.0-130-generic 5.4.0-1137-azure 5.4.0-1138-azure 5.4.0-1139-azure 5.4.0-1140-azure 5.4.0-1142-azure 5.4.0-195-generic 5.4.0-196-generic 5.4.0-198-generic 5.4.0-200-generic 5.4.0-202-generic 5.4.0-204-generic | 20.04 LTS | 9.63| 5.15.0-1070-azure 5.4.0-1135-azure 5.4.0-192-generic 5.15.0-1071-azure 5.15.0-118-generic 5.15.0-119-generic 5.4.0-1136-azure 5.4.0-193-generic 5.15.0-1072-azure 5.15.0-1073-azure 5.15.0-121-generic 5.15.0-122-generic 5.4.0-1137-azure 5.4.0-1138-azure 5.4.0-195-generic 5.4.0-196-generic | 20.04 LTS | 9.62| 5.15.0-1065-azure 5.15.0-1067-azure 5.15.0-113-generic 5.4.0-1131-azure 5.4.0-1132-azure 5.4.0-186-generic 5.4.0-187-generic 5.15.0-1068-azure 5.15.0-116-generic 5.15.0-117-generic 5.4.0-1133-azure 5.4.0-1134-azure 5.4.0-189-generic 5.4.0-190-generic 5.15.0-1074-azure 5.15.0-124-generic 5.4.0-1139-azure 5.4.0-198-generic | ||| 22.04 LTS | 9.66| 5.15.0-1088-azure 5.15.0-1089-azure 5.15.0-1090-azure 5.15.0-1091-azure 5.15.0-1092-azure 5.15.0-1094-azure 5.15.0-1095-azure 5.15.0-1096-azure 5.15.0-1097-azure 5.15.0-1098-azure 5.15.0-1099-azure 5.15.0-1101-azure 5.15.0-1103-azure 5.15.0-139-generic 5.15.0-140-generic 5.15.0-141-generic 5.15.0-142-generic 5.15.0-143-generic 5.15.0-144-generic 5.15.0-151-generic 5.15.0-152-generic 5.15.0-153-generic 5.15.0-156-generic 5.15.0-157-generic 5.15.0-160-generic 5.15.0-161-generic 5.15.0-168-generic 6.8.0-1028-azure 6.8.0-1029-azure 6.8.0-1030-azure 6.8.0-1031-azure 6.8.0-1034-azure 6.8.0-1036-azure 6.8.0-1040-azure 6.8.0-1041-azure 6.8.0-58-generic 6.8.0-59-generic 6.8.0-60-generic 6.8.0-64-generic 6.8.0-65-generic 6.8.0-78-generic 6.8.0-79-generic 6.8.0-83-generic 6.8.0-84-generic 6.8.0-85-generic 6.8.0-86-generic 6.8.0-87-generic 6.8.0-94-generic | 22.04 LTS | 9.65| 5.15.0-1082-azure 5.15.0-1084-azure 5.15.0-1086-azure 5.15.0-1087-azure 5.15.0-135-generic 5.15.0-136-generic 5.15.0-138-generic 6.8.0-1025-azure 6.8.0-1026-azure 6.8.0-1027-azure 6.8.0-57-generic| 22.04 LTS | 9.64| 5.15.0-1079-azure 5.15.0-1081-azure 5.15.0-131-generic 5.15.0-133-generic 5.15.0-134-generic 6.8.0-1021-azure 6.8.0-52-generic 5.15.0-1072-azure 5.15.0-1073-azure 5.15.0-1074-azure 5.15.0-1075-azure 5.15.0-1078-azure 5.15.0-121-generic 5.15.0-122-generic 5.15.0-124-generic 5.15.0-125-generic 5.15.0-126-generic 5.15.0-127-generic 5.15.0-130-generic 6.8.0-1008-azure 6.8.0-1009-azure 6.8.0-1010-azure 6.8.0-1012-azure 6.8.0-1013-azure 6.8.0-1014-azure 6.8.0-1015-azure 6.8.0-1017-azure 6.8.0-1018-azure 6.8.0-1020-azure 6.8.0-38-generic 6.8.0-39-generic 6.8.0-40-generic 6.8.0-45-generic 6.8.0-47-generic 6.8.0-48-generic 6.8.0-49-generic 6.8.0-50-generic 6.8.0-51-generic | 22.04 LTS | 9.63| 5.15.0-1070-azure 5.15.0-118-generic 5.15.0-1071-azure 5.15.0-119-generic 5.15.0-1072-azure 5.15.0-1073-azure 5.15.0-121-generic 5.15.0-122-generic 5.15.0-1074-azure 5.15.0-124-generic | 22.04 LTS | 9.62| 5.15.0-1066-azure 5.15.0-1067-azure 5.15.0-112-generic 5.15.0-113-generic 6.5.0-1022-azure 6.5.0-1023-azure 6.5.0-41-generic 5.15.0-1068-azure 5.15.0-116-generic 5.15.0-117-generic 6.5.0-1024-azure 6.5.0-1025-azure 6.5.0-44-generic 6.5.0-45-generic | ||| 24.04 LTS | 9.66| 6.14.0-1012-azure 6.14.0-1013-azure 6.14.0-1014-azure 6.14.0-24-generic 6.14.0-27-generic 6.14.0-28-generic 6.14.0-29-generic 6.14.0-32-generic 6.14.0-33-generic 6.14.0-34-generic 6.14.0-35-generic 6.14.0-36-generic 6.11.0-1008-azure 6.11.0-1012-azure 6.11.0-1013-azure 6.11.0-1014-azure 6.11.0-1015-azure 6.11.0-1017-azure 6.11.0-1018-azure 6.11.0-17-generic 6.11.0-19-generic 6.11.0-21-generic 6.11.0-24-generic 6.11.0-25-generic 6.11.0-26-generic 6.11.0-28-generic 6.11.0-29-generic 6.8.0-1028-azure 6.8.0-1029-azure 6.8.0-1030-azure 6.8.0-1031-azure 6.8.0-1034-azure 6.8.0-1038-azure 6.8.0-1040-azure 6.8.0-1041-azure 6.8.0-1042-azure 6.8.0-59-generic 6.8.0-60-generic 6.8.0-62-generic 6.8.0-63-generic 6.8.0-64-generic 6.8.0-71-generic 6.8.0-78-generic 6.8.0-79-generic 6.8.0-83-generic 6.8.0-84-generic 6.8.0-85-generic 6.8.0-86-generic 6.8.0-87-generic 6.8.0-88-generic 6.8.0-94-generic 6.8.0-100-generic | 24.04 LTS | 9.65| 6.8.0-1025-azure 6.8.0-1026-azure 6.8.0-1027-azure 6.8.0-56-generic 6.8.0-57-generic 6.8.0-58-generic| 24.04 LTS | 9.64| 6.8.0-1021-azure 6.8.0-52-generic 6.8.0-53-generic 6.8.0-54-generic 6.8.0-55-generic 6.8.0-1007-azure 6.8.0-1008-azure 6.8.0-1009-azure 6.8.0-1010-azure 6.8.0-1012-azure 6.8.0-1013-azure 6.8.0-1014-azure 6.8.0-1015-azure 6.8.0-1016-azure 6.8.0-1017-azure 6.8.0-1018-azure 6.8.0-1020-azure 6.8.0-31-generic 6.8.0-35-generic 6.8.0-36-generic 6.8.0-38-generic 6.8.0-39-generic 6.8.0-40-generic 6.8.0-41-generic 6.8.0-44-generic 6.8.0-45-generic 6.8.0-47-generic 6.8.0-48-generic 6.8.0-49-generic 6.8.0-50-generic 6.8.0-51-generic | 26.04 LTS | 9.67| [Supported kernels](https://github.com/Azure/Azure-SiteRecovery/blob/main/MobilityAgent/AzureToAzure/SupportedKernels/) | #### Supported Debian kernel versions for Azure VMs Release | Mobility service version | Kernel version | --- | --- | --- | Debian 7 | 9.66 | No new Debian 7 kernels supported in this release. | Debian 7 | 9.65 | No new Debian 7 kernels supported in this release. | Debian 7 | 9.64 | No new Debian 7 kernels supported in this release. | Debian 7 | 9.63| No new Debian 7 kernels supported in this release. | Debian 7 | 9.62| No new Debian 7 kernels supported in this release. | ||| Debian 8 | 9.66 | No new Debian 8 kernels supported in this release. | Debian 8 | 9.65 | No new Debian 8 kernels supported in this release. | Debian 8 | 9.64 | No new Debian 8 kernels supported in this release. | Debian 8 | 9.63| No new Debian kernels supported in this release. | Debian 8 | 9.62| No new Debian 8 kernels supported in this release. | ||| Debian 9 | 9.66 | No new Debian 9 kernels supported in this release. | Debian 9 | 9.65 | No new Debian 9 kernels supported in this release. | Debian 9 | 9.64 | No new Debian 9 kernels supported in this release. | Debian 9.1 | 9.63 | No new Debian kernels supported in this release. | Debian 9.1 | 9.62 | No new Debian 9.1 kernels supported in this release.| ||| Debian 10 | 9.66| No new Debian 10 kernels supported in this release. | Debian 10 | 9.65| No new Debian 10 kernels supported in this release. | Debian 10 | 9.64| No new Debian 10 kernels supported in this release. | Debian 10 | 9.63| No new Debian 10 kernels supported in this release. | Debian 10 | 9.62| 4.19.0-27-amd64 4.19.0-27-cloud-amd64 5.10.0-0.deb10.30-amd64 5.10.0-0.deb10.30-cloud-amd64 | ||| Debian 11 | 9.66 | 5.10.0-35-amd64 5.10.0-36-amd64 5.10.0-35-cloud-amd64 5.10.0-36-cloud-amd64 6.1.0-0.deb11.35-amd64 6.1.0-0.deb11.35-cloud-amd64 6.1.0-0.deb11.37-amd64 6.1.0-0.deb11.40-amd64 6.1.0-0.deb11.41-amd64 6.1.0-0.deb11.37-cloud-amd64 6.1.0-0.deb11.38-amd64 6.1.0-0.deb11.38-cloud-amd64 6.1.0-0.deb11.39-amd64 6.1.0-0.deb11.39-cloud-amd64 6.1.0-0.deb11.40-cloud-amd64 6.1.0-0.deb11.41-cloud-amd64 | Debian 11 | 9.65 | 6.1.0-0.deb11.32-amd64 6.1.0-0.deb11.32-cloud-amd64 | Debian 11 | 9.64 | 5.10.0-34-amd64 5.10.0-34-cloud-amd64 6.1.0-0.deb11.31-amd64 6.1.0-0.deb11.31-cloud-amd64 5.10.0-33-amd64 5.10.0-33-cloud-amd64 6.1.0-0.deb11.25-amd64 6.1.0-0.deb11.25-cloud-amd64 6.1.0-0.deb11.26-amd64 6.1.0-0.deb11.26-cloud-amd64 6.1.0-0.deb11.28-amd64 6.1.0-0.deb11.28-cloud-amd64 | Debian 11 | 9.63 | 5.10.0-26-amd64 5.10.0-26-cloud-amd64 5.10.0-31-amd64 5.10.0-31-cloud-amd64 5.10.0-32-amd64 5.10.0-32-cloud-amd64 6.1.0-0.deb11.13-amd64 6.1.0-0.deb11.13-cloud-amd64 6.1.0-0.deb11.17-amd64 6.1.0-0.deb11.17-cloud-amd64 6.1.0-0.deb11.18-amd64 6.1.0-0.deb11.18-cloud-amd64 6.1.0-0.deb11.21-amd64 6.1.0-0.deb11.21-cloud-amd64 6.1.0-0.deb11.22-amd64 6.1.0-0.deb11.22-cloud-amd64 | Debian 11 | 9.62| 5.10.0-30-amd64 5.10.0-30-cloud-amd64 6.1.0-0.deb11.21-amd64 6.1.0-0.deb11.21-cloud-amd64 | ||| Debian 12 | 9.66 | 6.1.0-34-amd64 6.1.0-34-cloud-amd64 6.1.0-35-amd64 6.1.0-35-cloud-amd64 6.1.0-37-amd64 6.1.0-40-amd64 6.1.0-41-amd64 6.1.0-37-cloud-amd64 6.1.0-38-amd64 6.1.0-38-cloud-amd64 6.1.0-39-amd64 6.1.0-39-cloud-amd64 6.1.0-40-cloud-amd64 6.1.0-41-cloud-amd64 | Debian 12 | 9.65 | 6.1.0-32-amd64 6.1.0-32-cloud-amd64 6.1.0-33-amd64 6.1.0-33-cloud-amd64| Debian 12 | 9.64 | 6.1.0-29-amd64 6.1.0-29-cloud-amd64 6.1.0-30-amd64 6.1.0-30-cloud-amd64 6.1.0-31-amd64 6.1.0-31-cloud-amd64 6.1.0-15-cloud-amd64 6.1.0-26-amd64 6.1.0-26-cloud-amd64 6.1.0-27-amd64 6.1.0-27-cloud-amd64 6.1.0-28-amd64 6.1.0-28-cloud-amd64 | Debian 12 | 9.63 | 6.1.0-25-amd64 6.1.0-25-cloud-amd64 6.1.0-26-amd64 6.1.0-26-cloud-amd64 | Debian 12 | 9.62| 6.1.0-22-amd64 6.1.0-22-cloud-amd64 6.1.0-23-amd64 6.1.0-23-cloud-amd64 6.5.0-0.deb12.4-cloud-amd64 | Debian 13 | 9.67| [Supported kernels](https://github.com/Azure/Azure-SiteRecovery/blob/main/MobilityAgent/AzureToAzure/SupportedKernels/) | #### Supported SUSE Linux Enterprise Server 12 kernel versions for Azure VMs Release | Mobility service version | Kernel version | --- | --- | --- | SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.66 | New SUSE 12 kernels aren't supported in this release. | SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.65 | All [stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported. 4.12.14-16.197-Azure: 5 4.12.14-16.200-Azure: 5 | SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.64 | All [stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported. 4.12.14-16.197-Azure: 5 4.12.14-16.200-Azure: 5 | SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.63 | All [stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported. 4.12.14-16.194-Azure: 5 4.12.14-16.197-Azure: 5 4.12.14-16.200-Azure: 5 | SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.62 | All [stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported. 4.12.14-16.185-Azure: 5 4.12.14-16.188-Azure: 5 4.12.14-16.191-Azure: 5 | #### Supported SUSE Linux Enterprise Server 15 kernel versions for Azure VMs Release | Mobility service version | Kernel version | --- | --- | --- | SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5, SP6, SP7) | 9.66 | All [stock SUSE 15 SP1, SP2, SP3, SP4, SP5, SP6, SP7 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported. 6.4.0-150600.8.37-azure:6 6.4.0-150600.8.40-azure:6 6.4.0-150600.8.43-azure:6 6.4.0-150600.8.48-azure:6 6.4.0-150600.8.52-azure:6 6.4.0-150700.18-azure:7 6.4.0-150700.20.11-azure:7 6.4.0-150700.20.3-azure:7 6.4.0-150700.20.6-azure:7 6.4.0-150700.20.15-azure:7 6.4.0-150700.20.18-azure:7 6.4.0-150700.20.24-azure:7 | SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5, SP6) | 9.65 | All [stock SUSE 15 SP1, SP2, SP3, SP4, SP5, SP6 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported. 6.4.0-150600.8.23-azure:6 6.4.0-150600.8.26-azure:6 6.4.0-150600.8.31-azure:6 6.4.0-150600.8.34-azure:6 | SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5, SP6) | 9.64 | All [stock SUSE 15 SP1, SP2, SP3, SP4, SP5, SP6 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported. 5.14.21-150500.33.66-azure:5 5.14.21-150500.33.69-azure:5 5.14.21-150500.33.72-azure:5 5.14.21-150500.33.75-azure:5 6.4.0-150600.6-azure:6 6.4.0-150600.8.11-azure:6 6.4.0-150600.8.14-azure:6 6.4.0-150600.8.17-azure:6 6.4.0-150600.8.20-azure:6 6.4.0-150600.8.5-azure:6 6.4.0-150600.8.8-azure:6 | SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5, SP6) | 9.63 | All [stock SUSE 15 SP1, SP2, SP3, SP4, SP5, SP6 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported. 5.14.21-150500.33.63-azure:5 5.14.21-150500.33.66-azure:5 6.4.0-150600.6-azure:6 6.4.0-150600.8.11-azure:6 6.4.0-150600.8.5-azure:6 6.4.0-150600.8.8-azure:6 6.4.0-150600.8.14-azure:6 5.14.21-150500.33.69-azure:5 | SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5) | 9.62 | All [stock SUSE 15 SP1, SP2, SP3, SP4, SP5 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported. 5.14.21-150500.33.54-azure:5 5.14.21-150500.33.57-azure:5 5.14.21-150500.33.60-azure:5 | #### Supported SUSE Linux Enterprise Server 16 kernel versions for Azure VMs Release | Mobility service version | Kernel version | --- | --- | --- | SUSE Linux Enterprise Server 16 | 9.67| [Supported kernels](https://github.com/Azure/Azure-SiteRecovery/blob/main/MobilityAgent/AzureToAzure/SupportedKernels/) | #### Supported Red Hat Linux kernel versions for Oracle Linux on Azure VMs Release | Mobility service version | Red Hat kernel version | --- | --- | --- | Oracle Linux 10.1 Oracle Linux 10 | 9.67 | 6.12.0-100.28.2.el10uek.x86_64 Oracle Linux 9.0 Oracle Linux 9.1 Oracle Linux 9.2 Oracle Linux 9.3 Oracle Linux 9.4 Oracle Linux 9.5 Oracle Linux 9.6 Oracle Linux 9.7 | 9.67 | 5.14.0-503.11.1 and later | Oracle Linux 9.0 Oracle Linux 9.1 Oracle Linux 9.2 Oracle Linux 9.3 Oracle Linux 9.4 Oracle Linux 9.5 Oracle Linux 9.6 | 9.66 | 5.14.0-503.11.1 and later | Oracle Linux 9.0 Oracle Linux 9.1 Oracle Linux 9.2 Oracle Linux 9.3 Oracle Linux 9.4 Oracle Linux 9.5 | 9.65 | 5.14.0-503.11.1 and later | Oracle Linux 9.0 Oracle Linux 9.1 Oracle Linux 9.2 Oracle Linux 9.3 Oracle Linux 9.4 | 9.64 | 5.14.0-284.73.1.el9_2.x86_64 5.14.0-284.75.1.el9_2.x86_64 5.14.0-284.77.1.el9_2.x86_64 5.14.0-284.79.1.el9_2.x86_64 5.14.0-284.80.1.el9_2.x86_64 5.14.0-284.82.1.el9_2.x86_64 5.14.0-284.84.1.el9_2.x86_64 5.14.0-284.85.1.el9_2.x86_64 5.14.0-284.86.1.el9_2.x86_64 5.14.0-427.13.1.el9_4.x86_64 5.14.0-427.16.1.el9_4.x86_64 5.14.0-427.18.1.el9_4.x86_64 5.14.0-427.20.1.el9_4.x86_64 5.14.0-427.22.1.el9_4.x86_64 5.14.0-427.24.1.el9_4.x86_64 5.14.0-427.26.1.el9_4.x86_64 5.14.0-427.28.1.el9_4.x86_64 5.14.0-427.31.1.el9_4.x86_64 5.14.0-427.33.1.el9_4.x86_64 5.14.0-427.35.1.el9_4.x86_64 5.14.0-427.37.1.el9_4.x86_64 | Oracle Linux 9.0 Oracle Linux 9.1 Oracle Linux 9.2 Oracle Linux 9.3 Oracle Linux 9.4 | 9.63 | 5.14.0-284.73.1.el9_2.x86_64 5.14.0-284.75.1.el9_2.x86_64 5.14.0-284.77.1.el9_2.x86_64 5.14.0-284.79.1.el9_2.x86_64 5.14.0-284.80.1.el9_2.x86_64 5.14.0-284.82.1.el9_2.x86_64 5.14.0-284.84.1.el9_2.x86_64 5.14.0-284.85.1.el9_2.x86_64 5.14.0-284.86.1.el9_2.x86_64 5.14.0-427.13.1.el9_4.x86_64 5.14.0-427.16.1.el9_4.x86_64 5.14.0-427.18.1.el9_4.x86_64 5.14.0-427.20.1.el9_4.x86_64 5.14.0-427.22.1.el9_4.x86_64 5.14.0-427.24.1.el9_4.x86_64 5.14.0-427.26.1.el9_4.x86_64 5.14.0-427.28.1.el9_4.x86_64 5.14.0-427.31.1.el9_4.x86_64 5.14.0-427.33.1.el9_4.x86_64 5.14.0-427.35.1.el9_4.x86_64 5.14.0-427.37.1.el9_4.x86_64 | Oracle Linux 9.0 Oracle Linux 9.1 Oracle Linux 9.2 Oracle Linux 9.3 | 9.62 | 5.14.0-70.97.1.el9_0.x86_64 5.14.0-70.101.1.el9_0.x86_64 5.14.0-284.62.1.el9_2.x86_64 5.14.0-284.64.1.el9_2.x86_64 5.14.0-284.66.1.el9_2.x86_64 5.14.0-284.67.1.el9_2.x86_64 5.14.0-284.69.1.el9_2.x86_64 5.14.0-284.71.1.el9_2.x86_64 | #### Supported Rocky Linux kernel versions for Azure VMs Release | Mobility service version | Red Hat kernel version | --- | --- | --- | Rocky Linux 10.0 Rocky Linux 10.1 | 9.66 | 6.12.0-55.9.1 and later 6.12.0-124.8.1 and later | Rocky Linux 10.2 | 9.67 | [Supported kernels](https://github.com/Azure/Azure-SiteRecovery/blob/main/MobilityAgent/AzureToAzure/SupportedKernels/) | Rocky Linux 9.0 Rocky Linux 9.1 Rocky Linux 9.2 Rocky Linux 9.3 Rocky Linux 9.4 Rocky Linux 9.5 Rocky linux 9.6 Rocky linux 9.7 | 9.66 | 5.14.0-611.5.1 and later | Rocky Linux 9.0 Rocky Linux 9.1 Rocky Linux 9.2 Rocky Linux 9.3 Rocky Linux 9.4 Rocky Linux 9.5 |9.65 | 5.14.0-70.97.1.el9_0.x86_64 5.14.0-70.101.1.el9_0.x86_64 5.14.0-284.62.1.el9_2.x86_64 5.14.0-284.64.1.el9_2.x86_64 5.14.0-284.66.1.el9_2.x86_64 5.14.0-284.67.1.el9_2.x86_64 5.14.0-284.69.1.el9_2.x86_64 5.14.0-284.71.1.el9_2.x86_64 5.14.0-427.13.1.el9_4.x86_64 5.14.0-427.16.1.el9_4.x86_64 5.14.0-427.18.1.el9_4.x86_64 5.14.0-427.20.1.el9_4.x86_64 5.14.0-427.22.1.el9_4.x86_64| Rocky Linux 9.0 Rocky Linux 9.1 |9.64 | 5.14.0-70.97.1.el9_0.x86_64 5.14.0-70.101.1.el9_0.x86_64 5.14.0-284.62.1.el9_2.x86_64 5.14.0-284.64.1.el9_2.x86_64 5.14.0-284.66.1.el9_2.x86_64 5.14.0-284.67.1.el9_2.x86_64 5.14.0-284.69.1.el9_2.x86_64 5.14.0-284.71.1.el9_2.x86_64 5.14.0-427.13.1.el9_4.x86_64 5.14.0-427.16.1.el9_4.x86_64 5.14.0-427.18.1.el9_4.x86_64 5.14.0-427.20.1.el9_4.x86_64 5.14.0-427.22.1.el9_4.x86_64| Rocky Linux 9.0 Rocky Linux 9.1 |9.63 | 5.14.0-70.97.1.el9_0.x86_64 5.14.0-70.101.1.el9_0.x86_64 5.14.0-284.62.1.el9_2.x86_64 5.14.0-284.64.1.el9_2.x86_64 5.14.0-284.66.1.el9_2.x86_64 5.14.0-284.67.1.el9_2.x86_64 5.14.0-284.69.1.el9_2.x86_64 5.14.0-284.71.1.el9_2.x86_64 5.14.0-427.13.1.el9_4.x86_64 5.14.0-427.16.1.el9_4.x86_64 5.14.0-427.18.1.el9_4.x86_64 5.14.0-427.20.1.el9_4.x86_64 5.14.0-427.22.1.el9_4.x86_64| Rocky Linux 9.0 Rocky Linux 9.1 |9.62 | 5.14.0-70.97.1.el9_0.x86_64 5.14.0-70.101.1.el9_0.x86_64 5.14.0-284.62.1.el9_2.x86_64 5.14.0-284.64.1.el9_2.x86_64 5.14.0-284.66.1.el9_2.x86_64 5.14.0-284.67.1.el9_2.x86_64 5.14.0-284.69.1.el9_2.x86_64 5.14.0-284.71.1.el9_2.x86_64 5.14.0-427.13.1.el9_4.x86_64 5.14.0-427.16.1.el9_4.x86_64 5.14.0-427.18.1.el9_4.x86_64 5.14.0-427.20.1.el9_4.x86_64 5.14.0-427.22.1.el9_4.x86_64| Rocky Linux 9.8 | 9.67 | [Supported kernels](https://github.com/Azure/Azure-SiteRecovery/blob/main/MobilityAgent/AzureToAzure/SupportedKernels/) | #### Supported Alma Linux kernel versions for Azure VMs Release | Mobility service version | Red Hat kernel version | --- | --- | --- | Alma Linux 10.0 Alma Linux 10.1 | 9.66 | 6.12.0-55.9.1 and later 6.12.0-124.8.1 and later | Alma Linux 10.2 | 9.67 | [Supported kernels](https://github.com/Azure/Azure-SiteRecovery/blob/main/MobilityAgent/AzureToAzure/SupportedKernels/) | Alma Linux 9.6 Alma Linux 9.7 | 9.66 | 5.14.0-611.5.1 and later | Alma Linux 9.0 Alma Linux 9.1 Alma Linux 9.2 Alma Linux 9.3 Alma Linux 9.4 Alma Linux 9.5 |9.65 | 5.14.0-70.97.1.el9_0.x86_64 5.14.0-70.101.1.el9_0.x86_64 5.14.0-284.62.1.el9_2.x86_64 5.14.0-284.64.1.el9_2.x86_64 5.14.0-284.66.1.el9_2.x86_64 5.14.0-284.67.1.el9_2.x86_64 5.14.0-284.69.1.el9_2.x86_64 5.14.0-284.71.1.el9_2.x86_64 5.14.0-427.13.1.el9_4.x86_64 5.14.0-427.16.1.el9_4.x86_64 5.14.0-427.18.1.el9_4.x86_64 5.14.0-427.20.1.el9_4.x86_64 5.14.0-427.22.1.el9_4.x86_64| Alma Linux 9.0 Alma Linux 9.1 |9.64 | 5.14.0-70.97.1.el9_0.x86_64 5.14.0-70.101.1.el9_0.x86_64 5.14.0-284.62.1.el9_2.x86_64 5.14.0-284.64.1.el9_2.x86_64 5.14.0-284.66.1.el9_2.x86_64 5.14.0-284.67.1.el9_2.x86_64 5.14.0-284.69.1.el9_2.x86_64 5.14.0-284.71.1.el9_2.x86_64 5.14.0-427.13.1.el9_4.x86_64 5.14.0-427.16.1.el9_4.x86_64 5.14.0-427.18.1.el9_4.x86_64 5.14.0-427.20.1.el9_4.x86_64 5.14.0-427.22.1.el9_4.x86_64| Alma Linux 9.8 | 9.67 | [Supported kernels](https://github.com/Azure/Azure-SiteRecovery/blob/main/MobilityAgent/AzureToAzure/SupportedKernels/) | ## <a name = "replicated-machines---linux-file-systemguest-storage"></a>Replicated machines: Linux file system/guest storage * **Root file systems**: ext3, ext4, XFS, and single-device BTRFS. Multi-device, spanned, and RAID BTRFS file systems aren't supported. * **Boot file system**: A separate `/boot` file system can also use ext2. A `/boot` file system on an LVM logical volume isn't supported if the logical volume spans multiple physical disks. * **Volume manager**: LVM2. If the root file system is on LVM, install the `lvm2` package and verify that `vgdisplay` is available before you enable replication. Multipath software isn't supported. ## <a name = "replicated-machines---compute-settings"></a>Replicated machines: Compute settings Setting | Support | Details --- | --- | --- Size | Supported when all requirements are met. | The VM must have at least two active vCPUs and 1 GiB RAM. For constrained-vCPU sizes, use the active vCPU count, not the nominal count in the base size name. Validate the exact source and target VM sizes, including disk-controller, security-type, generation, disk, networking, and target-region capabilities. CPU architecture | x64 is supported. Arm64 isn't supported. | Arm64-based VM sizes, including Azure Cobalt and Ampere Altra sizes, aren't supported. RAM | Site Recovery driver consumes 6% of RAM. Availability sets | Supported. | If you enable replication for an Azure VM with the default options, an availability set is created automatically based on the source region settings. You can modify these settings. Availability zones | Supported with restrictions. | Multiple source NIC IP configurations are supported only for regional replication. Azure Dedicated Host | Not supported. | Hybrid Use Benefit (HUB) | Supported. | If the source VM has a HUB license enabled, a test failover or failed-over VM also uses the HUB license. Virtual Machine Scale Set Flex | Availability scenario: Supported. Scalability scenario: Not supported. | Azure gallery images: Microsoft published | Supported. | Supported if the VM runs on a supported operating system. Azure Gallery images: Non-Microsoft published | Supported. | Supported if the VM runs on a supported operating system. Custom images: Non-Microsoft published | Supported. | The VM is supported if it runs on a supported operating system. During test failover and failover, Azure creates a VM with an Azure Marketplace image. Ensure that no custom Azure policy blocks this operation. VMs migrated by using Site Recovery | Supported. | If a VMware VM or physical machine was migrated to Azure by using Site Recovery, you need to uninstall the older version of the Mobility service running on the machine and restart the machine before you replicate it to another Azure region. Azure role-based access control (RBAC) policies | Not supported. | Azure role-based access control policies on VMs aren't replicated to the failover VM in the target region. Extensions | Not supported. | Extensions aren't replicated to the failover VM in the target region. It needs to be installed manually after failover. VM boot generation | Generation 1 and Generation 2 are supported. | Generation 1 uses PCAT boot and Generation 2 uses UEFI boot. A VM size-series suffix such as v5, v6, or v7 identifies a hardware-series version, not the VM boot generation. VM security type | Standard and Trusted Launch are supported with restrictions. Confidential VMs aren't supported. | Trusted Launch is subject to the [Trusted Launch support requirements](concepts-trusted-vm.md), including the 1,200 protected-disk subscription limit. Before enabling replication, update the Mobility service so that the detected security type matches the VM configuration. Specialized VM sizes | Validate the exact source and target size before protection. | For GPU, FPGA, HPC, RDMA-enabled, storage-optimized, isolated, and nested-virtualization sizes, verify target availability and equivalent accelerator, networking, isolation, and nested-virtualization capabilities. VM extensions and drivers aren't replicated. Local NVMe data and nested guests aren't protected. Proximity placement groups (PPGs) | Supported. | VMs located inside PPGs by using Site Recovery. Tags | Supported. | User-generated tags applied on source VMs are carried over to target VMs post-test failover or failover. Tags on the VMs replicate once every 24 hours for as long as the VMs are present in the target region. ## Replicated machines: Disk actions Action | Details --- | --- Resize a disk on a replicated VM. | Resizing up on the source VM is supported. Resizing down on the source VM isn't supported. Perform resizing before failover. No need to disable/re-enable replication. If you change the source VM after failover, the changes aren't captured. If you change the disk size on the Azure VM after failover, Site Recovery doesn't capture the changes. Failback is to the original VM size. If you resize to 4 TB or larger, see the Azure guidance on disk caching in [Azure Premium storage: Design for high performance](/Azure/virtual-machines/premium-storage-performance). Add a disk to a replicated VM. | Supported. Offline changes to protected disks. | Disconnecting disks and making offline modifications to them require triggering a full resync. Disk caching. | Disk caching isn't supported for disks 4 TB and larger. If multiple disks are attached to your VM, each disk that's smaller than 4 TB supports caching. Changing the cache setting of an Azure disk detaches and reattaches the target disk. If it's the operating system disk, the VM is restarted. Before you change the disk cache setting, stop all applications or services that this disruption might affect. Not following the recommendations could lead to data corruption. Change source disk SKU. | Supported. Changing the source disk SKU doesn't impact ongoing replication or failover operations. However, the replica disk SKU isn't automatically updated. The failover VM uses the disk SKU that existed when replication was enabled. ## <a name = "replicated-machines---storage"></a>Replicated machines: Storage > [!IMPORTANT] > Unmanaged Azure VM disks retired on March 31, 2026. They're no longer supported as source, replica, or failover target disks. Disable and re-enable protection after migrating the VM to managed disks. The following table summarizes support for the Azure VM OS disk, data disk, and temporary disk: - To avoid any performance issues, observe the VM disk limits and targets for [managed disks](/Azure/virtual-machines/disks-scalability-targets). - If you deploy with the default settings, Site Recovery automatically creates disks and storage accounts based on the source settings. - If you customize, ensure that you follow the guidelines. The following table shows the default managed-disk mapping. A source disk SKU change doesn't update the replica disk SKU. To change the replica configuration, disable and re-enable replication. Source disk | Replica disk | Failover disk | Notes --- | --- | --- | --- Standard HDD LRS (`Standard_LRS`) | `Standard_LRS` | `Standard_LRS` | Standard HDD remains supported for data disks. Standard HDD OS disks retire on September 8, 2028; use Standard SSD or Premium SSD for new recovery OS disks. Standard SSD LRS or ZRS (`StandardSSD_LRS`, `StandardSSD_ZRS`) | Matches the source redundancy | Matches the source redundancy | ZRS source disks are supported for regional disaster recovery, but not zone-to-zone disaster recovery. Premium SSD v1 LRS or ZRS (`Premium_LRS`, `Premium_ZRS`) | Matches the source redundancy | Matches the source redundancy | ZRS source disks are supported for regional disaster recovery, but not zone-to-zone disaster recovery. Premium SSD v2 LRS (`PremiumV2_LRS`) | `Premium_LRS` | `PremiumV2_LRS` | Generally available. Requires High Churn and must be selected when replication is enabled. Host caching isn't supported. Ultra Disk LRS (`UltraSSD_LRS`) | `Premium_LRS` | `UltraSSD_LRS` | Requires High Churn. Zone-to-zone disaster recovery and host caching aren't supported. Component | Support | Details --- | --- | --- Disk renaming | Supported. | OS disk maximum size | [4,095 GiB](/Azure/virtual-machines/managed-disks-overview#os-disk). | Learn more about [VM disks](/Azure/virtual-machines/managed-disks-overview). Temporary disk | Not supported. | The temporary disk is always excluded from replication. Don't store any persistent data on the temporary disk. Learn more about [temporary disks](/Azure/virtual-machines/managed-disks-overview). Data disk minimum size | 1 GiB. | No additional restrictions. Data disk maximum number | Up to 64, with LUNs 0 through 63. | The selected source or target VM size can impose a lower limit. Data disk maximum size | 32,767 GiB (approximately 32 TiB). | This Site Recovery limit also applies to Premium SSD v2 and Ultra Disk, even when Azure Disk Storage supports a larger disk. Disk subscription limits | Up to 3,000 (1,200 if Trusted VMs) protected disks per subscription. | Ensure that the source or target subscription doesn't have more than 3,000 (1,200 if Trusted VMs) Site Recovery-protected disks (both data and OS). Standard SSD | Supported. | Managed disk redundancy | LRS and ZRS are supported. | ZRS is available only for Standard SSD and Premium SSD v1. Premium SSD v2 and Ultra Disk don't have a ZRS SKU. Cool and hot storage | Not supported. | VM disks aren't supported on cool or hot storage. Storage Spaces | Supported. | NVMe storage interface | Supported | Remote managed-disk NVMe requires an eligible Generation 2 Standard or Trusted Launch image, a supported Mobility service version and operating system, and an available target VM size. Supported for Azure-to-Azure - Windows and [limited Linux distributions and versions](#linux-distributions-supported-for-nvme) for Gen2 VMs such as Da/Ea/Fa v6-series, Ddsv6, Edsv6, Ebsv5/Ebdsv5, and others that use NVMe interface. `curl` and access to Azure Instance Metadata Service are required during installation and upgrade. Mixed SCSI and NVMe controllers, multiple controller addresses of the same type, ephemeral OS disks, and local NVMe disks aren't supported. Local storage | Not replicated. | Azure temporary or resource disks and directly mapped local NVMe devices must not contain persistent data. A VM with an ordinary temporary disk can be protected when all other requirements are met. Ephemeral OS disks aren't supported. Performance Plus disk | Supported | For VMs using Premium SSD, Standard SSD, Standard HDD disks. Ensure that you use only premium storage accounts during replication. Requires High Churn. The setting is preserved for replication, test failover, and failover. Use a supported cache account and region. Disk performance settings | Supported with restrictions. | For Premium SSD v2 and Ultra Disk, only the IOPS and throughput configured when replication is enabled are copied to the target disk. Later changes aren't reflected. For Premium SSD v1 tier or SKU changes, wait for a new recovery point before failover. Replica disk SKU changes | Supported with restrictions. | You can move a replica disk to a higher supported tier after revoking its active shared access signature (SAS). Premium SSD v2 (`PremiumV2_LRS`) and Ultra Disk (`UltraSSD_LRS`) aren't supported as replica disk types in any Site Recovery scenario. If a replica disk is manually changed to either unsupported SKU, replication is blocked. Because the disk can't be downgraded to Premium SSD v1, disable and re-enable replication to create a supported replica disk. Premium SSD v2 and Ultra Disk replication operation duration | Supported with additional time. | Initial replication, checksum-based resynchronization, and reprotection can take longer than the same operations for Premium SSD v1. The relative difference decreases as disk size increases. For planning estimates, see [initial replication, reprotection, and resynchronization duration estimates](azure-to-azure-common-questions.md#initial-replication-reprotection-and-resynchronization-duration-estimates). Premium SSD v2 and Ultra Disk source snapshots | Retained by default. | During initial replication and resynchronization, Site Recovery creates a managed disk snapshot directly from each source disk. The retained snapshot helps a future resynchronization finish faster. To reduce snapshot charges, you can delete it after initial replication or resynchronization completes. Ongoing replication continues, but a future resynchronization can take longer because Site Recovery must create a new snapshot. Mixed controller VMs (SCSI + NVMe) | Not supported. | VM sizes such as Lsv3 aren't supported. Encryption at host | Source protection is supported, but the setting isn't preserved. | Encryption at host isn't enabled on test-failover or failover VMs. Select a supported target VM size and re-enable encryption at host after failover. For more information, see [Enable end-to-end encryption by using encryption at host](/Azure/virtual-machines/disks-enable-host-based-encryption-portal). Encryption at rest (SSE) | Supported. | SSE is the default setting on storage accounts. Encryption at rest (CMK) | Supported. | Both software and hardware security module (HSM) keys are supported for managed disks. Double encryption at rest | Supported. | Learn more about supported regions for [Windows](/Azure/virtual-machines/disk-encryption) and [Linux](/Azure/virtual-machines/disk-encryption). FIPS encryption | Not supported. Azure Disk Encryption for Windows OS | Supported for VMs with managed disks. | VMs using unmanaged disks aren't supported. HSM-protected keys aren't supported. Encryption of individual volumes on a single disk isn't supported. | Azure Disk Encryption for Linux OS | Supported for VMs with managed disks. | VMs using unmanaged disks aren't supported. HSM-protected keys aren't supported. Encryption of individual volumes on a single disk isn't supported. Known issue with enabling replication. For more information, see [Enable protection failed because the installer is unable to find the root disk](azure-to-azure-troubleshoot-errors.md). Shared access signature key rotation | Supported. | If the shared access signature key for storage accounts is rotated, you must disable and re-enable replication. | Host caching | Supported with disk-specific restrictions. | Validate the target VM cache capacity. Premium SSD v2, Ultra Disk, and shared disks don't support host caching. Hot add | Supported. | Enabling replication for a data disk that you add to a replicated Azure VM is supported for VMs that use managed disks. Use hot add to add only one disk at a time to an Azure VM. Parallel addition of multiple disks isn't supported. | Hot remove disk | Not supported. | If you remove a data disk on the VM, you need to disable replication and enable replication again for the VM. Exclude disk | Supported. Use [Azure PowerShell](azure-to-azure-exclude-disks.md) or go to the **Advanced Setting** > **Storage Settings** > **Disk to Replicate** option from the portal. | Temporary disks are excluded by default. Storage Spaces Direct | Supported for crash-consistent recovery points. Application-consistent recovery points aren't supported. | Scale-Out File Server | Supported for crash-consistent recovery points. Application-consistent recovery points aren't supported. | Distributed replicated block device (DRBD) | Disks that are part of a DRBD setup aren't supported. | Cache storage account redundancy | Supported. | LRS, ZRS, GRS, and read-access GRS are supported according to the storage account type and region availability. Cool and hot storage | Not supported. | VM disks aren't supported on cool or hot storage. Azure Storage firewalls for virtual networks | Supported. | If you want to restrict virtual network access to storage accounts, enable [Allow trusted Microsoft services](../storage/common/storage-network-security.md#exceptions). General-purpose V2 storage accounts (hot and cool tiers) | Supported. | Transaction costs increase substantially compared to general-purpose V1 storage accounts. Managed shared disk | Supported with restrictions. | See the [shared disk support matrix](shared-disk-support-matrix.md). The same shared-disk set must be attached to every protected Windows Server Failover Cluster node, and every node must have a healthy Mobility service. Managed Premium SSD v2 | Supported. | Since block blob storage accounts aren't supported in China North and China East regions, Site Recovery for Premium SSD v2 disks isn't supported there. Converting a protected Premium SSD v1 disk requires disabling and re-enabling replication. Public network access is required during enable protection or resynchronization operations. It can be disabled after the operation has completed. Ultra Disks | Supported. | Zone-to-zone disaster recovery isn't supported. Since block blob storage accounts aren't supported in China North and China East regions, Site Recovery for Ultra Disks isn't supported there. Public network access is required during enable protection or resynchronization operations. It can be disabled after the operation has completed. Secure transfer option | Supported. Write Accelerator-enabled disks | Not supported during protection. | Disable Write Accelerator before enabling replication. After failover, re-enable it manually only on a supported M-series VM with Premium SSD v1 and a compatible caching setting. Tags | Supported. | User-generated tags replicate every 24 hours. Soft delete | Not supported. | Soft delete isn't supported because after soft delete is enabled on a storage account, it increases cost. Site Recovery performs frequent creations and deletions of log files. Replicating causes costs to increase. iSCSI disks | Not supported. | Guest iSCSI disks can be migrated to Azure through the physical-machine migration workflow. They aren't supported for disaster recovery, failback, or Azure-to-Azure replication. Azure Elastic SAN volumes | Not supported as VM disks. | Site Recovery doesn't replicate Elastic SAN resources, snapshots, or iSCSI session configuration. Use Elastic SAN snapshots or application-level replication and recreate connectivity in the recovery site. Storage Replica | Not supported. >[!IMPORTANT] > To avoid performance issues, ensure that you follow VM disk scalability and performance targets for [managed disks](/Azure/virtual-machines/disks-scalability-targets). If you use default settings, Site Recovery creates the required disks and storage accounts based on the source configuration. If you customize and select your own settings, follow the disk scalability and performance targets for your source VMs. #### Linux distributions supported for NVMe Linux distribution | Supported versions --- | --- Red Hat Enterprise Linux (RHEL) | 9.0 to 9.7 Ubuntu | 24.04 LTS SUSE Linux Enterprise Server (SLES) | 15 (SP4 to SP7) ## Limits and data change rates The following table summarizes Site Recovery limits: - These limits are based on tests but don't cover all possible application I/O combinations. - Actual results can vary based on your app I/O mix. - Consider two limits: per-disk data churn and per-VM data churn. - Normal Churn supports up to 54 MB/s per VM. High Churn limits depend on VM memory, disk type and size, write size, operating system, region pair, Mobility service version, and cache account. Replica disk type | Average source disk I/O | Average source disk data churn | Total source disk data churn per day ---|---|---|--- Standard storage | 8 KB | 2 MBps | 168 GB per disk Premium SSD with disk size 128 GiB or more | 8 KB | 2 MBps | 168 GB per disk Premium SSD with disk size 128 GiB or more | 16 KB | 4 MBps | 336 GB per disk Premium SSD with disk size 128 GiB or more | 32 KB or greater | 8 MBps | 672 GB per disk Premium SSD with disk size 512 GiB or more | 8 KB | 5 MBps | 421 GB per disk Premium SSD with disk size 512 GiB or more | 16 KB or greater |20 MBps | 1,684 GB per disk Eligible High Churn configurations support up to 500 MB/s per VM and 250 MB/s per disk. Other High Churn configurations remain limited to 54 MB/s or 100 MB/s per VM. For the authoritative limits, see [Azure VM disaster recovery: High Churn support](./concepts-azure-to-azure-high-churn-support.md). ## <a name = "replicated-machines---networking"></a>Replicated machines: Networking Setting | Support | Details --- | --- | --- Network interface card (NIC) | Maximum number supported for a specific Azure VM size | NICs are created when the VM is created during failover. The number of NICs on the failover VM depends on the number of NICs on the source VM when replication was enabled. If you add or remove a NIC after enabling replication, it doesn't affect the number of NICs on the replicated VM after failover. The order of NICs after failover isn't guaranteed to be the same as the original order. You can rename NICs in the target region based on your organization's naming conventions. Internet load balancer | Not supported | Set up public/internet load balancers in the primary region. Site Recovery doesn't support public/internet load balancers in the DR region. Internal load balancer | Supported | The recovery load balancer must use the recovery virtual network and contain the selected backend pool. Its SKU and placement must be compatible with the VM zone, availability set, and VM size. Associate it by using an Azure Automation script in a recovery plan. Public IP address | Supported | The recovery public IP must exist in the target region, must not be attached to an unrelated NIC or VM, and must use a SKU compatible with the load balancer. Associate it with the NIC manually or by using an Azure Automation script in a recovery plan. Network security group (NSG) on NIC | Supported | Associate the NSG with the NIC by using an Azure Automation script in a recovery plan. NSG on subnet | Supported | Associate the NSG with the subnet by using an Azure Automation script in a recovery plan. Application security group (ASG) | Unsupported | Site Recovery doesn't support ASGs. Reserved (static) IP address | Supported | If the NIC on the source VM has a static IP address, and the target subnet has the same IP address available, the NIC is assigned to the failed-over VM. If the target subnet doesn't have the same IP address available, one of the available IP addresses in the subnet is reserved for the VM. You can also specify a fixed IP address and subnet in **Replicated items** > **Settings** > **Network** > **Network interfaces**. Dynamic IP address | Supported | If the NIC on the source has dynamic IP addressing, the NIC on the failed-over VM is also dynamic by default. You can modify to a fixed IP address if necessary. Multiple IP addresses | Supported | When you fail over a VM that has a NIC with multiple IP addresses, only the primary IP address of the NIC in the source region is kept by default. To fail over secondary IP configurations, go to the **Network** pane and configure them. Supported only for region replication. Zone-to-zone replication isn't supported. Azure Traffic Manager | Supported | You can preconfigure Traffic Manager so that traffic is regularly routed to the endpoint in the source region. You can also route traffic to the endpoint in the target region if there was failover. Azure Domain Name System (DNS) | Supported | Custom Domain Name System (DNS) | Supported | Unauthenticated proxy | Supported | Learn more about [networking in Azure VM disaster recovery](./azure-to-azure-about-networking.md). Authenticated proxy | Not supported | If the VM is using an authenticated proxy for outbound connectivity, it can't be replicated by using Site Recovery. VPN site-to-site connection to on-premises (with or without Azure ExpressRoute) | Supported | Ensure that the user-defined routes and NSGs are configured in such a way that the Site Recovery traffic isn't routed to on-premises. Learn more about [networking in Azure VM disaster recovery](./azure-to-azure-about-networking.md). Network-to-network connection | Supported | Learn more about [networking in Azure VM disaster recovery](./azure-to-azure-about-networking.md). Virtual network service endpoints | Supported | If you restrict the virtual network access to storage accounts, ensure that the trusted Microsoft services are allowed access to the storage account. Accelerated networking | Supported | You can enable accelerated networking on the recovery VM only if you enable it on the source VM also. Ensure that the source VM has sufficient network bandwidth and CPU capacity for the selected churn level. Learn more about [accelerated networking with Azure VM disaster recovery](azure-vm-disaster-recovery-with-accelerated-networking.md). Palo Alto Network Appliance | Not supported | With non-Microsoft appliances, the provider inside the VM often imposes restrictions. Site Recovery needs agents, extensions, and outbound connectivity to be available. The appliance doesn't allow any outbound activity to be configured inside the VM. IPv6 | Not supported | Mixed configurations that include both IPv4 and IPv6 are supported. Site Recovery uses any free IPv4 address that's available. If there are no free IPv4 addresses in the subnet, the configuration isn't supported. Private link access to Site Recovery | Supported | Learn more about how to [replicate machines with private endpoints](azure-to-azure-how-to-enable-replication-private-endpoints.md). Tags | Supported | User-generated tags on NICs replicate every 24 hours. ## Related content - Read [networking guidance](./azure-to-azure-about-networking.md) for replicating Azure VMs. - Deploy disaster recovery by [replicating Azure VMs](./azure-to-azure-quickstart.md).

Success! Branch created successfully. Create Pull Request on GitHub

Error: