Cloud Strategy, podcast with Gregor Hohpe

Protecting APIs published on Azure APIM with OAuth 2.0 authorization tokens.

In previous articles I’ve described how an Azure web application can be secured and isolated from Internet traffic using Private Integration Endpoints.
If the security requirements are not draconian, a simpler solution can provide the same results, meaning public internet access to web application is forbidden and traffic between web apps is routed only in the VNET.

As an architect in a company that is basically a “Microsoft shop”, most of my landscape (if not all) is made out of custom applications based on Microsoft technologies and .NET Framework, with versions starting from .NET 2.0 up to .NET 4.5, which are running along enterprise Microsoft applications like Sharepoint, Dynamics, Office 365 and so on.

When you have custom DNS servers for an Azure VNET, then private integration endpoints for web applications are working a bit differently.