Access restrictions can lock down your inbound traffic to a set of address blocks.Įach of those features satisfies a specific situation and there are trade offs.With private endpoints, you can reach the web app from anywhere that has network access to the private endpoint address. Private endpoints prevent data exfiltration and secure the listening service.With Service Endpoints, the source address must be in an Azure Virtual Network subnet. Service endpoints secure the listening service.There are multiple features that could be used for this purpose: They all involve securing your API application’s inbound traffic. There are multiple ways to secure your API applications so that they can only be reached from your front end applications. By itself this is not a complex concept, but when a user wants to secure the API applications so they are not internet accessible the architecture becomes more complex. The obvious question to start with is, what is a multi-tier web application? A multi-tier web application is an application with a front end that makes calls to one or more API applications behind it. In this article, you will learn how to build network-secured, multi-tier web applications in the multi-tenant App Service. In an App Service Environment you get a single tenant version of App Service that runs in your Azure Virtual Network.

Your apps are always secured but they share the network, address space, front ends, and some other components. In the multi-tenant service there are thousands of customers on the same infrastructure. The Azure App Service is offered as two deployment types: the multi-tenant service and the App Service Environment. Zero to Hero with App Service, Part 7: Multi-tier web applications

Azure web app deployment slot vnet