You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/key-vault/general/tutorial-net-create-vault-azure-web-app.md
+13-3Lines changed: 13 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,7 +101,7 @@ FTP and local Git can deploy to an Azure web app by using a *deployment user*. O
101
101
102
102
To configure the deployment user, run the [az webapp deployment user set](/cli/azure/webapp/deployment/user?view=azure-cli-latest#az-webapp-deployment-user-set) command. Choose a username and password that adheres to these guidelines:
103
103
104
-
- The username must be unique within Azure, and for local Git pushes, must not contain the ‘@’ symbol.
104
+
- The username must be unique within Azure, and for local Git pushes, must not contain the ‘@’ symbol.
105
105
- The password must be at least eight characters long, with two of the following three elements: letters, numbers, and symbols.
106
106
107
107
```azurecli-interactive
@@ -280,10 +280,20 @@ using Azure.Identity;
280
280
usingAzure.Security.KeyVault.Secrets;
281
281
```
282
282
283
-
Add these three lines before the `app.UseEndpoints` call, updating the URI to reflect the `vaultUri` of your key vault.
283
+
Add these lines before the `app.UseEndpoints` call, updating the URI to reflect the `vaultUri` of your key vault. Below code is using ['DefaultAzureCredential()'](/dotnet/api/azure.identity.defaultazurecredential?view=azure-dotnet) for authentication to key vault, which is using token from application managed identity to authenticate. It is also using exponential backoff for retries in case of key vault is being throttled.
0 commit comments