VM Licensing Cost

Question

We are trying to provision a new Windows VM D16s_v3 VM with the image "Windows Server 2025 Datacenter: Azure Edition"

The Azure portal's "Estimated monthly costs" panel shows an Image (Windows licence) cost of about $7,251.82/month. The actual billing shows the real licence charge is $0.574/hour (about $419/month), or $0 with Azure Hybrid Benefit (AHB). The panel is roughly 17x too high.

Answer 1

Hi,

This is bug/issue with that image and the estimator. The Pay-As-You-Go cost for Windows Server license running on non-burstable VM size is $0.046 per vCPU per hour. For 16 vCPUs it would be $0.736/hour, or $537.28 for 730 hour average month. This is separate from compute charge.

With Azure Hybrid Benefit the hourly license charge wouldn't apply.

To report this, please click Give feedback about your estimate experience, in box explain that window server license cost is incorrect, and submit. The team that owns the estimator functionality will be able to see it.

I have not seen them actually charge the inflated amount quoted by the estimator, but I still recommend verifying you are not being overcharged by viewing Cost analysis.

Please add a comment below if you have any questions.

Thanks.

-TP

Answer 2

Hi @Sahal Imran ,

This looks like a discrepancy in the Azure portal's cost estimator rather than the actual Windows Server licensing rate.

For Standard_D16s_v3 in East US, the Windows Server license charge being billed is around $0.574/hour, which is roughly $419/month at 730 hours. With Azure Hybrid Benefit, the Windows Server license portion should be $0.

However, the VM creation page is showing $7,251.82/month for the Windows Server 2025 Datacenter: Azure Edition image, which works out to around $9.93/hour. That doesn't align with the actual Windows Server meter of $0.574/hour.

I would recommend checking the actual Cost Analysis/meter details for the VM and comparing the meter name, region, VM size, and OS licensing charge with the pricing calculator. The $7,251.82 figure should not be treated as the actual Windows licensing cost without confirming the underlying meter.

If this is reproducible, it would also be worth reporting to Microsoft as a portal pricing-estimation issue, including the VM size, region, image, and the screenshot of the incorrect estimate.