diff --git a/modules/oadp-auth-azure-secret-based.adoc b/modules/oadp-auth-azure-secret-based.adoc
index f2b326a2920f..81f10468364c 100644
--- a/modules/oadp-auth-azure-secret-based.adoc
+++ b/modules/oadp-auth-azure-secret-based.adoc
@@ -13,7 +13,7 @@ The default name of the `Secret` is `{credentials}`.
 
 [NOTE]
 ====
-The `DataProtectionApplication` custom resource (CR) requires a default `Secret`.  Otherwise, the installation will fail. If the name of the backup location `Secret` is not specified, the default name is used.
+The `DataProtectionApplication` custom resource (CR) requires a default `Secret`. Otherwise, the installation fails. If the name of the backup location `Secret` is not specified, the default name is used.
 
 If you do not want to use the backup location credentials during the installation, you can create a `Secret` with the default name by using an empty `credentials-velero` file.
 ====
@@ -71,12 +71,13 @@ metadata:
   name: <dpa_sample>
   namespace: openshift-adp
 spec:
-...
+# ...
   backupLocations:
     - velero:
         config:
           resourceGroup: <azure_resource_group>
           storageAccount: <azure_storage_account_id>
+          storageAccountURI: <storage_account_blob_endpoint>
           subscriptionId: <azure_subscription_id>
         credential:
           key: cloud
@@ -97,4 +98,10 @@ spec:
 +
 where:
 +
-`<custom_secret>`:: Specifies the backup location `Secret` with custom name.
\ No newline at end of file
+`<storage_account_blob_endpoint>`:: Optional. Specifies the Azure storage account blob endpoint, for example, `\https://<storage_account_name>.blob.core.windows.net`. When you specify `storageAccountURI`, the `resourceGroup` and `storageAccount` fields are optional.
+`<custom_secret>`:: Specifies the backup location `Secret` with custom name.
++
+[NOTE]
+====
+If you experience Azure storage account throttling issues with HTTP 429 `TooManyRequests` errors in the Velero logs, you can add the `storageAccountURI` field to the backup storage location configuration. By providing the storage account blob endpoint directly, Velero bypasses the need to fetch the storage account properties. This also eliminates the need for Reader permission on the storage account.
+====
\ No newline at end of file