Azure

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.

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

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

As all Azure web applications are directly available over Internet, hence public, most of the times I need to have some form of protection for them, like an Web Application Firewall