Skip to content

Commit 7f8308f

Browse files
authored
Merge pull request #120279 from ashishsinghbhu/patch-4
Clarifying that adding service endpoint to Storage account is not same as creating storage account in a private network
2 parents cfe7d22 + f26ffe5 commit 7f8308f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-resource-manager/templates/deployment-script-template.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -660,7 +660,7 @@ The identity that your deployment script uses needs to be authorized to work wit
660660
With Microsoft.Resources/deploymentScripts version 2023-08-01, you can run deployment scripts in private networks with some additional configurations.
661661

662662
- Create a user-assigned managed identity, and specify it in the `identity` property. To assign the identity, see [Identity](#identity).
663-
- Create a storage account in the private network, and specify the deployment script to use the existing storage account. To specify an existing storage account, see [Use existing storage account](#use-existing-storage-account). Some additional configuration is required for the storage account.
663+
- Create a storage account, and specify the deployment script to use the existing storage account. To specify an existing storage account, see [Use existing storage account](#use-existing-storage-account). Some additional configuration is required for the storage account.
664664

665665
1. Open the storage account in the [Azure portal](https://portal.azure.com).
666666
1. From the left menu, select **Access Control (IAM)**, and then select the **Role assignments** tab.

0 commit comments

Comments
 (0)