Skip to content

Commit 5596feb

Browse files
authored
Merge pull request #311489 from dlepow/certip
[APIM] Managed cert suspension: DNS configuration etc.
2 parents e8cf0e9 + b5363e3 commit 5596feb

3 files changed

Lines changed: 30 additions & 4 deletions

File tree

articles/api-management/breaking-changes/managed-certificates-suspension-august-2025.md

Lines changed: 28 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: dlepow
66
ms.service: azure-api-management
77
ms.topic: reference
88
ai-usage: ai-assisted
9-
ms.date: 01/26/2026
9+
ms.date: 02/06/2026
1010
ms.author: danlep
1111
---
1212

@@ -36,11 +36,37 @@ If you need to add new managed certificates, plan to do so before August 15, 202
3636

3737
If you already have managed certificates for your custom domains, do the following to ensure continued access:
3838

39-
- Ensure that your API Management service allows [inbound traffic from DigiCert IP addresses on port 80](#allow-access-to-digicert-ip-addresses). This access is now required for the certificate autorenewal process.
39+
1. Ensure that your API Management service [allows inbound traffic from DigiCert IP addresses on port 80](#step-1-allow-access-to-digicert-ip-addresses). This access is now required for the certificate autorenewal process.
40+
1. [Configure DNS records](#step-2-configure-dns-records) to resolve your custom domain name.
41+
1. [Allow API Management service access to port 80](#step-3-allow-api-management-service-access-to-port-80) if you have inbound network restrictions in place.
4042

43+
### Step 1: Allow access to DigiCert IP addresses
4144

4245
[!INCLUDE [api-management-managed-certificate-ip-access.md](../../../includes/api-management-managed-certificate-ip-access.md)]
4346

47+
### Step 2: Configure DNS records
48+
49+
Configure DNS records for your custom domain to point to your API Management gateway. The type of DNS record you need to add depends on your API Management tier.
50+
51+
#### DNS records for Developer, Basic, Standard, or Premium tier
52+
53+
1. Add either a [CNAME](/azure/api-management/configure-custom-domain?tabs=custom#cname-record) or A-record with your DNS provider.
54+
55+
1. Add DigiCert as an authorized certificate authority (CA) in Azure DNS. For this, create a specific CAA record set within your domain's DNS zone using the Azure portal or other management tools.
56+
57+
#### DNS records for Consumption tier
58+
59+
1. Add either a [CNAME](/azure/api-management/configure-custom-domain?tabs=custom#cname-record) or [TXT](/azure/api-management/configure-custom-domain?tabs=managed#txt-record) record with your DNS provider. If you configure both, the TXT record takes precedence.
60+
1. Add DigiCert as an authorized certificate authority (CA) in Azure DNS. For this, you need to create a specific CAA record set within your domain's DNS zone using the Azure portal or other management tools
61+
62+
### Step 3: Allow API Management service access to port 80
63+
64+
If you have inbound network restrictions configured for your API Management service, allow the Azure API Management resource provider access on port 80. This is required to allow inbound traffic to support certificate revocation list (CRL) checks, certificate renewal, and management communication.
65+
66+
1. In the Azure portal, go to **Network security groups**.
67+
1. Select the network security group associated with your API Management subnet.
68+
1. Under **Settings** > **Inbound security rules**, add a new rule allowing traffic on port 80 from the **ApiManagement** service tag to the API Management instance.
69+
4470
## Help and support
4571

4672
If you have questions, get answers from community experts in [Microsoft Q&A](https://aka.ms/apim/azureqa/change/captcha-2022). If you have a support plan and need technical help, create a [support request](https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview).

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -126,6 +126,8 @@ API Management offers a free, managed TLS certificate for your domain, if you do
126126
* Supports only public domain names
127127
* Can only be configured when updating an existing API Management instance, not when creating an instance
128128

129+
### Allow access to DigiCert IP addresses
130+
129131
[!INCLUDE [api-management-managed-certificate-ip-access.md](../../includes/api-management-managed-certificate-ip-access.md)]
130132

131133
---

includes/api-management-managed-certificate-ip-access.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,6 @@ ms.author: danlep
77
ms.custom:
88
---
99

10-
### Allow access to DigiCert IP addresses
11-
1210
Starting January 2026, Azure API Management needs inbound access on port 80 to [specific DigiCert IP addresses](https://knowledge.digicert.com/alerts/ip-address-domain-validation?utm_medium=organic&utm_source=docs-digicert&referrer=https://docs.digicert.com/en/certcentral/manage-certificates/domain-control-validation-methods/automatic-domain-control-validation-check.html) to renew (rotate) your managed certificate.
1311

1412
If your API Management instance restricts incoming IP addresses, we recommend that you remove or modify existing IP restrictions by using one of the following methods based on your deployment architecture.

0 commit comments

Comments
 (0)