Load testing is most effective when it closely mirrors real-world usage and when test infrastructure is used efficiently.
We recently launched AI-assisted load test authoring which enables mirroring real-world usage. Today, we are taking another step for the efficient use of test infrastructure. Behind every load test run, there is dedicated infrastructure that needs to be provisioned, managed, and deprovisioned. Low-user or short-lived load test runs lead to inefficient use of test infrastructure. To keep the service cost-effective and ensure judicious use of test infrastructure, we are introducing a minimum usage per test run for load tests in Azure App Testing.
Effective March 1, 2026, load tests in Azure App Testing will incur a minimum Virtual User Hours (VUH) charge per test run. For each test run, the minimum VUH will be:
- 10 Virtual Users (VUs) per engine for the test run duration, or
- 10 VUs per engine for 10 minutes, if the test run duration is less than 10 minutes
If your test run already meets or exceeds this minimum usage, this change doesn’t impact you. Also, this change is only for load tests and does not impact Playwright tests in Azure App Testing.
How It Works?
Let’s make this concrete with a few examples.
Example 1: Low-user, long-duration test
- Configuration: 5 VUs, 1 engine, 3 hours
- Actual usage: 15 VUH = 5 VUs × 3 hours × 1 engine
- Minimum usage: 30 VUH = 10 VUs × 3 hours × 1 engine
You will be charged for 30 VUH, since the actual usage is below the minimum.
Example 2: Low-user, short-duration test
- Configuration: 5 VUs, 1 engine, 5 minutes
- Actual usage: 0.83 VUH = 5 VUs × (5 min / 60)
- Minimum usage: 1.67 VUH = 10 VUs × (10 min / 60) × 1 engine
You will be charged for 1.67 VUH, since the actual usage is below the minimum.
Example 3: High-user, short-duration test exceeding the minimum
- Configuration: 500 VUs, 2 engines, 5 minutes
- Actual usage: 83.34 VUH = 500 VUs × (5 min / 60) x 2 engines
- Minimum usage: 3.33 VUH = 10 VUs × (10 min / 60) × 2 engines
You will be charged for 83.34 VUH, since your usage exceeds the minimum.
What should you do?
Based on usage patterns we’ve observed, some of your test runs may fall below the minimum VUH and could incur a minimum charge. To avoid surprises, we recommend reviewing your test configurations:
- Low-user, high-engine tests? Reduce the engine count.
- Short-duration or low-user tests? Increase the user count or duration for meaningful load testing.
- Tests above minimum usage? No action needed!
A small configuration tweak can often make your tests both more effective and more cost-efficient.
Need Help?
The pricing page and pricing calculator will soon be updated to reflect these changes.
- If you have a support plan and need technical assistance, please create a support request in the Azure portal.
- For questions or feedback, share it with the product team on Developer Community
Happy load testing that is real-world and efficient!
Microsoft