Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: Support matrix for VMware/physical disaster recovery in Azure Site Recovery. description: Summarizes support for disaster recovery of VMware VMs and physical server to Azure using Azure Site Recovery. ms.topic: concept-article ms.service: azure-site-recovery ms.date: 09/21/2026 ms.author: v-gajeronika author: Jeronika-MS ms.custom: engagement-fy23, linux-related-content # Customer intent: "As an IT administrator managing disaster recovery solutions, I want to understand the support matrix for VMware VMs and physical servers in Azure Site Recovery, so that I can ensure compatibility and optimize our disaster recovery strategies." --- # Support matrix for disaster recovery of VMware VMs and physical servers to Azure > [!CAUTION] > This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Consider your use and plan accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life). This article summarizes supported components and settings for disaster recovery of VMware VMs and physical servers to Azure by using [Azure Site Recovery](site-recovery-overview.md). - [Learn more](vmware-azure-architecture-modernized.md) about VMware VM/physical server disaster recovery architecture. - Follow our [tutorials](tutorial-prepare-azure.md) to try out disaster recovery. > [!NOTE] > Site Recovery doesn't move or store customer data out of the target region, in which disaster recovery has been set up for the source machines. Customers can select a Recovery Services Vault from a different region if they so choose. The Recovery Services Vault contains metadata but no actual customer data. ## Deployment scenarios **Scenario** | **Details** --- | --- Disaster recovery of VMware VMs | Replication of on-premises VMware VMs to Azure. Deploy this scenario in the Azure portal or by using [PowerShell](vmware-azure-disaster-recovery-powershell.md). Disaster recovery of physical servers | Replication of on-premises Windows/Linux physical servers to Azure. Deploy this scenario in the Azure portal. ## On-premises virtualization servers **Server** | **Requirements** | **Details** --- | --- | --- vCenter Server | Version 9.0 and subsequent updates in this version, Version 8.0, 7.0, 6.7, or 6.5 | Use a vCenter server in your disaster recovery deployment. vSphere hosts | Version 9.0 and subsequent updates in this version, Version 8.0, 7.0, 6.7, or 6.5 | Locate vSphere hosts and vCenter servers in the same network as the process server. By default, the process server runs on the configuration server. [Learn more](vmware-azure-deploy-configuration-server.md). ## Azure Site Recovery replication appliance The replication appliance is an on-premises machine that runs Site Recovery components, including various Site Recovery services that help with discovery of on-premises environment, orchestration of disaster recovery, and act as a bridge between on-premises and Azure. - For VMware VMs, you can create the replication appliance by downloading an OVF template to create a VMware VM. - For physical servers, you can set up the replication appliance manually by running a PowerShell script. [!INCLUDE [end-of-support-notes-windows-server-2008-2012.md](./includes/end-of-support-notes-windows-server-2008-2012.md)] **Component** | **Requirements** --- |--- CPU cores | 8 RAM | 16 GB Number of disks | Two disks<br/><br/> Disks include the OS disk and data disk. Operating system | Windows Server 2022 with Desktop experience Operating system locale | English (en-us) Windows Server roles | Don't enable Active Directory Domain Services; Internet Information Services (IIS) or Hyper-V. Group policies| Don't enable these group policies: <br/> - Prevent access to the command prompt. <br/> - Prevent access to registry editing tools. <br/> - Trust logic for file attachments. <br/> - Turn on Script Execution. <br/> - [Learn more](/previous-versions/windows/it-pro/windows-7/gg176671(v=ws.10))| IIS | Make sure you:<br/><br/> - Don't have a preexisting default website <br/> - Enable [anonymous authentication](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731244(v=ws.10)) <br/> - Enable [FastCGI](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc753077(v=ws.10)) setting <br/> - Don't have preexisting website/app listening on port 443<br/> NIC type | VMXNET3 (when deployed as a VMware VM) Fully qualified domain name (FQDN) | Static Ports | 443 used for control channel orchestration<br/>9443 for data transport NAT | Supported > [!NOTE] > You must install the operating system with the English locale. Converting the locale after installation can result in potential issues. > > FQDN or NAT IP selection is a one time selection and can't change this selection later for the appliance. ## Replicated machines Site Recovery supports replication of any workload running on a supported machine. **Component** | **Details** --- | --- Machine settings | Machines that replicate to Azure must meet [Azure requirements](#azure-vm-requirements). Machine workload | Site Recovery supports replication of any workload running on a supported machine. [Learn more](./site-recovery-workload.md). Machine name | Ensure that the display name of machine doesn't fall into [Azure resource naming restrictions](../azure-resource-manager/management/resource-name-rules.md).<br/><br/> Logical volume names aren't case-sensitive. Ensure that no two volumes on a device have same name. For example, Volumes with names "voLUME1" and "volume1" can't be protected through Azure Site Recovery. Azure Virtual Machines as Physical | Failover of virtual machines with Marketplace image disks is currently not supported. >[!NOTE] > Different machines with same BIOS ID aren't supported. ### For Windows > [!NOTE] > Ensure that at least 600 MB of free space is available in the installation folder on the on-premises and Azure machines. **Operating system** | **Details** --- | --- Windows Server 2025 | Supported. Windows Server 2022 | Supported. Windows Server 2019 | Supported. Windows Server 2016 64-bit | Supported for Server Core, Server with Desktop Experience. Windows 11, Windows 10, Windows 8.1, Windows 8 | Only 64-bit system is supported. 32-bit system isn't supported. Windows 7 with SP1 64-bit | Supported. ### For Linux > [!NOTE] > This article retains distro, Mobility service, and kernel details for planning. Before enabling replication, also verify the exact running kernel against the latest Azure Site Recovery supported-kernel list. **Operating system** | **Details** --- | --- Linux | Only 64-bit system is supported. 32-bit system isn't supported.<br/><br/>Supported Linux systems must include the Hyper-V storage driver required to boot in Azure. The Mobility service explicitly validates `hv_storvsc` on Red Hat Enterprise Linux 5 and 6. Newer supported stock kernels are expected to include the driver.<br/><br/>Site Recovery orchestrates failover to run Linux servers in Azure. However, Linux vendors might limit support to distribution versions that haven't reached end of life.<br/><br/>Only stock kernels that are part of the distribution minor-version release or update are supported. For Ubuntu and Debian, the running kernel must exactly match an entry supported by the installed Mobility service.<br/><br/>Upgrading protected machines across major Linux distribution versions isn't supported. To upgrade, disable replication, upgrade the operating system, and then enable replication again.<br/><br/>Chained I/O isn't supported by Site Recovery.<br/><br/>Guest preparation and Azure Linux Agent installation or repair occur only when the selected recovery point requires preparation during failover. Red Hat Enterprise Linux | 5.2 to 5.11</b><br/> 6.1 to 6.10</b> </br> 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 Beta version](https://support.microsoft.com/help/4578241/), [7.9](https://support.microsoft.com/help/4590304/) </br> [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 higher), [8.5](https://support.microsoft.com/topic/883a93a7-57df-4b26-a1c4-847efb34a9e8) (4.18.0-348.5.1.el8_5.x86_64 or higher), [8.6](https://support.microsoft.com/topic/update-rollup-62-for-azure-site-recovery-e7aff36f-b6ad-4705-901c-f662c00c402b), 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 <br/> Few older kernels on servers running Red Hat Enterprise Linux 5.2-5.11 and 6.1-6.10 don't have the required Hyper-V storage driver preinstalled. Install the required driver before enabling replication. <br> <br> **Notes**: RHEL `9.x` and `10.x` is supported for [the following kernel versions](#supported-kernel-versions-for-red-hat-enterprise-linux-for-azure-virtual-machines) Ubuntu | Ubuntu 14.04* LTS server [(review supported kernel versions)](#ubuntu-kernel-versions)<br/>Ubuntu 16.04* LTS server [(review supported kernel versions)](#ubuntu-kernel-versions) </br> Ubuntu 18.04* LTS server [(review supported kernel versions)](#ubuntu-kernel-versions) </br> Ubuntu 20.04* LTS server [(review supported kernel versions)](#ubuntu-kernel-versions) <br> Ubuntu 22.04* LTS server [(review supported kernel versions)](#ubuntu-kernel-versions) <br> Ubuntu 24.04* LTS server [(review supported kernel versions)](#ubuntu-kernel-versions) Debian | Debian 7/Debian 8 (includes support for all 7. *x*, 8. *x* versions). [Ensure to download latest mobility agent installer on the configuration server](vmware-physical-mobility-service-overview.md#download-latest-mobility-agent-installer-for-suse-11-sp3-suse-11-sp4-rhel-5-cent-os-5-debian-7-debian-8-debian-9-oracle-linux-6-and-ubuntu-1404-server). <br/> Debian 9 (includes support for 9.1 to 9.13. Debian 9.0 isn't supported.). [Ensure to download latest mobility agent installer on the configuration server](vmware-physical-mobility-service-overview.md#download-latest-mobility-agent-installer-for-suse-11-sp3-suse-11-sp4-rhel-5-cent-os-5-debian-7-debian-8-debian-9-oracle-linux-6-and-ubuntu-1404-server). <br/> Debian 10, Debian 11, Debian 12 [(Review supported kernel versions)](#debian-kernel-versions). SUSE Linux | SUSE Linux Enterprise Server 12 SP1, SP2, SP3, SP4, [SP5](https://support.microsoft.com/help/4570609) [(review supported kernel versions)](#suse-linux-enterprise-server-12-supported-kernel-versions) <br/> SUSE Linux Enterprise Server 15, 15 SP1, SP2, SP3, SP4, SP5, SP6, SP7 [(review supported kernel versions)](#suse-linux-enterprise-server-15-supported-kernel-versions) <br/> SUSE Linux Enterprise Server 11 SP3. [Ensure to download latest mobility agent installer on the configuration server](vmware-physical-mobility-service-overview.md#download-latest-mobility-agent-installer-for-suse-11-sp3-suse-11-sp4-rhel-5-cent-os-5-debian-7-debian-8-debian-9-oracle-linux-6-and-ubuntu-1404-server). </br> SUSE Linux Enterprise Server 11 SP4 </br> **Notes**: <br> - Upgrading replicated machines from SUSE Linux Enterprise Server 11 SP3 to SP4 isn't supported. To upgrade, disable replication and re-enable after the upgrade. <br> - Support for SUSE Linux Enterprise Server 15 SP5, SP6, and SP7 is available for Modernized experience only. 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/b19c8190-5f88-43ea-85b1-d9e0cc5ca7e8), [8.3](https://support.microsoft.com/topic/b19c8190-5f88-43ea-85b1-d9e0cc5ca7e8), [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, 9.0, 9.1, 9.2, 9.3, 9.4, 9.5, 9.6, 10.0 <br/><br/>Unbreakable Enterprise Kernel Release 7 (UEK7) is supported from 8.7. <br/><br/> **Notes:** <br> Running the Red Hat compatible kernel or Unbreakable Enterprise Kernel Release 3, 4 & 5 (UEK3, UEK4, UEK5)<br/><br/>8.1<br/>Running on all UEK kernels and RedHat kernel <= 3.10.0-1062.* are supported in [9.35](https://support.microsoft.com/help/4573888/) Support for rest of the RedHat kernels is available in [9.36](https://support.microsoft.com/help/4578241/). <br> Oracle Linux `9.x` and `10.x` are supported for the [following kernel versions](#supported-red-hat-linux-kernel-versions-for-oracle-linux-on-azure-virtual-machines). Rocky Linux | [See supported versions](#rocky-linux-server-supported-kernel-versions). > [!NOTE] >- For each of the Windows versions, Azure Site Recovery only supports [Long-Term Servicing Channel (LTSC)](/windows-server/get-started/servicing-channels-comparison#long-term-servicing-channel-ltsc) builds. [Semi-Annual Channel](/windows-server/get-started/servicing-channels-comparison#semi-annual-channel) releases are currently unsupported at this time. >- Ensure that for Linux versions, Azure Site Recovery doesn't support customized OS images. Only the stock kernels that are part of the distribution minor version release/update are supported. >- Oracle Linux 6.10 isn't supported as a Generation 2 virtual machine on Azure. Generation 2 VM support for Oracle Linux begins with version 7.0 and later. #### Supported kernel versions for Red Hat Enterprise Linux for Azure virtual machines **Release** | **Mobility service version** | **Red Hat kernel version** | --- | --- | --- | RHEL 10.0 <br> RHEL 10.1 | 9.66 | 6.12.0-55.9.1 and later <br> 6.12.0-124.8.1 and later| RHEL 9.8 | 9.67 | [Supported kernels](https://github.com/Azure/Azure-SiteRecovery/tree/main/MobilityAgent/OnPremiseToAzure). RHEL 9.0 <br> RHEL 9.1 <br> RHEL 9.2 <br> RHEL 9.3 <br> RHEL 9.4 <br> RHEL 9.5 <br> RHEL 9.6 <br> RHEL 9.7 | 9.66 | 5.14.0-611.5.1 and later| RHEL 9.0 <br> RHEL 9.1 <br> RHEL 9.2 <br> RHEL 9.3 <br> RHEL 9.4 <br> RHEL 9.5 <br> RHEL 9.6 | 9.65 | 5.14.0-570.12.1 and later | RHEL 9.0 <br> RHEL 9.1 <br> RHEL 9.2 <br> RHEL 9.3 <br> RHEL 9.4 <br> RHEL 9.5 | 9.64 | 5.14.0-503.11.1 and higher. | RHEL 9.0 <br> RHEL 9.1 <br> RHEL 9.2 <br> RHEL 9.3 <br> RHEL 9.4 | 9.63 | 5.14.0-284.73.1.el9_2.x86_64 <br> 5.14.0-284.75.1.el9_2.x86_64 <br>5.14.0-284.77.1.el9_2.x86_64 <br>5.14.0-284.79.1.el9_2.x86_64 <br>5.14.0-284.80.1.el9_2.x86_64 <br>5.14.0-284.82.1.el9_2.x86_64 <br> 5.14.0-284.84.1.el9_2.x86_64 <br>5.14.0-284.85.1.el9_2.x86_64 <br> 5.14.0-284.86.1.el9_2.x86_64 <br> 5.14.0-427.24.1.el9_4.x86_64 <br> 5.14.0-427.26.1.el9_4.x86_64 <br> 5.14.0-427.28.1.el9_4.x86_64 <br> 5.14.0-427.31.1.el9_4.x86_64 <br> 5.14.0-427.33.1.el9_4.x86_64 <br> 5.14.0-427.35.1.el9_4.x86_64 <br> 5.14.0-427.37.1.el9_4.x86_64 | RHEL 9.0 <br> RHEL 9.1 <br> RHEL 9.2 <br> RHEL 9.3 <br> RHEL 9.4 | 9.62 | 5.14.0-70.97.1.el9_0.x86_64 <br> 5.14.0-70.101.1.el9_0.x86_64 <br> 5.14.0-284.62.1.el9_2.x86_64 <br> 5.14.0-284.64.1.el9_2.x86_64 <br> 5.14.0-284.66.1.el9_2.x86_64 <br> 5.14.0-284.67.1.el9_2.x86_64 <br> 5.14.0-284.69.1.el9_2.x86_64 <br> 5.14.0-284.71.1.el9_2.x86_64 <br> 5.14.0-427.13.1.el9_4.x86_64 <br> 5.14.0-427.16.1.el9_4.x86_64 <br> 5.14.0-427.18.1.el9_4.x86_64 <br> 5.14.0-427.20.1.el9_4.x86_64 <br> 5.14.0-427.22.1.el9_4.x86_64 | ### Ubuntu kernel versions **Supported release** | **Mobility service version** | **Kernel version** | --- | --- | --- | 14.04 LTS | 9.66 <br> 9.65 | No new kernels in this release. | 14.04 LTS | 9.62, 9.63, 9.64 | 3.13.0-24-generic to 3.13.0-170-generic,<br/>3.16.0-25-generic to 3.16.0-77-generic,<br/>3.19.0-18-generic to 3.19.0-80-generic,<br/>4.2.0-18-generic to 4.2.0-42-generic,<br/>4.4.0-21-generic to 4.4.0-148-generic,<br/>4.15.0-1023-azure to 4.15.0-1045-azure | ||| 16.04 LTS | 9.66 <br> 9.65 | No new kernels in this release. | 16.04 LTS | 9.62, 9.63, 9.64 | 4.4.0-21-generic to 4.4.0-210-generic,<br/>4.8.0-34-generic to 4.8.0-58-generic,<br/>4.10.0-14-generic to 4.10.0-42-generic,<br/>4.11.0-13-generic, 4.11.0-14-generic,<br/>4.13.0-16-generic to 4.13.0-45-generic,<br/>4.15.0-13-generic to 4.15.0-142-generic<br/>4.11.0-1009-azure to 4.11.0-1016-azure<br/>4.13.0-1005-azure to 4.13.0-1018-azure <br/>4.15.0-1012-azure to 4.15.0-1113-azure </br> 4.15.0-101-generic to 4.15.0-107-generic | ||| 18.04 LTS | 9.66 | 4.15.0-1188-azure <br> 4.15.0-1189-azure <br> 4.15.0-1190-azure <br> 4.15.0-1191-azure <br> 4.15.0-1192-azure <br> 4.15.0-237-generic <br> 4.15.0-238-generic <br> 4.15.0-239-generic <br> 4.15.0-240-generic <br> 4.15.0-241-generic <br> 4.15.0-242-generic <br> 4.15.0-243-generic <br> 4.15.0-245-generic <br> 5.4.0-1150-azure <br> 5.4.0-1151-azure <br> 5.4.0-1152-azure <br> 5.4.0-1153-azure <br> 5.4.0-215-generic <br> 5.4.0-216-generic <br> 5.4.0-218-generic <br> 5.4.0-219-generic <br> 5.4.0-220-generic <br> 5.4.0-221-generic <br> 5.4.0-222-generic <br> 5.4.0-223-generic | 18.04 LTS | 9.65 | 4.15.0-1185-azure <br> 4.15.0-1186-azure <br> 4.15.0-234-generic <br> 4.15.0-235-generic <br> 5.4.0-1143-azure <br> 5.4.0-1144-azure <br> 5.4.0-1145-azure <br> 5.4.0-206-generic <br> 5.4.0-207-generic <br> 5.4.0-209-generic | 18.04 LTS | 9.64 | 4.15.0-1181-azure <br> 4.15.0-1182-azure <br> 4.15.0-1183-azure <br> 4.15.0-1184-azure <br> 4.15.0-229-generic <br> 4.15.0-230-generic <br> 4.15.0-231-generic <br> 4.15.0-232-generic <br> 5.4.0-1137-azure <br> 5.4.0-1138-azure <br> 5.4.0-1139-azure <br> 5.4.0-1140-azure <br> 5.4.0-195-generic <br> 5.4.0-196-generic <br> 5.4.0-198-generic <br> 5.4.0-200-generic <br> 5.4.0-202-generic <br> 5.4.0-204-generic | 18.04 LTS | 9.63 | 4.15.0-1180-azure <br> 4.15.0-228-generic <br> 5.4.0-1136-azure <br> 5.4.0-193-generic | 18.04 LTS | 9.62 | 4.15.0-1178-azure <br>4.15.0-1179-azure <br>4.15.0-226-generic <br> 4.15.0-227-generic <br> 5.4.0-1131-azure <br> 5.4.0-1132-azure <br> 5.4.0-1133-azure <br>5.4.0-1134-azure <br>5.4.0-1135-azure <br> 5.4.0-186-generic <br>5.4.0-187-generic <br> 5.4.0-189-generic <br> 5.4.0-190-generic <br> 5.4.0-192-generic | ||| 20.04 LTS | 9.66 | 5.15.0-1088-azure <br> 5.15.0-1089-azure <br> 5.15.0-1091-azure <br> 5.15.0-1094-azure <br> 5.15.0-1095-azure <br> 5.15.0-1096-azure <br> 5.15.0-1097-azure <br> 5.15.0-1098-azure <br> 5.15.0-139-generic <br> 5.15.0-142-generic <br> 5.15.0-143-generic <br> 5.15.0-144-generic <br> 5.15.0-145-generic <br> 5.15.0-151-generic <br> 5.15.0-152-generic <br> 5.15.0-153-generic <br> 5.15.0-156-generic <br> 5.15.0-157-generic <br> 5.15.0-160-generic <br> 5.15.0-161-generic <br> 5.4.0-1150-azure <br> 5.4.0-1151-azure <br> 5.4.0-1152-azure <br> 5.4.0-1153-azure <br> 5.4.0-1154-azure <br> 5.4.0-215-generic <br> 5.4.0-216-generic <br> 5.4.0-218-generic <br> 5.4.0-219-generic <br> 5.4.0-220-generic <br> 5.4.0-221-generic <br> 5.4.0-222-generic <br> 5.4.0-223-generic | 20.04 LTS | 9.65 | 5.15.0-1080-azure <br> 5.15.0-1081-azure <br> 5.15.0-1083-azure <br> 5.15.0-133-generic <br> 5.15.0-135-generic <br> 5.4.0-1143-azure <br> 5.4.0-1144-azure <br> 5.4.0-1145-azure <br> 5.4.0-206-generic <br> 5.4.0-207-generic <br> 5.4.0-209-generic | 20.04 LTS | 9.64 | 5.15.0-1072-azure <br> 5.15.0-1073-azure <br> 5.15.0-1074-azure <br> 5.15.0-1075-azure <br> 5.15.0-1078-azure <br> 5.15.0-121-generic <br> 5.15.0-122-generic <br> 5.15.0-124-generic <br> 5.15.0-125-generic <br> 5.15.0-126-generic <br> 5.15.0-127-generic <br> 5.15.0-130-generic <br> 5.4.0-1137-azure <br> 5.4.0-1138-azure <br> 5.4.0-1139-azure <br> 5.4.0-1140-azure <br> 5.4.0-1142-azure <br> 5.4.0-195-generic <br> 5.4.0-196-generic <br> 5.4.0-198-generic <br> 5.4.0-200-generic <br> 5.4.0-202-generic <br> 5.4.0-204-generic | 20.04 LTS | 9.63 | 5.15.0-1071-azure <br> 5.15.0-119-generic <br> 5.4.0-1136-azure <br> 5.4.0-193-generic | 20.04 LTS | 9.62 | 5.15.0-1065-azure <br>5.15.0-1067-azure <br>5.15.0-1068-azure <br>5.15.0-1070-azure <br>5.15.0-113-generic <br>5.15.0-116-generic <br>5.15.0-117-generic <br>5.15.0-118-generic <br>5.4.0-1131-azure <br>5.4.0-1132-azure <br>5.4.0-1133-azure <br> 5.4.0-1134-azure <br>5.4.0-1135-azure <br>5.4.0-186-generic <br>5.4.0-187-generic <br>5.4.0-189-generic <br> 5.4.0-190-generic <br> 5.4.0-192-generic | ||| 22.04 LTS | 9.66 | 5.15.0-1088-azure <br> 5.15.0-1089-azure <br> 5.15.0-1090-azure <br> 5.15.0-1091-azure <br> 5.15.0-1092-azure <br> 5.15.0-1094-azure <br> 5.15.0-1095-azure <br> 5.15.0-1096-azure <br> 5.15.0-1097-azure <br> 5.15.0-1098-azure <br> 5.15.0-1099-azure <br> 5.15.0-1101-azure <br> 5.15.0-139-generic <br> 5.15.0-140-generic <br> 5.15.0-141-generic <br> 5.15.0-142-generic <br> 5.15.0-143-generic <br> 5.15.0-144-generic <br> 5.15.0-151-generic <br> 5.15.0-152-generic <br> 5.15.0-153-generic <br> 5.15.0-156-generic <br> 5.15.0-157-generic <br> 5.15.0-160-generic <br> 5.15.0-161-generic <br> 6.8.0-1028-azure <br> 6.8.0-1029-azure <br> 6.8.0-1030-azure <br> 6.8.0-1031-azure <br> 6.8.0-1034-azure <br> 6.8.0-1036-azure <br> 6.8.0-1040-azure <br> 6.8.0-1041-azure <br> 6.8.0-58-generic <br> 6.8.0-59-generic <br> 6.8.0-60-generic <br> 6.8.0-63-generic <br> 6.8.0-64-generic <br> 6.8.0-65-generic <br> 6.8.0-78-generic <br> 6.8.0-79-generic <br> 6.8.0-83-generic <br> 6.8.0-84-generic <br> 6.8.0-85-generic <br> 6.8.0-86-generic <br> 6.8.0-87-generic | 22.04 LTS | 9.65 | 5.15.0-1080-azure <br> 5.15.0-1081-azure <br> 5.15.0-1083-azure <br> 5.15.0-133-generic <br> 5.15.0-135-generic <br> 6.8.0-1022-azure <br> 6.8.0-1023-azure <br> 6.8.0-52-generic <br> 6.8.0-54-generic | 22.04 LTS | 9.64 | 5.15.0-1072-azure <br> 5.15.0-1073-azure <br> 5.15.0-1074-azure <br> 5.15.0-1075-azure <br> 5.15.0-1078-azure <br> 5.15.0-121-generic <br> 5.15.0-122-generic <br> 5.15.0-124-generic <br> 5.15.0-125-generic <br> 5.15.0-126-generic <br> 5.15.0-127-generic <br> 5.15.0-128-generic <br> 5.15.0-130-generic <br> 6.8.0-1008-azure <br> 6.8.0-1009-azure <br> 6.8.0-1010-azure <br> 6.8.0-1012-azure <br> 6.8.0-1013-azure <br> 6.8.0-1014-azure <br> 6.8.0-1015-azure <br> 6.8.0-1017-azure <br> 6.8.0-1018-azure <br> 6.8.0-1020-azure <br> 6.8.0-38-generic <br> 6.8.0-39-generic <br> 6.8.0-40-generic <br> 6.8.0-45-generic <br> 6.8.0-47-generic <br> 6.8.0-48-generic <br> 6.8.0-49-generic <br> 6.8.0-50-generic <br> 6.8.0-51-generic | 22.04 LTS | 9.63 | 5.15.0-1071-azure <br> 5.15.0-119-generic | 22.04 LTS | 9.62 | 5.15.0-1066-azure <br> 5.15.0-1067-azure <br>5.15.0-1068-azure <br>5.15.0-1070-azure <br>5.15.0-112-generic <br>5.15.0-113-generic <br>5.15.0-116-generic <br>5.15.0-117-generic <br>5.15.0-118-generic <br>6.5.0-1022-azure <br>6.5.0-1023-azure <br>6.5.0-1024-azure <br>6.5.0-1025-azure <br>6.5.0-41-generic <br>6.5.0-44-generic <br>6.5.0-45-generic | ||| 24.04 LTS | 9.66 | 6.14.0-1012-azure <br> 6.14.0-1013-azure <br> 6.14.0-1014-azure <br> 6.14.0-24-generic <br> 6.14.0-27-generic <br> 6.14.0-28-generic <br> 6.14.0-29-generic <br> 6.14.0-32-generic <br> 6.14.0-33-generic <br> 6.14.0-34-generic <br> 6.14.0-35-generic <br> 6.14.0-36-generic <br> 6.11.0-1008-azure <br> 6.11.0-1012-azure <br> 6.11.0-1013-azure <br> 6.11.0-1014-azure <br> 6.11.0-1015-azure <br> 6.11.0-1017-azure <br> 6.11.0-1018-azure <br> 6.11.0-17-generic <br> 6.11.0-19-generic <br> 6.11.0-21-generic <br> 6.11.0-24-generic <br> 6.11.0-25-generic <br> 6.11.0-26-generic <br> 6.11.0-28-generic <br> 6.11.0-29-generic <br> 6.8.0-1028-azure <br> 6.8.0-1029-azure <br> 6.8.0-1030-azure <br> 6.8.0-1031-azure <br> 6.8.0-1034-azure <br> 6.8.0-59-generic <br> 6.8.0-60-generic <br> 6.8.0-63-generic <br> 6.8.0-64-generic <br> 6.8.0-71-generic <br> 6.8.0-78-generic <br> 6.8.0-79-generic <br> 6.8.0-83-generic <br> 6.8.0-84-generic <br> 6.8.0-85-generic <br> 6.8.0-86-generic <br> 6.8.0-87-generic <br> 6.8.0-88-generic | 24.04 LTS | 9.65 | 6.8.0-1022-azure <br> 6.8.0-1023-azure <br> 6.8.0-52-generic <br> 6.8.0-54-generic | 24.04 LTS | 9.64 | 6.8.0-1007-azure <br> 6.8.0-1008-azure <br> 6.8.0-1009-azure <br> 6.8.0-1010-azure <br> 6.8.0-1012-azure <br> 6.8.0-1013-azure <br> 6.8.0-1014-azure <br> 6.8.0-1015-azure <br> 6.8.0-1016-azure <br> 6.8.0-1017-azure <br> 6.8.0-1018-azure <br> 6.8.0-1020-azure <br> 6.8.0-31-generic <br> 6.8.0-35-generic <br> 6.8.0-36-generic <br> 6.8.0-38-generic <br> 6.8.0-39-generic <br> 6.8.0-40-generic <br> 6.8.0-41-generic <br> 6.8.0-44-generic <br> 6.8.0-45-generic <br> 6.8.0-47-generic <br> 6.8.0-48-generic <br> 6.8.0-49-generic <br> 6.8.0-50-generic <br> 6.8.0-51-generic | ### Debian kernel versions **Supported release** | **Mobility service version** | **Kernel version** | --- | --- | --- | Debian 7 | 9.66 | No new Debian kernels in this release. | Debian 7 | 9.65 | No new Debian kernels in this release. | Debian 7 | 9.62, 9.63, 9.64 | 3.2.0-4-amd64 to 3.2.0-6-amd64, 3.16.0-0.bpo.4-amd64 | ||| Debian 8 | 9.66 | No new Debian kernels in this release. | Debian 8 | 9.65 | No new Debian kernels in this release. | Debian 8 | 9.62, 9.63, 9.64 | 3.16.0-4-amd64 to 3.16.0-11-amd64, 4.9.0-0.bpo.4-amd64 to 4.9.0-0.bpo.12-amd64 | ||| Debian 9.1 | 9.66 | No new Debian kernels in this release. | Debian 9.1 | 9.65 | No new Debian kernels in this release. | Debian 9.1 | 9.64 | No new Debian 9.1 kernels supported in this release. | Debian 9.1 | 9.63 | No new Debian 9.1 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 kernels in this release. | Debian 10 | 9.65 | No new Debian kernels in this release. | Debian 10 | 9.64 | No new Debian kernels in this release. | Debian 10 | 9.63 | No new Debian kernels in this release. | Debian 10 | 9.62 | 4.19.0-27-amd64 <br> 4.19.0-27-cloud-amd64 <br> 5.10.0-0.deb10.30-amd64 <br> 5.10.0-0.deb10.30-cloud-amd64 | ||| Debian 11 | 9.66 | 5.10.0-35-amd64 <br> 5.10.0-35-cloud-amd64 <br> 5.10.0-36-amd64 <br> 5.10.0-36-cloud-amd64 <br> 6.1.0-0.deb11.35-amd64 <br> 6.1.0-0.deb11.35-cloud-amd64 <br> 6.1.0-0.deb11.37-amd64 <br> 6.1.0-0.deb11.37-cloud-amd64 <br> 6.1.0-0.deb11.38-amd64 <br> 6.1.0-0.deb11.38-cloud-amd64 <br> 6.1.0-0.deb11.39-amd64 <br> 6.1.0-0.deb11.39-cloud-amd64 <br> 6.1.0-0.deb11.40-amd64 <br> 6.1.0-0.deb11.40-cloud-amd64 <br> 6.1.0-0.deb11.41-amd64 <br> 6.1.0-0.deb11.41-cloud-amd64 | Debian 11 | 9.65 | 6.1.0-0.deb11.32-amd64 <br> 6.1.0-0.deb11.32-cloud-amd64 | Debian 11 | 9.64 | 5.10.0-33-amd64 <br> 5.10.0-33-cloud-amd64 <br> 6.1.0-0.deb11.25-amd64 <br> 6.1.0-0.deb11.25-cloud-amd64 <br> 6.1.0-0.deb11.26-amd64 <br> 6.1.0-0.deb11.26-cloud-amd64 <br> 6.1.0-0.deb11.28-amd64 <br> 6.1.0-0.deb11.28-cloud-amd64 | Debian 11 | 9.63 | No new Debian kernels in this release. | Debian 11 | 9.62 | **Debian 11 kernels support added for Modernized experience:** <br> 5.10.0-30-amd64 <br> 5.10.0-30-cloud-amd64 <br> 6.1.0-0.deb11.21-amd64 <br> 6.1.0-0.deb11.21-cloud-amd64 <br> 5.10.0-31-amd64 <br> 5.10.0-31-cloud-amd64 <br> 5.10.0-32-amd64 <br> 5.10.0-32-cloud-amd64 <br> 6.1.0-0.deb11.13-amd64 <br> 6.1.0-0.deb11.13-cloud-amd64 <br> 6.1.0-0.deb11.17-amd64 <br> 6.1.0-0.deb11.17-cloud-amd64 <br> 6.1.0-0.deb11.18-amd64 <br> 6.1.0-0.deb11.18-cloud-amd64 <br> 6.1.0-0.deb11.21-amd64 <br> 6.1.0-0.deb11.21-cloud-amd64 <br> 6.1.0-0.deb11.22-amd64 <br> 6.1.0-0.deb11.22-cloud-amd64 | Debian 12 | 9.66 | 6.1.0-34-amd64 <br> 6.1.0-34-cloud-amd64 <br> 6.1.0-35-amd64 <br> 6.1.0-35-cloud-amd64 <br> 6.1.0-37-amd64 <br> 6.1.0-37-cloud-amd64 <br> 6.1.0-38-amd64 <br> 6.1.0-38-cloud-amd64 <br> 6.1.0-39-amd64 <br> 6.1.0-39-cloud-amd64 <br> 6.1.0-40-amd64 <br> 6.1.0-40-cloud-amd64 <br> 6.1.0-41-amd64 <br> 6.1.0-41-cloud-amd64 | Debian 12 | 9.65 | 6.1.0-32-amd64 <br> 6.1.0-32-cloud-amd64 <br> 6.1.0-33-amd64 <br> 6.1.0-33-cloud-amd64 | Debian 12 | 9.64 | 6.1.0-15-cloud-amd64 <br> 6.1.0-26-amd64 <br> 6.1.0-26-cloud-amd64 <br> 6.1.0-27-amd64 <br> 6.1.0-27-cloud-amd64 <br> 6.1.0-28-amd64 <br> 6.1.0-28-cloud-amd64 | Debian 12 | 9.63 | 6.1.0-25-amd64 <br> 6.1.0-25-cloud-amd64 | Debian 12 | 9.62 | 6.1.0-15-cloud-amd64 <br> 6.1.0-22-amd64 <br> 6.1.0-22-cloud-amd64 <br> 6.1.0-23-amd64 <br> 6.1.0-23-cloud-amd64 | ### SUSE Linux Enterprise Server 12 supported kernel versions **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 | By default, all [stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported. <br> 4.12.14-16.197-azure:5 <br> 4.12.14-16.200-azure:5 | SUSE Linux Enterprise Server 12, SP1, SP2, SP3, SP4, SP5 | 9.64 | By default, all [stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported.</br> 4.12.14-16.197-azure:5 <br> 4.12.14-16.200-azure:5 | SUSE Linux Enterprise Server 12, SP1, SP2, SP3, SP4, SP5 | 9.63 | By default, all [stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported.</br> No new kernels in this release. | SUSE Linux Enterprise Server 12, SP1, SP2, SP3, SP4, SP5 | 9.62 | By default, all [stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported.</br> **SUSE 12 Azure kernels support added for Modernized experience:** <br> 4.12.14-16.185-azure:5 <br> 4.12.14-16.188-azure:5 <br> 4.12.14-16.191azure:5 <br> 4.12.14-16.194-azure:5 | ### SUSE Linux Enterprise Server 15 supported kernel versions **Release** | **Mobility service version** | **Kernel version** | --- | --- | --- | SUSE Linux Enterprise Server 15, SP1, SP2, SP3, SP4, SP5, SP6, SP7 | 9.66 | By default, all [stock SUSE 15 SP1, SP2, SP3, SP4, SP5, SP6, SP7 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported. <br> 6.4.0-150600.8.37-azure:6 <br> 6.4.0-150600.8.40-azure:6 <br> 6.4.0-150600.8.43-azure:6 <br> 6.4.0-150600.8.48-azure:6 <br> 6.4.0-150600.8.52-azure:6 <br> 6.4.0-150700.18-azure:7 <br> 6.4.0-150700.20.11-azure:7 <br> 6.4.0-150700.20.3-azure:7 <br> 6.4.0-150700.20.6-azure:7 <br> 6.4.0-150700.20.15-azure:7 <br> 6.4.0-150700.20.18-azure:7 | SUSE Linux Enterprise Server 15, SP1, SP2, SP3, SP4, SP5, SP6 | 9.65 | By default, all [stock SUSE 15 SP1, SP2, SP3, SP4, SP5, SP6 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported. <br> 6.4.0-150600.8.23-azure:6 <br> 6.4.0-150600.8.26-azure:6 <br> 6.4.0-150600.8.31-azure:6 <br> 6.4.0-150600.8.34-azure:6 | SUSE Linux Enterprise Server 15, SP1, SP2, SP3, SP4, SP5 | 9.64 | By default, all [stock SUSE 15 SP1, SP2, SP3, SP4, SP5, SP6 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported.</br> 5.14.21-150500.33.66-azure:5 <br> 5.14.21-150500.33.69-azure:5 <br> 5.14.21-150500.33.72-azure:5 <br> 5.14.21-150500.33.75-azure:5 <br> 6.4.0-150600.6-azure:6 <br> 6.4.0-150600.8.11-azure:6 <br> 6.4.0-150600.8.14-azure:6 <br> 6.4.0-150600.8.17-azure:6 <br> 6.4.0-150600.8.20-azure:6 <br> 6.4.0-150600.8.5-azure:6 <br> 6.4.0-150600.8.8-azure:6 | SUSE Linux Enterprise Server 15, SP1, SP2, SP3, SP4, SP5 | 9.63 | By default, all [stock SUSE 15 SP1, SP2, SP3, SP4, SP5, SP6 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported.</br> No new kernels in this release. | SUSE Linux Enterprise Server 15, SP1, SP2, SP3, SP4, SP5 | 9.62 | By default, all [stock SUSE 15 SP1, SP2, SP3, SP4, SP5 kernels](https://www.suse.com/support/kb/doc/?id=000019587) are supported.</br> **SUSE 15 Azure kernels support added for Modernized experience:** <br> 5.14.21-150500.33.54-azure:5 <br> 5.14.21-150500.33.57-azure:5 <br> 5.14.21-150500.33.60-azure:5 <br> 5.14.21-150500.33.63-azure:5 | #### Supported Red Hat Linux kernel versions for Oracle Linux on Azure virtual machines **Release** | **Mobility service version** | **Red Hat kernel version** | --- | --- | --- | Oracle Linux 10.0 | 9.66 | 6.12.0-55.9.1 and later Oracle Linux 9.0 <br> Oracle Linux 9.1 <br> Oracle Linux 9.2 <br> Oracle Linux 9.3 <br> Oracle Linux 9.4 <br> Oracle Linux 9.5 <br> Oracle Linux 9.6 | 9.66 | 5.14.0-503.11.1 and later | Oracle Linux 9.0 <br> Oracle Linux 9.1 <br> Oracle Linux 9.2 <br> Oracle Linux 9.3 <br> Oracle Linux 9.4 <br> Oracle Linux 9.5 | 9.65 | 5.14.0-503.11.1 and later | Oracle Linux 9.0 <br> Oracle Linux 9.1 <br> Oracle Linux 9.2 <br> Oracle Linux 9.3 <br> Oracle Linux 9.4 | 9.64 | No new kernels in this release.| Oracle Linux 9.0 <br> Oracle Linux 9.1 <br> Oracle Linux 9.2 <br> Oracle Linux 9.3 <br> Oracle Linux 9.4 | 9.63 | 5.14.0-284.73.1.el9_2.x86_64 <br> 5.14.0-284.75.1.el9_2.x86_64 <br> 5.14.0-284.77.1.el9_2.x86_64 <br> 5.14.0-284.79.1.el9_2.x86_64 <br> 5.14.0-284.80.1.el9_2.x86_64 <br> 5.14.0-284.82.1.el9_2.x86_64 <br> 5.14.0-284.84.1.el9_2.x86_64 <br> 5.14.0-284.85.1.el9_2.x86_64 <br> 5.14.0-284.86.1.el9_2.x86_64 <br> 5.14.0-427.13.1.el9_4.x86_64 <br> 5.14.0-427.16.1.el9_4.x86_64 <br> 5.14.0-427.18.1.el9_4.x86_64 <br> 5.14.0-427.20.1.el9_4.x86_64 <br> 5.14.0-427.22.1.el9_4.x86_64 <br>5.14.0-427.24.1.el9_4.x86_64 <br> 5.14.0-427.26.1.el9_4.x86_64 <br> 5.14.0-427.28.1.el9_4.x86_64 <br> 5.14.0-427.31.1.el9_4.x86_64 <br> 5.14.0-427.33.1.el9_4.x86_64 <br> 5.14.0-427.35.1.el9_4.x86_64 <br> 5.14.0-427.37.1.el9_4.x86_64 | Oracle Linux 9.0 <br> Oracle Linux 9.1 <br> Oracle Linux 9.2 <br> Oracle Linux 9.3 | 9.62 | 5.14.0-70.97.1.el9_0.x86_64 <br> 5.14.0-70.101.1.el9_0.x86_64 <br> 5.14.0-284.62.1.el9_2.x86_64 <br> 5.14.0-284.64.1.el9_2.x86_64 <br> 5.14.0-284.66.1.el9_2.x86_64 <br> 5.14.0-284.67.1.el9_2.x86_64 <br> 5.14.0-284.69.1.el9_2.x86_64 <br> 5.14.0-284.71.1.el9_2.x86_64 | ### Rocky Linux Server supported kernel versions **Release** | **Mobility service version** | **Red Hat kernel version** | --- | --- | --- | Rocky Linux 10.0 <br> Rocky Linux 10.1 | 9.66 | 6.12.0-55.9.1 and later <br> 6.12.0-124.8.1 and later | Rocky Linux 9.0 <br> Rocky Linux 9.1 <br> Rocky Linux 9.2 <br> Rocky Linux 9.3 <br> Rocky Linux 9.4 <br> Rocky Linux 9.5 <br> Rocky linux 9.6 <br> Rocky linux 9.7 | 9.66 | 5.14.0-611.5.1 and later | Rocky Linux 9.0 <br> Rocky Linux 9.1 <br> Rocky Linux 9.2 <br> Rocky Linux 9.3 <br> Rocky Linux 9.4 <br> Rocky Linux 9.5 | 9.65 | 5.14.0-70.97.1.el9_0.x86_64 <br> 5.14.0-70.101.1.el9_0.x86_64 <br> 5.14.0-284.62.1.el9_2.x86_64 <br> 5.14.0-284.64.1.el9_2.x86_64 <br> 5.14.0-284.66.1.el9_2.x86_64 <br> 5.14.0-284.67.1.el9_2.x86_64 <br> 5.14.0-284.69.1.el9_2.x86_64 <br> 5.14.0-284.71.1.el9_2.x86_64 <br> 5.14.0-427.13.1.el9_4.x86_64 <br> 5.14.0-427.16.1.el9_4.x86_64 <br> 5.14.0-427.18.1.el9_4.x86_64 <br> 5.14.0-427.20.1.el9_4.x86_64 <br> 5.14.0-427.22.1.el9_4.x86_64 | Rocky Linux 9.0 <br> Rocky Linux 9.1 | 9.64 | No new kernels in this release. | Rocky Linux 9.0 <br> Rocky Linux 9.1 | 9.63 | No new kernels in this release. | Rocky Linux 9.0 <br> Rocky Linux 9.1 | 9.62 | 5.14.0-70.97.1.el9_0.x86_64 <br> 5.14.0-70.101.1.el9_0.x86_64 <br> 5.14.0-284.62.1.el9_2.x86_64 <br> 5.14.0-284.64.1.el9_2.x86_64 <br> 5.14.0-284.66.1.el9_2.x86_64 <br> 5.14.0-284.67.1.el9_2.x86_64<br> 5.14.0-284.69.1.el9_2.x86_64<br> 5.14.0-284.71.1.el9_2.x86_64<br> 5.14.0-427.13.1.el9_4.x86_64<br> 5.14.0-427.16.1.el9_4.x86_64<br> 5.14.0-427.18.1.el9_4.x86_64<br> 5.14.0-427.20.1.el9_4.x86_64<br> 5.14.0-427.22.1.el9_4.x86_64 | ## Linux file systems/guest storage **Component** | **Supported** --- | --- File systems | Supported root file systems are ext3, ext4, XFS, and BTRFS. A separate `/boot` file system can also use ext2. Logical volume management (LVM) provisioning| Thick provision - Yes <br></br> Thin provision - Yes, it's supported from [Update Rollup 61](https://support.microsoft.com/topic/update-rollup-61-for-azure-site-recovery-kb5012960-a1cc029b-03ad-446f-9365-a00b41025d39) onwards. Earlier Mobility service versions don't support it. Volume manager | - LVM is supported. If the root file system is on LVM, install the `lvm2` package and ensure that `vgdisplay` is available before enabling replication.<br/> - /boot on LVM is supported from [Update Rollup 31](https://support.microsoft.com/help/4478871/) (version 9.20 of the Mobility service) onwards. Earlier Mobility service versions don't support it.<br/> - `/boot` on an LVM logical volume that spans more than one physical disk isn't supported.<br/> - Multiple OS disks aren't supported. Paravirtualized storage devices | Devices exported by paravirtualized drivers aren't supported. <br><br> Supported only for VMware and not for AWS (Physical). Multi-queue block IO devices | Not supported. Physical servers with the HP CCISS storage controller | Not supported. Device/Mount point naming convention | Device name or mount point name should be unique.<br/> Ensure that no two devices/mount points have case-sensitive names. For example, naming devices for the same VM as *device1* and *Device1* isn't supported. Directories | If you're running a version of the Mobility service earlier than version 9.20 (released in [Update Rollup 31](https://support.microsoft.com/help/4478871/)), then these restrictions apply:<br/><br/> - These directories (if set up as separate partitions/file-systems) must be on the same OS disk on the source server: /(root), /boot, /usr, /usr/local, /var, /etc.</br> - The /boot directory should be on a disk partition and not be an LVM volume. Boot directory | Boot disks with GPT partition format are supported. GPT disks are also supported as data disks.<br/><br/> Multiple boot disks on a VM aren't supported.<br/><br/> - /boot on an LVM volume across more than one disk isn't supported.<br/> - A machine without a boot disk can't be replicated. Free space requirements | The installer enforces at least 1 GiB free on the root file system. Keep 2 GB free as the recommended operational minimum.<br/><br/>Keep at least 600 MB free in the installation folder. XFSv5 | XFSv5 features on XFS file systems, such as metadata checksum, are supported (Mobility service version 9.10 onwards).<br/> Use the xfs_info utility to check the XFS superblock for the partition. If `ftype` is set to 1, then XFSv5 features are in use. BTRFS | Supported only when the file system is backed by one disk. Multi-device, spanned, or RAID BTRFS file systems aren't supported. Oracle Grid with Automatic Storage Management | BTRFS is supported from [Update Rollup 34](https://support.microsoft.com/help/4490016) (version 9.22 of the Mobility service) onwards. BTRFS isn't supported if:<br/><br/> - The BTRFS file system subvolume is changed after enabling protection.</br> - The BTRFS file system is spread over multiple disks.</br> - The BTRFS file system supports RAID. ## VM/Disk management **Action** | **Details** --- | --- Resize disk on replicated VM | You can resize up on the source VM. Resizing down on the source VM isn't supported. Resize the disk before failover, directly in the VM properties. You don't need to disable or re-enable replication.<br/><br/> If you change the source VM after failover, the changes aren't captured.<br/><br/> If you change the disk size on the Azure VM after failover, when you fail back, Site Recovery creates a new VM with the updates. Add disk on replicated VM | Supported.<br/> You can manually enable replication on a disk added after a VMware VM is protected. [Learn more](vmware-azure-enable-replication-added-disk.md). Remove disk from replicated VM | Not supported. Disable replication, remove the disk, and then enable replication again for the updated disk configuration. Exclude disk before replicating VM | Supported for VMware machines. <br/><br/> Not supported for Physical machines, if using modernized experience. > [!NOTE] > - Any change to disk identity isn't supported. For example, if you change the disk partitioning from GPT to MBR or vice versa, the disk identity changes. In this scenario, the replication breaks and requires a fresh setup. > - For Linux machines, device name change isn't supported as it impacts the disk identity. > - In Modernized, resizing the disk size to reduce it from its original size isn't supported. ## Network **Component** | **Supported** --- | --- Host network NIC Teaming | Supported for VMware VMs and physical machine replication. Host network VLAN | Yes. Host network IPv4 | Yes. Host network IPv6 | No. Guest/server network NIC Teaming | No. Guest/server network IPv4 | Yes. Guest/server network IPv6 | No. Guest/server network static IP (Windows) | Yes. Guest/server network static IP (Linux) | Yes. <br/><br/>VMs are configured to use DHCP on failback. Guest/server network multiple NICs | Yes. Private link access to Site Recovery service | Yes. [Learn more](hybrid-how-to-enable-replication-private-endpoints.md). > [!NOTE] > VMs must allow TCP 443 for control-channel orchestration and TCP 9443 for data transport to the appliance, unless the data-transport port was customized. > > Select a regular workload subnet for recovery. `GatewaySubnet` and `AzureFirewallSubnet` aren't supported as recovery subnets. For VMware storage-based mapping, `AzureBastionSubnet`, `RouteServerSubnet`, delegated subnets, and subnets used by external resources also aren't supported. ## Azure VM network (after failover) **Component** | **Supported** --- | --- Azure ExpressRoute | Yes ILB | Yes ELB | Yes Azure Traffic Manager | Yes Multi-NIC | Yes Reserved IP address | Yes IPv4 | Yes Retain source IP address | Yes Azure virtual network service endpoints<br/> | Yes Accelerated networking | No ## Storage **Component** | **Supported** --- | --- Dynamic disk | OS disk must be a basic disk. <br/><br/>Data disks can be dynamic disks. <br><br> Data disks can be spanned volumes. Docker disk configuration | No Host NFS | Yes for VMware<br/><br/> No for physical servers Host SAN (iSCSI/FC) | Yes Host vSAN | Yes for VMware<br/><br/> N/A for physical servers Host multipath (MPIO) | Yes, tested with Microsoft DSM, EMC PowerPath 5.7 SP4, EMC PowerPath DSM for CLARiiON Host Virtual Volumes (VVols) | Yes for VMware<br/><br/> N/A for physical servers. <br> Failback and Reprotect isn't supported. Guest/server VMDK | Yes Guest/server shared cluster disk | No Guest/server encrypted disk | No FIPS encryption | No Guest/server NFS | No Guest/server iSCSI | Included only for forward migration to Azure when the machine is protected by using the physical-machine workflow.<br/>Not supported for disaster recovery, Azure-to-on-premises failback, or Azure-to-Azure protection. Guest/server SMB 3.0 | No Guest/server RDM | Yes<br/><br/> However, when failing back such VMs from Azure to on-premises VMware, the RDM disks attach as more disks. <br> N/A for physical servers Guest/server disk > 1 GB | Yes, disk must be larger than 1,024 MB.<br/><br/>Up to 32,767 GiB (approximately 32 TiB) when replicating to managed disk (version 9.41 onwards).<br></br> Up to 4,095 GiB when replicating to storage accounts. Guest/server disk with 512-byte logical sectors | Supported for 512n and 512e disks, subject to the other disk requirements in this matrix. Guest/server disk with 4-KiB logical sectors | Not supported, whether the physical sector size is 4 KiB (4Kn) or 512 bytes. This restriction applies to both OS and data disks. Guest/server volume with striped disk >4 TB | Yes Logical volume management (LVM)| Thick provisioning - Yes <br></br> Thin provisioning - Yes, it's supported from [Update Rollup 61](https://support.microsoft.com/topic/update-rollup-61-for-azure-site-recovery-kb5012960-a1cc029b-03ad-446f-9365-a00b41025d39) onwards. It wasn't supported in earlier Mobility service versions. Guest/server - Storage Spaces | No Guest/server - NVMe interface | Yes, for Windows machines. Not supported for Linux machines. Guest/server hot add | Yes Guest/server - remove disk | No Guest/server - exclude disk | Yes Guest/server multipath (MPIO) | No ReFS | Resilient File System is supported with Mobility service version 9.23 or higher Guest/server EFI/UEFI boot | - Site Recovery uses the discovered BIOS or EFI firmware and guest boot layout to determine the recovery VM generation.<br/> - Windows UEFI protection requires Windows 8 or Windows Server 2012 or later, with the boot and system partitions on the same disk. The `atapi`, `vmbus`, `storflt`, `storvsc`, and `intelide` boot-driver services must be available.<br/> - Secure Boot is supported for Windows 10, Windows 11, and Windows Server 2016 or later. Disable Secure Boot for earlier Windows versions and for Linux machines.<br/> - Validate the operating system and boot layout before changing generation-conversion behavior. Storage vMotion | Supported for migration. Not supported for disaster recovery. BIOS | Supported. > [!NOTE] > Older non-storage-based VMware mapping is deprecated and blocked for new production operations. Use storage-based mapping or the modernized protection architecture. ## Replication channels |**Type of replication** |**Supported** | |---------|---------| |Offloaded Data Transfers (ODX) | No | |Offline Seeding | No | | Azure Data Box | No ## Azure storage **Component** | **Supported** --- | --- Locally redundant storage | Yes Geo-redundant storage | Yes Read-access geo-redundant storage | Yes Cool storage | No Hot storage| No Block blobs | No Encryption at host | No Encryption at rest (SSE)| Yes Encryption at rest (CMK)| Yes (via PowerShell Az 3.3.0 module onwards) Double Encryption at rest | Yes (via PowerShell Az 3.3.0 module onwards). Learn more on supported regions for [Windows](/azure/virtual-machines/disk-encryption) and [Linux](/azure/virtual-machines/disk-encryption). Premium storage | Yes Standard HDD LRS recovery disk | Supported for OS and data disks, subject to size and VM requirements. Standard SSD LRS recovery disk | Supported for OS and data disks, subject to size and VM requirements. Standard SSD ZRS recovery disk | Supported with modernized protection when the target region supports ZRS and the placement configuration is compatible. Premium SSD v1 LRS recovery disk | Supported for OS and data disks, subject to size and VM requirements. Premium SSD v1 ZRS recovery disk | Supported with modernized protection when the target region supports ZRS and the placement configuration is compatible. Premium SSD v2 and Ultra Disk source and recovery disks | Not supported for on-premises-to-Azure protection as source or recovery-target disk types. Performance Plus and shared recovery disks | Not supported. Secure transfer option | Yes Import/export service | No Azure Storage firewalls for VNets | Yes.<br/> Configured on target storage/cache storage account (used to store replication data). General-purpose v2 storage accounts (hot and cool tiers) | Yes (Transaction costs are substantially higher for V2 compared to V1) Soft delete | Not supported. Disk subscription limits | Up to 3,000 protected disks per subscription. Ensure that the target subscription doesn't have more than 3000 Azure Site Recovery-protected Disks (Both Data and OS). Notating hierarchical namespace | Not supported. ## Azure compute **Feature** | **Supported** --- | --- Availability sets | Yes Proximity Placement Groups | Yes Availability zones | Supported with modernized protection when the target region, subscription, disk type, and VM size support the selected zone. An availability set and availability zone can't be configured together. Secure VM target types | Trusted Launch and Confidential VM conversion are supported only for designated migration scenarios. They aren't supported as recovery targets for VMware or physical disaster recovery. HUB | Yes Managed disks | Yes ## Azure VM requirements On-premises VMs replicated to Azure must meet the Azure VM requirements summarized in this table. When Site Recovery runs prerequisites check for replication, the check fails if some of the requirements aren't met. **Component** | **Requirements** | **Details** --- | --- | --- Guest operating system | Verify [supported operating systems](#replicated-machines) for replicated machines. | Check fails if unsupported. Guest operating system architecture | 64-bit. | Check fails if unsupported. Operating system disk size | Up to 2,048 GB for Generation 1 machines. <br> Up to 4,095 GB for Generation 2 machines. | Check fails if unsupported. Operating system disk count | 1 </br> boot and system partition on different disks isn't supported | Check fails if unsupported. Data disk count | Up to 64 data disks, using LUNs 0 through 63. | The selected target VM size can impose a lower limit. The number of supported disks can also be reduced when the logical-volume metadata is large. In such scenarios, use the formula to calculate the maximum supported count of data disks. </br></br> If all disks share a logical volume: </br></br> D < 627790 / (450 + (Count of Logical Volume * 317))</br></br> If logical volume shared by disks is varying: </br></br> D < (627790 - (Count of times Logical Volume is repeated * Count of Logical Volume * 317)) / 450 </br></br> Here **D** is the maximum count of data disks that can be protected. Data disk size | From 1 GiB through 32,767 GiB (approximately 32 TiB) when replicating to managed disk (version 9.41 onwards).<br> Up to 4,095 GiB when replicating to a storage account.</br> Each premium storage account can host up to 35 TB of data. | Check fails if unsupported. RAM | Site Recovery driver consumes 6% of RAM. Network adapters | Multiple adapters are supported. | Shared VHD | Not supported. | Check fails if unsupported. FC disk | Not supported. | Check fails if unsupported. BitLocker | Not supported. | BitLocker must be disabled before you enable replication for a machine and should stay disabled while the machine is replicating via Site Recovery. | VM name | From 1 to 63 characters.<br/><br/> Restricted to letters, numbers, and hyphens.<br/><br/> The machine name must start and end with a letter or number. | Update the value in the machine properties in Site Recovery. ## Resource group limits To understand the number of virtual machines that you can protect under a single resource group, see [subscription limits and quotas](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-resource-group-limits). ## Churn limits The following table provides the Azure Site Recovery limits. - These limits are based on tests, but they don't cover all possible app I/O combinations. - Actual results can vary based on your application I/O mix. - For best results, run the [Deployment Planner tool](site-recovery-deployment-planner.md), and perform extensive application testing by using test failovers to get the true performance picture for your app. **Replication target** | **Average source disk I/O size** |**Average source disk data churn** | **Total source disk data churn per day** ---|---|---|--- Standard storage | 8 KB | 2 MB/s | 168 GB per disk Premium P10 or P15 disk | 8 KB | 2 MB/s | 168 GB per disk Premium P10 or P15 disk | 16 KB | 4 MB/s | 336 GB per disk Premium P10 or P15 disk | 32 KB or greater | 8 MB/s | 672 GB per disk Premium P20 or P30 or P40 or P50 disk | 8 KB | 5 MB/s | 421 GB per disk Premium P20 or P30 or P40 or P50 disk | 16 KB or greater |20 MB/s | 1,684 GB per disk **Source data churn** | **Maximum Limit** ---|--- Peak data churn across all disks on a VM | 54 MB/s Maximum data churn per day supported by a Process Server | 2 TB - These numbers are averages assuming a 30 percent I/O overlap. - The 54-MB/s value is the aggregate VM limit, not a per-disk limit. Per-disk limits are listed in the preceding table and depend on disk tier and average write size. - Site Recovery can handle higher throughput based on overlap ratio, larger write sizes, and actual workload I/O behavior. - These numbers assume a typical backlog of approximately five minutes. That is, after data is uploaded, it's processed and a recovery point is created within five minutes. ## Cache storage account This table summarizes support for the cache storage account that Site Recovery uses during replication. **Setting** | **Support** | **Details** --- | --- | --- General purpose V2 storage accounts | Supported | Site Recovery is transaction-intensive. A general-purpose v1 account might be more cost-effective. Soft delete | Not supported | Soft delete isn't supported because it increases cost when enabled on the cache storage account. Azure Site Recovery frequently creates and deletes log files during replication, which increases costs. As average churn on the disks increases, the number of disks that a storage account can support decreases. Use the following table as a guide for deciding how many storage accounts to provision. **Storage account type** | **Churn = 4 MBps per disk** | **Churn = 8 MBps per disk** --- | --- | --- V1 storage account | 600 disks | 300 disks V2 storage account | 1,500 disks | 750 disks These limits apply to VMware and Hyper-V scenarios only. ## Vault tasks **Action** | **Supported** --- | --- Move vault across resource groups | No Move vault within and across subscriptions | No Move storage, network, and Azure VMs across resource groups | No Move storage, network, and Azure VMs within and across subscriptions | No ## Obtain latest components **Name** | **Description** | **Details** --- | --- | --- Configuration server | Installed on-premises.<br/> Coordinates communications between on-premises VMware servers or physical machines, and Azure. | - [Learn about](vmware-azure-deploy-configuration-server.md) the configuration server.<br/> - [Learn about](vmware-azure-manage-configuration-server.md#upgrade-the-configuration-server) upgrading to the latest version.<br/> - [Learn about](vmware-azure-deploy-configuration-server.md) setting up the configuration server. Process server | Installed by default on the configuration server.<br/> Receives replication data, optimizes it with caching, compression, and encryption, and sends it to Azure.<br/> As your deployment grows, you can add more process servers to handle larger volumes of replication traffic. | - [Learn about](vmware-azure-manage-process-server.md) the process server.<br/> - [Learn about](vmware-azure-manage-process-server.md#upgrade-a-process-server) upgrading to the latest version.<br/> - [Learn about](vmware-physical-large-deployment.md#set-up-a-process-server) setting up scale-out process servers. Mobility Service | Installed on VMware VM or physical servers you want to replicate.<br/> Coordinates replication between on-premises VMware servers/physical servers and Azure.| - [Learn about](vmware-physical-mobility-service-overview.md) the Mobility service.<br/> - [Learn about](vmware-physical-manage-mobility-service.md#update-mobility-service-from-azure-portal) upgrading to the latest version.<br/> ## Next steps [Learn how](tutorial-prepare-azure.md) to prepare Azure for disaster recovery of VMware VMs. [9.32 UR]: https://support.microsoft.com/en-in/help/4538187/update-rollup-44-for-azure-site-recovery [9.31 UR]: https://support.microsoft.com/en-in/help/4537047/update-rollup-43-for-azure-site-recovery [9.30 UR]: https://support.microsoft.com/en-in/help/4531426/update-rollup-42-for-azure-site-recovery [9.29 UR]: https://support.microsoft.com/en-in/help/4528026/update-rollup-41-for-azure-site-recovery [9.28 UR]: https://support.microsoft.com/en-in/help/4521530/update-rollup-40-for-azure-site-recovery [9.27 UR]: https://support.microsoft.com/en-in/help/4517283/update-rollup-39-for-azure-site-recovery [9.26 UR]: https://support.microsoft.com/en-in/help/4513507/update-rollup-38-for-azure-site-recovery [9.25 UR]: https://support.microsoft.com/en-in/help/4508614/update-rollup-37-for-azure-site-recovery [9.24 UR]: https://support.microsoft.com/en-in/help/4503156 [9.23 UR]: https://support.microsoft.com/en-in/help/4494485/update-rollup-35-for-azure-site-recovery [9.22 UR]: https://support.microsoft.com/help/4489582/update-rollup-33-for-azure-site-recovery [9.21 UR]: https://support.microsoft.com/help/4485985/update-rollup-32-for-azure-site-recovery [9.20 UR]: https://support.microsoft.com/help/4478871/update-rollup-31-for-azure-site-recovery [9.19 UR]: https://support.microsoft.com/help/4468181/azure-site-recovery-update-rollup-30 [9.18 UR]: https://support.microsoft.com/help/4466466/update-rollup-29-for-azure-site-recovery