Share via

APIM Standard v2 Developer Portal shows azure-api.net instead of custom gateway domain

Stefan 0 Reputation points
2025-12-19T11:20:25.9+00:00

We have an API Management instance on the Standard v2 tier.

Our gateway custom domain is correctly configured and healthy (for example: https://<custom-domain>).

However, the Developer Portal still displays the default *.azure-api.net URL in the API documentation and “Try it” console, instead of our custom domain.

Steps we tried:

  • Republished the Developer Portal
  • Cleared browser cache and service worker
  • Verified DNS and certificate configuration

Impact:

  • Developers copy the wrong base URL from the portal
  • Leads to integration issues when the expected custom domain is not used

This looks like the Standard v2 bug described here: Issues with custom domains in APIM Standard v2

We's appreciate an ETA for rollout of the fix in our region.

Our gateway custom domain is correctly configured and healthy (for example: https://<custom-domain>).

However, the Developer Portal still displays the default *.azure-api.net URL in the API documentation and “Try it” console, instead of our custom domain.

Steps we tried:

  • Republished the Developer Portal
  • Cleared browser cache and service worker
  • Verified DNS and certificate configuration

Impact:

  • Developers copy the wrong base URL from the portal
  • Leads to integration issues when the expected custom domain is not used
Azure API Management
Azure API Management
An Azure service that provides a hybrid, multi-cloud management platform for APIs.

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-12-19T11:20:38.8733333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It appears that you are experiencing an issue where the Developer Portal for your Azure API Management instance on the Standard v2 tier is still displaying the default *.azure-api.net URL instead of your configured custom domain. This can indeed lead to confusion for developers who may inadvertently use the wrong base URL for integration.

    From the context provided, it seems that the issue you are facing is a known bug related to custom domains in the Standard v2 tier. Unfortunately, the specific details regarding the ETA for a fix rollout in your region are not available in the context provided. It is advisable to keep an eye on updates from Microsoft regarding this issue or to reach out to Azure support for more specific timelines.

    In the meantime, ensure that all configurations are correct and consider informing your developers about the current situation to mitigate any potential integration issues until the problem is resolved.

  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.