Study guide
8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication
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
8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication
Key Takeaways Explain This Topic AI
Application Gateway needs its own dedicated subnet, and the v2 SKU requires inbound TCP 65200–65535 from the GatewayManager service tag or the gateway becomes unhealthy.
Listener certificates should be referenced from Azure Key Vault through a user-assigned managed identity rather than uploaded as PFX files.
End-to-end TLS re-encrypts traffic to the backend and requires the backend certificate to be trusted by the gateway.
Mutual TLS is configured with an SSL profile containing a trusted client CA certificate chain, and can be applied per listener.
A TLS policy sets the minimum protocol version and cipher suite list; predefined policies are convenient, custom policies are how you ban weak ciphers.
Last updated: August 2026
Where Application Gateway Fits
Application Gateway is a regional, layer 7 reverse proxy . It terminates HTTP and HTTPS, makes routing decisions on host name and URL path, and is the hosting point for the regional Web Application Firewall (WAF_v2) . Compare it with the other front-end services:
Service Layer Scope WAF Typical use
Application Gateway 7 (HTTP/S) Regional, inside your VNet Yes (regional WAF) Internal and regional web apps; mutual TLS; VNet-native backends
- Azure Front Door 7 (HTTP/S) Global edge Yes (edge WAF) Global apps, edge caching, multi-region failover
- Azure Firewall 3–7 Regional No (IDPS instead) Egress control, non-HTTP protocols, network segmentation
- Azure Load Balancer 4 Regional No TCP/UDP distribution
A common enterprise pattern chains them: Front Door at the edge for global routing and DDoS/WAF, then Application Gateway regionally for VNet-internal routing and mutual TLS.
Deployment Prerequisites That Break Things
Dedicated subnet. The gateway must live in its own subnet containing no other resource type. Microsoft recommends a /24 ; the platform reserves addresses for each instance and for scale-out.
Inbound TCP 65200–65535 from the GatewayManager service tag must be allowed on the subnet NSG for v2 SKUs. This is control-plane traffic protected by certificates; blocking it does not "harden" the gateway, it makes the gateway report unhealthy and stop receiving configuration. This is one of the most reliably tested facts on the objective.
Outbound internet access is required for CRL/OCSP checks and platform communication. If you force-tunnel 0.0.0.0/0 off the gateway subnet, the gateway breaks unless the required destinations remain reachable.
Network isolation (private-only deployment) allows a v2 gateway with a private frontend IP only , no public IP, which is what you deploy behind Front Door or for internal line-of-business apps.
- Certificates and TLS Policy
- Key Vault integration
Rather than uploading a PFX to the gateway, reference the certificate in Azure Key Vault :
Create a user-assigned managed identity and attach it to the gateway.
Grant that identity Key Vault Secrets User (RBAC model) or a get-secret access policy.
Point the HTTPS listener at the Key Vault certificate's secret identifier.
Benefits: rotation happens in Key Vault and the gateway picks up the new version, the private key never sits in a deployment pipeline, and access is auditable. If the gateway's Key Vault firewall blocks it, add the gateway subnet or use a private endpoint plus the trusted-services allowance.
TLS policy
A TLS (SSL) policy controls the minimum protocol version and the cipher suite list .
Predefined policies (for example the 2022 policy set) are curated by Microsoft and update over time.
A custom policy lets you pin the minimum version to TLS 1.2 or 1.3 and enumerate exactly which cipher suites are offered — the answer whenever a scenario says "the audit found CBC ciphers / TLS 1.0 must be impossible".
Policies can be applied gateway-wide or per listener through an SSL profile .
End-to-end TLS
By default the gateway decrypts at the listener and may talk plain HTTP to the backend. End-to-end TLS re-encrypts on the backend side. For a v2 gateway, the backend's certificate must be trusted: upload the backend's root certificate as a trusted root certificate on the backend HTTP setting, or use a certificate issued by a well-known CA. Self-signed backend certificates without this step produce a 502 with an "unhealthy backend" probe result.
Mutual TLS (Client Certificate Authentication)
Mutual TLS makes the client prove its identity with a certificate before the request is proxied. Configuration:
Build an SSL profile .
Upload the trusted client CA certificate chain — the full chain, not just the leaf.
Associate the SSL profile with the listener that must require client certificates.
Optionally enable certificate chain verification and use header rewrite to pass client certificate attributes (subject, issuer, thumbprint, validity) to the backend so the app can authorize on them.
Mutual TLS is the standard answer for partner-to-partner APIs, IoT device fleets, and B2B integrations where the caller cannot use an interactive identity. Remember that it authenticates the transport , not a user — the backend still needs authorization logic.
Layered Controls Around the Gateway
WAF_v2 policy attached to the gateway, a listener, or a path-based rule — Prevention mode with a managed core rule set, plus custom rules for rate limiting and geo-filtering.
NSG on the backend subnet allowing traffic only from the gateway subnet, so nobody can bypass the gateway by hitting the VM directly.
Private endpoints on backend PaaS resources , so the gateway is the only reachable path.
Health probes with custom match conditions , so a compromised or broken backend is removed from rotation instead of serving errors.
Diagnostic logs ( ApplicationGatewayAccessLog , ApplicationGatewayFirewallLog , ApplicationGatewayPerformanceLog ) shipped to a Log Analytics workspace, which is what feeds Microsoft Sentinel detections for web attacks.