Merge pull request #263637 from ntrogh/alt-increase-criteria

[Azure Load Testing] Update max number of test criteria from 10 to 50

Author: prmerger-automator[bot]

articles/load-testing/how-to-define-test-criteria.md

@@ -28,7 +28,7 @@ You can define test criteria at two levels. A load test can combine criteria at
 - At the load test level. For example, to ensure that the total error percentage doesn't exceed a threshold.
 - At the JMeter request level (JMeter sampler). For example, you could specify a response time threshold of the *getProducts* request, but disregard the response time of the *sign in* request.
 
-You can define a maximum of 10 test criteria for a load test. If there are multiple criteria for the same client metric, the criterion with the lowest threshold value is used.
+You can define a maximum of 50 test criteria for a load test. If there are multiple criteria for the same client metric, the criterion with the lowest threshold value is used.
 
 ### Fail criteria structure
 

articles/load-testing/resource-limits-quotas-capacity.md

@@ -44,7 +44,7 @@ The following limits apply on a per-region, per-subscription basis.
 | Test runs per test | 5000 | |
 | File uploads per test | 1000 | |
 | App Components per test or test run | 100 | |
-| [Test criteria](./how-to-define-test-criteria.md#load-test-fail-criteria) per test | 10 | |
+| [Test criteria](./how-to-define-test-criteria.md#load-test-fail-criteria) per test | 50 | |
 
 <sup>2</sup> If you aren't already at the maximum limit, you can request an increase. We aren't currently able to approve increase requests past our maximum limitations stated above. To request an increase for your default limit, contact Azure Support. Default limits vary by offer category type.