Study guide
9.2 Privacy Principles and Microsoft Priva
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.2 Privacy Principles and Microsoft Priva
Key Takeaways Explain This Topic AI
Microsoft's approach to privacy rests on six principles: control, transparency, security, strong legal protections, no content-based targeting, and benefits to you.
Microsoft Priva is the privacy product family: Priva Privacy Risk Management detects risks like data hoarding, oversharing, and transfers; Priva Subject Rights Requests automates DSR fulfillment.
No content-based targeting means Microsoft does not use your email, chat, or files to target advertising.
On SC-900, map explicit privacy/personal-data language to Priva — not Defender (security) or Compliance Manager (general posture).
Last updated: June 2026
Microsoft's Six Privacy Principles
SC-900 expects you to know that Microsoft's approach to privacy is built on six foundational principles . These describe how Microsoft handles the data you entrust to its cloud:
Principle What it means
Control Microsoft puts you in control of your privacy with easy-to-use tools and clear choices.
Transparency Microsoft is transparent about data collection and use so you can make informed decisions.
Security Microsoft protects the data you entrust to it through strong security and encryption.
Strong legal protections Microsoft respects local privacy laws and defends privacy as a fundamental human right.
No content-based targeting Microsoft does not use your email, chat, files, or other personal content to target ads.
Benefits to you When Microsoft collects data, it uses it to benefit you and improve your experiences.
A frequent exam item asks which option is not one of the six (distractors like "data minimization," "consent," "accountability," or "anonymization" sound plausible but are not on the list). Memorize the six exact terms. The principle most often tested in isolation is no content-based targeting — Microsoft will not mine your Exchange, Teams, or OneDrive content to sell ads. A close second is strong legal protections , where Microsoft commits to challenging government data requests and treating privacy as a fundamental human right.
Privacy is distinct from security and from general compliance, and SC-900 leans on that distinction:
Discipline Core question Example Microsoft tool
Security Are systems, identities, and data protected from attack and unauthorized access? Microsoft Defender, Sentinel
- Compliance Can we demonstrate we meet our obligations? Compliance Manager
- Privacy Is personal data handled responsibly, honoring individuals' rights? Microsoft Priva
Security protects systems and data from unauthorized access; compliance demonstrates you meet obligations and can prove it; privacy governs the responsible handling of personal data and the rights of the people that data describes. The three overlap — a privacy breach is often also a security incident with compliance consequences — but the exam wants you to pick the privacy-specific product when the stated goal is personal-data handling or individual rights, even though security and compliance products appear in the same answer set.
Microsoft Priva
Microsoft Priva is the product family that operationalizes privacy inside the Microsoft Purview/Priva ecosystem. It helps organizations proactively identify and protect against privacy risks and respond to data-subject requests. The two capabilities SC-900 most often references are:
Priva Privacy Risk Management
Scans the data estate to detect privacy risks and helps remediate them. The three risk patterns called out by Microsoft are:
Data overexposure / oversharing — personal data shared more broadly than it should be.
Data hoarding — personal data kept longer than necessary, with no business need.
Data transfers — personal data moving across departmental or geographic boundaries in risky ways.
Priva can establish policies that detect these conditions, then notify users directly with recommended actions (for example, a guided email nudging an employee to remove oversharing) so remediation scales without manual investigation of every file.
Priva Subject Rights Requests (SRR)
Manages data subject requests (DSRs / subject rights requests) at scale — the requests individuals make under laws like GDPR or CCPA to access, correct, or delete their personal data. Priva SRR provides automated data discovery, conflict detection, and file review and redaction , plus collaboration workflows, so privacy teams fulfill requests faster and more confidently than searching mailboxes and sites by hand. (The broader Priva suite also includes capabilities such as Consent Management, Privacy Assessments, and Tracker Scanning, but Risk Management and Subject Rights Requests are the SC-900 anchors.)
Selection cues
Scenario language Best answer Why
"Detect data oversharing / hoarding / risky transfers of personal data" Priva Privacy Risk Management Privacy risk detection and remediation
"Respond to GDPR data-subject access/deletion requests at scale" Priva Subject Rights Requests Automates DSR discovery, review, redaction
"We don't want our email content used for advertising" No content-based targeting (privacy principle) A stated Microsoft commitment, not a product
- "Detect malware on a laptop" Microsoft Defender for Endpoint Security, not privacy
- "Track our compliance score and improvement actions" Compliance Manager General posture, not privacy-specific
Common trap: Priva looks like "just compliance," so test-takers pick Compliance Manager. If the goal is explicitly about personal-data privacy risk or subject rights requests , choose Priva ; Compliance Manager is for broad regulatory posture and scoring, not the day-to-day privacy operations Priva automates.
Worked privacy scenario
A privacy officer reports that employees keep copying customer records containing personal data into a shared site accessible company-wide, and that the volume of GDPR access requests is overwhelming the team. Two needs, two Priva capabilities:
Personal data shared too broadly → Priva Privacy Risk Management creates a policy that detects the oversharing and nudges users to fix it.
GDPR access requests piling up → Priva Subject Rights Requests automates the discovery, review, and redaction needed to fulfill each request.
Notice that neither answer is a Defender product (no threat is being detected), an Entra control (no identity decision), or the Service Trust Portal (no Microsoft audit document is needed). The goal is responsible handling of personal data and the rights of the people it describes — that is the Priva lane.
Why not Compliance Manager? Compliance Manager helps assess and document GDPR posture overall and earn a score, but it does not operationally discover oversharing or process individual subject requests . When the scenario describes the hands-on privacy operation rather than the assessment-and-scoring view, Priva is the precise answer.