Merge pull request #277420 from Nagarjuna-Vipparthi/main

YAML updates for multi-region load tests

Author: prmerger-automator[bot]

articles/load-testing/reference-test-config-yaml.md

@@ -41,6 +41,7 @@ A load test configuration uses the following keys:
 | `keyVaultReferenceIdentity` | string | N |  | Resource ID of the user-assigned managed identity for accessing the secrets from your Azure Key Vault. If you use a system-managed identity, this information isn't needed. Make sure to grant this user-assigned identity access to your Azure key vault. Learn more about [managed identities in Azure Load Testing](./how-to-use-a-managed-identity.md). |
 | `subnetId` | string | N |  | Resource ID of the virtual network subnet for testing privately hosted endpoints. This subnet hosts the injected test engine VMs. For more information, see [how to load test privately hosted endpoints](./how-to-test-private-endpoint.md). |
 | `publicIPDisabled` | boolean | N |  | Disable the deployment of a public IP address, load balancer, and network security group while testing a private endpoint. For more information, see [how to load test privately hosted endpoints](./how-to-test-private-endpoint.md). |
+| `regionalLoadTestConfig` | object | N |  | Distribute load across regions to simulate user traffic from multiple regions. For more information, See [regional load test configuration](#regional-load-test-configuration) for more details. |
 
 ### Load test configuration sample
 
@@ -329,6 +330,40 @@ The requests JSON file uses the following properties for defining the load confi
 | `spikeMultiplier` | integer | Spike | The factor to multiply the number of target users with during the spike duration. |
 | `spikeHoldTimeInSeconds` | integer | Spike | Total duration in seconds to maintain the spike load. |
 
+### Regional load test configuration
+
+You can distribute load across regions to better simulate real life traffic patterns. You can specify the regions that you want to generate the load from and the amount of load that you want to simulate from each region. You can do that by specifying the region name and the number of engine instances that you want in that region. Learn more about [generating load from multiple regions](./how-to-generate-load-from-multiple-regions.md).
+
+| Key | Type | Default value | Description | 
+| ----- | ----- | ----- | ---- |
+| `region` | string |  | Name of the Azure region. |
+| `engineInstances` | integer |  | Number of engine instances for that Azure region. |
+
+#### Regional load test configuration sample
+
+The following code snippet shows a load test configuration, which specifies two Azure regions `eastus` and `eastasia` and the number of engine instances for each region.
+
+```yaml
+displayName: Sample Test
+testPlan: sampleScript.jmx
+description: 'Load test website home page'
+engineInstances: 4
+testId: SampleTest
+testType: Locust
+splitAllCSVs: False
+regionalLoadTestConfig:
+- region: eastus
+  engineInstances: 2
+- region: eastasia
+  engineInstances: 2
+failureCriteria:
+- p90(response_time_ms) > 10000
+autoStop:
+  errorPercentage: 90
+  timeWindow: 60
+```
+
+
 ## Related content
 
 - Learn how to build [automated regression testing in your CI/CD workflow](./quickstart-add-load-test-cicd.md).