Azure API management helps in creating consistent API gateways for back-end services. API management provides methods for a successful API program through developer engagement, business insights, and protection. It is a great service for abstracting your back-end services and present a set of APIs using a single HTTPs endpoint. Within no time, API management became every developer’s favorite tool. But organizations have common questions and queries when it comes to Azure API management, and some of them are:

  • How can we protect the internet-facing public endpoint of API management?
  • How can we selectively expose some APIs externally whilst keeping all other APIs internal?

Microsoft has a few solutions to the above questions. The key components are:

  • API management deployed in “internal” VNET mode
  • Application gateway for exposing a subset of API’s externally

Although the blueprint provided by Microsoft works well, it somehow eliminates several key elements to get it up and running. Now let’s say if you want to find out how APIs deemed “external” are accessible via the internet? Is it through API-M or App Gateway?

Well, it turns out that the solution is a combination of both. Either we can create separate URLs for external and internal within API-M or a path-based routing rule can be created within the application gateway. Check out this link for a detailed guide to answer the above questions >>>

Azure API Management and Application Gateway integration

Azure Blogs

Translate »