Australia East - Standard_NV4as_v4 retired - suggested to migrate to NVads_V710_v5 but not available in region with no other gpu optoins?

Hi James,

The NVads_V710_v5 series is currently only available in a limited set of regions (East US, North Central US, South Central US, West US, Spain Central, and West Europe). Australia East is not on that list yet, so you're correct that it won't appear in your sizing list there.

Here's how I'd think about your options:

Option 1 (Recommended if data residency allows): Migrate to NVads_A10_v5 within Australia East

The official retirement guide actually lists two recommended replacement series — NVads_V710_v5 is the primary recommendation, but NVads_A10_v5 is the explicitly supported alternative for regions where V710 isn't available yet. Importantly, NVads_A10_v5 has broader regional availability and is worth checking for Australia East.

You can verify the exact regions where NVads_A10_v5 is available via the Azure Products by Region page:

https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/

If it's available in Australia East, resizing there would be the cleanest path — same region, no data residency concerns, and it's a supported migration target.

https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/nvv4-retirement

Option 2: Migrate to NVads_V710_v5 in a nearby region

If NVads_A10_v5 is also not available in Australia East, or if you specifically need the V710 series, your nearest option at the moment would be moving to a region where it's already GA. Since neither Southeast Asia nor Australia Southeast is currently listed either, this may involve a trade-off on latency or data residency — worth flagging internally before committing.

You can find the resize guide here:

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

Option 3: Request regional expansion via Azure Feedback

If Australia East is a hard requirement for your workloads, the right channel is to raise this directly with Microsoft through a support request or via the Azure feedback portal. There's no public ETA for NVads_V710_v5 in Australia East, but regional expansion requests do influence the rollout roadmap.

Just a heads-up: Microsoft has acknowledged a known resize operation error when migrating from NVv4 to NVads_V710_v5. A fix was targeted for April 2026, so that should be resolved by now but if you do run into issues during the resize, the workaround is documented here:

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---

The deadline to keep in mind: All NVv4-series VMs will be forcibly deallocated on September 30, 2026, so there's time to plan, but it's worth getting the migration scoped sooner rather than later to avoid any last-minute pressure.

Thanks,
Manish.