Share via

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

Stefan 5 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.

0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rakesh Mishra 9,340 Reputation points Microsoft External Staff Moderator
    2025-12-19T12:44:27.33+00:00

    Hi @Stefan , Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

    I had reached out to you over private message regarding some information.

    After providing that, I raised the support request with internal team to fix the issue. And as confirmed the issue is fixed now.

    I will also update on the timelines of the permanent fix as in when I have an update on that.

    Was this answer helpful?

    1 person found this answer helpful.
  2. Robert Jan Quist 0 Reputation points
    2026-01-15T14:44:08.55+00:00

    We are still facing the same issue. How can we resolve this?

    Was this answer helpful?

  3. 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

  4. AI answer

    2025-12-19T11:20:38.8733333+00:00

    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.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.