Skip to content

Commit afabe81

Browse files
committed
format
1 parent 584dd17 commit afabe81

1 file changed

Lines changed: 2 additions & 4 deletions

File tree

articles/api-management/backends.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: api-management
55
author: dlepow
66
ms.service: azure-api-management
77
ms.topic: concept-article
8-
ms.date: 11/14/2025
8+
ms.date: 11/20/2025
99
ms.author: danlep
1010
ms.custom:
1111
- build-2024
@@ -100,8 +100,6 @@ If the backend service is secured with a certificate issued by a well-known CA,
100100

101101
If the backend service uses a custom CA certificate, you can reference the custom CA certificate in the backend entity. You might need to do this step to establish trust for the backend server certificate - for example, with self-signed certificates, untrusted root certificates, or partial certificate chains.
102102

103-
104-
105103
> [!NOTE]
106104
> Currently, you can only configure CA certificate details in a backend entity in the [v2 tiers](v2-service-tiers-overview.md).
107105
@@ -115,7 +113,7 @@ To add CA certificate details, follow these steps:
115113
1. Select **Add**.
116114
1. Select **Create**.
117115

118-
:::image type="content" source="media/backends/ca-certificate.png" alt-text="Screenshot of configuring CA certificate details for a backend in the portal.":::
116+
:::image type="content" source="media/backends/ca-certificate.png" alt-text="Screenshot of configuring CA certificate details for a backend in the portal.":::
119117

120118
> [!NOTE]
121119
> When you configure details of a custom CA certificate in the backend entity, API Management always validates the certificate name and certificate chain, regardless of whether you enable or disable validation settings in the backend's `backendTlsProperties`.

0 commit comments

Comments
 (0)