Networking, VNet Integration & Private Endpoints hosting your Applications
Home » Microsoft  »  Networking, VNet Integration & Private Endpoints hosting your Applications
Networking, VNet Integration & Private Endpoints hosting your Applications

Introduction

When I look at an Azure App Service deployment, one of the first things I consider after getting the application up and running is its network connectivity.

At the beginning, things often look quite straightforward. We deploy an App Service, configure the application, connect a database, and everything works.

But when we start moving towards a production or enterprise environment, the networking requirements become a completely different discussion. For example: 

  • Should the application be accessible from the public internet?

  • How can the application communicate with an Azure SQL Database using a private IP?

  • How do we connect App Service to an internal API?

  • Can it communicate with an on-premises application?

  • How do we control outbound internet traffic?

  • Can we force application traffic through Azure Firewall?

  • How do we make sure that secrets and backend services aren't exposed publicly?

These are the kinds of questions that start coming up when we move beyond a basic App Service deployment.

One thing I have learned is that securing an application isn't just about securing the application itself. We also need to understand how it communicates with everything around it.

That's where Azure App Service networking features become important.

In this part, I want to go through how I look at App Service networking, particularly VNet Integration, Private Endpoints, DNS, outbound connectivity and how these components fit together in a real-world architecture.

How App Service Networking Works

Before getting into VNet Integration and Private Endpoints, there is one important thing to understand.

A standard Azure App Service doesn't automatically run inside your own Azure Virtual Network. This is something that sometimes causes confusion.

When we deploy an App Service using the normal multi-tenant App Service platform, Microsoft manages the underlying infrastructure. We don't directly manage the virtual machines or place the application into our own VNet in the same way we would with a virtual machine.

However, Microsoft provides networking capabilities that allow us to connect the App Service to our virtual network.

There are two directions we need to think about:

Inbound connectivity – How users, employees, or other applications reach our App Service.

Outbound connectivity – How our App Service reaches other services, such as databases, storage accounts, APIs and on-premises systems.

I always try to separate these two requirements when designing the network. As Azure features used for inbound and outbound connectivity are different. For example:

  • VNet Integration is primarily for outbound connectivity.

  • Private Endpoints provide private inbound connectivity to the App Service.

  • Access Restrictions help control which sources can access the public endpoint.

  • NAT Gateway and Azure Firewall can help control outbound traffic.

Understanding this distinction makes the rest of the architecture much easier.

VNet Integration – Allowing App Service to Communicate With Your Network

Imagine that we have deployed an application in Azure App Service, but the database is not publicly accessible. The database is hosted inside a private network, and we only allow connections from approved network locations. How does our App Service communicate with it?

This is where VNet Integration comes in. VNet Integration allows an App Service application to send outbound traffic through a subnet in an Azure Virtual Network. Think of it as giving your application a route into your private network.

For example:

IMAGE

Now the application can communicate with resources in the integrated VNet, peered VNets, and supported resources reachable through VPN or ExpressRoute connectivity.

One important point is that VNet Integration does not make your App Service privately accessible from the VNet. It is designed for outbound connectivity from the application.

What Can We Access Through VNet Integration?

There are quite a few practical scenarios. For example, we can use it to connect an App Service to:

  • Azure SQL Database through a Private Endpoint.

  • Azure Database for PostgreSQL.

  • Azure Storage Accounts.

  • Azure Key Vault.

  • Internal APIs hosted on Azure VMs.

  • Applications hosted in peered VNets.

  • On-premises systems through VPN or ExpressRoute.

This becomes particularly useful when the organization wants to keep backend services private rather than exposing them through public endpoints.

Introduction

When I look at an Azure App Service deployment, one of the first things I consider after getting the application up and running is its network connectivity.

At the beginning, things often look quite straightforward. We deploy an App Service, configure the application, connect a database, and everything works.

But when we start moving towards a production or enterprise environment, the networking requirements become a completely different discussion. For example: 

  • Should the application be accessible from the public internet?

  • How can the application communicate with an Azure SQL Database using a private IP?

  • How do we connect App Service to an internal API?

  • Can it communicate with an on-premises application?

  • How do we control outbound internet traffic?

  • Can we force application traffic through Azure Firewall?

  • How do we make sure that secrets and backend services aren't exposed publicly?

These are the kinds of questions that start coming up when we move beyond a basic App Service deployment.

One thing I have learned is that securing an application isn't just about securing the application itself. We also need to understand how it communicates with everything around it.

That's where Azure App Service networking features become important.

In this part, I want to go through how I look at App Service networking, particularly VNet Integration, Private Endpoints, DNS, outbound connectivity and how these components fit together in a real-world architecture.

Share the Post on:
WhatsApp Image 2025-03-17 at 13.01.27_45cefa7f

I, M Ashfarq Kariapper, currently working as a Cloud Solution Architect / Tech Lead - Infrastructure. My expertise lies in designing and implementing on-prem and cloud solutions, particularly on Microsoft Azure and traditional environment. Possess extensive experience in cloud infrastructure, Data Engineering, and integrating various enterprise systems like SAP and Oracle. Moreover,  I'm passionate about education and community development initiatives supporting local socio-economic projects in Sri Lanka. Also the Co-Founder of International Council for Virtual & Research Education (Pvt) Ltd.