Study guide
2.5 Governance, Risk, and Compliance
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.5 Governance, Risk, and Compliance
Key Takeaways Explain This Topic AI
Governance, Risk, and Compliance (GRC) is an integrated set of practices combining policies, processes, and technology to manage rules, risk decisions, and obligations.
Governance defines the rules, accountability, ownership, and direction; risk management identifies, assesses, responds to, and monitors threats; compliance means meeting laws, regulations, standards, and internal policies.
Risk responses are accept, mitigate, transfer, or avoid — the goal is informed decisions, not eliminating every risk.
Compliance is not the same as security: compliance often defines minimum requirements, while security is the broader set of practices that protect systems and data.
Data residency = where data is physically stored; data sovereignty = the laws of the jurisdiction governing that data; data privacy = proper handling of personal data (consent, rights, use).
Last updated: June 2026
GRC turns obligations and risk into a managed program
Governance, Risk, and Compliance (GRC) is an integrated approach that combines policies, operational processes, and technologies so an organization can manage its rules, risk decisions, and obligations in a structured way rather than ad hoc. For SC-900, the essential skill is to distinguish the three words and then recognize which Microsoft capabilities (covered later under Microsoft Purview) help operationalize each.
Governance is the system of rules, practices, and processes an organization uses to direct and control its activities. In a security context, governance includes data-classification policies, identity and access standards, privileged-access approval processes, control ownership, and the overall security strategy. Governance answers three questions: who decides , what rules apply , and who is accountable . If a scenario is about defining a policy, setting standards, or assigning ownership and accountability, the cue is governance.
The three GRC terms at a glance
- Term Plain meaning Exam cue
- Governance Rules, policies, accountability, and control direction 'Define a policy' / 'assign ownership'
- Risk Identify, assess, respond to, and monitor threats 'Weigh likelihood and impact' / 'decide a response'
Compliance Meet laws, regulations, standards, and internal policies 'Demonstrate adherence' / 'provide audit evidence'
Risk management and the compliance distinction
Risk management is the process of identifying, assessing, responding to, and monitoring threats or events that could negatively affect objectives or trust. Microsoft frames it as a continuous cycle: identify risks, assess their likelihood and impact, respond , then monitor over time. The goal is not to eliminate every possible risk — that is impossible — but to understand risks well enough to make informed decisions. The four classic risk responses are:
Accept — tolerate a low or unavoidable risk.
Mitigate — reduce likelihood or impact with controls.
Transfer — shift the risk to a third party (for example, insurance).
Avoid — stop the activity that creates the risk.
Compliance means adhering to applicable laws, regulations, standards, and internal policies. A subtle but tested point from Microsoft Learn: compliance is not the same as security . Compliance often defines minimum requirements an organization must meet, while security is the broader set of processes, technologies, and practices that protect systems and data from threats. An organization can be compliant on paper yet still insecure if it does only the minimum — and the reverse is also possible. Treat them as overlapping but distinct.
Reasoning through GRC scenarios
Rules and accountability -> governance .
Likelihood, impact, or a response choice (accept/mitigate/transfer/avoid) -> risk .
Laws, standards, audits, or required evidence -> compliance .
Residency, sovereignty, and privacy
SC-900 places three related data concepts under security and compliance. They sound similar and are deliberately mixed in distractors, so define each precisely:
Concept What it concerns Memory hook
Data residency The physical location where data is stored, and rules about transferring it 'Where the data lives'
Data sovereignty The laws and regulations of the jurisdiction where data is collected, held, or processed 'Whose laws apply'
Data privacy Proper handling of personal data — consent, rights, use, and protection 'How personal data is treated'
Data residency is about geography: an organization may be required to keep customer data within a specific country or region, which affects where it is stored, transferred, processed, or accessed. Data sovereignty goes further than location — even data stored in a given country is subject to that country's laws and may be accessible to its authorities, so the legal jurisdiction matters. Data privacy is about the appropriate handling of personal data: obtaining consent, honoring individuals' rights, limiting use, and protecting the data. A privacy regulation such as GDPR drives many of these requirements.
Where GRC reappears
These concepts return in the Microsoft Purview chapters, because Compliance Manager, sensitivity labels, data loss prevention (DLP), retention, eDiscovery, audit, insider risk management, and Microsoft Priva are the compliance-domain capabilities that operationalize GRC. In Domain 1 your job is to nail the vocabulary; later you select the right product. A candidate who can cleanly define governance, risk, compliance, residency, sovereignty, and privacy is far less likely to confuse a risk-decision scenario with an identity or threat-detection scenario on the exam.
How the three GRC pieces interact
The three components are not independent silos; they form a cycle. Governance sets the rules and accountability that define an organization's risk appetite and required controls. Risk management operates within that governance to identify what could go wrong, assess it, and choose a response (accept, mitigate, transfer, avoid). Compliance then verifies — often with audit evidence — that the controls demanded by governance and risk decisions actually satisfy applicable laws, regulations, and standards. A simple way to remember the flow: governance sets direction , risk makes informed decisions , and compliance proves adherence .
A final exam reminder: regulations and standards (such as GDPR for privacy, or industry frameworks) are external drivers of compliance, while policies are internal rules set by governance. When a question references a specific law or audit requirement, lean toward compliance; when it references an organization's own policy and accountability structure, lean toward governance. Holding these flows in mind keeps the three terms from blurring together under exam pressure.