Study guide

2.3 Zero Trust Model

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

2.3 Zero Trust Model

Key Takeaways Explain This Topic AI

Zero Trust is a security strategy and architecture, not a single product — it replaces the old 'trusted internal network' assumption with 'never trust, always verify.'

The three guiding principles are verify explicitly, use least privileged access (just-in-time / just-enough-access), and assume breach.

Microsoft's six Zero Trust pillars are identities, devices (endpoints), applications, data, infrastructure, and networks, coordinated by visibility, automation, and orchestration.

Identity is treated as the primary control plane because access can originate from any network, device, location, or application.

Exam framing is product-neutral: Entra implements identity verification, Defender/Sentinel implement detection and response, and Purview implements data protection — but no single product 'is' Zero Trust.

Last updated: June 2026

Zero Trust replaces the trusted-network assumption

Zero Trust is a security strategy for the modern workplace, where users work from many locations, use varied device types, and reach data spread across cloud services, on-premises systems, and partner applications. The traditional 'castle and moat' model assumed anything inside the corporate network perimeter was safe and anything outside was hostile. That assumption no longer fits: with remote work, BYOD, and SaaS, there is no single perimeter to defend. Zero Trust answers this with a simple mantra — never trust, always verify .

The most important exam point: Zero Trust is a strategy and architecture , not a product you can buy. Microsoft sells services that implement parts of Zero Trust, but enabling one feature (even MFA) does not 'complete' Zero Trust. SC-900 questions reward you for treating it as a reasoning framework: every access request is evaluated, every identity gets only the access it needs, and every design limits damage if a control fails.

Why identity is the control plane

Because access can come from any network, device, location, or app, Zero Trust makes identity the primary control point. Instead of trusting the network a request came from, you authenticate and authorize the identity behind every request, using rich signals before granting access.

The three guiding principles

Microsoft Learn defines Zero Trust through three principles. Each maps to a recognizable exam scenario:

Principle What it means Scenario cue

Verify explicitly Always authenticate and authorize using all available signals: identity, location, device health, service or workload, data classification, and anomalies/risk 'Allow access only after checking the user, device compliance, location, and sign-in risk'

Use least privileged access Limit access with just-in-time and just-enough-access (JIT/JEA) and risk-based adaptive policies; reduce standing privilege 'Grant only the permissions needed, only for as long as needed' — broad standing admin rights are the wrong answer

Assume breach Design as if an attacker is already inside: minimize blast radius, segment access, verify end-to-end encryption, and use analytics to detect and respond 'Limit lateral movement and monitor activity so a compromise is contained'

The principles are heavily tested through scenario language . If a question describes granting broad administrator rights 'just in case,' the violated principle is least privileged access . If it describes evaluating user, device, location, and risk before allowing access, the cue is verify explicitly . If it describes containing an attacker who already has a foothold, the cue is assume breach . Train yourself to map the wording to the principle.

The six pillars

Zero Trust principles are applied across six technology pillars , tied together by cross-cutting visibility, automation, and orchestration that collect signals and drive responses:

Identities — users, services, and devices that request access; verify each strongly (MFA), govern, and apply least privilege.

Devices (endpoints) — monitor device health and compliance; require devices to meet a security bar before they connect to data.

Applications — discover shadow IT, control in-app permissions, gate access, and monitor for abnormal behavior.

Data — classify, label, and encrypt data based on sensitivity so protection follows the data wherever it travels.

Infrastructure — assess servers, VMs, containers, and cloud resources for configuration drift, version, and just-in-time access; flag and block unusual behavior.

Networks — segment networks (including micro-segmentation), use real-time threat protection, and encrypt internal traffic instead of assuming the internal network is safe.

Product-neutral mapping (and the big trap)

Microsoft products implement pieces of the pillars, and the exam keeps this product-neutral:

Microsoft Entra -> identities and access decisions (Conditional Access verifies explicitly).

Microsoft Intune / Defender for Endpoint -> device compliance and health.

Microsoft Defender XDR and Microsoft Sentinel -> detection, posture, and the assume-breach response loop.

Microsoft Purview -> data classification, labeling, and protection.

The classic trap is assuming that buying one service 'completes' Zero Trust. MFA strengthens verification but is not the whole strategy; segmentation supports assume breach but does not replace identity governance; data labels help protect content but access still must be authorized. When a scenario describes modern remote work, personal devices, cloud apps, or partner access, the old 'trusted internal network' option is almost always the wrong answer.

Signals, decision, and enforcement

It helps to picture Zero Trust as a continuous loop. Signals are gathered from every pillar — the user's identity and sign-in risk, the device's compliance state, the application requested, the sensitivity of the data, the location, and the time. A policy engine makes a decision based on those signals (allow, block, or allow with conditions such as MFA or a compliant device). Then the decision is enforced at the resource. In Microsoft's stack, Microsoft Entra Conditional Access is the canonical example: it evaluates signals at sign-in and enforces controls in real time, which is exactly 'verify explicitly' put into practice.

This loop is why Zero Trust is described as signal-driven rather than perimeter-driven. The same request from the same user can be allowed from a compliant corporate laptop and blocked from an unmanaged device showing risky behavior, because the decision adapts to the signals rather than to the network location.

Quick exam recap

Zero Trust is a strategy/architecture , never a single product.

Three principles : verify explicitly, use least privileged access, assume breach.

Six pillars : identities, devices, applications, data, infrastructure, networks — plus visibility, automation, and orchestration tying them together.

Identity is the control plane ; signals drive every access decision.