Skip to content

Commit 318134f

Browse files
Merge pull request #222134 from msangapu-msft/patch-24
Update configure-connect-to-azure-storage.md
2 parents e05f916 + 461805e commit 318134f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/app-service/configure-connect-to-azure-storage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -268,7 +268,7 @@ To validate that the Azure Storage is mounted successfully for the app:
268268

269269
- To avoid potential issues related to latency, place the app and the Azure Storage account in the same Azure region. Note, however, if the app and Azure Storage account are in same Azure region, and if you grant access from App Service IP addresses in the [Azure Storage firewall configuration](../storage/common/storage-network-security.md), then these IP restrictions are not honored.
270270

271-
- In the Azure Storage account, avoid [regenerating the access key](../storage/common/storage-account-keys-manage.md) that's used to mount the storage in the app. The storage account contains two different keys. Use a stepwise approach to ensure that the storage mount remains available to the app during key regeneration. For example, assuming that you used **key1** to configure storage mount in your app:
271+
- In the Azure Storage account, avoid [regenerating the access key](../storage/common/storage-account-keys-manage.md) that's used to mount the storage in the app. The storage account contains two different keys. Azure App Services stores Azure storage account key. Use a stepwise approach to ensure that the storage mount remains available to the app during key regeneration. For example, assuming that you used **key1** to configure storage mount in your app:
272272
273273
1. Regenerate **key2**.
274274
1. In the storage mount configuration, update the access the key to use the regenerated **key2**.
@@ -297,7 +297,7 @@ To validate that the Azure Storage is mounted successfully for the app:
297297

298298
- Mounting the storage to `/home` is not recommended because it may result in performance bottlenecks for the app.
299299

300-
- In the Azure Storage account, avoid [regenerating the access key](../storage/common/storage-account-keys-manage.md) that's used to mount the storage in the app. The storage account contains two different keys. Use a stepwise approach to ensure that the storage mount remains available to the app during key regeneration. For example, assuming that you used **key1** to configure storage mount in your app:
300+
- In the Azure Storage account, avoid [regenerating the access key](../storage/common/storage-account-keys-manage.md) that's used to mount the storage in the app. The storage account contains two different keys. Azure App Services stores Azure storage account key. Use a stepwise approach to ensure that the storage mount remains available to the app during key regeneration. For example, assuming that you used **key1** to configure storage mount in your app:
301301
302302
1. Regenerate **key2**.
303303
1. In the storage mount configuration, update the access the key to use the regenerated **key2**.

0 commit comments

Comments
 (0)