Study guide

7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes

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.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes

Key Takeaways Explain This Topic AI

Security admin rules are evaluated before NSG rules, apply at the virtual network level, and add an Always Allow action that NSGs cannot override.

Only one security admin configuration can be deployed per region, but a configuration may hold multiple rule collections.

Security admin rule priority is 1–4096 with lower numbers winning, and rules skip subnets containing Azure Firewall, Bastion, Application Gateway, VPN, ExpressRoute, Route Server, and Virtual WAN gateways.

Azure route selection uses longest prefix match first; on a tie, a user-defined route beats a BGP route, which beats a system route.

Forced tunnelling is a 0.0.0.0/0 UDR with next hop Virtual appliance or Virtual network gateway, applied to the workload subnet.

Last updated: August 2026

The Problem Virtual Network Manager Solves

Network security groups (NSGs) are owned by whoever owns the subnet or NIC. In a large tenant that means an application team can, deliberately or accidentally, author an NSG rule that opens TCP 3389 to the internet, and the central security team has no way to stop it except by policy audit after the fact. Azure Virtual Network Manager (AVNM) closes that gap with security admin rules — global rules that are evaluated before NSGs and that application teams cannot override.

An AVNM instance is created at a scope (a management group or a subscription). It can only manage virtual networks inside that scope; a virtual network outside the scope simply never receives the rules.

Network Groups: Static and Dynamic Membership

A network group is the collection of virtual networks a configuration targets.

  • Membership type How it works When to use
  • Static You add specific virtual networks by hand Small, stable estates; exceptions

Dynamic (conditional) An Azure Policy definition matches virtual networks on name, tag, subscription, or resource group and adds them automatically Production at scale — new VNets inherit policy the moment they are tagged

Dynamic membership is the security win: a VNet created next month with environment=prod joins the production network group and picks up the deny rules without anyone remembering to add it.

Configurations come in two families:

Connectivity configurations — build hub-and-spoke or mesh topologies automatically, including direct connectivity between spokes and transitive connections through the hub.

Security admin configurations — carry the rule collections described below.

A deployment is what pushes a configuration to a region. You can deploy only one security admin configuration per region , though multiple connectivity configurations may coexist in a region. If you need more rules in a region, add more rule collections inside the single security configuration rather than trying to deploy a second configuration.

Security Admin Rules vs NSGs

  • Security admin rules NSG rules
  • Audience Central network/security governance team Application or service team
  • Applied to Virtual networks Subnets and NICs
  • Evaluation order First After security admin rules
  • Actions Allow, Deny, Always Allow Allow, Deny
  • Priority range 1–4096, lower wins 100–4096, lower wins

The three actions behave differently:

Allow — the traffic passes the admin layer and is then still evaluated by NSGs, so a team NSG can still deny it. Use for "permitted, but teams may tighten further".

Always Allow — evaluation terminates ; NSGs cannot deny the traffic. Use for control-plane or monitoring traffic that must never be broken by a team misconfiguration.

Deny — evaluation terminates and the packet is dropped. Teams cannot re-allow it. This is the control for high-risk ports such as 22, 3389, 445, 111, 135, 161/162, and 2049.

Sources and destinations accept IP/CIDR lists or service tags (with the exception of AzurePlatformDNS , AzurePlatformIMDS , and AzurePlatformLKM ). Supported protocols are TCP, UDP, ICMP, ESP, AH, and Any.

Exceptions you must remember

Security admin rules are not applied in two situations:

Whole virtual network skipped when it contains Azure SQL Managed Instance or Azure Databricks , because those services enforce their own network intent policy. You can set the configuration to AllowRulesOnly so at least the Allow rules apply, or request an exemption from Microsoft.

Individual subnets skipped when they host Azure Application Gateway, Azure Bastion, Azure Firewall, Azure Route Server, VPN Gateway, ExpressRoute Gateway, or Virtual WAN . Other subnets in the same VNet are still governed.

Deployment uses an eventual consistency model: rules land on existing and newly created resources after a short delay, not instantly. Private endpoints inside a managed virtual network are also currently outside the scope of security admin rules.

User-Defined Routes and Forced Tunnelling

Azure creates system routes automatically: intra-VNet traffic, peering, gateway-learned routes, and a default 0.0.0.0/0 route to the internet. A user-defined route (UDR) in a route table associated with a subnet replaces that default behaviour.

Next hop types:

  • Next hop type Meaning
  • Virtual appliance Send to an NVA or Azure Firewall private IP — the inspection pattern
  • Virtual network gateway Send to a VPN or ExpressRoute gateway — on-premises inspection
  • Virtual network Keep inside the VNet address space
  • Internet Send directly out to the internet, bypassing an NVA
  • None Blackhole the traffic

Route selection follows a strict order:

Longest prefix match wins. A /32 route beats a /24 route beats 0.0.0.0/0 , regardless of route source.

On an equal prefix , a UDR beats a BGP-learned route, which beats a system route.

Forced tunnelling is a 0.0.0.0/0 UDR whose next hop is the firewall or the gateway, applied to the workload subnet. Three traps appear regularly:

Applying the 0.0.0.0/0 route to the AzureFirewallSubnet with the firewall as next hop creates a routing loop; the firewall subnet should keep its internet route.

A /32 route for a monitoring endpoint silently bypasses your firewall, because longest prefix match outranks your default route.

Service Endpoints override routing entirely for the enabled service, so a UDR alone will not force storage traffic through an appliance if a service endpoint is enabled on the subnet.

AVNM can also centralize route tables through routing configurations, which is the same governance idea applied to UDRs rather than to filtering rules.