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
@@ -141,7 +141,7 @@ The following procedure shows how to create a role with the minimum permission,
141
141
142
142
---
143
143
144
-
The samples assign the custom role to the user on the resource group level.
144
+
The samples assign the custom role to the user on the resource group level.
145
145
146
146
When using a Key Vault with the template for a [Managed Application](../managed-applications/overview.md), you must grant access to the **Appliance Resource Provider** service principal. For more information, see [Access Key Vault secret when deploying Azure Managed Applications](../managed-applications/key-vault-access.md).
147
147
@@ -172,9 +172,9 @@ The following template deploys a SQL server that includes an administrator passw
172
172
},
173
173
"resources": [
174
174
{
175
-
"name": "[parameters('sqlServerName')]",
176
175
"type": "Microsoft.Sql/servers",
177
176
"apiVersion": "2015-05-01-preview",
177
+
"name": "[parameters('sqlServerName')]",
178
178
"location": "[resourceGroup().location]",
179
179
"tags": {},
180
180
"properties": {
@@ -195,24 +195,24 @@ In the following parameter file, the key vault secret must already exist, and yo
The previous section showed how to pass a static resource ID for the key vault secret from the parameter. However, in some scenarios, you need to reference a key vault secret that varies based on the current deployment. Or, you may want to pass parameter values to the template rather than create a reference parameter in the parameter file. In either case, you can dynamically generate the resource ID for a key vault secret by using a linked template.
253
253
254
-
You can't dynamically generate the resource ID in the parameters file because template expressions aren't allowed in the parameters file.
254
+
You can't dynamically generate the resource ID in the parameters file because template expressions aren't allowed in the parameters file.
255
255
256
256
In your parent template, you add the nested template and pass in a parameter that contains the dynamically generated resource ID. The following image shows how a parameter in the linked template references the secret.
257
257
@@ -261,109 +261,109 @@ The following template dynamically creates the key vault ID and passes it as a p
0 commit comments