An Azure service that provides a hybrid, multi-cloud management platform for APIs.
Thank you for reaching out to Microsoft Q&A.
Based on the current Azure API Management (APIM) documentation and platform behavior, there is no supported, APIM‑native way to enforce HTTPS‑only access or to configure an HTTP → HTTPS redirect specifically for a Developer Portal custom domain.
When using a custom domain for the Developer Portal, Azure API Management does not expose any configuration or setting that allows you to:
- Disable HTTP access for the Developer Portal endpoint, or
- Configure an automatic HTTP - HTTPS redirection within APIM itself
The Azure API Management documentation and security baseline focus on general best practices (for example, recommending encrypted protocols such as HTTPS/WSS for APIs and data-in-transit protection). However, they do not document any feature, toggle, or policy that enforces HTTPS-only behavior on the Developer Portal custom domain endpoint or performs protocol-level redirection for it.
Key clarification for security / compliance documentation
APIM platform limitation:
As of now, this is a platform limitation of Azure API Management. There is no supported, built‑in capability within APIM to force HTTPS‑only access or redirect HTTP traffic to HTTPS for the Developer Portal custom domain. [learn.microsoft.com]
Scope of existing HTTPS enforcement:
APIM does support TLS/HTTPS for custom domains and requires valid certificates, but this only ensures HTTPS availability, not HTTP disablement or redirection behavior for the Developer Portal endpoint.
Common workaround (outside APIM)
While not part of APIM itself, many customers address this requirement by placing a service such as Azure Front Door or Azure Application Gateway in front of APIM, where:
HTTP can be disabled entirely, or
HTTP → HTTPS redirection can be enforced at the edge
This workaround is external to APIM and should be documented as such if adopted.