Skip to content

Commit a094065

Browse files
author
gitName
committed
[APIM] KV access updates
1 parent 4d26aa6 commit a094065

6 files changed

+35
-10
lines changed

articles/api-management/api-management-howto-properties.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,7 @@ Using key vault secrets is recommended because it helps improve API Management s
6161

6262
[!INCLUDE [api-management-key-vault-access](../../includes/api-management-key-vault-access.md)]
6363

64+
[!INCLUDE [api-management-key-vault-secret-access](../../includes/api-management-key-vault-secret-access.md)]
6465

6566
[!INCLUDE [api-management-key-vault-network](../../includes/api-management-key-vault-network.md)]
6667

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,10 +123,12 @@ The `tenantId` property identifies which Microsoft Entra tenant the identity bel
123123
124124
## Configure Key Vault access using a managed identity
125125

126-
The following configurations are needed for API Management to access secrets and certificates from an Azure key vault.
126+
The following configurations are needed for API Management to access certificates from an Azure key vault.
127127

128128
[!INCLUDE [api-management-key-vault-access](../../includes/api-management-key-vault-access.md)]
129129

130+
[!INCLUDE [api-management-key-vault-certificate-access](../../includes/api-management-key-vault-certificate-access.md)]
131+
130132
[!INCLUDE [api-management-key-vault-network](../../includes/api-management-key-vault-network.md)]
131133

132134
## Supported scenarios using system-assigned identity

articles/api-management/configure-custom-domain.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,7 @@ To fetch a TLS/SSL certificate, API Management must have the list and get secret
9191

9292
[!INCLUDE [api-management-key-vault-access](../../includes/api-management-key-vault-access.md)]
9393

94+
[!INCLUDE [api-management-key-vault-certificate-access](../../includes/api-management-key-vault-certificate-access.md)]
9495

9596
If the certificate is set to `autorenew` and your API Management tier has an SLA (that is, in all tiers except the Developer tier), API Management will pick up the latest version automatically, without downtime to the service.
9697

includes/api-management-key-vault-access.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -19,12 +19,3 @@ ms.author: danlep
1919
1. On the **Principal** tab, **Select principal**, search for the resource name of your managed identity, and then select **Next**.
2020
If you're using a system-assigned identity, the principal is the name of your API Management instance.
2121
1. Select **Next** again. On the **Review + create** tab, select **Create**.
22-
23-
**To configure Azure RBAC access:<br/>**
24-
25-
1. In the left menu, select **Access control (IAM)**.
26-
1. On the **Access control (IAM)** page, select **Add role assignment**.
27-
1. On the **Role** tab, select **Key Vault Secrets User**.
28-
1. On the **Members** tab, select **Managed identity** > **+ Select members**.
29-
1. On the **Select managed identity** page, select the system-assigned managed identity or a user-assigned managed identity associated with your API Management instance, and then select **Select**.
30-
1. Select **Review + assign**.
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
author: dlepow
3+
ms.service: azure-api-management
4+
ms.topic: include
5+
ms.date: 02/21/2025
6+
ms.author: danlep
7+
---
8+
**To configure Azure RBAC access:<br/>**
9+
10+
1. In the left menu, select **Access control (IAM)**.
11+
1. On the **Access control (IAM)** page, select **Add role assignment**.
12+
1. On the **Role** tab, select **Key Vault Certificate User**.
13+
1. On the **Members** tab, select **Managed identity** > **+ Select members**.
14+
1. On the **Select managed identity** page, select the system-assigned managed identity or a user-assigned managed identity associated with your API Management instance, and then select **Select**.
15+
1. Select **Review + assign**.
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
author: dlepow
3+
ms.service: azure-api-management
4+
ms.topic: include
5+
ms.date: 02/21/2025
6+
ms.author: danlep
7+
---
8+
**To configure Azure RBAC access:<br/>**
9+
10+
1. In the left menu, select **Access control (IAM)**.
11+
1. On the **Access control (IAM)** page, select **Add role assignment**.
12+
1. On the **Role** tab, select **Key Vault Secrets User**.
13+
1. On the **Members** tab, select **Managed identity** > **+ Select members**.
14+
1. On the **Select managed identity** page, select the system-assigned managed identity or a user-assigned managed identity associated with your API Management instance, and then select **Select**.
15+
1. Select **Review + assign**.

0 commit comments

Comments
 (0)