FAQ: Azure Retirement of vMX Instance Type
Introduction
This document was created jointly between the Cisco Meraki vMX and Microsoft Azure PM teams to answer a number of questions on Azure's planned retirement of the F4s_v2 instance type.
We are working on enabling support for newer instance types and are targeting full support in June of 2026*. No action is required from customers at this time.
*= Barring any major issues found during Quality testing
Why am I seeing “SKU not available” when deploying Meraki vMX on Azure?
The Meraki vMX appliance on Azure currently relies on the Standard_F4s_v2 virtual machine size, which belongs to the Fs_v2 VM family. Although this SKU has not yet reached its official retirement date, Microsoft has announced its retirement and is gradually shifting focus to newer VM generations. As part of this transition, Azure is no longer broadly expanding capacity for Fs_v2, and availability has become increasingly region- and subscription-dependent. As a result, new deployments or scale-outs may encounter “SKU not available” errors even though the VM size is still listed as supported. This behavior is expected for SKUs announced for retirement and running on older hardware platforms.
Has F4s_v2 retired early?
No. The published retirement date for the Fsv2 family has not changed. However, reduced availability means that F4s_v2 instances may not be readily available to deploy in regions for new subscriptions that don't have previous usage of the SKU. Existing Meraki vMX deployments running on F4s_v2 continue to operate.
Retired Azure VM size series - Azure Virtual Machines | Microsoft Learn
Can Azure or Cisco guarantee F4s_v2 capacity?
No. Azure cannot guarantee capacity availability for the Standard_Fs_v2 SK. While the Fs_v2 family remains supported through its published retirement date of November 2028, Microsoft does not guarantee capacity. As part of the retirement cycle, no new capacity is added, and Azure also applies additional restrictions (such as limiting availability for new subscriptions or regions) to discourage new usage of SKUs approaching retirement.
Customers should therefore plan with the assumption that F4s_v2 capacity may become increasingly limited and proactively work toward migrating off the SKU ahead of the 2028 retirement date.
Is there an exception or waiver to keep using F4s_v2?
There is no formal waiver or exemption program that guarantees continued access to F4s_v2. Customers can request assistance through Azure Support, but approvals are case-by-case, depending on region capacity availability, and not guaranteed.
What should I do if I’m blocked right now?
If you are unable to deploy or expand a Meraki vMX instance:
- Open an Azure support request through the subscription blocked describing the error, affected region, and business impact, and stating of the awareness of retirement and willingness to continue using the F4sv2 series.
- Contact your Cisco/Meraki and Microsoft account teams and share the support case number.
- Evaluate alternatives, such as migrating to a Meraki supported replacement VM size.
What is the recommended long-term approach?
Treat F4s_v2 as a constrained, legacy VM size and plan a migration to supported Azure VM platforms that are certified for Meraki vMX. This provides greater long-term stability and avoids future deployment blockers.
How is Cisco/Meraki supporting customers?
Cisco/Meraki is working closely with Microsoft to:
- Provide clear and consistent guidance
- Help customers understand available options
- Minimize disruption while customers plan and complete migrations
This FAQ will be updated as conditions change.
Where can I get help or updates?
Azure Support: https://portal.azure.com
Meraki Support: https://account.meraki.com/help
If you are unsure where to start, contact your Meraki Support engineer or account team.