Skip to content

Commit 269d1d2

Browse files
committed
Fix typo
Azure key vault -> Azure Key Vault
1 parent 0c5787c commit 269d1d2

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/load-testing/how-to-parameterize-load-tests.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ To use secrets with Azure Load Testing, you perform the following steps:
4747

4848
You can use Azure Key Vault to pass secret values to your test script in Azure Load Testing. You add a reference to the secret in the Azure Load Testing configuration. Azure Load Testing then uses this reference to retrieve the secret value in the test script.
4949

50-
You also need to grant Azure Load Testing access to your Azure key vault to retrieve the secret value.
50+
You also need to grant Azure Load Testing access to your Azure Key Vault to retrieve the secret value.
5151

5252
> [!NOTE]
5353
> If you run a load test as part of your CI/CD process, you might also use the related secret store. Skip to [Use the CI/CD secret store](#cicd_secrets).
@@ -57,11 +57,11 @@ You also need to grant Azure Load Testing access to your Azure key vault to retr
5757
1. [Add the secret value to your key vault](/azure/key-vault/secrets/quick-create-portal#add-a-secret-to-key-vault), if you haven't already done so.
5858

5959
> [!IMPORTANT]
60-
> If you restricted access to your Azure key vault by a firewall or virtual networking, follow these steps to [grant access to trusted Azure services](/azure/key-vault/general/overview-vnet-service-endpoints#grant-access-to-trusted-azure-services).
60+
> If you restricted access to your Azure Key Vault by a firewall or virtual networking, follow these steps to [grant access to trusted Azure services](/azure/key-vault/general/overview-vnet-service-endpoints#grant-access-to-trusted-azure-services).
6161
6262
1. Retrieve the key vault **secret identifier** for your secret. You use this secret identifier to configure your load test.
6363

64-
The **secret identifier** is the full URI of the secret in the Azure key vault. Optionally, you can also include a version number. For example, `https://myvault.vault.azure.net/secrets/mysecret/` or `https://myvault.vault.azure.net/secrets/mysecret/abcdef01-2345-6789-0abc-def012345678`.
64+
The **secret identifier** is the full URI of the secret in the Azure Key Vault. Optionally, you can also include a version number. For example, `https://myvault.vault.azure.net/secrets/mysecret/` or `https://myvault.vault.azure.net/secrets/mysecret/abcdef01-2345-6789-0abc-def012345678`.
6565

6666
#### Add the secret to your load test
6767

@@ -89,7 +89,7 @@ You also need to grant Azure Load Testing access to your Azure key vault to retr
8989

9090
* If you're configuring a CI/CD workflow and use Azure Key Vault, you can specify the reference identity in the YAML configuration file by using the `keyVaultReferenceIdentity` property. For more information about the syntax, see the [Test configuration YAML reference](./reference-test-config-yaml.md).
9191

92-
#### Grant access to your Azure key vault
92+
#### Grant access to your Azure Key Vault
9393

9494
[!INCLUDE [include-grant-key-vault-access-secrets](includes/include-grant-key-vault-access-secrets.md)]
9595

0 commit comments

Comments
 (0)