Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The following content is for customers running existing Virtual Machine (VM) Sizes using Accelerated Networking.
Important
For timelines pertaining to VM series running on MANA-capable hardware, see the announcement.
Existing VM series are supported on Azure Network Adapter (MANA) capable hardware. However, since these VM series were introduced before MANA was released, they may not fully benefit from all performance, reliability, and resiliency improvements.
Newer VM series are built and optimized with MANA in mind and are designed to take full advantage of its performance, reliability, and resiliency improvements. For this reason, it is recommended to use newer VM sizes for the most optimal networking experience.
However, you can continue running workloads on your existing VM series. These VM series remain supported and can run on both Mellanox (previous generation) and MANA‑enabled hardware until the series is retired. While most workloads are expected to transition to MANA-capable hardware without issue, you should ensure that your workload is compatible with MANA for optimal networking performance.
Applicable VM series
The VM series listed below are eligible to land on MANA-capable hardware and may require additional validation to fully benefit from networking improvements.
| Family | Series |
|---|---|
| A-family | Av2* |
| B-family | Bsv2 |
| D-family | Dv1*, Dsv1* Dv2*, Dsv2* Dv3, Dsv3 Dv4, Dsv4, Ddv4, Ddsv4 Dv5, Dsv5, Ddv5, Ddsv5, Dlsv5, Dldsv5 Dpsv6, Dpdsv6, Dplsv6, Dpldsv6 |
| E-family | Ev3, Esv3 Ev4, Esv4, Edv4, Edsv4 Ev5, Esv5, Edv5, Edsv5 Epsv6, Epdsv6 |
| Eb-family | Ebsv5, Ebdsv5 |
| F-family | F*, Fs*, Fsv2* |
| G-family | G*, Gs* |
| L-family | Ls* |
*These VM series are announced for retirement. If you’re currently using one of these VM series, view the migration guide to switch to a replacement series as soon as possible to avoid service interruption, capacity limitations, and forced deallocation as the series approaches retirement.
Compatibility
Use the following steps to verify that your workload is compatible with the Azure Network Adapter (MANA). If you are running a Network Virtual Appliance (NVA) or DPDK-based workload, see NVA guidance or DPDK guidance for more information.
Note
If Accelerated Networking is not enabled on your VM, no action is required. While your VM may still be placed on MANA-capable hardware, your workload will continue to run as expected without changes.
Check OS support
Ensure your VM is running an operating system that supports MANA. If your OS supports MANA, no further action is needed.- Linux: See Linux VMs with MANA
- Windows: See Windows VMs with MANA
Resize Intel-based workloads if possible
Intel-based workloads are recommended to resize to Intel v6 or later VM series, which support MANA regardless of the operating system.Update operating system to support MANA if resizing is not possible
If you are running Arm-based workloads and/or cannot resize your VM, update your operating system to supportMANA. MANA-eligible VM series can run on both hardware with Mellanox (ConnectX-3,ConnectX-4 Lx,ConnectX-5) and MANA NICs, so existingmlx4andmlx5support still needs to be present.- Linux: Use a supported kernel version
- Windows: Install the required MANA drivers
Validate workload behavior
After deployment or resizing, verify that your workload performs as expected.
Custom images
Azure may place VMs on MANA-capable hardware even if the OS doesn't support MANA. To maximize performance, we recommend using an operating system that supports MANA.
Network performance impacts
Networking limits in Azure are tied to the VM size, not the underlying hardware. No change in performance is expected when moving to MANA-capable hardware if your VM's operating system supports all network devices used in Azure.
Note
While Azure performs extensive testing across a wide range of use cases, virtual machines may still experience rare intermittent connectivity or degraded performance. In such cases, it is highly recommended to migrate to the latest generation of VMs or at a minimum, utilize an operating system that is compatible with MANA.
If a VM is placed on MANA-capable hardware but the OS doesn't support MANA, networking automatically falls back to the NetVSC network adapter. In this scenario:
- The MANA Virtual Function (VF) may be visible, but no interfaces are exposed by the MANA driver.
- Performance is expected to be comparable to SR‑IOV-based
ConnectX‑3,ConnectX‑4 Lx, andConnectX‑5devices. - Workloads with a high number of concurrent connections may see reduced performance.
FAQ
Where can I find more information about MANA?
To learn more about MANA, visit the Azure Network Adapter (MANA) Overview.
Will my existing VM be deployed on MANA hardware?
Both existing and newly created VMs in the supported series may be placed on MANA-capable hardware.
- Existing VMs can land on MANA-capable hardware after a "stop-deallocate and start" operation or standard Azure maintenance event.
- New VMs created in the supported VM series are also eligible to be deployed on MANA capable hardware.
How can I check if my VM is deployed on MANA capable hardware?
If you are using a Linux operating system, follow the instructions described in Linux VMs with the Azure Network Adapter. You'll see a PCIe device in the virtual machine and on the bonded NIC.
Are DPDK-based application impacted by this change workload?
Yes. If your workload doesn't support MANA yet, we recommend that you update your DPDK-based applications. See Azure Network Adapter (MANA) and DPDK on Linux for the minimum MANA compatibility requirements.
Are Network Virtual Appliances (NVAs) impacted by this change?
Yes. NVAs on applicable VM series may also be deployed on MANA capable hardware. Visit the NVA support page for more information about MANA support for NVAs.
What should I do if I have issues?
We’re here to help. Contact Microsoft Support, who can assist with troubleshooting, guidance, and next steps. You can open a support request through the Azure portal by selecting Help + support, or visit the Microsoft Support site to start a new case. A support engineer reviews your request, engage internal teams as needed, and keep you updated until the issue is resolved.
Are Azure Kubernetes Service (AKS) instances impacted?
No. AKS instances aren't impacted and will continue to perform as expected when deployed on MANA hardware.
Is VNet encryption impacted?
No. VNet encryption will continue to perform as expected if VMs are deployed on MANA hardware.