Study guide
7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub
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.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub
Key Takeaways Explain This Topic AI
ExpressRoute private peering is not encrypted by default — add MACsec on ExpressRoute Direct for layer 2 or an IPsec site-to-site VPN over private peering for layer 3.
MACsec on ExpressRoute Direct stores its CAK and CKN in Azure Key Vault and protects the link between your edge routers and Microsoft Enterprise Edge routers.
Point-to-site OpenVPN and IKEv2 support Microsoft Entra ID or certificate authentication; SSTP is TLS-based, Windows-only, and capped at 128 concurrent connections.
A custom IPsec/IKE policy lets you force strong ciphers such as AES-256, SHA-384, and DH Group 24 instead of accepting the default proposal set.
A secured virtual hub is a Virtual WAN hub with Azure Firewall or a partner provider deployed inside it, and routing intent sends private and internet traffic through that firewall.
Last updated: August 2026
The Encryption Assumption That Fails the Exam
Candidates routinely assume ExpressRoute is encrypted because it is "private". It is not. ExpressRoute private peering is a dedicated layer 3 circuit through a connectivity provider — it bypasses the public internet, but the packets are not encrypted. If a scenario says "data in transit to Azure must be encrypted to satisfy a regulator", a plain ExpressRoute circuit does not satisfy it. Two answers do.
Option 1 — MACsec on ExpressRoute Direct (layer 2)
ExpressRoute Direct gives you 10 Gbps or 100 Gbps ports directly into the Microsoft global network. On those ports you can enable MACsec (IEEE 802.1AE) , which encrypts the layer 2 link between your edge routers and the Microsoft Enterprise Edge (MSEE) routers.
The connectivity association key (CAK) and connectivity association key name (CKN) are stored as secrets in Azure Key Vault , and the ExpressRoute Direct resource is granted access with a managed identity.
Cipher options are GCM-AES-128 and GCM-AES-256 (and their XPN variants for extended packet numbering).
MACsec protects the link , not end-to-end sessions, and it is only available on ExpressRoute Direct — not on provider-managed circuits.
Option 2 — IPsec over ExpressRoute private peering (layer 3)
Run a site-to-site VPN tunnel through the ExpressRoute private peering so the payload is IPsec-encrypted end to end between your on-premises VPN device and an Azure VPN gateway. This works on any ExpressRoute circuit, including provider-managed ones, at the cost of gateway throughput and some latency.
Site-to-Site VPN Hardening
A site-to-site connection uses IKE (IKEv1 or IKEv2) plus IPsec. The default Azure proposal set is broad for interoperability, which means it will accept algorithms your security policy would reject. Custom IPsec/IKE policy on the connection is the control:
Phase Configurable elements
IKE (Phase 1) Encryption (AES256/AES128/GCM), integrity (SHA384/SHA256), DH group (2, 14, 19, 20, 24, ECP256/384)
IPsec (Phase 2) Encryption (AES256/GCM), integrity, PFS group , SA lifetime in seconds and kilobytes
Setting Perfect Forward Secrecy (PFS) means a compromised long-term key cannot decrypt previously captured sessions. Also enable UsePolicyBasedTrafficSelectors only when the on-premises device requires it, and prefer IKEv2 — IKEv1 is legacy and limited to older gateway SKUs.
Additional hardening: use active-active gateways with two public IPs for resilience, choose a zone-redundant (AZ) gateway SKU in supported regions, and use BGP so failover is automatic rather than route-table surgery.
Point-to-Site VPN Security
Point-to-site (P2S) lets individual clients dial in without a device tunnel.
Tunnel type Transport Authentication options Notes
OpenVPN TLS over TCP 443 Certificate, Microsoft Entra ID , RADIUS Best firewall traversal; required for Entra ID authentication
IKEv2 IPsec/IKE, UDP 500 and 4500 Certificate, RADIUS Native OS clients; blocked by restrictive outbound firewalls
SSTP TLS over TCP 443 Certificate, RADIUS Windows only , capped at 128 concurrent connections
Microsoft Entra ID authentication (OpenVPN only) is the security-relevant choice, because it brings the VPN under Conditional Access : you can demand MFA, a compliant device, or a trusted location before a tunnel is established, and you can revoke access by disabling the user rather than by revoking a certificate. Certificate authentication instead relies on a root certificate uploaded to the gateway, and revocation means maintaining a thumbprint revocation list on the gateway.
The Basic gateway SKU is legacy: it does not support IKEv2, OpenVPN, Entra ID authentication, active-active, or zone redundancy. Any hardening scenario implies VpnGw1–VpnGw5 (or their AZ variants).
Virtual WAN and the Secured Virtual Hub
Azure Virtual WAN is a Microsoft-managed hub-and-spoke backbone. Each virtual hub terminates VPN, ExpressRoute, and point-to-site connections and connects spoke virtual networks, with transitive routing handled by the platform.
A secured virtual hub is a virtual hub with a security provider deployed inside it:
Azure Firewall (managed through Azure Firewall Manager ), or
A supported partner security provider for internet-bound traffic.
Routing intent is how you make the firewall actually see traffic. Instead of hand-crafting route tables on every spoke, you declare intent at the hub:
Internet traffic → next hop Azure Firewall (protects egress and enforces application rules).
Private traffic → next hop Azure Firewall (inspects VNet-to-VNet, branch-to-VNet, and branch-to-branch flows, giving you east-west inspection).
Virtual WAN also enforces useful constraints: you cannot attach NSGs to hub-managed subnets, so the firewall policy in the hub is the enforcement point rather than a patchwork of subnet rules. Firewall policies themselves are hierarchical — a base policy owned by the security team, inherited by child policies that application teams extend but cannot loosen.
Choose a secured virtual hub when the scenario mentions many branches, global transit, or "managed hub"; choose a customer-managed hub VNet with Azure Firewall when the scenario needs custom NVAs, unusual subnetting, or fine-grained control over the hub itself.