Study guide

7.2 Azure Virtual Network Manager Security Admin Rules

Microsoft Certified: Cloud and AI Security Engineer Associate SC-500

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Skills Measured & Weightings 1.3 Study Path, Prerequisites & Exam Strategy

2 Microsoft Entra ID Secure Access

2.1 Privileged Identity Management (PIM) 2.2 Conditional Access Policies 2.3 MFA and Passwordless Authentication 2.4 Application Identities, OAuth Consent & Managed Identities

3 Azure Key Vault Secrets and Keys

3.1 Deploy and Configure Key Vault 3.2 Access Control and Firewall for Key Vault 3.3 Keys, Secrets, Certificates & Defender for Key Vault

4 Governance, Policy & RBAC

4.1 Azure Policy for Security Controls 4.2 Defender for Cloud Compliance & Security Standards 4.3 Resource Locks and Azure RBAC 4.4 Custom Roles, Overprivileged Access, Backup & IaC Security

5 Secure Storage Accounts

5.1 Storage Account Security Fundamentals 5.2 Storage Firewalls and Access Policies 5.3 Defender for Storage

6 Secure Databases

6.1 Azure SQL Platform Security 6.2 Database Auditing 6.3 Defender for Databases

7 Network Security Groups & Virtual Network Manager

7.1 Network Security Groups and Application Security Groups 7.2 Azure Virtual Network Manager Security Admin Rules 7.3 Virtual WAN and VPN Security

8 Private Access, Private Link & Azure Firewall

8.1 Microsoft Entra Private Access 8.2 Private Endpoints and Private Link 8.3 Azure Firewall 8.4 Network Watcher Diagnostics and Effective Rules

9 Security for AI Workloads

9.1 Purview DSPM for AI and Data Overexposure 9.2 Copilot Studio Protection and Agent Management 9.3 Microsoft Entra Agent ID Security 9.4 Defender for AI, Foundry Guardrails & AI Gateway

10 Secure Servers and Virtual Machines

10.1 Disk Encryption 10.2 Azure Bastion and JIT VM Access 10.3 Azure Arc and Defender for Servers 10.4 Trusted Launch, VM Security Features & Machine Configuration

11 Application Platform Security

11.1 Containers: AKS, ACR, ACI, Container Apps & Defender for Containers 11.2 Azure Functions and Logic Apps Security 11.3 Azure App Service Security 11.4 Web Application Firewall and API Management Protection

12 Defender for Cloud Security Posture

12.1 Defender CSPM and Secure Score 12.2 Workload Protection Plans and Multicloud Connectors 12.3 Vulnerability Management and Defender EASM

13 Microsoft Sentinel Activity and Event Collection

13.1 Workspaces, Roles & Content Hub 13.2 Data Connectors, Syslog/CEF & Windows Event Collection 13.3 Custom Tables, Retention & Purview Audit 13.4 Automation Rules and Playbooks

14 Microsoft Security Copilot & Final Review

14.1 Microsoft Security Copilot Workspaces and Roles 14.2 Plugins and Security Agents 14.3 Final Review and Exam-Day Strategy

7.2 Azure Virtual Network Manager Security Admin Rules

Key Takeaways Explain This Topic AI

Azure Virtual Network Manager (AVNM) centrally manages connectivity and security across many VNets using network groups and deployable configurations.

Security admin rules are organization-level allow/deny/always-allow policies applied to VNets in network groups and are evaluated before NSG rules.

Always Allow and Deny admin actions terminate evaluation so conflicting NSGs cannot weaken the central mandate; plain Allow still continues to NSG evaluation.

Connectivity configurations create mesh or hub-and-spoke topologies (including connected groups and optional spoke direct connectivity) separate from security admin configurations.

Deploy configurations per region intentionally; use admin rules for enterprise baselines such as blocking Internet RDP/SSH at scale while teams keep local NSGs for app detail.

Last updated: July 2026

Why Virtual Network Manager Appears on SC-500

The blueprint calls out implement and configure network access policies by using Azure Virtual Network Manager . In large landing zones, thousands of VNets and application teams cannot each invent Internet RDP exposure or skip baseline denies. Azure Virtual Network Manager (AVNM) is the control plane for:

Network groups — dynamic or static collections of virtual networks (often with Azure Policy-driven membership).

Connectivity configurations — mesh and hub-and-spoke topologies at scale.

Security admin configurations — global Layer-3/4 rules enforced on member VNets.

NSGs remain the application-team tool. Security admin rules are the central governance tool. Exam stems often test whether you pick the control that cannot be undone by a careless NSG allow.

Network Groups: The Scope Unit

A network group is the set of virtual networks a configuration targets. Membership can be:

  • Membership style Behavior Security value
  • Static You add specific VNets Precise; manual drift risk

Dynamic (policy-based) Conditions select VNets (for example environment=prod tags) New VNets automatically enter scope

Security admin rules apply to virtual networks in the group , not to unmanaged VNets outside the AVNM scope. When a VNet joins a group with a deployed security configuration, resources in that VNet receive the admin rules (eventual consistency—brief delay after create/join).

Design tip: Align groups to governance boundaries—Production, Sandbox, PCI, Hub-Shared—not to every application name. Application micro-segmentation still uses ASGs/NSGs inside those VNets.

Connectivity Configurations (Overview for Security Engineers)

Connectivity configuration is not the same as security admin configuration, but SC-500 expects conceptual literacy because topology and security travel together in enterprise designs.

Topology What AVNM builds Security relevance

Mesh Connected group—member VNets communicate without classic peering objects Need strong admin/NSG east-west controls; mesh is not a free pass for open ports

Hub-and-spoke (VNet hub) Peerings between hub and spokes Centralize shared services, firewalls, gateways

Hub-and-spoke (Virtual WAN hub) VNet connections to a vWAN hub (preview capabilities evolve) Aligns AVNM with global transit hubs

Optional settings you will see in documentation and exams:

Direct connectivity among spokes in a group (adds a connected group on top of hub-spoke).

Global mesh for cross-region spoke-to-spoke within a group.

Use hub as a gateway so spokes use hub VPN/ExpressRoute gateways.

Peering enforcement so critical peerings cannot be deleted outside AVNM.

Address overlap: Mesh can include overlapping address spaces, but traffic to overlapping prefixes is dropped (nondeterministic routing). Some configurations can disallow overlap. Do not assume mesh magically fixes IP planning mistakes.

Connectivity configs can coexist regionally in multiple forms; security admin has a stricter deployment rule (next section).

Security Admin Rules vs NSGs

This comparison is core exam material:

  • Aspect Security admin rules (AVNM) NSG rules
  • Primary audience Central network/security admins Application or workload teams
  • Applied on Virtual networks in network groups Subnets and/or NICs
  • Evaluation order Higher priority—evaluated first After admin rules (when traffic still eligible)
  • Actions Allow , Deny , Always Allow Allow, Deny only
  • Independence Can enforce baselines even if no NSG exists Often missing when teams forget to attach NSGs
  • Scale One config → many VNets Per subnet/NIC management burden
  • Action types and evaluation termination

Allow (admin): Traffic is permitted at the admin layer, then continues to NSG evaluation. Teams can still deny with NSGs.

Always Allow: Traffic is forced allowed; NSGs cannot deny it . Evaluation stops. Use sparingly for mandatory management or monitoring paths that app teams must not block.

Deny: Traffic is blocked; NSGs never see it . Evaluation stops. Ideal for “no Internet RDP/SSH anywhere in prod.”

Exam trap: “Always Allow” is not the same as “Allow.” If the goal is a non-negotiable open path, Always Allow. If the goal is “central allow but local teams may tighten,” use Allow.

Admin rules also have priority (1–4096, lower number higher priority), direction , protocol (TCP, UDP, ICMP, ESP, AH, Any), and source/destination as IP/CIDR or service tags (with a few platform tags unsupported).

High-risk ports baseline

Microsoft guidance for security admin rules commonly blocks management and historically abused ports from untrusted sources—examples include 22 (SSH) , 3389 (RDP) , 445 (SMB) , unencrypted FTP ports, and other remote management vectors. Create exceptions (higher-priority allows from Bastion subnet, jump host ASG/CIDR, or Always Allow only where justified) rather than leaving Internet exposure.

  • Configuration Structure and Deployment
  • Think of the object model as: Virtual Network Manager instance
  • └── Security admin configuration
  • └── Rule collection(s) → associated to network group(s)
  • └── Security admin rule(s)

Deployment notes:

You deploy configurations to target regions . Rules are not live from save alone—deployment is the commit step.

Only one security admin configuration can be deployed to a given region at a time. Need multiple rule sets? Put multiple rule collections inside that single security configuration rather than expecting several simultaneous security configs per region.

Multiple connectivity configurations can exist more flexibly than security admin deployments.

Eventual consistency: after deploy or after adding VMs/VNets, allow a short propagation window.

Non-application / exceptions

Some platform services have network intent policies. Security admin rules may skip certain VNets or subnets (examples historically include subnets hosting Azure Firewall, Bastion, VPN Gateway, ExpressRoute Gateway, Virtual WAN components, and some services like SQL Managed Instance or Databricks at VNet level unless special allow-rules-only modes are used). For SC-500, remember: admin rules are powerful but not literally universal on every platform subnet —do not assume they replace service-specific required rules.

Private endpoints: Security admin rules currently do not apply to private endpoints under a managed VNet in the same way as ordinary NICs—design private endpoint controls with NSG network policies, Private Link, and PaaS firewalls as appropriate.

Enterprise-Scale Use Cases

Use case Admin rule approach Why not NSG-only?

Block Internet inbound RDP/SSH on all prod VNets Deny from Internet service tag to * on 3389/22 App teams forget NSGs or add Allow *

Enforce no SMB lateral movement from untrusted prefixes Deny 445 between network groups Consistent lateral-movement reduction

Guarantee connectivity to a monitoring agent endpoint Always Allow specific egress Prevents accidental NSG deny breaking security tooling

PCI segment isolation Deny between cardholder network group and open corporate group Central auditability

Sandbox freedom with guardrails Deny only high-risk Internet inbound; Allow rest to NSGs Balance agility and risk

Governance model: Platform team owns AVNM + admin baselines. Application teams own NSGs/ASGs for micro-segmentation inside the allowed envelope. Network Watcher effective security rules show both layers on a NIC.

Worked Scenario: Contoso Landing Zone

Contoso has 120 spoke VNets. Auditors require: no direct Internet RDP/SSH; DNS to Azure DNS allowed; app teams still control HTTP east-west.

Solution sketch:

Deploy AVNM at the intermediate root management group scope covering landing-zone subscriptions.

Dynamic network group ng-prod for VNets with env=prod .

Security admin configuration with rule collection on ng-prod :

Priority 100: Deny inbound Internet → any on TCP 3389.

Priority 110: Deny inbound Internet → any on TCP 22.

Priority 200: Allow inbound VirtualNetwork → VirtualNetwork on necessary ports or leave east-west to NSGs after a broad admin Allow if required by design.

Deploy to all regions hosting prod hubs/spokes.

App teams attach subnet NSGs + ASGs for tiering.

Validate a random VM NIC with Network Watcher effective rules—confirm admin Denies appear above NSG allows.

If a team creates an NSG Allow Internet→3389 at priority 100, admin Deny still wins (evaluated first and terminates). That is the SC-500 punchline for central enforcement.

SC-500 Exam Traps (AVNM)

Admin rules outrank NSGs; Always Allow/Deny stop NSG processing.

Deploy the configuration—saving is not enforcement.

One security admin configuration per region deployment slot—use rule collections for multiple policies.

Connectivity mesh ≠ secure by default; pair with admin rules/NSGs.

ASGs are not AVNM network groups (NICs vs VNets).

Admin rules are not a full substitute for Azure Firewall L7 inspection.