Skip to content

Commit 87fd913

Browse files
Last look.
1 parent 50e0d88 commit 87fd913

2 files changed

Lines changed: 8 additions & 6 deletions

File tree

includes/api-management-client-certificate-key-vault.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,16 @@
22
author: dlepow
33
ms.service: azure-api-management
44
ms.topic: include
5-
ms.date: 01/11/2023
5+
ms.date: 01/29/2026
66
ms.author: danlep
77
ms.custom: sfi-image-nochange
88
---
99

1010
### Prerequisites for key vault integration
1111

12-
1. If you don't already have a key vault, create one. For information about creating a key vault, see [Quickstart: Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal).
12+
- If you don't already have a key vault, create one. For information about creating a key vault, see [Quickstart: Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal).
1313

14-
1. Enable a system-assigned or user-assigned [managed identity](../articles/api-management/api-management-howto-use-managed-service-identity.md) in API Management.
14+
- Enable a system-assigned or user-assigned [managed identity](../articles/api-management/api-management-howto-use-managed-service-identity.md) in API Management.
1515

1616
[!INCLUDE [api-management-key-vault-access](./api-management-key-vault-access.md)]
1717

@@ -33,7 +33,7 @@ To add a key vault certificate to API Management:
3333

3434
1. In the [Azure portal](https://portal.azure.com), go to your API Management instance.
3535
1. Under **Security**, select **Certificates**.
36-
1. Select **Certificates** > **+ Add**.
36+
1. Select **Certificates**, then **+ Add**.
3737
1. In **Id**, enter a name.
3838
1. In **Certificate**, select **Key vault**.
3939
1. Enter the identifier of a key vault certificate, or choose **Select** to select a certificate from a key vault.
@@ -60,7 +60,7 @@ To upload a client certificate to API Management:
6060

6161
1. In the [Azure portal](https://portal.azure.com), go to your API Management instance.
6262
1. Under **Security**, select **Certificates**.
63-
1. Select **Certificates** > **+ Add**.
63+
1. Select **Certificates**, then **+ Add**.
6464
1. In **Id**, enter a name.
6565
1. In **Certificate**, select **Custom**.
6666
1. Browse to select the certificate .pfx file, and enter its password.

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,9 @@ If [Key Vault firewall](/azure/key-vault/general/network-security) is enabled on
2727

2828
> [!IMPORTANT]
2929
>
30-
> Starting March 2026, trusted service connectivity to Azure services from the API Management gateway by enabling the **Allow Trusted Microsoft Services to bypass this firewall** firewall setting will no longer be supported. To continue accessing these services from the API Management gateway after this change, ensure that you choose a different supported network access option. For control-plane operations, you can continue to use trusted service connectivity. [Learn more](../articles/api-management/breaking-changes/trusted-service-connectivity-retirement-march-2026.md).
30+
> Starting March 2026, trusted service connectivity to Azure services from the API Management gateway by enabling the **Allow Trusted Microsoft Services to bypass this firewall** firewall setting are no longer supported.
31+
>
32+
> To continue accessing these services from the API Management gateway after this change, ensure that you choose a different supported network access option. For control-plane operations, you can continue to use trusted service connectivity. [Learn more](../articles/api-management/breaking-changes/trusted-service-connectivity-retirement-march-2026.md).
3133
3234
#### Virtual network requirements
3335

0 commit comments

Comments
 (0)