You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/load-testing/how-to-test-private-endpoint.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -303,11 +303,11 @@ Follow these steps to [enable inbound access](/azure/load-testing/how-to-test-pr
303
303
304
304
The virtual network isn't in the same subscription and region as your Azure load testing resource. Either move or recreate the Azure virtual network or the Azure load testing resource to the same subscription and region.
305
305
306
-
### Creating or updating the load test fails with `An azure policy is restricting engine deployment to your subscription (ALTVNET012)`
306
+
### Provisioning fails with `An azure policy is restricting engine deployment to your subscription (ALTVNET012)`
307
307
308
308
An Azure policy is restricting load test engine deployment to your subscription. Check your policy restrictions and try again.
309
309
310
-
### Creating or updating the load test fails with `Engines could not be deployed due to an error in subnet configuration (ALTVNET013)`
310
+
### Provisioning fails with `Engines could not be deployed due to an error in subnet configuration (ALTVNET013)`
311
311
312
312
The load test engine instances couldn't be deployed due to an error in the subnet configuration. Verify your subnet configuration. If the issue persists, raise a ticket with support along with the run ID of the test.
0 commit comments