Study guide
5.2 Azure Firewall and Firewall Manager
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
5.2 Azure Firewall and Firewall Manager
Key Takeaways Explain This Topic AI
Azure Firewall is a cloud-native, stateful firewall-as-a-service operating across Layer 3 to Layer 7 with built-in high availability and auto-scaling.
Rule collections are evaluated in strict hierarchical sequence: DNAT rules run first, followed by Network rules, and finally Application rules.
Azure Firewall Premium SKU introduces advanced security capabilities including TLS Inspection, signature-based IDPS, Web Categories, and URL filtering.
Outbound TLS inspection requires a custom Intermediate CA certificate stored in Azure Key Vault, authenticated via Managed Identity.
Azure Firewall Manager centralizes security policy governance across Hub Virtual Networks and Secured Virtual Hubs (Azure Virtual WAN) using hierarchical policies.
Last updated: August 2026
4.2 Azure Firewall and Firewall Manager
Azure Firewall is a managed, cloud-native stateful network security service that secures Azure Virtual Network resources. Operating as a fully managed service with built-in high availability and auto-scaling, Azure Firewall provides centralized Layer 3 to Layer 7 rule enforcement across subscriptions and virtual networks. Centralized policy governance across multi-hub deployments is managed through Azure Firewall Manager .
Azure Firewall SKU Comparison
Azure Firewall is available in three distinct Service Keeping Units (SKUs) tailored to different organizational scale and security requirements:
Feature / Capability Basic SKU Standard SKU Premium SKU
Target Use Case Small/SMB environments (< 250 Mbps) Enterprise L3–L7 perimeter defense High-security & compliance workloads
Max Throughput 250 Mbps 30 Gbps 100 Gbps
Stateful L3–L7 Filtering Yes (IP, Port, Protocol, FQDN) Yes (IP, Port, Protocol, FQDN) Yes (IP, Port, Protocol, FQDN/URL)
- Threat Intelligence Alert-only Alert and Deny Alert and Deny (Enhanced feeds)
- IDPS (Signature-Based) Not Supported Not Supported Supported (67,000+ signatures)
- TLS / SSL Decryption Not Supported Not Supported Supported (Inbound & Outbound)
- URL Filtering & Web Categories FQDN filtering only FQDN filtering only Full URL path + Web Category filtering
- Availability Zones Supported Supported Supported
- Management Integration Firewall Manager Firewall Manager Firewall Manager
- Rule Processing Order & Evaluation Mechanics
Azure Firewall evaluates incoming and outgoing network traffic using a strict, non-configurable rule processing hierarchy.
1. DNAT Rules (Inbound Destination NAT)
Inbound DNAT rules translate a public IP address and port on the firewall to a private IP address and port of a workload VM or load balancer.
DNAT rules are evaluated first .
When a DNAT rule matches, an implicit network allow rule is automatically applied to permit the translated packet through to the backend target.
2. Network Rules
Network rules filter Layer 3 and Layer 4 traffic based on source IP addresses, destination IP addresses, Service Tags, FQDNs (resolved to IPs via firewall DNS proxy), target ports, and protocols (TCP, UDP, ICMP).
Network rules are evaluated second .
Rule collections are evaluated strictly by priority integer (lowest number first).
If a matching Network rule is found, processing terminates immediately (either Allowed or Denied). Application rules are never evaluated if a Network rule matches.
3. Application Rules
Application rules configure Layer 7 filtering for outbound or cross-subnet traffic based on Fully Qualified Domain Names (FQDNs), HTTP/HTTPS headers, MSSQL connection attributes, and Web Categories.
Application rules are evaluated third (only if no Network rule matched the packet).
If no Application rule matches, the packet is dropped by default ( Deny ).
- Advanced Security Capabilities (Premium SKU)
- Intrusion Detection and Prevention System (IDPS)
Azure Firewall Premium incorporates a signature-based IDPS engine analyzing network traffic across all ports and protocols for known exploit patterns, vulnerability probing, and Command-and-Control (C2) botnet traffic.
IDPS operates in one of three selectable modes:
Off: IDPS signature inspection is disabled.
Alert: Inspects traffic and logs signature detections to Log Analytics workspace without blocking traffic.
Alert and Deny: Inspects traffic, logs detections, and actively drops/resets malicious packets.
TLS Inspection Architecture
Because over 80% of enterprise web traffic is encrypted via TLS/SSL, legacy firewalls cannot inspect HTTP payloads without decryption. Azure Firewall Premium performs outbound TLS inspection by intercepting client HTTPS sessions, decrypting payload content for IDPS and URL filtering, and re-encrypting the session toward the target destination.
TLS Certificate Requirements:
Requires an Intermediate Certificate Authority (CA) certificate (or Enterprise Root CA certificate) stored in Azure Key Vault .
Azure Firewall accesses the Key Vault using a User-Assigned Managed Identity .
Client endpoints (VMs) must trust the Root/Intermediate CA certificate in their local OS trusted root certificate store to prevent browser security warnings.
Azure Firewall Manager & Security Governance
Azure Firewall Manager provides centralized security policy management and automated routing configuration across enterprise cloud topologies.
Architecture Deployment Models
Hub Virtual Network: Centralized firewall deployed within a standard Azure Virtual Network hub connected to spoke VNets via VNet Peering.
Secured Virtual Hub (Azure Virtual WAN): Managed hub infrastructure created by Virtual WAN where security policies and routing intents (Automated Routing Intent) direct all inter-spoke and internet egress traffic through Azure Firewall or integrated third-party Security-as-a-Service (SECaaS) partners.
Hierarchical Firewall Policies
Firewall Manager utilizes Firewall Policies that can be shared across multiple firewall instances:
Parent Policy: Maintained by central security teams containing enterprise-wide compliance rules (e.g., global blocklists, mandatory logging).
Child Policy: Inherits all rules from the Parent Policy while allowing business unit teams to append localized application rules. Child policies cannot override or drop explicit deny rules established in the Parent policy.