Study guide

10.3 Sensitivity Labels and Label Policies

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.3 Sensitivity Labels and Label Policies

Key Takeaways Explain This Topic AI

A sensitivity label both CLASSIFIES content (Public, General, Confidential, Highly Confidential) and can PROTECT it with encryption, content marking, and access restrictions.

A sensitivity label is persistent and metadata-based: it travels with the file wherever it goes, so protection stays attached even outside Microsoft 365.

Labels are made available to users through a label policy, which publishes them to specific users/groups and can set a default, mandatory labeling, or a justification for downgrades.

Labels can be applied manually by users, automatically by policy, or recommended; only one sensitivity label applies at a time, chosen by priority order.

Last updated: June 2026

What a Sensitivity Label Does

Sensitivity labels are the heart of Microsoft Purview Information Protection (the capability formerly called Microsoft Information Protection, and before that Azure Information Protection). A sensitivity label does two jobs at once: it classifies content with a sensitivity level, and it can protect that content by applying real enforcement. Most organizations build a small hierarchy of labels such as Public → General → Confidential → Highly Confidential , sometimes with sub-labels (for example Confidential\Finance , Confidential\Legal ).

The protection a label can enforce includes:

Encryption — the label can apply rights-management encryption that controls who can open the content and what they can do (read, edit, print, forward, copy). Encryption is enforced by usage rights, so even a leaked file stays unreadable to unauthorized people.

Content marking — automatic headers, footers, and watermarks (for example a "Confidential" watermark on every page).

Protection for containers — labels can also be applied to Teams, Microsoft 365 Groups, and SharePoint sites to control external sharing, guest access, and privacy.

Auto-labeling — a label can be applied automatically when classification (a SIT or trainable classifier) matches, so users do not have to remember.

The most-tested property is persistence . A sensitivity label is written into the file as metadata that travels with the content . If a labeled and encrypted document is emailed outside the company, copied to a USB drive, or uploaded to a non-Microsoft service, the label and its protection stay attached . This is why labels — not DLP — are the answer when a scenario asks for protection that follows the data everywhere .

  • Label capability What it does Example exam clue
  • Classification Tags content with a sensitivity level "Mark documents as Confidential"
  • Encryption Restricts who can open/edit/print via usage rights "Only the finance team can open the file"
  • Content marking Adds header, footer, or watermark "Add a Confidential watermark"
  • Container labeling Controls sharing on Teams/Groups/SharePoint "Block guest access on a site"
  • Persistence Label and protection travel with the file "Protection must follow the file outside the org"

Label Policies and How Labels Are Applied

Creating a label is only half the work — users cannot see a label until it is published through a sensitivity label policy (also called a label policy ). The policy controls who gets which labels and how they behave :

Scope — which users and groups the labels are published to (you can give different labels to different departments).

Default label — a label automatically pre-selected on new documents and emails.

Mandatory labeling — require users to apply a label before they can save a document or send mail ("no label, no save").

Justification for downgrade — require a reason when a user lowers a label (Confidential → General) or removes one. These events show up in Activity explorer .

A link to the help page that explains the labels to users.

Labels can reach content three ways: manual (the user picks it from the Sensitivity button in Office, Outlook, or the web), automatic (an auto-labeling policy applies it when classification matches), and recommended (Office prompts the user to apply a suggested label and lets them accept or dismiss it). A crucial rule: only one sensitivity label can be applied to an item at a time , and when multiple auto-labeling conditions match, the label with the higher priority (its order in the list) wins.

Sensitivity vs Retention — the key trap

SC-900 deliberately tests the difference between the two Purview label families because both use the word "label":

  • Sensitivity label Retention label
  • Purpose Protect data (classify, encrypt, mark) Govern lifecycle (retain / delete)

Question it answers How sensitive is this and who may use it? How long must we keep this and then what?

  • Enforcement Encryption, watermark, access rights Retain, delete, or mark as a record
  • Travels with file outside M365? Yes (persistent protection) No (lifecycle is governed in M365)
  • How many per item One sensitivity label One retention label

Remember the one-line distinction: sensitivity labels protect data; retention labels govern its lifecycle. If a scenario mentions confidentiality, encryption, watermarks, or controlling who can open a file, choose a sensitivity label . If it mentions keeping records for seven years, deleting after a period, or declaring a record, choose a retention label (next two sections). Mixing these up is one of the most common SC-900 mistakes.

A Worked Label Hierarchy and Common Distinctions

A typical organization publishes a short, ordered label set. Order matters because it sets priority — a label lower in the list is more restrictive and wins when auto-labeling conditions overlap:

  • Label (low → high) Classification meaning Protection it might apply
  • Public Approved for public release None
  • General Internal business data, not for outside release Footer "Internal use only"
  • Confidential Sensitive business data Header/watermark + encryption for staff
  • Confidential\Finance (sub-label) Sensitive, finance-only Encryption limited to the finance group
  • Highly Confidential Most sensitive (e.g., legal, M&A) Strong encryption, no forwarding, watermark

Sub-labels (like Confidential\Finance ) let you offer departmental variants under one parent without cluttering the top-level list.

Several distinctions appear repeatedly on the exam:

Label vs label policy. The label defines what protection (encryption, marking). The label policy defines who can use the label and how it behaves (default, mandatory, justification). A question that says "users can't see the labels" is a policy problem; a question about what encryption is applied is a label problem.

Manual vs automatic vs recommended. Users can choose a label themselves, the service can apply one automatically when classification matches, or Office can recommend one and let the user accept or dismiss it.

Persistent protection. Because the label is metadata embedded in the file and the encryption is enforced by usage rights, the protection works even outside Microsoft 365 — on a USB stick or a competitor's cloud. This is the property DLP does not have; DLP acts at the service boundary, while the label travels with the file.

One label at a time. An item has at most one sensitivity label. If you need both protection and lifecycle governance, you pair one sensitivity label with one retention label.

For SC-900 you will not configure encryption keys or rights — you will choose sensitivity labels whenever the requirement is to classify, mark, or protect content, and you will separate that cleanly from DLP (prevent sharing) and retention (govern lifecycle).