Skip to content

Commit e7a8c31

Browse files
committed
Update documentation via Content Mentor Quick Workspace
1 parent 8d3c29a commit e7a8c31

1 file changed

Lines changed: 7 additions & 3 deletions

File tree

articles/api-management/api-management-howto-mutual-certificates.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: dlepow
77

88
ms.service: azure-api-management
99
ms.topic: how-to
10-
ms.date: 03/30/2026
10+
ms.date: 03/31/2026
1111
ms.author: danlep
1212
ms.custom:
1313
- devx-track-azurepowershell
@@ -48,7 +48,11 @@ We recommend that you use key vault certificates because doing so improves API M
4848
* If you haven't created an API Management instance yet, see [Create an API Management service instance](get-started-create-service-instance.md).
4949
* Configure your backend service client certificate authentication. For information about configuring certificate authentication in Azure App Service, see [Configure TLS mutual authentication in App Service][to configure certificate authentication in Azure WebSites refer to this article].
5050
* Ensure that you have access to the certificate and the password for management in an Azure key vault, or a certificate to upload to the API Management service. The certificate must be in PFX format. Self-signed certificates are allowed.
51-
* If you use a self-signed certificate or other custom CA certificate and your API Management instance is in one of the classic tiers, disable certificate chain validation. See [Disable certificate chain validation for self-signed certificates](#disable-certificate-chain-validation-for-self-signed-certificates) later in this article.
51+
* If you use a self-signed certificate and your API Management instance is in one of the classic tiers, disable certificate chain validation. See [Disable certificate chain validation for self-signed certificates](#disable-certificate-chain-validation-for-self-signed-certificates) later in this article.
52+
53+
> [!NOTE]
54+
> When a client certificate is used by API Management for **outbound authentication** (for example, when API Management presents the certificate to a backend service), you don't need to upload the root or intermediate CA certificates to the API Management CA store. In this scenario, API Management *presents* the client certificate and doesn't perform certificate chain validation.
55+
> Uploading trusted root or intermediate CA certificates is only required when API Management must *validate* a certificate chain, such as during inbound client certificate authentication.
5256
5357
[!INCLUDE [api-management-ca-certificate-v2-tiers](../../includes/api-management-ca-certificate-v2-tiers.md)]
5458

@@ -112,4 +116,4 @@ To delete a certificate, select **Delete** on the ellipsis (**...**) menu:
112116
[Create an API Management service instance]: get-started-create-service-instance.md
113117

114118
[WebApp-GraphAPI-DotNet]: https://github.com/AzureADSamples/WebApp-GraphAPI-DotNet
115-
[to configure certificate authentication in Azure WebSites refer to this article]: ../app-service/app-service-web-configure-tls-mutual-auth.md
119+
[to configure certificate authentication in Azure WebSites refer to this article]: ../app-service/app-service-web-configure-tls-mutual-auth.md

0 commit comments

Comments
 (0)