Study guide

7.2 Azure Private Endpoints & Private Link Architecture

Designing and Implementing Microsoft Azure Networking Solutions AZ-700

Track your progress as you read

Finished sections get a check mark.

1 Introduction & AZ-700 Exam Overview

0.1 About the AZ-700 Exam: Format, Scoring & Skills Measured

2 Chapter 1: Azure Virtual Networks, Addressing & Subnet Architecture

1.1 VNet Planning, IP Addressing & Subnet Design 1.2 Virtual Network Peering & Global Peering 1.3 Azure NAT Gateway & Outbound Connectivity 1.4 Azure Virtual Network Manager (AVNM) & Network Groups 1.5 Public IP Addresses, Public IP Prefixes & Custom IP Prefixes (BYOIP)

3 Chapter 2: Azure Name Resolution & Core Routing

2.1 Azure DNS & Private DNS Zones 2.2 Azure Private DNS Resolver & Hybrid Name Resolution 2.3 System Routes & User-Defined Routes (UDR) 2.4 BGP & Custom Route Propagation 2.5 Azure Route Server & Dynamic NVA Route Exchange

4 Chapter 3: Hybrid Connectivity with Azure VPN Gateway

3.1 Azure VPN Gateway Architecture & SKUs 3.2 Site-to-Site (S2S) VPN & High Availability 3.3 Point-to-Site (P2S) VPN & Client Authentication 3.4 Azure Extended Network, Always On VPN & Azure Network Adapter

5 Chapter 4: Azure ExpressRoute & Virtual WAN

4.1 Azure ExpressRoute Architecture & Peering Models 4.2 ExpressRoute Routing, Resiliency & Global Reach 4.3 Azure Virtual WAN Architecture & Hub Routing 4.4 ExpressRoute BFD, Monitoring & Connection Troubleshooting

6 Chapter 5: Regional Load Balancing & Application Gateway

5.1 Azure Load Balancer Architecture & Rules 5.2 Azure Application Gateway Architecture & Routing 5.3 Web Application Firewall (WAF) on Application Gateway 5.4 Inbound NAT Rules, Port Forwarding & Health Probe Design

7 Chapter 6: Global Traffic Management & Azure Front Door

6.1 Azure Front Door Architecture & Routing 6.2 Azure Traffic Manager & DNS Load Balancing 6.3 Load Balancing Decision Matrix & Multi-Tier Design 6.4 Web Application Firewall on Azure Front Door

8 Chapter 7: Azure Private Link & Service Endpoints

7.1 Virtual Network Service Endpoints & Policies 7.2 Azure Private Endpoints & Private Link Architecture 7.3 Private Endpoint DNS Integration & Hybrid Resolution 7.4 Azure Private Link Service for Multi-Tenant Solutions

9 Chapter 8: Network Security Groups & Azure Bastion

8.1 Network Security Groups (NSGs) & Application Security Groups (ASGs) 8.2 Azure Bastion Architecture & Secure Remote Access 8.3 Azure Virtual Network Manager Security Admin Rules

10 Chapter 9: Azure Firewall & Security Policies

9.1 Azure Firewall Architecture & Rule Processing 9.2 Azure Firewall Manager & DDoS Protection

11 Chapter 10: Azure Network Observability & Troubleshooting

10.1 Network Watcher Diagnostic Tools 10.2 NSG Flow Logs, VNet Flow Logs & Traffic Analytics 10.3 Network Troubleshooting Scenarios & End-to-End Connectivity 10.4 Azure Monitor Network Insights & Defender for Cloud Network Posture

7.2 Azure Private Endpoints & Private Link Architecture

Key Takeaways Explain This Topic AI

An Azure Private Endpoint is a specialized virtual network interface (NIC) assigned a private IPv4/IPv6 address from a customer subnet, establishing direct private connectivity to a specific Azure PaaS resource or Private Link Service.

Private Link enforces strictly unidirectional connection initiation from consumer to provider, completely eliminating reverse-tunnel intrusion risks and preventing data exfiltration by anchoring connectivity to a discrete resource instance.

Private Endpoints support cross-region, cross-subscription, and cross-tenant architectures over Azure's global SDN fabric without requiring VNet peering, utilizing an explicit approval workflow (Auto vs Manual) for unauthorized subscriptions.

Subnet-level Private Endpoint Network Policies ( PrivateEndpointNetworkPolicies ) can be set to Enabled to enforce Network Security Groups (NSGs) for traffic filtering and User-Defined Routes (UDRs) for next-hop inspection through firewalls.

Unlike Service Endpoints, Private Endpoints fully support hybrid transitive access from on-premises networks across Site-to-Site VPN, ExpressRoute, and peered VNets using standard private IP routing.

Last updated: August 2026

Azure Private Endpoints & Private Link Architecture

While Service Endpoints optimize routing across the Azure backbone, they still require interacting with the PaaS service's public IP address and lack transitive hybrid reachability. Azure Private Link represents the ultimate evolution in private cloud access, bringing Azure PaaS services, customer-owned applications, and third-party SaaS solutions directly inside your Virtual Network's private IP address space.

At the core of this architecture is the Azure Private Endpoint —a specialized virtual network interface (NIC) deployed within a customer-managed subnet. This private network interface is assigned a private IP address drawn directly from the subnet's CIDR block, transforming the remote PaaS service into a first-class private node within the virtual network.

1. Private Endpoint Core Mechanics & Unidirectional Security

When you provision a Private Endpoint for an Azure resource (e.g., an Azure SQL Database or Azure Storage Account), Azure creates a read-only Network Interface inside your specified subnet. +-----------------------------------------------------------------------------+

  • | AZURE PRIVATE ENDPOINT ARCHITECTURE |
  • | |
  • | CUSTOMER VIRTUAL NETWORK (10.2.0.0/16) |
  • | +---------------------------------------------------------------------+ |
  • | | Subnet-App (10.2.1.0/24) | |
  • | | [VM: 10.2.1.10] | |
  • | | | | |
  • | | | (Standard TCP/IP Flow: Dest = 10.2.2.5) | |
  • | | v | |
  • | | Subnet-PrivateEndpoints (10.2.2.0/24) | |
  • | | [Private Endpoint NIC: 10.2.2.5] | |
  • | +---------------------------------------------------------------------+ |
  • | | |
  • | (Azure SDN Encapsulation) |
  • | (Microsoft Global Mesh ) |
  • | v |
  • | MICROSOFT PAAS INFRASTRUCTURE / MULTI-TENANT FABRIC |
  • | +---------------------------------------------------------------------+ |
  • | | Azure SQL Database Instance (Target Resource) | |
  • | | - Public Access: DISABLED (0.0.0.0 / No Public Exposure) | |
  • | | - Private Link Connection: Active & Linked to NIC 10.2.2.5 | |
  • | +---------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------+

Key Architectural Characteristics:

Private IP Allocation: The Private Endpoint receives a private IP (e.g., 10.2.2.5 ) directly from your subnet. You can configure static IP allocation or allow DHCP to assign an address.

Unidirectional Connection Initiation: Communication across a Private Link is strictly one-way in initiation (consumer to provider). Workloads in your VNet can open TCP connections to the PaaS resource, but the PaaS resource cannot initiate inbound network connections into your VNet through the Private Endpoint.

Granular Instance Binding: A Private Endpoint connects to a specific, discrete resource instance (e.g., sqldb-production-eastus or blob sub-resource of storageacct01 ), rather than the entire service. This eliminates data exfiltration because compromised workloads cannot reach unauthorized instances through that endpoint.

Public Network Access Elimination: With Private Endpoints in place, you can configure the PaaS firewall's Public network access setting to Disabled , completely closing the PaaS resource's public IP and internet ingress.

Loading diagram... End-to-End Hybrid and VNet Private Link Connectivity

2. Cross-Region, Cross-Subscription & Cross-Tenant Connectivity

One of the most powerful architectural capabilities of Azure Private Link is its ability to span organizational and regional boundaries without requiring traditional network interconnects.

Cross-Region Private Link

A Private Endpoint deployed in a Virtual Network in East US can connect directly to a PaaS service or Private Link Service hosted in West Europe or Southeast Asia . The traffic is encapsulated and transported securely across Microsoft's dedicated global dark fiber backbone.

No VNet Peering Required: You do not need to configure Global VNet Peering between regions.

Bandwidth & Latency: Cross-region traffic benefits from Microsoft's predictable backbone performance, though standard cross-region data transfer fees apply.

Cross-Subscription & Cross-Tenant Connection Workflow

Private Link allows a consumer in Tenant A / Subscription A to securely connect to a service hosted in Tenant B / Subscription B. When the consumer does not have Azure Role-Based Access Control (RBAC) permissions on the target resource, Azure enforces an asynchronous Connection Approval Workflow . +-----------------------------------------------------------------------------+

  • | CROSS-TENANT PRIVATE LINK APPROVAL WORKFLOW |
  • | |
  • | CONSUMER (Tenant A / Sub A) PROVIDER (Tenant B / Sub B) |
  • | --------------------------- --------------------------- |
  • | 1. Requests PE creation using |
  • | Target Resource ID or Alias |
  • | (State: 'Pending') |
  • | | |
  • | v |
  • | 2. Receives connection request|
  • | in Private Link Center |
  • | 3. Reviews Consumer Request |
  • | and clicks 'Approve' |
  • | | |
  • | 4. Connection State changes to <--------------------------+ |
  • | 'Approved' |
  • | 5. Data Plane traffic starts flowing |
  • +-----------------------------------------------------------------------------+

Connection States Lifecycle:

Pending : The Private Endpoint has been created by the consumer, but the resource owner has not yet granted authorization.

Approved : The resource owner approved the request; the Azure SDN fabric programs the forwarding path and data flows immediately.

Rejected : The resource owner denied the connection request.

Disconnected : The resource owner or consumer severed an existing connection.

3. Private Endpoint Network Policies: NSG & UDR Management

Historically, subnets containing Private Endpoints operated with specialized network policy bypasses: Network Security Groups (NSGs) and User-Defined Routes (UDRs) were completely disabled for Private Endpoint NICs ( PrivateEndpointNetworkPolicies: Disabled ).

Modern Azure networking introduces granular control over Private Endpoint subnet policies via the subnet properties: PrivateEndpointNetworkPolicies . +-----------------------------------------------------------------------------+

  • | PRIVATE ENDPOINT NETWORK POLICIES SETTINGS |
  • | |
  • | Property Value NSG Enforcement UDR Enforcement |
  • | -------------------------------- ------------------ --------------- |
  • | Disabled (Legacy default) Ignored for PE NIC Ignored for PE |
  • | Enabled (or RouteTableEnabled / ENFORCED for PE ENFORCED for PE |
  • | NetworkSecurityGroup..) Traffic Traffic |
  • +-----------------------------------------------------------------------------+
  • 1. Network Security Group (NSG) Enforcement

When NSG policies are Enabled on the Private Endpoint subnet:

Inbound NSG Rules: Evaluated on traffic arriving at the Private Endpoint NIC from client VMs in the VNet or on-premises. You can restrict which source subnets, IP ranges, or ports (e.g., TCP 1433 for SQL or TCP 443 for HTTPS) can communicate with the Private Endpoint.

Outbound NSG Rules: Evaluated on responses returning from the Private Endpoint.

2. User-Defined Route (UDR) Enforcement

When Route Table policies are Enabled on the Private Endpoint subnet:

Traffic Inspection via Firewall / NVA: Administrators can apply a UDR on client subnets pointing to an Azure Firewall (e.g., 10.2.2.5/32 -> Next Hop: VirtualAppliance ), forcing all traffic destined for the Private Endpoint through the firewall for deep packet inspection and intrusion detection (IDPS).

Asymmetric Routing Avoidance: If a UDR is applied on the client subnet pointing to a firewall, the firewall performs Source NAT (SNAT) or the Private Endpoint subnet must route response traffic back through the firewall to maintain stateful connection symmetry.

4. Deep Comparative Analysis: Service Endpoints vs. Private Endpoints

A central focus of the AZ-700 exam is selecting the appropriate private connectivity architecture based on precise functional, security, and topological constraints.

  • Architectural Dimension Virtual Network Service Endpoints Azure Private Endpoints (Private Link)
  • PaaS IP Representation Public IP address (unchanged) Private IP address from customer subnet

Packet Routing Path Direct Azure backbone via VirtualNetworkServiceEndpoint system route Standard VNet local routing across Azure SDN fabric

Hybrid On-Premises Reachability Unsupported (Cannot traverse VPN/ExpressRoute) Fully Supported (Routable across S2S VPN, ExpressRoute, P2S, and Peered VNets)

Scope of Access Grants subnet access to entire PaaS service (all accounts/databases) Grants access to one specific PaaS instance (e.g., single storage account)

Data Exfiltration Protection Requires Service Endpoint Policies (Azure Storage only) Inherent & Architectural (Locked to specific resource ID)

Cross-Tenant / Cross-Region Limited regional scoping; requires complex multi-subscription configuration Native & Global (Supports cross-region, cross-subscription, and cross-tenant with approval)

PaaS Public Network Access Must remain Enabled (restricted to selected networks) Can be completely Disabled (zero internet/public attack surface)

  • DNS Architecture Standard Public DNS Requires Azure Private DNS Zones or custom DNS forwarding
  • Cost & Licensing Free (No additional charge) Hourly billing per endpoint + data processing fees (per GB)

NSG / UDR Support Standard NSG/UDR behavior on client subnet Controlled by PrivateEndpointNetworkPolicies ( Enabled / Disabled )