We’re excited to announce support for private CNAME records in Azure API Management Premium v2, providing greater flexibility for customers deploying API gateways in private network environments.
Organizations increasingly rely on private networking to securely expose APIs to internal applications, enterprise workloads, and services connected through virtual networks. With this enhancement, customers can now use private DNS CNAME records to resolve custom gateway hostnames to their Azure API Management Premium v2 instances, simplifying DNS management and enabling more flexible private networking architectures.
What's new?
Azure API Management Premium v2 now supports private CNAME resolution for gateway endpoints accessed through private networking.
Previously, customers configuring private DNS for Premium v2 deployments could encounter limitations when using CNAME records, requiring alternative DNS configurations to resolve gateway endpoints.
With this enhancement, customers can configure private CNAME records that point to their API Management gateway hostnames, allowing internal applications to access APIs using familiar, organization-defined DNS names.
Key benefits
Simplified private DNS management
Customers can use CNAME records within their private DNS infrastructure instead of managing direct IP address mappings for every internal gateway alias. This reduces DNS maintenance overhead and simplifies endpoint configuration.
Greater flexibility for enterprise networking
Organizations can align API Management gateway DNS configurations with existing enterprise DNS naming conventions, making it easier to integrate Premium v2 into established private networking environments.
Improved operational efficiency
Using DNS aliases helps decouple internal application configurations from underlying gateway DNS records, reducing the need for application-level changes when DNS mappings are updated.
Support for private API architectures
The enhancement makes it easier to deploy Premium v2 as a centralized API gateway for internal applications and services, including workloads connected through Azure virtual networks and hybrid enterprise networks with appropriate DNS resolution and network connectivity.
Example scenario
Consider an organization deploying Azure API Management Premium v2 to expose APIs privately to applications running within its enterprise network.
The organization wants internal applications to access APIs through a consistent hostname, such as:
api.contoso.com
With private CNAME support, the organization can configure a DNS alias in its private DNS infrastructure:
api.contoso.com. CNAME myapim.azure-api.net.
Internal applications can then resolve the custom hostname through the organization's private DNS infrastructure, while the underlying gateway hostname resolves to the appropriate private endpoint address.
The custom hostname must also be configured on the API Management gateway with an appropriate TLS certificate. DNS aliasing alone does not configure the gateway to accept the custom hostname.
Getting started
To use private CNAME records with Azure API Management Premium v2:
- Deploy or use an existing Azure API Management Premium v2 instance with the appropriate private networking configuration.
- Configure private DNS resolution for the API Management gateway endpoint.
- Create a private CNAME record that points your preferred internal hostname to the gateway hostname.
- Configure the corresponding custom gateway hostname and TLS certificate in API Management.
- Verify that internal clients can resolve the hostname to the expected private IP address and establish secure HTTPS connections.
For more information, see the Azure API Management documentation:
Availability
Private CNAME support is now available for Azure API Management Premium v2, enabling customers to simplify private DNS configurations and integrate API gateways more seamlessly into enterprise networking environments.
This enhancement is part of our continued investment in Azure API Management Premium v2, helping organizations build secure, scalable, and enterprise-ready API architectures.