Skip to content

Commit a08b49b

Browse files
committed
validation
1 parent 5a3e0f5 commit a08b49b

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/api-management/api-management-howto-use-managed-service-identity.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -149,14 +149,16 @@ The following example shows an Azure Resource Manager template that uses the sys
149149

150150
#### Prerequisites
151151

152-
* An API Management service instance configured with a system-assigned managed identity. To create the instance, you can use an [Azure Quickstart Template](https://azure.microsoft.com/en-us/resources/templates/api-management-create-with-msi/).
152+
* An API Management service instance configured with a system-assigned managed identity. To create the instance, you can use an [Azure Quickstart Template](https://azure.microsoft.com/resources/templates/api-management-create-with-msi/).
153153
* An Azure Key Vault instance in the same resource group, hosting a certificate that will be used as a custom domain certificate in API Management.
154154

155-
The following template contains the following steps. When you run the template, provide parameter values appropriate for your environment.
155+
The following template contains the following steps.
156156

157157
1. Update the access policies of the Azure Key Vault instance and allow the API Management instance to obtain secrets from it.
158158
1. Update the API Management instance by setting a custom domain name through the certificate from the Key Vault instance.
159159

160+
When you run the template, provide parameter values appropriate for your environment.
161+
160162
```json
161163
{
162164
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",

0 commit comments

Comments
 (0)