Study guide

10.4 Data Loss Prevention

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

10.4 Data Loss Prevention

Key Takeaways Explain This Topic AI

Data loss prevention (DLP) detects sensitive content in motion and at rest and enforces actions to stop inappropriate sharing or exposure.

A single DLP policy spans multiple locations: Exchange Online email, SharePoint Online, OneDrive, Microsoft Teams chat/channels, Office apps, and Windows/macOS endpoints (Endpoint DLP).

Endpoint DLP uses the Microsoft Purview agent integrated with Microsoft Defender for Endpoint to control USB copy, print, clipboard, and cloud-upload actions on devices.

DLP actions include blocking, restricting, auditing, showing policy tips to users, and allowing a justified override; conditions reuse sensitive information types, trainable classifiers, and sensitivity labels.

Last updated: June 2026

What DLP Detects and Where It Enforces

Data loss prevention (DLP) is the Microsoft Purview capability that stops sensitive information from being shared, leaked, or exposed inappropriately . Where classification identifies data and sensitivity labels protect a file, DLP watches actions — sending, sharing, copying, uploading — and intervenes when those actions would expose sensitive content. The exam keyword is prevent .

DLP detects sensitive content using the same classification building blocks from earlier in this chapter: sensitive information types , trainable classifiers , and sensitivity labels . So a DLP rule can say, in effect, "if a message contains a credit card number" (SIT), "or a document the Resume classifier matched" (trainable classifier), "or anything labeled Highly Confidential" (sensitivity label), then take an action.

The most important SC-900 fact is coverage : a single DLP policy can apply across many Microsoft 365 locations at once . The tested locations are:

  • Location What DLP protects there
  • Exchange Online Email messages and attachments leaving or moving in the org
  • SharePoint Online Documents shared from team and communication sites
  • OneDrive Files shared from users' personal cloud storage
  • Microsoft Teams Chat and channel messages containing sensitive info
  • Devices (Endpoint DLP) Windows 10/11 and macOS — USB copy, print, clipboard, cloud upload
  • Office apps Word, Excel, PowerPoint enforcement in real time
  • Microsoft Defender for Cloud Apps Sensitive data in connected third-party/SaaS cloud apps
  • On-premises (scanner) File shares and SharePoint Server via the information-protection scanner

This breadth is the point: an administrator authors one policy and Purview distributes it to all the selected enforcement points, so the same rule protects an email, a Teams chat, a SharePoint document, and a USB copy on a laptop.

Endpoint DLP, Actions, and Policy Tips

Endpoint DLP extends prevention from cloud services down to the physical device. It uses the Microsoft Purview agent integrated with Microsoft Defender for Endpoint to monitor file activity on Windows 10/11 and macOS machines and to block or audit risky actions such as copying a sensitive file to a USB drive, printing it, copying it to the clipboard, uploading it to an unallowed cloud service, or opening it in an unapproved app . This is why Endpoint DLP scenarios often mention Defender for Endpoint — the agent is shared.

When a rule matches, DLP can take graduated actions :

Audit only — log the event for visibility without disrupting the user (good for tuning).

Block — stop the action entirely (for example, prevent the email from being sent externally).

Block with override — block but let the user justify and proceed, which is recorded.

Restrict access or encrypt the content.

Show a policy tip — an in-context message in Outlook, Office, or Teams warning the user before they do something risky and explaining why.

Notify admins via incident reports and surface matches in Activity explorer and DLP alerts .

Policy tips are an exam favorite because they educate users at the moment of risk rather than silently blocking — they reduce accidental leaks while keeping people informed.

Choosing DLP vs the neighbors

DLP sits next to sensitivity labels, and the two cooperate (a DLP rule can act on labeled content), but they answer different verbs:

"Classify / mark / encrypt this file so protection follows it" → sensitivity label .

"Stop users from sharing or copying this sensitive data" → DLP .

"Keep or delete this content on a schedule" → retention .

"Find and review content for a legal case" → eDiscovery .

Trap: the word "prevent" can lure candidates toward a security product. Microsoft Defender protects endpoints, identities, and workloads against threats ; Azure Firewall / NSGs filter network traffic. Preventing sensitive data from being shared inappropriately is squarely a Microsoft Purview DLP task. Likewise, DLP is not visibility-only — if a scenario merely wants to see where sensitive data is, that is Content explorer / classification , not DLP.

How a DLP Policy Is Built and Monitored

A DLP policy is assembled from a few parts that SC-900 may reference by name. Understanding the structure helps you recognize DLP in a scenario:

Locations — the workloads the policy applies to (Exchange, SharePoint, OneDrive, Teams, Devices, Office apps, Defender for Cloud Apps, on-premises).

Rules — each rule contains conditions , actions , and user notifications . A policy can hold several rules with different sensitivity thresholds.

Conditions — what to look for, reusing classification: a sensitive information type , a trainable classifier , a sensitivity label , or a count threshold (for example "10 or more credit card numbers").

Actions — what to do: block, restrict, encrypt, or audit.

User notifications and policy tips — what the user sees and whether they can override.

Incident reports / alerts — who gets notified when the rule matches.

A common design pattern is graduated enforcement : a low-count rule that only audits and shows a policy tip , and a high-count rule that blocks with override when a lot of sensitive data is present. This balances productivity against protection — most accidental exposures are caught by the tip, while serious leaks are blocked.

DLP policy part Question it answers

Locations Where does the rule apply?

Conditions What sensitive content triggers it? (SIT, classifier, label)

Actions What happens — block, restrict, audit, encrypt?

User notifications Does the user see a policy tip? Can they override?

Incident reports Who is alerted and where is it logged?

Once live, DLP results are monitored in the DLP alerts dashboard and surfaced in Activity explorer , tying this section back to the visibility tools earlier in the chapter. So the full loop is: classify the data, label it, write a DLP policy that acts on the classification or label, then monitor matches in Activity explorer and DLP alerts. For SC-900 you do not configure these in detail — you recognize that DLP is the prevention control, that one policy spans many locations, and that it consumes the same classification signals as labels and retention.