Study guide
8.4 Network Watcher Diagnostics and Effective 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
8.4 Network Watcher Diagnostics and Effective Rules
Key Takeaways Explain This Topic AI
IP flow verify tests whether a VM 5-tuple (TCP/UDP) is allowed or denied by NSG and Virtual Network Manager admin rules and names the matching rule.
Next hop diagnoses routing (UDR, peering, gateway, virtual appliance) and is the correct tool when filtering allows traffic but packets take the wrong path.
Effective security rules and NSG diagnostics reveal the merged NIC+subnet rule set and support broader targets such as VMSS and Application Gateway.
Connection troubleshoot provides an on-demand end-to-end connectivity check; packet capture supports deep packet analysis after path/filter checks are clean.
SC-500 scenarios that ask you to evaluate effective security rules expect Network Watcher diagnostics—not flow logs alone—and a methodical filter-then-route troubleshooting order.
Last updated: July 2026
Network Watcher and the SC-500 Skill
The blueprint skill Evaluate effective security rules by using Azure Network Watcher diagnostics is highly scenario-driven. Microsoft expects you to know which tool answers which question when connectivity fails or when you must prove what NSG/admin rules actually allow.
Azure Network Watcher is the IaaS network monitoring and diagnostics suite for VMs, VNets, load balancers, application gateways, and related constructs. It is not a PaaS application APM tool. Capabilities group into monitoring, network diagnostic tools , and traffic logging/analytics.
You need a Network Watcher instance in the region of the resources under test (auto-enabled in many subscriptions/regions, but know it must be available).
Diagnostic Tools Map (Memorize This Table)
Tool Question it answers Primary failure class
IP flow verify Would this 5-tuple be allowed or denied by security/admin rules on a VM NIC ? Which rule decided? NSG / Virtual Network Manager admin rules filtering
NSG diagnostics Broader filtering analysis for VM, VMSS , or Application Gateway ; can suggest higher-priority rules NSG rule design issues at more resource types
Effective security rules What is the combined rule set on a NIC from NIC NSG + subnet NSG (aggregate view)? Understanding merged allow/deny reality
Next hop Where does Azure route this packet next (next hop type, IP, route table)? UDR / system route / BGP / peering routing problems
Connection troubleshoot One-shot connectivity check between endpoints (latency, probes, hop issues) End-to-end path problems combining route + filter + reachability
Packet capture What packets are actually on the wire on a VM? Deep inspection, asymmetric issues, app-level surprises
VPN troubleshoot Gateway/connection diagnostics S2S/P2S VPN health
SC-500 “effective security rules” language maps especially to IP flow verify , NSG diagnostics , and the Effective security rules viewer—use them when the exam describes “blocked by NSG” uncertainty.
IP Flow Verify
IP flow verify tests whether a packet to or from a VM is allowed by configured NSG rules and Azure Virtual Network Manager security admin rules .
- Inputs
- Direction (inbound/outbound)
- Protocol ( TCP or UDP —not ICMP; use NSG diagnostics for ICMP scenarios)
- Local IP (VM NIC) and local port
- Remote IP and remote port
- Outputs
- Allow or Deny
- The specific rule that matched (name/priority source)
- Considerations
Requires Network Watcher in the VM’s region and proper RBAC.
Evaluates rules on the VM’s NIC association path (NIC NSG + subnet NSG + AVNM admin rules).
For VM scale sets , prefer NSG diagnostics .
Does not test guest OS firewalls, application bind failures, or asymmetric return paths beyond security rules.
Exam use: “Traffic to port 443 is failing; is an NSG denying it?” → IP flow verify first for a single VM 5-tuple.
Next Hop
Next hop diagnoses routing , not filtering.
Provide a source VM and destination IP; Azure returns:
- Field Meaning
- Next hop type e.g., Internet, Virtual appliance, VNet local, VNet peering, Virtual network gateway, None
- Next hop IP Appliance/gateway address when applicable
- Route table Which effective route table produced the decision
- Classic findings
- Symptom Likely next hop insight
- Spoke cannot reach internet but should via Firewall Next hop is Internet directly → missing UDR to firewall
- Traffic blackholed to wrong NVA Next hop virtual appliance IP unexpected → fix UDR
- On-premises unreachable Next hop not Virtual network gateway → peering/gateway transit/UDR issue
- Next hop type None No route—packet will not leave
Exam trap: IP flow verify says Allow , but traffic still fails → check Next hop (routing) and then OS/app layers. Filtering and routing are different planes.
- NSG Diagnostics and Effective Security Rules
- Effective security rules
Effective security rules shows the applied security configuration for a NIC:
- Rules from NSG associated to the NIC
- Rules from NSG associated to the subnet
- The aggregate effective set the platform enforces
Use this when multiple NSGs exist and humans cannot mentally merge priorities, defaults, and denies. Remember Azure NSG evaluation: rules processed by priority (lower number = higher priority); default rules exist; deny can override broader allows depending on priority.
NSG diagnostics
NSG diagnostics expands filtering troubleshooting:
- Targets VM , VMSS , or Application Gateway
- Tests whether traffic is allowed/denied for IP/prefix/ service tag sources
- Identifies which rule matched
- Can help you craft a higher-priority rule to fix the issue
Compared with IP flow verify: NSG diagnostics is the broader multi-resource filtering tool; IP flow verify is the quick VM 5-tuple check (TCP/UDP).
- Need Prefer
- Quick VM TCP/UDP allow/deny + rule name IP flow verify
- VMSS or App Gateway filtering analysis NSG diagnostics
- Human-readable merge of NIC+subnet rules Effective security rules
- ICMP test NSG diagnostics (not IP flow verify)
- Connection Troubleshoot and Packet Capture
- Connection troubleshoot
Runs a one-time connectivity check from a source (often a VM) to a destination (VM, App Gateway, Bastion, IP/FQDN depending on capability). Results highlight:
- Whether connectivity succeeded
- Latency measurements
- Hints about network path problems (security rules, routing, user configuration)
Use when the exam scenario needs an end-to-end probe rather than isolated “only NSG” or “only route” checks. For continuous monitoring, Connection Monitor is the longer-running relative (monitoring set)—know the difference: troubleshoot = on-demand diagnostic; monitor = ongoing.
Packet capture
Packet capture installs/uses an extension capability to capture traffic on a VM for analysis (Wireshark, etc.). Use for:
- Proving whether SYN packets arrive
- Investigating unexpected protocols
- Validating that NSG/firewall allow still fails inside the guest
Packet capture is heavier and more forensic; exams usually prefer IP flow verify/next hop first, then capture if needed.
- Evaluating Effective Security Rules in Exam Scenarios
- Use a consistent decision tree: Connectivity failure reported
- │
- ├─► IP flow verify / NSG diagnostics
- │ Deny? → Fix NSG or AVNM admin rule (priority/source/port)
- │ Allow? → continue
- │
- ├─► Next hop
- │ Wrong hop / None? → Fix UDR, peering, gateway transit
- │ Correct hop? → continue
- │
- ├─► Connection troubleshoot
- │ Path-level confirmation of remaining Azure issues
- │
- └─► Packet capture + guest OS firewall + application bind
- Issues outside Azure control plane
- Scenario pack (exam style)
- Scenario 1 — “Port 22 closed.”
IP flow verify inbound TCP 22 from admin IP → Deny by subnet NSG default-like custom deny. Fix: higher-priority allow for jump host subnet only.
Scenario 2 — “Allow rule exists but still blocked.”
Effective security rules show a lower-number deny on NIC NSG. Priority beats broader allow. Fix priority order—not “add another allow at 4000.”
Scenario 3 — “NSG allows internet, still no egress.”
Next hop shows Virtual appliance firewall IP, but firewall network rules deny. Not an NSG problem—fix Azure Firewall rules / UDRs.
Scenario 4 — “AVNM security admin rules.”
IP flow verify attributes deny to a security admin rule with precedence over NSG. Fix admin rule assignment/configuration in Virtual Network Manager—not only the local NSG.
Scenario 5 — “VMSS instances cannot reach SQL private endpoint.”
NSG diagnostics on scale set; also verify private DNS and next hop toward private endpoint subnet; NSG on PE subnet may deny.
Related Traffic Tools (Awareness)
- Capability Role
- NSG flow logs / VNet flow logs Historical traffic allow/deny logging (not the same as NSG diagnostics)
- Traffic Analytics Visualize and query flow log data
- Topology Visual map of network resources
Exam trap: Flow logs record traffic; NSG diagnostics / IP flow verify simulate/evaluate whether rules would allow a hypothetical or current configuration. Do not interchange them.
- Permissions and Prerequisites
- Network Watcher enabled in region
- RBAC to read NICs, NSGs, route tables, and run Network Watcher actions
- VM running/accessible for some probes (connection troubleshoot, packet capture)
- Correct source NIC selection on multi-NIC VMs
- SC-500 Exam Traps (Network Watcher)
IP flow verify = filtering; Next hop = routing.
IP flow verify: TCP/UDP only ; not ICMP.
Effective security rules = merged NIC + subnet reality.
AVNM admin rules appear in flow verify—don’t only stare at NSG JSON.
Allow in Azure still fails if guest firewall or app is down—capture/OS tools next.
Blueprint phrase “evaluate effective security rules” → Network Watcher diagnostics, not guessing from a single portal blade.
Practical Checklist for Candidates
Reproduce 5-tuple precisely (direction, protocol, IPs, ports).
Run IP flow verify or NSG diagnostics .
Open effective security rules if multiple NSGs confuse the result.
Run next hop for the destination IP.
Use connection troubleshoot for path confirmation.
Escalate to packet capture only when Azure path is proven clean.
If firewall is in path, remember Azure Firewall rules are outside NSG effective rules—diagnose firewall separately.
Mastering this toolkit is how you pass scenario questions that stack NSG, UDR, Firewall, and private endpoints—exactly the multi-layer failures real Cloud and AI Security Engineers debug.