FX2mds v2 is not available for my VM

Question

FX2mds v2 is not available for my VM

CITI Office 365 GA 0

Hello all,

I'm trying to resize my VM to get FX2mds v2 package, but it's not available in the list of CPUs. It is available in my region, but not for my VM. What can it be?

Manish Deshpande 6,915 Reputation points Microsoft External Staff Moderator

2026-06-03T15:38:25.9366667+00:00
Hello @CITI Office 365 GA

The most likely culprit here is a local temporary disk mismatch. The FXmdsv2 series includes a local temp disk (you can tell by the 'd' in the name 'mds'). Azure has a rule that prevents resizing between VM sizes that have a local temp disk and those that don't especially on Windows. So if your current VM size doesn't have a local temp disk, FXmdsv2 simply won't show up in the resize list, even if it's available in your region.

Azure VMs with no local temp disk:
https://learn.microsoft.com/en-us/azure/virtual-machines/azure-vms-no-temp-disk#can-i-resize-a-vm-size-that-has-a-local-temp-disk-to-a-vm-size-with-no-local-temp-disk

The second thing worth trying is stopping (deallocating) your VM before attempting the resize. When a VM is running, it's pinned to a specific hardware cluster — and that cluster may not have the FXmdsv2 hardware available. Deallocating it gives Azure the flexibility to place it on a different cluster that does.

Go to your VM in the Azure Portal → click Stop (not just restart — this needs to be a full deallocation).

Once it shows as Stopped (deallocated), go to Settings → Size and search for FXmdsv2 again.

If it still doesn't appear, check whether your current VM size has a local temp disk. You can look this up on the VM size specs page.

https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/resize-vm

If your current VM has no local temp disk and you're on Windows**, a direct resize won't be possible due to platform limitations. In that case, the recommended workaround is:

Take a snapshot of your OS disk.

Create a new managed disk from that snapshot.

Deploy a new VM from that disk and select FXmdsv2 as the size.

Once you've verified everything works, you can safely delete the old VM.

How to migrate from a VM with local temp disk to one without :
https://learn.microsoft.com/en-us/azure/virtual-machines/azure-vms-no-temp-disk#how-do-i-migrate-from-a-vm-size-with-local-temp-disk-to-a-vm-size-with-no-local-temp-disk

Also worth a quick check — make sure your subscription has sufficient quota for the FXv2 family in your region. You can verify this under Subscriptions → Usage + Quotas in the portal.
https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/allocation-failure

Thanks,
Manish.
Manish Deshpande 6,915 Reputation points Microsoft External Staff Moderator

2026-06-12T13:32:45.06+00:00

Hello @CITI Office 365 GA

I wanted to check if my last response made sense. I’d be glad to assist further or explain anything in more detail and please accept as Yes and upvote if the answer is helpful so that it can help others in the community.

1 answer

Your answer

Manish Deshpande 6,915 Reputation points Microsoft External Staff Moderator

2026-06-12T13:32:45.06+00:00

Hello @CITI Office 365 GA

I wanted to check if my last response made sense. I’d be glad to assist further or explain anything in more detail and please accept as Yes and upvote if the answer is helpful so that it can help others in the community.

Answer 1

FX2mds v2 belongs to the FXmdsv2-series, which has specific hardware characteristics (5th Gen Intel Xeon Platinum 8573C, high memory-to-CPU ratio, local SSD, specific NIC and storage capabilities).

If FX2mds v2 is available in the region but not shown as a resize option for an existing VM, typical causes are:

Series/Hardware incompatibility
Not all VM series can be resized to all other series. The existing VM’s current series, hardware cluster, or availability construct (Availability Set/Zone, isolated host, etc.) may not support moving to FXmdsv2. In such cases, the portal will not list FX2mds v2 as a valid target size.
SKU availability per cluster/subscription
Even when a SKU is available in the region, it might not be available on the specific cluster where the VM currently runs, or it may be restricted for the subscription. The “Unavailable virtual machine SKU” guidance indicates that if a size is restricted for a subscription in a region, it cannot be used for that VM.
Constrained vCPU variants vs. base sizes
FX-family constrained vCPU sizes (for example, Standard_FX4-2mds_v2, Standard_FX8-4mds_v2, etc.) are separate SKUs from the base FXmdsv2 sizes. If the environment or quota is configured only for certain constrained sizes or base sizes, some SKUs may not appear.

To proceed:

Verify SKU availability and restrictions
Use the Azure portal or Azure CLI to check whether Standard_FX2mds_v2 is marked as restricted for the subscription in that region. If it is restricted, request access or choose another size.
Try a new VM deployment
Attempt to create a new VM in the same region using FX2mds v2. If creation is allowed but resize is not, the limitation is likely due to the current VM’s hardware/availability configuration. In that case, migrate workloads (backup/restore, image, or disk attach) to a new FX2mds v2 VM.
Select a different FXmdsv2 size or FXmsv2 size
If FX2mds v2 is not offered, but other FXmdsv2 or FXmsv2 sizes are, consider one of those that meets requirements.
Open a support request if needed
If the VM is pinned to specific hardware (for example, part of an availability set or special configuration) and cannot be resized to FX2mds v2, open an Azure Support request and select “Assistance with resizing my VM” so support can check cluster-level constraints and offer a migration path.

References:

Share via

FX2mds v2 is not available for my VM

1 answer

Your answer