Blog Post

Azure Infrastructure Blog
2 MIN READ

Announcing Microsoft Azure Network Adapter (MANA) support for Existing VM SKUs

ali_sheriff's avatar
ali_sheriff
Icon for Microsoft rankMicrosoft
Feb 06, 2026

As a leader in cloud infrastructure, Microsoft ensures that Azure’s IaaS customers always have access to the latest hardware. Our goal is to consistently deliver technology to support business critical workloads with world class efficiency, reliability, and security. Customers benefit from cutting-edge performance enhancements and features, helping them to future proof their workloads while maintaining business continuity.    

Azure will be a deploying new hardware generation to support capacity demands for existing VM Size Families. The hardware is optimized for these VM sizes, utilizing Intel’s Emerald Rapid CPU, native NVMe SSD support for higher storage bandwidth and lower latency, and Microsoft Azure Network Adapter (MANA). Deployment timelines will be communicated via Service Health Advisory updates. The intent is to provide the benefits of new server hardware to customers of existing VM SKUs as they work towards migrating to newer SKUs. The deployments will be based on capacity needs and won’t be restricted by region. Once the hardware is available in a region, VMs can be deployed to it as needed.   

Workloads on operating systems which fully support MANA will benefit from sub-second Network Interface Card (NIC) firmware upgrades, higher throughput, lower latency, increased Security and Azure Boost-enabled data path accelerations. If your workload doesn't support MANA today, you'll still be able to access Azure’s network on MANA enabled SKUs, but performance will be comparable to previous generation (non-MANA) hardware. Check out the Azure Boost Overview and the Microsoft Azure Network Adapter (MANA) overview for more detailed information and OS compatibility.   

To determine whether your VMs are impacted and what actions (if any) you should take, start with MANA support for existing VM SKUs. This article provides additional information about which VM Sizes are eligible to be deployed on the new MANA-enabled hardware, what actions (if any) you should take, and how to determine if the workload has been deployed on MANA-enabled hardware.

Updated Jun 12, 2026
Version 5.0

8 Comments

  • TC_Security's avatar
    TC_Security
    Copper Contributor

    Does this verbiage -- "The deployments will be based on capacity needs and won’t be restricted by region. Once the hardware is available in a region, VMs can be deployed to it as needed." -- mean that customers can opt in on their time table and no opt out tagging is needed at all?

    The 'MANA support for Network Virtual Appliances (NVAs)' article still references the opt out tag with the "end of September" deadline. Is that document just outdated now? It would be hard to believe that an opt out process would only be available for two months, if deployment is starting on August 1st.

    • franklin19c's avatar
      franklin19c
      Tin Contributor

      If you haven't seen it yet, I've seen some places now say May 30, 2027 as the new deadline for when opting out no longer works.

      • TC_Security's avatar
        TC_Security
        Copper Contributor

        Thanks. And yeah, I saw all their updated verbiage in their tech docs on MANA. The deadline for the opt-out tagging is August 1st, but the general deadline for all VMs to be MANA-ready is May 30th next year.

        I didn't see a way to delete my post on here actually, maybe just missing it.

  • adnl0389393's avatar
    adnl0389393
    Copper Contributor

    Thank you for the article however I've been informed there may be some timeline changes and other considerations to the planned migration. Is this information still current?