Study guide

7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance

Microsoft Azure Security Technologies AZ-500

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Azure Security Architecture Foundation

1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles

2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM

2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)

3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity

3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration

4 Chapter 4: Microsoft Entra Application Access & Consent Governance

4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials

5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection

5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door

6 Chapter 6: Secure Azure Networking - Private Access & Monitoring

6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring

7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity

7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance

8 Chapter 8: Public and Edge Access Protection

8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management

9 Chapter 9: Compute, Container & Registry Security

9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control

10 Chapter 10: Storage Security, Access Methods & Data Protection

10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup

11 Chapter 11: Data Platform & Database Security

11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration

12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection

12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc

13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection

13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud

14 Chapter 14: External Attack Surface & Vulnerability Management

14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab

15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation

15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation

7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance

Key Takeaways Explain This Topic AI

Regional virtual network integration secures App Service outbound traffic and requires an empty subnet delegated to Microsoft.Web/serverFarms.

Setting vnetRouteAllEnabled forces all outbound App Service traffic — not just RFC 1918 ranges — through the virtual network and any firewall on it.

Private endpoints control inbound access to App Service; access restrictions apply separately to the SCM/Kudu deployment site.

An App Service Environment v3 with an internal load balancer places both inbound and outbound app traffic inside your virtual network with no public endpoint.

Azure SQL Managed Instance is injected into a delegated subnet that must keep its mandatory NSG rules and route table entries or the instance breaks.

Last updated: August 2026

Two Directions, Two Different Controls

The recurring exam trap in this objective is mixing up inbound and outbound. For App Service and Azure Functions they are governed by completely different features:

Direction Feature What it does

Inbound Private endpoint Assigns a private IP in your VNet; the app is reachable only from the VNet and connected networks

Inbound Access restrictions Allow/deny lists based on IPv4/IPv6 CIDR, service tags , or a virtual network service endpoint

Outbound Regional VNet integration The app’s outbound calls originate inside your subnet, so they can reach private endpoints, NVAs, and on-premises

Outbound vnetRouteAllEnabled Forces all outbound traffic through the VNet instead of just private address ranges

A private endpoint on a web app does not change where the app’s outbound calls come from, and VNet integration does not stop anyone on the internet from reaching the app. Real hardening needs both.

Regional Virtual Network Integration

Requirements and behaviours to memorize:

The integration subnet must be empty and delegated to Microsoft.Web/serverFarms . It cannot host other resources.

Size it generously — the platform consumes addresses during scale-out and slot swaps. A /26 is the practical minimum for anything beyond a lab.

By default only RFC 1918 private ranges and service endpoint traffic are routed into the VNet. Setting vnetRouteAllEnabled = true (historically the WEBSITE_VNET_ROUTE_ALL=1 app setting) sends everything, including internet-bound calls, through the VNet so an Azure Firewall or NVA can inspect and log it. That single setting is what makes egress filtering for App Service real.

Plan support: VNet integration requires Basic, Standard, Premium, or Isolated App Service plans. For Azure Functions it requires Premium (Elastic Premium) , Dedicated , or Flex Consumption ; classic Consumption plan functions cannot integrate with a virtual network , which is a common scenario discriminator.

The SCM site is a separate attack surface

Every App Service has a companion SCM/Kudu site ( <app>.scm.azurewebsites.net ) used for deployment, the console, and log streaming. It has its own access restrictions , and by default they can be inherited from the main site or set independently. Locking the main site while leaving Kudu open to the internet is a real-world finding — and an exam distractor. When you create a private endpoint for the app, the SCM site is reachable over the same private endpoint.

App Service Environment v3

An App Service Environment (ASE) v3 is a single-tenant deployment of App Service injected into your own virtual network on dedicated infrastructure.

  • Deployment mode Inbound address Use case
  • Internal (ILB) ASE Private IP from your subnet No public endpoint at all; internal line-of-business apps
  • External ASE Public VIP Internet-facing apps that still need dedicated infrastructure and VNet-native outbound

Key security properties:

The ASE subnet is delegated to Microsoft.Web/hostingEnvironments and must be dedicated to the ASE. Microsoft recommends a /24 .

An ILB ASE needs a private DNS zone for its domain so clients resolve the internal address, and a certificate that matches that domain.

Outbound traffic can be forced through Azure Firewall with a route table on the ASE subnet, subject to the platform dependencies the ASE requires.

NSGs on the ASE subnet must permit the platform’s required management traffic; blocking it makes the ASE unhealthy rather than merely restricted.

Choose an ILB ASE when the requirement is "no public endpoint and dedicated compute"; choose a multi-tenant plan with a private endpoint when the requirement is only "no public endpoint" — it is far cheaper.

Azure SQL Managed Instance Networking

SQL Managed Instance (SQL MI) is not a public PaaS endpoint with an optional private endpoint. It is injected directly into a subnet of your virtual network , which changes how you secure it.

Mandatory conditions:

The subnet is delegated to Microsoft.Sql/managedInstances and must contain no other resource type.

Size it for the deployment plus growth — a /27 is the minimum , and larger is recommended because address consumption scales with instance count and updates.

The subnet requires a route table and an NSG that preserve the mandatory inbound and outbound rules the service-aided subnet configuration creates for management traffic. Azure will maintain these for you under service-aided configuration; deleting or overriding them puts the instance into a failed state. This is also why AVNM security admin rules skip virtual networks containing SQL MI.

You may add your own rules around the mandatory ones — for example, denying inbound 1433 from everything except the application subnet.

Public endpoint: SQL MI can optionally expose a public endpoint on port 3342 (the private VNet-local endpoint remains 1433). The public endpoint is disabled by default and, when the scenario says "management access from outside the VNet must not be possible", the answer is to leave it disabled and reach the instance through VPN, ExpressRoute, or a jump host. If it must be enabled, restrict it with an NSG rule allowing only known source prefixes and enforce Microsoft Entra-only authentication .

For connectivity, SQL MI supports Proxy and Redirect connection types. Redirect gives lower latency by connecting the client straight to the node after the initial handshake, but requires ports 11000–11999 to be open from the client subnet; Proxy uses only 1433 but adds a hop. Choosing Redirect without opening that port range is a classic troubleshooting scenario.