An Azure service that provides a hybrid, multi-cloud management platform for APIs.
Hello @Mohamed Farees M
Hey Mohamed — I see what you’re running into. Based on the info you shared, this looks consistent with the managed certificate creation being temporarily suspended for APIM custom domains during the migration window (Aug 15, 2025 → Jun 30, 2026) and the behavior you describe (Portal showing the warning and blocking creation).
- During the suspension period, when you go to APIM → Custom domains → Add → Managed (Preview), the portal will show that managed-certificate request is temporarily not supported.
- Per the published change, existing managed certificates are expected to auto-renew and continue working normally, but new managed certificates can’t be created during the suspension window.
So even if you’re past the end date, if the backend feature flag/backend capability hasn’t been re-enabled yet in your tenant/region, you may still see the same “can’t create managed certificates” behavior.
As a workaround:
Since the portal managed option is blocked, the supported workaround is to bring your own certificate:
- Obtain a certificate from a trusted third-party (for example, DigiCert/Let’s Encrypt) and upload it to APIM for the custom domain.
- Your certificate can be uploaded directly in APIM as a .pfx (includes private key), or referenced from Azure Key Vault (recommended approach for certificate handling).
If your APIM is in a restricted network setup (or you’re relying on certificate revocation/renewal connectivity), ensure that:
- Port 80 access is allowed to the APIM instance from the
ApiManagementservice tag, because the change doc calls out that port 80 access is required for CRL checks, renewal, and management communication.
The community and KB content you referenced indicates the managed-certificate capability is controlled as a platform change and may not instantly flip back exactly at the date for every customer. If you confirm the portal still blocks creation with the same message after Jun 30, 2026, it’s likely a feature availability/back-end re-enable issue rather than something you misconfigured.
Hello @Mohamed Farees M If the assistance was helpful, kindly take a moment to click on
and click on Yes for was this answer helpful. And, if you have any further query do let us know.