Study guide

2.1 Shared Responsibility 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.1 Shared Responsibility Model

Key Takeaways Explain This Topic AI

The shared responsibility model divides security tasks between the cloud provider and the customer, and the split depends on the service model (IaaS, PaaS, SaaS) or on-premises.

Microsoft's responsibility matrix marks customer data, configurations and settings, and identities and users as 'Customer' for every deployment type, including SaaS.

Four responsibilities you ALWAYS retain are data, endpoints, accounts, and access management — moving to the cloud never transfers these.

As you move on-premises -> IaaS -> PaaS -> SaaS, Microsoft takes on more of the underlying stack (OS, runtime, physical hosts), but the customer never hands off everything.

Exam trap: 'the cloud is secure so I don't have to do anything' is wrong — provider investment reduces infrastructure burden, not customer accountability.

Last updated: June 2026

Why shared responsibility exists

The shared responsibility model describes which security tasks the cloud provider handles and which tasks remain with you, the customer. Microsoft Learn states it plainly: as you evaluate public cloud services, it is critical to understand which security work transfers to Microsoft and which stays with you. In an on-premises datacenter you own the entire stack — the building, physical network, physical hosts, the operating system, applications, identities, and data. As workloads move to the cloud, some of that work transfers to Microsoft, but the transfer is partial and depends on the service model.

The model matters for SC-900 because it underlies almost every later decision: which Microsoft Entra, Defender, and Purview capability you must configure yourself versus what Microsoft operates for you. A candidate who internalizes the direction of the responsibility shift can answer a large family of 'who is responsible for X?' questions without memorizing every control.

The three cloud service models

Microsoft Learn defines the three models by what you manage:

IaaS (Infrastructure as a Service): You manage virtual machines, operating systems, and applications. Examples: Azure Virtual Machines, Azure Disk Storage, virtual networks.

PaaS (Platform as a Service): You deploy applications without managing VMs or operating systems. Examples: Azure App Service, Azure Functions, Azure SQL Database, Azure Storage.

SaaS (Software as a Service): You use ready-made applications. Examples: Microsoft 365, Dynamics 365.

Many real Azure solutions combine models, but the exam tests the clean cases.

The responsibility matrix

Microsoft publishes a responsibility matrix showing who owns each layer per deployment type. Memorizing the pattern is exam gold:

  • Responsibility area On-prem IaaS PaaS SaaS
  • Customer data Customer Customer Customer Customer
  • Configurations and settings Customer Customer Customer Customer
  • Identities and users Customer Customer Customer Customer
  • Client devices (endpoints) Customer Customer Customer Shared
  • Applications Customer Customer Shared Shared
  • Network controls Customer Customer Shared Microsoft
  • Operating system Customer Customer Microsoft Microsoft
  • Physical hosts Customer Microsoft Microsoft Microsoft
  • Physical network Customer Microsoft Microsoft Microsoft
  • Physical datacenter Customer Microsoft Microsoft Microsoft

Read the table top-down: the top three rows are always Customer , the bottom three (physical layers) flip to Microsoft the moment you leave on-premises, and the middle rows transition as the service becomes more managed. Note the precise cells the exam loves: the operating system becomes Microsoft's at PaaS , network controls become Microsoft's only at SaaS , and client devices become Shared (not fully Microsoft) at SaaS.

Responsibilities you ALWAYS retain

Regardless of deployment type, Microsoft Learn says you always keep four responsibilities:

Data — classification, protection, encryption decisions, and data-governance compliance.

Endpoints — protecting client devices (mobiles, laptops, desktops) that access cloud services.

Accounts — creating, managing, and removing user accounts.

Access management — RBAC, multifactor authentication, and Conditional Access policies.

A shorter mnemonic many use is 'you always own your data and identities .' These are the highest-value SC-900 cues: if a scenario asks who classifies sensitive data, manages permissions, secures laptops, or enforces MFA, the answer is the customer.

Selection scenarios and traps

Which side is responsible? Use this reasoning pattern:

Physical datacenter security for a SaaS service? -> Microsoft . The provider owns facilities, physical hosts, and physical network in every cloud model.

Who decides who can read sensitive records in a SaaS app? -> Customer (access management never transfers).

Who patches the guest operating system on an Azure VM (IaaS)? -> Customer — at IaaS the OS row is still yours; at PaaS it would be Microsoft.

Who manages network firewalls in PaaS? -> Shared — Microsoft provides baseline network security, you configure application-level controls.

The big trap

The classic wrong answer is that 'moving to the cloud means Microsoft handles all security.' It does not. Cloud adoption changes the split of tasks; it does not remove customer accountability. A misconfigured tenant, an over-permissive role assignment, or a compromised identity can expose resources even when Microsoft's underlying platform is perfectly secure. Microsoft Learn frames the cloud advantage as shifting day-to-day infrastructure burden to the provider so you can reallocate effort to data protection, identity governance, and monitoring — not as eliminating your duties.

Why the cloud still helps

The doc notes that on-premises organizations often have unmet responsibilities due to limited resources: delayed patching, weak physical security, incomplete monitoring, outdated hardware, and untested backups. By shifting infrastructure work to Microsoft, you reduce these gaps and can use cloud-scale intelligence to improve detection and response. For SC-900, hold two ideas at once: the cloud meaningfully reduces infrastructure risk, yet you still own data, identities, endpoints, and configuration choices everywhere.

A note on AI workloads

Microsoft Learn now extends the model to AI services. For AI workloads, Microsoft secures the AI infrastructure and model hosting, while you remain accountable for how AI is applied: protecting sensitive data, managing prompt security, and meeting regulatory requirements. The pattern matches the traditional model — Microsoft owns the platform, you own your data and how you use it. Remember too that the model describes security tasks , not legal ownership: you always own your data and identities, and the matrix simply tells you which protective work is yours versus Microsoft's at each layer.