Study guide
7.5 NSGs, ASGs, and Effective Security Rules
AZ-104 Microsoft Azure Administrator Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Orientation and Microsoft Learn Source Control
1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log
2 Chapter 2: Identity, RBAC, and Governance Foundations
2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab
3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization
3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab
4 Chapter 4: Storage Accounts, Access, and Data Protection
4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab
5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep
5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab
6 Chapter 6: Containers, App Service, and Platform Compute
6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab
7 Chapter 7: Virtual Networking, Routing, and Secure Access
7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab
8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting
8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab
9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery
9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab
10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs
10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab
11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path
11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths
7.5 NSGs, ASGs, and Effective Security Rules
Key Takeaways Explain This Topic AI
NSGs filter inbound and outbound traffic at subnet and NIC scopes using priority, direction, protocol, source, destination, and port.
Default NSG rules allow VNet-internal traffic and outbound internet but deny unsolicited inbound internet traffic.
ASGs group VM NICs logically so NSG rules can target application roles without hard-coded IP addresses.
Effective security rules show the combined subnet and NIC NSG result for a network interface.
AZ-104 troubleshooting requires separating route failures, NSG denies, guest firewall blocks, and application listener issues.
Last updated: May 2026
NSG rule mechanics
A network security group, or NSG, contains inbound and outbound security rules. Each rule has a priority, direction, access action, protocol, source, source port, destination, destination port, and optional service tag or application security group. Lower priority numbers are evaluated first. When a rule matches, processing stops for that direction.
NSGs can be associated with a subnet, a network interface, or both. When both apply to a VM NIC, the effective result includes both scopes. For inbound traffic, the subnet NSG and NIC NSG must both allow the traffic. For outbound traffic, both scopes can also affect the flow. A deny at either relevant scope can block traffic.
Basic rule example:
Priority Direction Source Destination Port Access Purpose
100 Inbound Internet ASG asg-web 443 Allow Public HTTPS to web tier.
110 Inbound ASG asg-web ASG asg-app 8080 Allow Web tier to app tier.
120 Inbound ASG asg-app ASG asg-db 1433 Allow App tier to database tier.
4096 Inbound * * * Deny Explicit cleanup rule before defaults if needed.
Default rules matter
Default NSG rules are exam-relevant. They allow inbound traffic from the virtual network, allow inbound traffic from Azure load balancer probes, and deny other inbound traffic. They allow outbound traffic to the virtual network and internet, then deny other outbound traffic. The practical result is that VMs in the same VNet can often communicate privately unless you add rules to restrict them, while unsolicited inbound internet traffic is denied unless you allow it.
Do not assume that placing VMs in separate subnets automatically blocks them. If the NSGs allow VNet traffic through defaults, private communication may still work. To create tier isolation, add explicit rules with priorities that allow only required flows and deny broad VNet traffic where needed. Be careful not to block required health probes, management flows, or platform dependencies.
Application Security Groups
Application Security Groups, or ASGs, let you group VM NICs by application role. Instead of writing rules for individual IP addresses, you can write rules such as asg-web to asg-app on TCP 8080. This makes scale-out and replacement easier because new NICs can join the ASG without rewriting every NSG rule.
ASGs are especially useful in three-tier designs: Internet -> Load balancer or App Gateway -> web VMs (asg-web)
- web VMs (asg-web) -> app VMs (asg-app) on 8080
- app VMs (asg-app) -> db VMs (asg-db) on 1433
ASGs are not a global identity system for every Azure resource. They apply to NIC-based VMs in a virtual network context. If the scenario targets PaaS access such as Storage or SQL private endpoints, NSGs may affect private endpoint NIC traffic depending on configuration, but ASGs themselves are not the same as RBAC, private DNS, or firewall rules on the service.
Effective security rules
Effective security rules are the best way to understand what Azure applies to a NIC. Portal path: Network interface > Effective security rules . This view combines subnet-level NSGs, NIC-level NSGs, default rules, and augmented rules into a readable result. It does not replace guest OS firewall checks, but it answers the Azure NSG question.
Network Watcher IP flow verify is even more direct. You provide a VM, direction, protocol, local IP and port, remote IP and port, and it returns allow or deny plus the rule responsible. This is the tool to use when a question says identify whether traffic is allowed by NSG rules.
- CLI examples: az network nic list-effective-nsg \
- -resource-group rg-network \
- -name nic-web-01 \
- -output table
- az network watcher test-ip-flow \
- -resource-group rg-network \
- -vm vm-web-01 \
- -direction Inbound \
- -protocol TCP \
- -local 10.41.1.4 443 \
- -remote 203.0.113.10 50000
- Effective-rule troubleshooting workflow
Use this order when connectivity fails:
Confirm the destination IP and port are correct.
Confirm routing with effective routes or next hop.
Check effective security rules on the destination NIC for inbound traffic.
Check effective security rules on the source NIC for outbound traffic if outbound rules are customized.
Use IP flow verify to identify the exact NSG rule.
Check Azure Firewall, load balancer health, application gateway backend health, or NVA policy if the path includes them.
Check the VM guest firewall and application listener.
This order prevents a common mistake: editing NSG rules when the packet never reaches the subnet because a UDR points to the wrong next hop. It also prevents blaming Azure when Windows Firewall, Linux firewalld, or the application binding blocks the port.
Rule design patterns
Use service tags for Azure platform ranges and common sources when they match the requirement. For example, Internet , VirtualNetwork , AzureLoadBalancer , and service-specific tags can simplify rules. Use ASGs for your own VM application roles. Use explicit IP prefixes for known external partner networks when the requirement is strict allowlisting.
Avoid overly broad rules such as allowing Any source to Any destination on Any port unless the scenario is a temporary lab and the requirement permits it. For production-like exam scenarios, least privilege is the safer answer. Use lower priority numbers for specific allows, then a deliberate deny for broad lateral movement if required.
Scenario traps
A public IP does not bypass an NSG. A route table does not allow a blocked port. An NSG allow rule does not make an application listen. A subnet boundary alone does not isolate tiers. These are the four most common NSG traps.
Another trap is priority ordering. If priority 100 denies TCP 443 from Internet to a subnet, a later priority 200 allow for TCP 443 will not matter. The deny matched first. To fix the rule set, change priority, scope, source, destination, or remove the conflicting rule.
Finally, remember load balancer health probes. Blocking AzureLoadBalancer probe traffic can make backends appear unhealthy even when the application works locally. If a public load balancer stops sending traffic after NSG hardening, inspect probe ports and the default or explicit rules that allow the probe source.