Study guide
5.5 Virtual Networks, Subnets, and Network Security Groups
Azure SC-900 Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map
1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map
2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC
2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation
3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication
3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities
4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection
4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk
5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault
5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets
6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score
6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans
7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks
7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks
8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence
8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence
9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score
9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager
10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit
10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management
11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps
11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop
12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path
12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900
5.5 Virtual Networks, Subnets, and Network Security Groups
Key Takeaways Explain This Topic AI
Azure Virtual Network (VNet) is the private network building block; subnets segment its address space into boundaries where resources sit and where controls attach.
Network security groups (NSGs) filter inbound and outbound traffic using 5-tuple rules: source, destination, source port, destination port, and protocol, plus a priority and an allow/deny action.
NSG rules are processed by priority (lower number first, 100-4096) and stop at the first match; NSGs are stateful, so a return packet for an allowed flow is permitted automatically.
Choose an NSG for simple subnet/NIC allow-deny filtering; choose Azure Firewall when the scenario needs centralized stateful policy, FQDN rules, or threat intelligence across the environment.
Last updated: June 2026
Segment Azure Networks with VNets, Subnets, and NSGs
Azure Virtual Network (VNet) provides the private network foundation for Azure resources. It lets resources such as virtual machines communicate securely with each other, the internet, and on-premises networks while using familiar networking concepts (address spaces, subnets, routing). For SC-900 the main idea is not advanced routing — it is that VNets and subnets provide logical containment , and NSGs provide traffic filtering within that containment.
Subnets divide a VNet's address space into smaller segments. A simple three-tier workload might place web servers in one subnet, application services in a second, and data services in a third. Segmentation alone does not create a complete security boundary, but it gives you places to apply controls . Network security groups (NSGs) are the core Azure feature in this chapter for allowing or denying traffic at subnet or network-interface (NIC) scope. An NSG can be associated with a subnet (covering everything in it) or with an individual NIC (covering one VM), and both can apply at once.
How NSG Rules Work: the 5-Tuple, Priority, and State
An NSG contains security rules that allow or deny inbound or outbound traffic. Each rule is built on the classic 5-tuple plus a priority and an action:
- Rule property What it contributes
- Priority A number from 100 to 4096; lower numbers are processed first
- Direction Inbound or outbound
- Source Source IP/CIDR, service tag, or application security group
- Destination Destination IP/CIDR, service tag, or application security group
- Source / destination port Single port, range, or *
- Protocol TCP, UDP, ICMP, or Any
- Action Allow or Deny
Rules are evaluated in priority order , and processing stops at the first match for that traffic. This is why priority planning matters: a broad allow rule at a lower priority number can short-circuit a later, higher-numbered deny rule, leaving the deny ineffective. Azure also adds default rules (such as allowing intra-VNet traffic and outbound to the internet, denying everything else) at very high priority numbers; your custom rules sit at lower numbers and override them. Application security groups (ASGs) let you group VMs by role and reference that group in rules instead of hard-coding IPs.
NSGs are stateful . If you allow an outbound flow to a destination on a port, the return traffic is permitted automatically — you do not need a matching inbound rule for the response. The same applies in reverse for permitted inbound flows. This is exam-relevant because it distinguishes NSGs from a naive stateless packet filter that would require explicit rules for both directions.
NSG vs Azure Firewall, and Segmentation Strategy
NSGs are not the same as Azure Firewall . If a question asks for central inspection, logging, FQDN/application rules, or threat intelligence across multiple networks, Azure Firewall is the better fit. If a question asks to allow web-subnet traffic to an app subnet , deny direct database access from the web tier , or filter inbound management traffic to a VM subnet , an NSG is the direct match. In real designs the two combine: NSGs do local subnet/NIC filtering while Azure Firewall provides centralized, stateful, environment-wide policy.
NSGs are also not a complete segmentation strategy by themselves. Segmentation starts with VNets, subnets, and architecture boundaries; NSGs then enforce traffic rules inside those boundaries. Additional controls — private endpoints (to reach PaaS services over a private IP), user-defined routes (to force traffic through a firewall), and service tags (named groups of Microsoft service IP ranges) — strengthen the design, but SC-900 usually just asks for the basic purpose of the named service.
Quick rules for the exam:
Use VNets as private network containers for Azure resources.
Use subnets to divide address space and group related resources.
Use NSGs to allow or deny inbound and outbound 5-tuple traffic at subnet or NIC scope.
Use Azure Firewall when the prompt asks for centralized managed firewall policy.
Remember NSGs are stateful and priority-ordered (first match wins, lowest number first).
Service Tags, Application Security Groups, and a Worked Rule Set
Two features make NSG rules far easier to manage at scale, and both can appear in scenarios. Service tags are Microsoft-maintained named groups of IP ranges for Azure services — for example, Internet , VirtualNetwork , AzureLoadBalancer , Storage , or Sql . Instead of tracking changing Microsoft IP ranges, you reference the tag and Azure keeps it current. Application security groups (ASGs) group VMs by role (such as web or db ), so a rule can say "allow web to reach db on 1433" without listing individual IPs; as you add VMs to the role, the rules apply automatically.
Picture a two-tier rule set on an application subnet's NSG:
- Priority Direction Source Destination Port Action
- 100 Inbound web ASG app ASG 443 Allow
- 200 Inbound Internet (service tag) Any Any Deny
- 4096 Inbound (default rules) Allow VNet / Deny all else
Because the allow at priority 100 is evaluated before the broad deny at 200, web-tier traffic to the app tier on 443 is permitted, while all other inbound internet traffic is denied. Reorder those two and the deny would never let the web traffic through — the classic priority trap.
NSG Limitations the Exam Tests
Know what an NSG cannot do, because distractors exploit it. An NSG does not inspect packet content (no SQL-injection or malware detection — that is WAF and Defender). It does not do FQDN/domain-based filtering or centralized cross-network policy (that is Azure Firewall ). It does not provide DDoS mitigation, store secrets, or manage identities. And NSG rules are limited to the 5-tuple plus tags/ASGs — they are filters , not a full firewall. When a stem needs anything beyond simple subnet/NIC allow-deny, the answer usually escalates to Azure Firewall, WAF, DDoS Protection, or an identity/data service.