Skip to content

Commit eb803bf

Browse files
committed
feedback
1 parent 278886e commit eb803bf

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -133,6 +133,8 @@ The following configurations are required if you want to use API Management to a
133133

134134
## Supported scenarios that use system-assigned identity
135135

136+
Following are some common scenarios for using a system-assigned managed identity in Azure API Management.
137+
136138
### Obtain a custom TLS/SSL certificate for the API Management instance from Key Vault
137139

138140
You can use the system-assigned identity of an API Management instance to retrieve custom TLS/SSL certificates that are stored in Key Vault. You can then assign these certificates to custom domains in the API Management instance. Take these considerations into account:
@@ -445,6 +447,8 @@ The `principalId` property is a unique identifier for the identity that's used f
445447
446448
## Supported scenarios that use user-assigned managed identities
447449

450+
Following are some common scenarios for using a user-assigned managed identity in Azure API Management.
451+
448452
### Obtain a custom TLS/SSL certificate for the API Management instance from Key Vault
449453

450454
You can use a user-assigned identity to establish trust between an API Management instance and Key Vault. This trust can then be used to retrieve custom TLS/SSL certificates that are stored in Key Vault. You can then assign these certificates to custom domains in the API Management instance.

0 commit comments

Comments
 (0)