Study guide
9.5 Compliance Score and Improvement Actions
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
9.5 Compliance Score and Improvement Actions
Key Takeaways Explain This Topic AI
Compliance score measures your progress completing improvement actions; each action is weighted by risk impact, not counted equally.
Action point values: preventative+mandatory = 27, preventative+discretionary = 9, detective/corrective mandatory = 3, detective/corrective discretionary = 1.
Mandatory actions can't be bypassed (e.g., enforced password policy); discretionary actions rely on the user (e.g., lock-when-away).
Compliance score (Purview, regulatory posture) is different from Microsoft Secure Score (Defender, security posture) — a top SC-900 trap.
Last updated: June 2026
How the Compliance Score Is Calculated
The compliance score on the Compliance Manager dashboard is a personalized, risk-weighted measure of your progress completing improvement actions within controls. It is not the percentage of actions done — actions are weighted by how much risk they reduce . Points are awarded when you complete an action's implementation; your status updates on the dashboard within about 24 hours .
Microsoft assigns each action a value based on two dimensions :
Mandatory vs. discretionary — can the control be bypassed?
Mandatory : cannot be bypassed intentionally or accidentally (e.g., a centrally enforced password policy ). Worth more.
Discretionary : relies on the user to comply (e.g., a policy to lock your computer when unattended ). Worth less.
Preventative vs. detective vs. corrective — what does the control do?
Preventative : stops a risk from occurring (e.g., encrypting data at rest ; separation of duties). Highest value.
Detective : monitors to find irregularities (e.g., access auditing , reviewing privileged actions).
Corrective : limits damage and restores systems after an incident (e.g., privacy incident response ).
The exact point table (memorize)
- Action type Assigned score
- Preventative + mandatory 27
- Preventative + discretionary 9
- Detective + mandatory 3
- Detective + discretionary 1
- Corrective + mandatory 3
- Corrective + discretionary 1
So preventative beats detective/corrective , and mandatory beats discretionary — a preventative mandatory control (27 points) is worth 27× a discretionary detective/corrective one (1 point). Points are awarded per action per assessment : an action worth 10 points appearing in two assessments contributes 20 points overall (with an exception that technical actions scoped to the whole tenant are counted once).
Why the weighting works this way
The weighting is deliberate risk math. Preventative controls stop a problem before it happens, so they reduce risk the most and earn the most points. Detective controls only spot a problem after it starts, and corrective controls only limit damage afterward — valuable, but less risk-reducing, so they earn far fewer points. Layered on top, mandatory controls can't be bypassed, so their protection is reliable; discretionary controls depend on humans remembering to comply, so they're scored lower.
The practical takeaway for both the exam and real life: to raise your compliance score efficiently , prioritize the preventative + mandatory improvement actions worth 27 points each, not a long list of 1-point discretionary detective tasks.
Score levels
A score value is assigned at three levels, and you should know the hierarchy: each improvement action has a point value; each assessment has a score calculated from its actions; and the overall compliance score rolls those up across all assessments (counting each Microsoft action once, each technical action once, and each non-technical action once per group). Because of that counting logic, your overall score may not equal the simple average of your individual assessment scores — a detail Microsoft explicitly calls out.
Improvement Actions, Your Initial Score, and the Secure Score Trap
Improvement actions are the concrete, assignable tasks that raise your score. Each carries the point value above and includes implementation guidance, an owner, status (e.g., not implemented, implemented, tested), and evidence. For actions covering Azure resources supported by Microsoft Defender for Cloud , an action's score is the average across its subscriptions , and each subscription is scored by the status of its relevant resources (e.g., subscription A at 0% and subscription B at 50% average to a 25% action score).
Your initial score comes from the default Microsoft 365 Data Protection Baseline — Compliance Manager starts scoring you against it automatically, so you have a starting posture before configuring anything. As you complete improvement actions (and add assessments for your specific regulations), the score moves.
The single biggest scoring trap on SC-900
Do not confuse these two scores:
- Score Product What it measures
- Compliance score Compliance Manager (Microsoft Purview) Progress on compliance/regulatory improvement actions
Microsoft Secure Score Microsoft Defender (Defender XDR / Defender for Cloud) Security posture — how well you're protected against threats
If the scenario says regulatory, assessment, control, GDPR/HIPAA, improvement action → compliance score . If it says security recommendations, protect against threats, harden resources, secure posture → Secure Score . They share a similar shape (complete recommendations to raise a number) but live in different families.
Other traps: the compliance score is not a guarantee of compliance and not the SC-900 exam passing score (700/1000). Treat it as a prioritization and progress signal: completing high-value preventative mandatory actions raises it fastest, which is exactly why those are scored at 27 points.
Worked scoring example
Suppose your default Data Protection Baseline lists four outstanding improvement actions: encrypt data at rest ( preventative mandatory, 27 ), enforce a centrally managed password policy ( preventative mandatory, 27 ), enable access auditing ( detective mandatory, 3 ), and ask users to lock their screens ( discretionary, 1 ). Completing the two 27-point preventative-mandatory actions adds 54 points to your tenant — far more than the 4 points the other two combine to give. This is why a security architect chasing a higher score in a hurry implements encryption and enforced policy first.
For an Azure action covered by Microsoft Defender for Cloud , remember the per-subscription averaging : if subscription A has 0 of 1 resource compliant (0%) and subscription B has 1 of 2 compliant (50%), the action scores 25% of its point value, not a flat all-or-nothing. Knowing both the point table and this averaging rule lets you answer the calculation-flavored items SC-900 sometimes includes, while the compliance-score-versus-Secure-Score distinction handles the conceptual ones. Keep "compliance = Purview/regulatory" and "Secure Score = Defender/security" locked in, and this section's questions become reliable points.