Azure Loat Testing Pricing

Question

Azure Loat Testing Pricing

Mohammed Sharukh 0

Hi,

Virtual User Hour (VUH) usage	0 - 10,000 Virtual User Hours - $0.15/VUH10,000+ Virtual User Hours - $0.06/VUH
Virtual User Hour (VUH) usage	0 - 10,000 Virtual User Hours - $0.15/VUH10,000+ Virtual User Hours - $0.06/VUH

I am trying to understand above pricing. Lets say i want run a test with 10k users just to login my website. This will max take 10 sec to complete. How will the pricing gets calculated?

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

Christos Panagiotidis 3,551 Reputation points

2026-07-29T10:56:36.3866667+00:00

Azure Load Testing consumption is measured in Virtual User Hours, not simply by the number of login attempts. The calculation is the number of active virtual users multiplied by their active duration in hours. Microsoft measures active users at ten-second intervals and bills fractional VUH.

If 10,000 users are actually active for only 10 seconds, the calculation is 10,000 × 10 ÷ 3,600, which is approximately 27.78 VUH. Using the $0.15 rate quoted in your question, that run would be approximately $4.17 before taxes, contractual discounts, or currency conversion, assuming your monthly usage remains in that pricing tier. Include ramp-up, steady-state, and ramp-down time when estimating because users active during those periods also count. A script that takes longer than expected will consume more VUH. Use the Azure pricing calculator for the applicable region and agreement, and configure a monthly VUH usage limit on the Load Testing resource to prevent accidental overspending.
Sina Salam 31,456 Reputation points Volunteer Moderator

2026-07-29T15:48:31.5966667+00:00
Hello Mohammed Sharukh,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you would like to know how Azure Load Testing pricing is calculated.

Azure Load Testing is billed based on Virtual User Hours (VUH). It does not reserve or charge a full hour for short-running tests. Instead, Azure calculates the equivalent fractional VUH consumed during the test and charges accordingly.

For your scenario:

10 seconds ÷ 3600 = 0.0027778 hours

10,000 Virtual Users × 0.0027778 hours = 27.78 VUH

Using the published rate of US$0.15 per VUH:

27.78 × US$0.15 = approximately US$4.17

Therefore, assuming your subscription is within the published 0–10,000 monthly VUH pricing tier, the estimated usage charge for this test is approximately US$4.17. Pricing tiers are based on your total monthly Virtual User Hour consumption, not the number of virtual users in a single test. For production cost planning, verify your regional pricing and monthly usage with the Azure Pricing Calculator.

Use the following resources for additional information:

Azure App Testing (Azure Load Testing) Pricing - https://azure.microsoft.com/pricing/details/app-testing/

Azure Load Testing Documentation - https://learn.microsoft.com/azure/app-testing/load-testing/

Azure Load Testing Pricing - https://techcommunity.microsoft.com/blog/appsonazureblog/azure-load-testing-pricing/3805812

I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.

Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.

Christos Panagiotidis 3,551 Reputation points

2026-07-29T10:56:36.3866667+00:00

Azure Load Testing consumption is measured in Virtual User Hours, not simply by the number of login attempts. The calculation is the number of active virtual users multiplied by their active duration in hours. Microsoft measures active users at ten-second intervals and bills fractional VUH.

If 10,000 users are actually active for only 10 seconds, the calculation is 10,000 × 10 ÷ 3,600, which is approximately 27.78 VUH. Using the $0.15 rate quoted in your question, that run would be approximately $4.17 before taxes, contractual discounts, or currency conversion, assuming your monthly usage remains in that pricing tier. Include ramp-up, steady-state, and ramp-down time when estimating because users active during those periods also count. A script that takes longer than expected will consume more VUH. Use the Azure pricing calculator for the applicable region and agreement, and configure a monthly VUH usage limit on the Load Testing resource to prevent accidental overspending.
Sina Salam 31,456 Reputation points Volunteer Moderator

2026-07-29T15:48:31.5966667+00:00

Hello Mohammed Sharukh,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you would like to know how Azure Load Testing pricing is calculated.

Azure Load Testing is billed based on Virtual User Hours (VUH). It does not reserve or charge a full hour for short-running tests. Instead, Azure calculates the equivalent fractional VUH consumed during the test and charges accordingly.

For your scenario:

10 seconds ÷ 3600 = 0.0027778 hours

10,000 Virtual Users × 0.0027778 hours = 27.78 VUH

Using the published rate of US$0.15 per VUH:

27.78 × US$0.15 = approximately US$4.17

Therefore, assuming your subscription is within the published 0–10,000 monthly VUH pricing tier, the estimated usage charge for this test is approximately US$4.17. Pricing tiers are based on your total monthly Virtual User Hour consumption, not the number of virtual users in a single test. For production cost planning, verify your regional pricing and monthly usage with the Azure Pricing Calculator.

Use the following resources for additional information:

Azure App Testing (Azure Load Testing) Pricing - https://azure.microsoft.com/pricing/details/app-testing/

Azure Load Testing Documentation - https://learn.microsoft.com/azure/app-testing/load-testing/

Azure Load Testing Pricing - https://techcommunity.microsoft.com/blog/appsonazureblog/azure-load-testing-pricing/3805812

I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.

Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.