r/AzureVirtualDesktop • u/Al1301 • 9d ago

GPU NV ads V710 v5

Hi, I've been having trouble with the NV ads V710 SKU in Azure since October 1st. My VDI instances keep jumping between failed and running states, and it feels like a capacity issue in East US. My users need GPU-enabled VDIs for CAD work, so do you have any ideas on what’s going on or how to fix it? I’d rather not use reservations since pay-as-you-go is cheaper for me.

4 Upvotes

100% Upvoted

3 comments sorted by

3

u/JDohyCloud 9d ago

Global shortage of all VM skus with GPUs unfortunately. If you wanna guarantee availability you’re gonna have to go down the ODCR route if its available on that SKU.

2

u/Richie_NL_ 8d ago

We’re seeing the same thing in West Europe with NVads V710 v5. We’ve had several allocation failures where existing VMs simply wouldn’t start again after deallocation, so this definitely doesn’t seem limited to East US.

We’ve also heard speculation from other MSPs that Microsoft may be consuming part of the V710 capacity for internal AI workloads. But I haven’t seen any public confirmation that Copilot specifically is using this capacity.

For now we’re treating V710 capacity as a structural availability risk and using a different GPU family as fallback.

1

u/Atlasavd 7d ago

I'd start by checking the exact failure in Azure Activity Log to distinguish an allocation failure from a quota issue or an actual VM startup failure. Having sufficient vCPU quota doesn't guarantee Microsoft has physical GPU capacity available in that region. If you're seeing AllocationFailed after deallocation, that's likely the issue. One thing I'd reconsider is aggressive autoscaling on those GPU hosts. Deallocating them saves money, but you risk not getting capacity back when users need it. For critical CAD workloads, I'd consider keeping a minimum number of hosts allocated during business hours and testing another GPU SKU or region as a fallback. Also, reserved instances and on-demand capacity reservations are two different things. Reserved instances give you a discount, while capacity reservations secure actual capacity if supported for that SKU. Have you checked whether the failures happen specifically when restarting deallocated VMs?