Merge pull request #299245 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: v-alje

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

@@ -47,7 +47,7 @@ To use secrets with Azure Load Testing, you perform the following steps:
 
 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.
 
-You also need to grant Azure Load Testing access to your Azure key vault to retrieve the secret value.
+You also need to grant Azure Load Testing access to your Azure Key Vault to retrieve the secret value.
 
 > [!NOTE]
 > 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
 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.
 
     > [!IMPORTANT]
-    > 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).
+    > 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).
 
 1. Retrieve the key vault **secret identifier** for your secret. You use this secret identifier to configure your load test.
 
-    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`.
+    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`.
 
 #### Add the secret to your load test
 
@@ -89,7 +89,7 @@ You also need to grant Azure Load Testing access to your Azure key vault to retr
 
     * 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).
 
-#### Grant access to your Azure key vault
+#### Grant access to your Azure Key Vault
 
 [!INCLUDE [include-grant-key-vault-access-secrets](includes/include-grant-key-vault-access-secrets.md)]
 

articles/load-testing/includes/include-grant-key-vault-access-secrets.md

@@ -12,9 +12,9 @@ ms.date: 10/19/2023
 
 When you store load test secrets or certificates in Azure Key Vault, your load testing resource uses a [managed identity](../how-to-use-a-managed-identity.md) for accessing the key vault. After you configure the manage identity, you need to grant the managed identity of your load testing resource permissions to read these values from the key vault.
 
-To grant your Azure load testing resource permissions to read secrets or certificates from your Azure key vault:
+To grant your Azure load testing resource permissions to read secrets or certificates from your Azure Key Vault:
 
-1. In the [Azure portal](https://portal.azure.com/), go to your Azure key vault resource.
+1. In the [Azure portal](https://portal.azure.com/), go to your Azure Key Vault resource.
 
     If you don't have a key vault, follow the instructions in [Azure Key Vault quickstart](/azure/key-vault/secrets/quick-create-cli) to create one.
 

articles/service-bus-messaging/service-bus-prefetch.md

@@ -29,6 +29,8 @@ You can set **prefetch_count** on the [azure.servicebus.ServiceBusReceiver](/pyt
 
 While messages are available in the prefetch buffer, any subsequent receive calls are immediately fulfilled from the buffer. The buffer is replenished in the background as space becomes available. If there are no messages available for delivery, the receive operation empties the buffer and then waits or blocks, as expected.
 
+It's important to note that `PrefetchCount` defines the maximum number of messages that can exist in the local buffer at any time. This also means that it acts as a strict upper limit on how many messages can be processed concurrently. If `MaxConcurrentCalls` is set higher than `PrefetchCount`, the processor will not be able to utilize all concurrent message handlers, as only up to `PrefetchCount` messages can be active in memory at once.
+
 ## Why is Prefetch not the default option?
 Prefetch speeds up the message flow by having a message readily available for local retrieval before the application asks for one. This throughput gain is the result of a trade-off that the application author must make explicitly.