Catalog
ND/NC/NV families as on-demand when we have a published hour. Low-priority labeled.
Provider review / verified 2026-09-05
Azure sells ND/NC/NV GPU VMs next to the Microsoft estate: Entra, Blob, Azure ML. If your company already signed the EA, the GPU hour is a rounding error in a political sense. If you are an indie lab, it is a trap.
Our reading
Azure GPUs are for Microsoft shops. I will not talk you out of ND-H100 if your data cannot leave the tenant. I will talk you out of Azure if you are a five-person lab with a Hugging Face repo and a dream. The catalog hour is usually not the win. The win is staying inside a compliance boundary you already paid lawyers for.
Rent it if Enterprises on Azure ML / Fabric / Entra who need NVIDIA in the same tenant.
Skip it if Everyone shopping a 4090. Startups with no Microsoft relationship hunting a cheap H100.
How we compare hoursSame standard, every cloud
Four checks we apply to every provider. This is not a score, and it is not a paid ranking.
ND/NC/NV families as on-demand when we have a published hour. Low-priority labeled.
Hyperscaler band. EA discounts are real and invisible to a public table, we do not invent them.
Azure VM + GPU. Platform first, GPU second.
Quota, region, VM size. Your EA price is not our catalog price. Confirm both.
Catalog listings
Published on-demand hours first. Spot and waitlists are labeled. Confirm the live rate before you provision.
If Microsoft already takes a percentage of your IT spend, adding ND-instances can be ‘free’ in the only way CFOs understand. That is not the same as cheap. GPUBeacon shows a public-shaped hour. Your EA is a private conversation. I will not fake it into a green cell.
Managed training services are a product. ND VMs are a product. Compare them separately. I rent VMs when I want nvidia-smi. I use managed services when I want Microsoft to own the plumbing. Mixing them in a blog post is how you get a surprise bill.
If not, open Lambda or CoreWeave. If yes, continue.
The SKU is not ‘H100.’ It is a VM size.
Our table is public. Your account manager is not. Use both.
FAQ
It depends on EA, region, and SKU. Public list vs public list is a coin flip by generation. Both lose to many neoclouds on raw hours.
Azure if the tenant is the constraint. CoreWeave if the GPU cluster is the product and data can move.
Yes, with credits. Credits end. Plan the hour after credits or you will do a midnight migration.
Anyone who is not already a Microsoft shop and who does not have a compliance gun to their head.
Sources
Prices and SKUs are from the GPUBeacon catalog sample. Ranking rules are on the methodology page. Outbound links may be affiliate. They never change the hour we display.
Keep comparing
Same fields, different product. Compare the GPU hour before you lock a brand.