Developer Portal uses built-in gateway hostname instead of custom domain for API endpoints and “Try it” requests

[man-tas]

Bug description

The Developer Portal displays and uses the built-in gateway hostname (e.g., https://<service-name>.azure-api.net) for API endpoints and “Try it” requests, even when a custom Gateway domain is configured and working. Testing the API from the Azure Portal “Test” tab uses the custom domain correctly; only the Developer Portal keeps showing and calling the built-in URL.

Reproduction steps

1. Configure a custom domain for the Gateway (e.g., api.example.com) in APIM and verify it’s working (valid cert, DNS OK).
2. Publish an API with base path (e.g., /v1).
3. Open the Managed Developer Portal and navigate to the API details page.
4. Observe the endpoint shown in the header/samples and in the Try it console.
5. Send a request via Try it.
6. Compare with the same API called from Azure Portal → APIM → APIs → Your API → Test tab (which uses the custom domain).

Actual behavior

• Developer Portal displays and calls the API using the built-in hostname https://<service-name>.azure-api.net/....
• The Host and request URL in the browser’s dev tools also reflect the built-in hostname.

Expected behavior

• Developer Portal should display and use the configured custom Gateway domain (e.g., https://api.example.com/...) in the UI, samples, and “Try it” requests — or provide a clear setting to choose which hostname to use.

Is self-hosted portal?

No (Managed Developer Portal).

[man-tas]

@Onatolich any ideas?

[tlonergan]

I would like to add a vote to this. I am also seeing this issue, and it effecting the communication of a production release

[scottmckendry]

I was having this issue up until yesterday, but it seems to have fixed itself now?

[h-fletcher]

We also have this issue - seems to only affect APIM v2 tiers as our v1 tiers don't have this bug.
https://learn.microsoft.com/en-us/answers/questions/5671934/apim-standard-v2-developer-portal-shows-azure-api

[tlane-convey]

We are also having this issue, again also affecting a production release. Is there any update on this?

[jjquist]

It looks like you cannot resolve the issue by yourself. You need to contact Microsoft Support for now to resolve the issue. They helped us to get the right host-url in the developer portal.