From a1dbe72410e189a09ade07926d2ae902076c0c22 Mon Sep 17 00:00:00 2001 From: Paul Yuknewicz Date: Wed, 29 May 2024 20:45:01 -0700 Subject: [PATCH] Fixes check for "pinning localized MSFT doc" by removing en-us from URL Signed-off-by: Paul Yuknewicz --- .github/iac/swa/readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/iac/swa/readme.md b/.github/iac/swa/readme.md index eb8211849..80d88015c 100644 --- a/.github/iac/swa/readme.md +++ b/.github/iac/swa/readme.md @@ -28,7 +28,7 @@ setx AZURE_RESOURCE_GROUP "rg-dapr-docs-test" setx IDENTITY_RESOURCE_GROUP "rg-my-identities" ``` -This assumes you have an existing [user-assigned managed identity](https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp) (see L39 in `./infra/main.bicep` to use or modify name) in a resource group that you can reference as the runtime identity of this static web app. We recommend storing this in a different resource group from your application, to keep the permissions and lifecycles separate of your identity and your web app. We also recommend narrowly limiting who has access to view, contribute or own this identity, and also only apply it to single resource scopes, not to entire resource groups or subscriptions, to avoid elevation of priviledges. +This assumes you have an existing [user-assigned managed identity](https://learn.microsoft.com/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp) (see L39 in `./infra/main.bicep` to use or modify name) in a resource group that you can reference as the runtime identity of this static web app. We recommend storing this in a different resource group from your application, to keep the permissions and lifecycles separate of your identity and your web app. We also recommend narrowly limiting who has access to view, contribute or own this identity, and also only apply it to single resource scopes, not to entire resource groups or subscriptions, to avoid elevation of priviledges. 2) Deploy using the Azure Dev CLI