Azure-docs: What is the meaning of "API Management service only responds on its configured Hostnames." ?
The documentation note says - API Management service only responds on its configured Hostnames.
What is the meaning of this?
Document Details
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 8d854b3c-f9f9-7f6a-f889-e19acac2961c
- Version Independent ID: ed544e54-d24b-2f37-05b6-8b60eacd2026
- Content: How to use Azure API Management with virtual networks
- Content Source: articles/api-management/api-management-using-with-vnet.md
- Service: api-management
- GitHub Login: @vlvinogr
- Microsoft Alias: apimpm
Anand-Moghe
All 4 comments
@Anand-Moghe Since APIM is deployed in VNETs owned by a user, one might expect that they can access the instance via its private IP. But that is not the case and the same is conveyed through that note.
The only way to access APIM is via its hostnames
<serviceName>.azure-api.net<serviceName>.portal.azure-api.net<serviceName>.management.azure-api.net<serviceName>.scm.azure-api.net
The reason for this is because requests are routed to the corresponding (internal) service based on the hostname and also through a load balancer when working with multiple instances of APIM.
PramodValavala-MSFT
on 21 Feb 2019
@PramodValavala-MSFT Thank you very much. So I am in that exact situation. The APIM is installed in VNET with External setting. There is no problem accessing the developer portal from public internet. But the users in a work station inside on-premise VNET is unable to access the developer portal. I think this explains why.
Anand-Moghe
on 21 Feb 2019
This answer explain the question so closing it.
Anand-Moghe
on 21 Feb 2019
@Anand-Moghe Glad we could help! 😄
PramodValavala-MSFT
on 21 Feb 2019
Related issues
spottedmahn
·
3Comments
jamesgallagher-ie
·
3Comments
paulmarshall
·
3Comments
AronT-TLV
·
3Comments
jharbieh
·
3Comments
Most helpful comment
@Anand-Moghe Since APIM is deployed in VNETs owned by a user, one might expect that they can access the instance via its private IP. But that is not the case and the same is conveyed through that note.
The only way to access APIM is via its hostnames
<serviceName>.azure-api.net<serviceName>.portal.azure-api.net<serviceName>.management.azure-api.net<serviceName>.scm.azure-api.netThe reason for this is because requests are routed to the corresponding (internal) service based on the hostname and also through a load balancer when working with multiple instances of APIM.