SC-401 Cheat Sheet
Implement information protection
Implement and manage data classification
Read full chapterCheat sheet
Sharp facts the exam loves — scan these before test day.
- A classification taxonomy must express business sensitivity in terms users understand
A sensitivity taxonomy translates business and regulatory requirements into recognizable categories and handling expectations. Define label names and descriptions with business stakeholders, include concrete examples in tooltips, and test the terminology with the people who will classify content. Configure the protection required for each category after establishing what belongs in it.
Trap Using department names as the entire sensitivity hierarchy when the same department handles both public and restricted information, because ownership alone does not identify handling requirements.
4 questions test this
- You have a Microsoft 365 E5 subscription. You are defining sensitivity labels for 5,000 users. Draft names from the security team include CL-3-RESTRICT and DPA-ART9. Pilot users often pick the wrong l
- You have a Microsoft 365 E5 subscription. The compliance team finalized label names and tooltips in a workshop with legal and IT stakeholders. You plan to publish the labels to the whole organization
- You have a Microsoft 365 E5 subscription. A project team wants to create sensitivity labels with encryption and watermarks right away. No classification categories have been agreed with business owner
- You have a Microsoft 365 E5 subscription. Users can't tell whether a project budget belongs under General or Confidential. You plan to update each label so users see guidance when hovering over it in
- Recognizing sensitive information and enforcing its handling are separate configuration decisions
Microsoft Purview classifiers identify sensitive content, while sensitivity labels and policies determine how that content is classified and protected. A sensitivity label can deliberately identify a category without adding encryption or markings, allowing an organization to measure usage before introducing protection. Choose the detection requirement and the required handling action separately rather than treating a match as an automatic grant or restriction of access.
Trap Using a custom sensitive information type as the access-control policy, because a detector supplies classification evidence rather than a set of authorized readers.
5 questions test this
- You have a Microsoft 365 E5 subscription. Leadership wants to know how much content is sensitive and where it's used before deciding on any restrictions. Users must be able to label documents now with
- You have a Microsoft 365 E5 subscription. Compliance requires two outcomes for documents that contain U.S. Social Security numbers. The content must be identified, and each document must display a CON
- You have a Microsoft 365 E5 subscription. You created a custom sensitive information type named HRSIT that detects employee review files. A manager expects that once HRSIT matches a file, only HR memb
- You have a Microsoft 365 E5 subscription. A custom sensitive information type named PayrollSIT detects payroll files. Only members of the Payroll group must be able to open matching files, wherever th
- You have a Microsoft 365 E5 subscription. A custom sensitive information type named SIT1 detects merger documents in SharePoint, and Content explorer shows thousands of matches. None of the matching f
- Classifier changes require management permission and review of dependent policies
Before editing or deleting a classifier, use an account with classifier-management permission and inspect the policies that depend on it. The Information Protection Admin role, available through Information Protection Admins, permits classifier creation, editing, and deletion without requiring Global Administrator; Information Protection Analyst and Investigator provide view-only classifier access rather than classifier-management authority. On the Classifiers page, inspect the policy-usage count and dependencies so you can assess the effect on consuming policies before changing their detector. The Classified items count measures detected items, not how many policies depend on the classifier.
Trap Using the Classified items count as the safety check before deleting a detector, because content prevalence does not reveal which configured policies still reference it.
3 questions test this
- You have a Microsoft 365 E5 subscription. User1 investigates DLP incidents. User1 must manage DLP alerts, use Activity explorer and Content explorer, and open file contents. User1 must have view-only
- You have a Microsoft 365 E5 subscription. User1 must create, edit and delete trainable classifiers and sensitive information types. User1 must not manage eDiscovery or insider risk. The solution must
- You have a Microsoft 365 E5 subscription. You plan to delete a custom sensitive information type named ProjCodes. Data explorer shows 12,000 classified items for ProjCodes. Before deleting it, you mus
- A supported built-in sensitive information type can be copied when its detection needs customization
When a Microsoft-provided pattern already meets the requirement, use its built-in sensitive information type to avoid maintaining a separate detector. For organization-specific changes, copy a supported built-in type and edit the custom copy, or define a custom type from scratch. Built-in definitions themselves are not editable, and the portal documents exceptions that cannot be copied, including several bundled identification types. Named-entity SITs cannot be edited or copied. For an otherwise copyable SIT with 10 text processors or restricted text processors, use PowerShell because the portal cannot copy it directly.
Trap Using a named-entity SIT as an editable template, because its definition supports neither copying nor editing.
6 questions test this
- You have a Microsoft 365 E5 subscription. You copied the built-in Credit Card Number type, named the copy Contoso CC, and added keywords to it. An existing DLP policy that references Credit Card Numbe
- You have a Microsoft 365 E5 subscription. Coders need detection of International classification of diseases (ICD-10-CM) codes that also requires the keyword Claim nearby. The ICD-10-CM overview page i
- You have a Microsoft 365 E5 subscription. You need to create customized detection based on the following built-in sensitive information types: - Canada driver's license number - U.S. / U.K. passport n
- You have a Microsoft 365 E5 subscription. A DLP policy must detect any U.S. Social Security number in email, not only employee numbers. A consultant proposes building a custom regex type. The Microsof
- You have a Microsoft 365 E5 subscription. You want to narrow the All physical addresses type by adding exclusions for your office addresses. In the Microsoft Purview portal, neither a Copy option nor
- You have a Microsoft 365 E5 subscription. You plan to customize a built-in sensitive information type named SIT1 that has 10 text processors, including keyword lists, regular expressions and functions
- Bundled and unbundled named entities offer different detection breadth
Choose a bundled named-entity SIT such as All physical addresses for broad recognition, or an unbundled entity for a particular country, region, or class of terms. Named-entity sensitive information types recognize person names, physical addresses, and medical terms and conditions. Verify E5 licensing before choosing advanced named-entity detection. For a bundled SIT in Endpoint DLP, also verify that Advanced classification scanning and protection is enabled.
Trap Using a keyword dictionary of known customers for an open-ended requirement to identify previously unseen personal names, because a vocabulary list only matches its supplied terms.
4 questions test this
- You have a Microsoft 365 E5 subscription. A DLP policy must detect customer full names in emails sent to external recipients. New customers are added daily, and many names that must be detected will n
- You have a Microsoft 365 E5 subscription. A health insurer needs a DLP policy for Exchange that detects any medical condition, test or medication term in outgoing email. The compliance team wants the
- You have a Microsoft 365 E5 subscription. A DLP policy for an Australian subsidiary must detect physical addresses in Australia, including addresses that aren't already known. Matches on addresses fro
- You have a Microsoft 365 E5 subscription. A pharmacy chain needs an auto-labeling policy that labels documents mentioning brand-name medicines such as Tylenol. Documents that mention only blood tests
- All credentials detects the credential family while individual members narrow the requirement
Select the All credentials sensitive information type when the requirement is to detect the full set of credential-scanning types available in the portal. Each member can also be used as a standalone SIT when only a particular credential type belongs in the detection scope. Credential-scanning SITs require an E5 license, so verify that entitlement before choosing this built-in detector family.
Trap Using All credentials for a rule limited to one credential type, because the bundle includes the other credential detectors and broadens the matching population.
5 questions test this
- You have a Microsoft 365 E5 subscription. A DLP rule named Rule1 must block Teams messages that contain GitHub personal access tokens only. Rule1 currently uses All credentials and also blocks message
- You have a Microsoft 365 E5 subscription. A DLP rule for a database team's SharePoint site must detect Azure SQL connection strings only. Other credential types in that site are expected and must not
- You have a Microsoft 365 E5 subscription. You create a DLP policy named DLP1 for SharePoint sites used by the DevOps team. DLP1 must detect Azure DevOps personal access tokens, Azure SQL connection st
- You have a Microsoft 365 E3 subscription. You plan a DLP policy for SharePoint sites that uses the All credentials sensitive information type. Before you design the policy rules, you need to confirm t
- You have a Microsoft 365 E5 subscription. Rule1 must block Exchange email that contains GitHub personal access tokens. Rule2 must audit email that contains any other credential type that the portal ca
- A custom sensitive information pattern combines a primary match with corroborating evidence
A custom sensitive information type contains one or more patterns, each defining a primary element, confidence level, character proximity, and any supporting elements. Use a regular expression for a structured identifier, a keyword list or dictionary for known terms, or an available function for supported detection logic. Supporting elements provide contextual corroboration, and multiple patterns let the same information type recognize different evidence combinations.
Trap Using a trainable classifier to implement an exact timestamp-shaped document ID, because learning a document category is unnecessary for a deterministic format requirement.
5 questions test this
- You have a Microsoft 365 E5 subscription. Order IDs at your company combine an eight-digit date stamp, a hyphen and a six-digit sequence, such as 20261108-004512. A DLP policy named DLP1 must detect t
- You have a Microsoft 365 E5 subscription. You are creating a custom sensitive information type named SIT1 whose primary element is a regex for member IDs. Matches must be corroborated by a nearby date
- You have a Microsoft 365 E5 subscription. You are defining a pattern in a custom sensitive information type. The primary element must match any of 12 fixed project names, such as Falcon and Osprey, wh
- You have a Microsoft 365 E5 subscription. You define a custom sensitive information type named SIT1 for contract numbers. Matches that have the keyword Contract nearby must be reported at high confide
- You have a Microsoft 365 E5 subscription. A custom sensitive information type named SIT1 detects nine-digit policy numbers by using a regular expression. SIT1 matches many unrelated nine-digit values.
- Sensitive information confidence thresholds trade false positives against false negatives
Sensitive information types use low, medium, and high confidence values of 65, 75, and 85. Selecting low includes low, medium, and high matches; medium includes medium and high; high selects only high-confidence matches. Higher-confidence patterns generally require stronger corroboration and reduce false positives at the cost of potentially missing sensitive content, so choose confidence and occurrence thresholds together for the intended protection.
Trap Increasing a rule's occurrence threshold to repair an overbroad primary pattern, because the threshold changes how many detections are needed rather than improving each detection's evidence.
4 questions test this
- You have a Microsoft 365 E5 subscription. A legacy custom sensitive information type named SIT1 was created with a pattern confidence value of 70. You review SIT1 in the Microsoft Purview portal, whic
- You have a Microsoft 365 E5 subscription. A DLP rule named Rule1 is configured with medium confidence for a custom sensitive information type named SIT1. A file contains a SIT1 match that SIT1 rates a
- You have a Microsoft 365 E5 subscription. For a legal hold review, the compliance team wants a DLP rule named Rule1 to return every possible match of a custom type, accepting many false positives. SIT
- You have a Microsoft 365 E5 subscription. You define a custom sensitive information type in rule package XML. The Entity element sets recommendedConfidence, and one Pattern element sets confidenceLeve
- Character proximity determines which supporting evidence belongs to a primary match
Character proximity defines how close supporting evidence must be to the primary element of a sensitive information pattern. The complete supporting value must fit within the configured proximity window; a window that reaches only the beginning of the value is insufficient. Set a narrow window for tightly formatted records and a wider one when legitimate context is farther away, validating that unrelated records do not supply accidental corroboration.
Trap Selecting a higher pattern confidence level to connect a distant customer name with an identifier, because confidence selection does not extend the character window.
6 questions test this
- You have a Microsoft 365 E5 subscription. A custom sensitive information type named SIT1 has a regex primary element and two supporting elements. The keyword Invoice must be within 50 characters of th
- You have a Microsoft 365 E5 subscription. You customize a copy of the Credit Card Number entity in rule package XML. Its keywords must count as corroborative evidence when they appear up to 600 charac
- You have a Microsoft 365 E5 subscription. A custom type named SIT1 requires Name or DateOfBirth within 250 characters of each SSN value. In a file, a Name value and a DateOfBirth value sit next to eac
- You have a Microsoft 365 E5 subscription. You widened the proximity of SIT1 from 300 to 2,000 characters so that contract numbers match customer names in a letter's signature block. Before production,
- You have a Microsoft 365 E5 subscription. A custom type named SIT1 uses an account number regex as its primary element and one supporting element: CustomerName within 200 characters. In invoices, each
- You have a Microsoft 365 E5 subscription. A custom type named SIT1 detects eight-digit member IDs and uses the keyword Member within 1,000 characters as supporting evidence. In exported lists, unlabel
- Custom sensitive information regex patterns require one primary capturing group
Microsoft Purview custom sensitive information regex patterns use one primary capturing group, with noncapturing groups for any additional grouping. Put alternative formats inside that single capturing group rather than using separate top-level captures. Avoid positional anchors such as ^ and $, because the content-scanning process does not guarantee a stable document start or end for matching.
4 questions test this
- You have a Microsoft 365 E5 subscription. A custom type named SIT1 uses one primary capturing group, noncapturing delimiters and no anchors. A new ID variant, two letters plus four letters plus one di
- You have a Microsoft 365 E5 subscription. You create a custom type named SIT1 with the primary regex ^CT[0-9]{8}$. The Test option shows matches when a file contains only a contract number, but docume
- You have a Microsoft 365 E5 subscription. You try to save a custom type that uses this primary regex: (?:\s)([A-Z]{2}[0-9]{3})(?:\s)|(?:\s)([A-Z]{2}[0-9]{5})(?:\s) Validation blocks the pattern. You n
- You have a Microsoft 365 E5 subscription. You need a custom type named SIT1 to detect employee IDs in the format EMP plus six digits or the legacy format CT plus eight digits, separated from text by w
- An XML-based custom SIT needs distinct identifiers and a Unicode rule-package import
When creating a custom SIT from an exported definition, give the RulePack and Entity new GUIDs and make each localized Resource idRef match the corresponding Entity id. In Security & Compliance PowerShell, export definitions with Get-DlpSensitiveInformationTypeRulePackage and write the SerializedClassificationRuleCollection bytes to an XML file before extracting and modifying the required rule. Save the custom rule XML with Unicode encoding matching its utf-16 declaration, then import its bytes with New-DlpSensitiveInformationTypeRulePackage -FileData ([System.IO.File]::ReadAllBytes('C:\Rules\Custom.xml')). Verify the resulting SIT and its display name with Get-DlpSensitiveInformationType before adding it to a consuming policy.
Trap Reusing the exported Entity GUID while changing only its display name, because the GUID identifies the rule independently of the localized name.
5 questions test this
- You have a Microsoft 365 E5 subscription. You pasted the built-in Credit Card Number Entity element, with GUID 50842eb7-edc8-4019-85dd-5a5c1f2bb085, into a new rule package for a customized version. Y
- You have a Microsoft 365 E5 subscription. You plan to customize the XML definition of the built-in Credit Card Number type. You connect to Security & Compliance PowerShell. You need to store the organ
- You have a Microsoft 365 E5 subscription. You uploaded a custom rule package that defines a new type named Contoso Card. Before you add Contoso Card to a DLP policy, you need to confirm in Security &
- You have a Microsoft 365 E5 subscription. In Security & Compliance PowerShell, you ran $ruleCollections = Get-DlpSensitiveInformationTypeRulePackage. You now need an XML file of the rules that you can
- You have a Microsoft 365 E5 subscription. You edited an exported rule package in a text editor and saved it as MyNewRulePack.xml with UTF-8 encoding. The XML declaration specifies encoding="utf-16". A
- Keyword dictionaries provide reusable vocabulary matching at larger scale than keyword lists
When the sensitive content is defined by a maintained vocabulary, use a keyword dictionary as a primary or supporting element in a custom sensitive information type. In the portal, create or edit the type and its pattern before uploading a TXT or CSV dictionary, reusing an existing dictionary, or entering terms. Dictionaries support any language and share a combined tenant limit of 1 MB after compression. For Security & Compliance PowerShell imports, save one keyword per line in a Unicode-encoded text file, read it with [System.IO.File]::ReadAllBytes, and pass those bytes to New-DlpKeywordDictionary -FileData.
Trap Using a regular expression that enumerates every changing project code, because a managed vocabulary is easier to update and reuse than embedding the entire inventory in pattern logic.
4 questions test this
- You have a Microsoft 365 E5 subscription. In the Microsoft Purview portal, you are creating a custom sensitive information type and choose Keyword dictionary as the primary element. Your terms are in
- You have a Microsoft 365 E5 subscription. Legal maintains about 4,000 matter code names that change monthly and appear in English, French, and Japanese documents. Several custom sensitive information
- You have a Microsoft 365 E5 subscription. Three departments plan keyword dictionaries of 400 KB, 350 KB and 450 KB after compression for their own custom types. You need to determine whether the plan
- You have a Microsoft 365 E5 subscription. You exported 3,000 project code names to codes.txt, one name per line, saved with Unicode encoding. In Security & Compliance PowerShell, you read the file int
- Regex validators test whether a well-shaped identifier is actually valid
A regex validator supplements a format match with checks such as a checksum, Luhn validation, or a date embedded in the identifier. Configure checksum weights, modulus, and check-digit position for the identifier's algorithm, or choose the date format and the starting offset of its date substring. Use these validators when format alone accepts invalid values; a date beginning at the first character has offset 0.
Trap Adding a nearby employee keyword to validate an embedded hire date, because contextual evidence does not verify that the identifier contains an acceptable date.
3 questions test this
- You have a Microsoft 365 E5 subscription. You configure a checksum validator for an eight-digit account number. The algorithm multiplies digits 1 through 7 by weights and takes the result modulo 9. Th
- You have a Microsoft 365 E5 subscription. Employee IDs are nine digits: the first six digits are the hire date in DDMMYY format, and the last three are random. You define the primary element as \d{9}
- You have a Microsoft 365 E5 subscription. You are creating a custom type for eight-digit license numbers. The eighth digit is a check digit equal to the weighted sum of the digits modulo 9. Random eig
- Additional checks refine a sensitive information match without replacing its primary pattern
Sensitive information type additional checks can exclude specified test values, reject repeated identical characters, constrain starting or ending characters, and include or exclude immediate prefixes and suffixes. Choose the check that expresses the known false-positive rule instead of weakening all detection. Prefix and suffix checks concern adjacent text, while a supporting element uses a proximity relationship.
Trap Raising the confidence requirement to remove a known test identifier, because the same test value can still appear with convincing contextual evidence.
4 questions test this
- You have a Microsoft 365 E5 subscription. A custom type named OrderSIT detects 10-digit order numbers. QA logs contain test orders written as 4820019375:TEST, which trigger DLP alerts. Real order numb
- You have a Microsoft 365 E5 subscription. A custom type named SIT1 matches 32-character hexadecimal tokens. Log files contain many identifiers written as GUID: followed by a matching value, which must
- You have a Microsoft 365 E5 subscription. A custom type must detect only card numbers that start with 41, 42 or 43. Numbers with any other leading digits must be ignored. You need to configure the res
- You have a Microsoft 365 E5 subscription. A custom type named SIT1 detects six-digit employee IDs. Placeholder values such as 111111 and 000000 in templates cause false positives. No valid employee ID
- Custom sensitive information types require workload-specific testing and tuning
Testing a sensitive information type evaluates the uploaded file rather than refreshing historical classification: test representative matching and nonmatching files and review the number of matches at each confidence level; an Exchange Online license must exist in the tenant for the portal's SIT test option to be available. Also validate the custom detector in each consuming workload, such as Exchange, SharePoint or OneDrive, and endpoints, because extraction and processing limits can change results, and tune against representative false positives and false negatives there. Endpoint DLP evaluates all tenant SITs, including custom types unused by any DLP policy, so reduce excessive classification traffic by removing unused detectors or redesigning overbroad definitions rather than just removing their policy references. After changing a custom definition, unchanged SharePoint and OneDrive files do not automatically acquire updated classification results; use the documented recrawl or on-demand classification process as appropriate, then evaluate policy matches separately.
Trap Restarting an auto-labeling simulation as the mechanism for refreshing old classifier results, because simulation evaluates available classification rather than rescanning all file content.
3 questions test this
- You have a Microsoft 365 E5 subscription. You changed the regex of a custom type named SIT1. A SharePoint auto-labeling policy in simulation misses older unchanged files that contain the new format. R
- You have a Microsoft 365 E5 subscription. You built a custom type named SIT1 that will be used in an Exchange mail flow rule, a SharePoint DLP policy and an Endpoint DLP policy. A test with one sample
- You have a Microsoft 365 E5 subscription that has 50 custom sensitive information types, 40 of which no DLP policy references. After onboarding to Endpoint DLP, devices show excessive classification t
- Mixed Chinese or Japanese patterns need spaced and unspaced variants
Define both spaced and unspaced keyword or regex variants when Chinese or Japanese text is combined with English or single-byte characters. Purview normalizes double-byte text by inserting spaces between words and removing special characters, so a keyword such as 机密的document needs both 机密的document and 机密的 document. Keep double-byte and mixed-language vocabulary in a separate dictionary or keyword list from English-only terms. For these keyword lists, prefer string matching over word matching as Microsoft recommends, rather than relying on English-style word boundaries.
Trap Using only the visually identical unspaced mixed-language keyword with word matching, because token normalization can insert a boundary absent from that literal form.
4 questions test this
- You have a Microsoft 365 E5 subscription. A custom sensitive information type uses a keyword dictionary that contains the mixed term 秘密plan, entered without a space. Some documents that contain 秘密plan
- You have a Microsoft 365 E5 subscription. You are creating a custom sensitive information type with a new keyword list. It must detect the mixed Japanese and English phrase 極秘report. Users type it wit
- You have a Microsoft 365 E5 subscription. A keyword list for a custom type contains Japanese and Chinese phrases. Some phrases aren't detected when they appear inside longer runs of text without space
- You have a Microsoft 365 E5 subscription. You need a custom type that detects the phrases Highly confidential, 機密性が高い and 机密的document in documents. You will use keyword lists for the primary element.
- Document fingerprinting identifies documents derived from a standard textual form
When employees fill in a standard business form, create a fingerprint-based sensitive information type by uploading the blank form or template. Purview derives a word-pattern fingerprint and stores its hash rather than the original document, so the template cannot be reconstructed from the stored value. The template must provide between 256 and 204,800 extracted text characters, and text inside embedded documents is not used to build the fingerprint. Fingerprint definitions share a separate rule pack with a 300 KB maximum size, supporting approximately 100 fingerprints per tenant. To adopt expanded matching capabilities for an existing fingerprint, edit its SIT and upload the same template again rather than creating another fingerprint from an already-used template, which is unsupported.
Trap Using exact data match against a list of employees to recognize the organization's blank HR form, because reference-record matching identifies supplied values rather than the form's stable textual structure.
4 questions test this
- You have a Microsoft 365 E5 subscription. You plan to create a fingerprint-based sensitive information type from the blank merger term sheet that deal teams fill in. Security reviewers worry that a re
- You have a Microsoft 365 E5 subscription. The HR department uses a Word form named NewHire.docx to collect employee details. Completed forms must be detected when they're emailed outside the organizat
- You have a Microsoft 365 E5 subscription. Over several years, departments have created about 100 fingerprint-based sensitive information types, and many are no longer used. Creating a new fingerprint
- You have a Microsoft 365 E5 subscription. You try to create a fingerprint-based sensitive information type from a short cover sheet template named Cover.docx. The template's extracted text is only abo
- Fingerprint matching can tolerate partial similarity or require identical text
Fingerprint-based sensitive information types can assign low, medium, and high confidence thresholds for partial matching using text-match percentages from 30% to 90%. For a strict unchanged-document requirement, set the high-confidence match to Exact, which accepts only identical text and rejects even a small deviation. In Security & Compliance PowerShell, create the fingerprint SIT with New-DlpSensitiveInformationType or modify an existing one with Set-DlpSensitiveInformationType -Identity, passing the blank template's bytes from [System.IO.File]::ReadAllBytes to -FileData. Configure -ThresholdConfig @{low=40;medium=60;high=80} with -IsExact $false when completed or altered forms must still be recognized, or use -IsExact $true for identical-text matching.
Trap Using an exact file hash inventory to recognize filled-in versions of a template, because inserting field values changes file identity even when the form's shared wording remains.
4 questions test this
- You have a Microsoft 365 E5 subscription. You need to create a fingerprint named Patent SIT from C:\Docs\patent.docx by using Security & Compliance PowerShell, with partial-match thresholds of 40, 60
- You have a Microsoft 365 E5 subscription. You are uploading a template to create a fingerprint named FormFP. Low confidence must flag documents that contain at least 40 percent of the template's text,
- You have a Microsoft 365 E5 subscription. You create a document fingerprint from a blank contract template. A DLP rule must detect only files whose text is exactly the same as the fingerprint, and fil
- You have a Microsoft 365 E5 subscription. You run New-DlpSensitiveInformationType -Name "Contract SIT" -FileData $form -ThresholdConfig @{low=40;medium=60;high=80} to create a fingerprint. Contract SI
- Fingerprint protection depends on licensing, readable content, and workload support
Verify E5 licensing before creating or modifying fingerprint SITs or adopting the expanded fingerprint feature set; existing E3 fingerprints and their policies can continue working without granting those management rights. Fingerprint SITs can be used by DLP for Exchange, SharePoint, OneDrive, Teams, and devices, and by auto-labeling for Exchange, SharePoint, and OneDrive. Document fingerprinting excludes password-protected files, image-only files, and files larger than 4 MB. Device use additionally requires Advanced classification scanning and protection, so validate both content eligibility and the destination workload before relying on a fingerprint policy.
Trap Using only an Exchange mail flow rule to protect local USB transfers with a fingerprint, because mail transport does not evaluate endpoint copy activities.
3 questions test this
- You have a Microsoft 365 E5 subscription. You plan to use a fingerprint SIT named NDAFP in an auto-labeling policy that applies the Confidential sensitivity label. You need to identify which location
- You have a Microsoft 365 E5 subscription. A DLP policy for Exchange uses a fingerprint SIT built from the blank claims form. It detects completed 300 KB claims forms sent by email, except when users p
- You have a Microsoft 365 E5 subscription. A DLP policy named DLP1 applies to the Devices location and uses a fingerprint SIT for a tax form. DLP1 detects the form in Exchange and SharePoint, but not w
- Exact data match narrows detection to sensitive values in an organization's reference table
When generic identifiers produce too many unrelated matches, use an EDM sensitive information type to compare detected content against an authoritative structured dataset. EDM checks one-way cryptographic hashes of the supplied values and can use associated fields to strengthen recognition. The source database can contain up to 100 million rows and can be refreshed daily, allowing detection to follow changes in employees, customers, or patients. EDM supports Purview DLP in Exchange Online, SharePoint, OneDrive, Teams chat, and devices, but its documented Defender for Cloud Apps locations are SharePoint and OneDrive. For EDM auto-labeling, supported client-side locations are Word, Excel, PowerPoint, and Exchange desktop clients, while service-side locations are Exchange Online, SharePoint, and OneDrive.
Trap Using a generic national-ID detector alone for a requirement limited to current customers, because format recognition does not establish membership in the customer dataset.
4 questions test this
- You have a Microsoft 365 E5 subscription. You plan to use an EDM-based type named PatientEDM in a sensitivity label's client-side auto-labeling condition so that users get a recommendation while editi
- You have a Microsoft 365 E5 subscription. A bank wants DLP to detect its own account numbers. The account table has 80 million rows and changes every night. An administrator proposes a keyword diction
- You have a Microsoft 365 E5 subscription. You plan to use an EDM-based sensitive information type named CustomerEDM in a Microsoft Defender for Cloud Apps file policy. You need to identify which apps
- You have a Microsoft 365 E5 subscription. You propose an EDM type for the customer table. Legal objects because the table's values must not be shared with anyone, including Microsoft. You need to expl
- An EDM schema defines the reference fields and their matching behavior
The EDM XML schema identifies the DataStore and maps its field names one-to-one to the source table's column headers. It also identifies searchable fields, multi-token corroborative fields, and configurable matching behavior such as ignoring case or delimiters. Keep the exported schema aligned with the data used for hashing and uploading so that the service interprets each column as intended.
Trap Changing the display name of a sensitive information type to repair a source-column mapping error, because field interpretation comes from the EDM schema rather than the display label.
4 questions test this
- You have a Microsoft 365 E5 subscription. An EDM source table stores the LastName corroborative field in uppercase, such as LANGER. Documents write names in mixed case, such as Langer, so expected sup
- You have a Microsoft 365 E5 subscription. An EDM source table includes an Address field with values such as 1 Microsoft Way, Redmond, WA, used as corroborating evidence for patient numbers. No existin
- You have a Microsoft 365 E5 subscription. An EDM schema for employee records has the fields EmployeeID and LastName. EDM must run exact lookups on EmployeeID values found in content. LastName must ser
- You have a Microsoft 365 E5 subscription. Your EDM schema defines the fields PatientID, FirstName, LastName and DateOfBirth. The exported source table uses the column header DOB instead of DateOfBirth
- An EDM primary field needs a detector before exact lookup can validate the record
An EDM rule associates its primary field with an existing sensitive information type that discovers candidate values, then performs exact lookup and checks nearby corroboration. Prefer a strongly defined primary detector and a field with discriminating values, because very broad matches or many repeated primary values increase lookup work and can miss detections through processing timeouts. For supporting values such as full names or addresses, configure multi-token matching when an appropriate pattern detector is impractical.
Trap Selecting a common surname as the primary lookup field to maximize the number of candidates, because frequent repeated values make exact lookup less selective and more expensive.
3 questions test this
- You have a Microsoft 365 E5 subscription. You are designing an EDM type from a 5-million-row orders table. The candidate primary field CountryCode has about 40 distinct values repeated across all rows
- You have a Microsoft 365 E5 subscription. In the new EDM experience, you map the primary field CustomerNumber to a type that matches any eight-digit number, and the system warns about a loosely define
- You have a Microsoft 365 E5 subscription. An EDM source table contains MedicalRecordNumber, which follows a fixed pattern, and PatientName, which is free-form text with first and last names. You need
- The classic EDM experience is required when multiple sensitive information types must share a schema
Use the classic EDM experience when multiple SITs must share a schema, more than 10 SITs are needed, or custom schema naming is required. A tenant supports at most 10 EDM schemas, and the new experience creates a schema and SIT together with a one-to-one relationship. The new experience can infer structure from 10 to 20 representative nonsensitive sample rows. Classic-created and PowerShell-uploaded schemas are not manageable in the new experience.
Trap Creating a separate new-experience schema for every departmental rule over the same customer table, because each creation consumes another of the tenant's schema slots.
4 questions test this
- You have a Microsoft 365 E5 subscription. Your organization needs 14 EDM-based sensitive information types for different regional customer tables. Several of the types should share one schema. You nee
- You have a Microsoft 365 E5 subscription. You create an EDM sensitive information type named PatientNumber in the new experience, which creates the schema automatically. You need the schema name to do
- You have a Microsoft 365 E5 subscription. You create an EDM type in the new experience and choose to provide a sample data file so that the system builds the schema from its headers. The file isn't ha
- You have a Microsoft 365 E5 subscription. Two years ago, an administrator uploaded an EDM schema as an XML file by using PowerShell. You switch to the new EDM experience to add a field. The schema doe
- EDM can separate sensitive-data hashing from the internet-connected upload computer
Use the EDM Upload Agent to hash source data with a salt before uploading it. For stronger separation, create the hash on a secure computer and copy the resulting hash and salt files to the upload computer; both computers must run the same Upload Agent version. The single-computer method requires the clear-text source table on the internet-connected machine, while a schema-inference sample file is a separate upload that must contain nonsensitive representative values.
Trap Uploading a spreadsheet encrypted with a document password as the EDM reference dataset, because the ingestion workflow requires the agent's schema-aware salted hashes.
5 questions test this
- You have a Microsoft 365 E5 subscription. You plan to hash and upload a patient records table for an exact data match type. Security policy forbids the clear-text table from ever residing on a compute
- You have a Microsoft 365 E5 subscription. On an isolated computer, you run EdmUploadAgent.exe /CreateHash for a table named PatientRecords without specifying /Salt. You now need to move the output to
- You have a Microsoft 365 E5 subscription. Using the two-computer method, you copied PatientRecords.EdmHash and its salt file to the internet-connected computer and authorized the EDM Upload Agent. You
- You have a Microsoft 365 E5 subscription. A small company approves hashing and uploading an employee table from one computer named Computer1. Computer1 connects directly to the tenant and stores the c
- You have a Microsoft 365 E5 subscription. You use the two-computer method for an exact data match upload. Computer1 is isolated and creates the hash. Computer2 connects to the internet and uploads it.
- EDM data upload uses a dedicated security group and agent authorization
Add the Microsoft 365 work or school account used for EDM uploads to the EDM_DataUploaders security group, then authorize the Upload Agent with that account. Schema authoring, data ingestion, and policy use are separate phases, so creating the SIT is not evidence that its reference values have been uploaded and indexed. Review upload and indexing status before validating the resulting detector or activating dependent protection.
Trap Publishing a sensitivity label to the upload operator as the authorization for EDM ingestion, because label availability does not assign data-uploader rights.
4 questions test this
- You have a Microsoft 365 E5 subscription. User1 will run the EDM Upload Agent to upload hashed data for an exact data match type. User1 signs in after running /Authorize, but the upload is refused. Yo
- You have a Microsoft 365 E5 subscription. You installed the EDM Upload Agent in C:\EDM\Data on Computer2. User1 is a member of EDM_DataUploaders. Before User1 runs /UploadHash for the first time, the
- You have a Microsoft 365 E5 subscription. You created an EDM sensitive information type named PatientEDM, and its schema appears in the Microsoft Purview portal. User1 then ran the upload. Before you
- You have a Microsoft 365 E5 subscription. Your exact data match data store named PatientRecords is refreshed daily by a scheduled upload. You need to display all the data uploads to PatientRecords and
- EDM source data must be validated against the exact schema before ingestion
Validate an EDM source file with EdmUploadAgent.exe /ValidateData using its /DataFile and /Schema values before hashing and uploading. CSV is the default input format; tab-separated and pipe-separated data are also supported when the delimiter is specified. Embedded delimiters and inconsistent quoting can change the parsed column count, so correct the export format rather than modifying detection confidence to compensate for an ingestion error.
4 questions test this
- You have a Microsoft 365 E5 subscription. A daily EDM upload of 2 million rows fails whenever a handful of rows are malformed. The data owner accepts skipping up to 5 percent of rows. You need the upl
- You have a Microsoft 365 E5 subscription. A vendor system exports a CSV source table for EDM with fields such as "Title, Role" in double quotes and inconsistent single quoting. You can't change the ex
- You have a Microsoft 365 E5 subscription. /ValidateData reports mismatched column counts for an EDM customer table exported as CSV. The affected rows contain names with apostrophes, such as Tom O'Neil
- You have a Microsoft 365 E5 subscription. Before uploading an employee table for an exact data match type, you want to catch formatting and column-mapping problems. You have the data file and the sche
- Trainable classifiers recognize content categories that are difficult to express as deterministic patterns
Use a trainable classifier when the meaning and structure of examples identify a category such as contracts or strategic plans. A Microsoft-provided pretrained classifier is ready to use without your own training, while a custom classifier requires representative organizational examples. Custom classifier language support is limited to English, and classifier processing requires unencrypted items. Check the consuming solution before investing in custom training: Communication Compliance accepts Microsoft-provided trainable classifiers only, so a custom classifier cannot satisfy that consumer's requirement.
Trap Using document fingerprinting for a collection of independently written legal agreements with no shared template, because a common form's text is not available as a stable fingerprint.
4 questions test this
- You have a Microsoft 365 E5 subscription. The pretrained Source code classifier detects code files in a SharePoint site, except for files protected by a sensitivity label that applies encryption. You
- You have a Microsoft 365 E5 subscription. You published a custom trainable classifier named Contracts that you seeded with English-language contracts. An auto-labeling policy that uses Contracts label
- You have a Microsoft 365 E5 subscription. Legal stores thousands of nondisclosure agreements drafted by different outside firms. Each firm uses its own structure and wording, and there's no shared tem
- You have a Microsoft 365 E5 subscription. You built and published a custom trainable classifier named Harassment that performs well in auto-labeling. When creating a Communication Compliance policy, y
Prepare 50 to 500 positive samples and 150 to 1,500 negative samples for a custom trainable classifier, placing the collections in separate dedicated SharePoint folders. Use text-based supported files, including suitable Office files and text-bearing PDFs, and allow at least an hour for a newly created seed location to be indexed. The training account needs access to both folders; OneDrive folders, Teams folder types, images, and image-only PDFs are unsuitable seed locations or content. Processing uses up to the 2,000 most recently created samples by file creation timestamp, so keep the seed folders controlled to prevent unintended newer files from displacing the examples you selected.
Trap Using only highly representative positive examples to accelerate training, because the model also needs content that establishes what falls outside the category.
4 questions test this
- You have a Microsoft 365 E5 subscription. The positive seed folder for a custom classifier named Policies holds 450 curated policy documents. An automated job also saves about 2,000 new meeting notes
- You have a Microsoft 365 E5 subscription. You seed a custom classifier with 200 scanned contracts saved as image-only PDF files and 300 Word documents as negative samples. The classifier fails to lear
- You have a Microsoft 365 E5 subscription. User1 uploaded positive and negative seed documents for a custom classifier to two folders in User1's OneDrive. The creation wizard can't use the folders. You
- You have a Microsoft 365 E5 subscription. You plan a custom trainable classifier named Reviews for engineering design review documents. You collected 30 positive samples and 400 negative samples. You
- Trainable-classifier lifecycle changes require validation and policy-impact review
Review a custom classifier's predictions and verify true positives, true negatives, false positives, and false negatives before publishing it for policy use. By default, the creator is the person who can train it and review its predictions. Improve an unpublished classifier by updating samples and restarting training; a published custom classifier must be removed and recreated to improve its accuracy because retraining it is unsupported. To suppress automatic Content explorer display of trainable-classifier detections not used in labeling policies, request the display change through Microsoft Support rather than disabling classifier scanning. Disabling scanning is a separate support request that stops sensitivity-labeling and DLP policies using those classifiers from working, so review dependent protection before requesting it.
Trap Editing a sensitivity label's confidence threshold to retrain a published classifier, because policy evaluation settings do not rebuild the learned model.
4 questions test this
- You have a Microsoft 365 E5 subscription. Testing of an unpublished custom classifier named Specs, seeded from engineering specification documents, shows many incorrect predictions. Specs hasn't been
- You have a Microsoft 365 E5 subscription. A custom classifier named Invoices shows the status Training is complete and items have been tested. Policies will use Invoices next month. You need to follow
- You have a Microsoft 365 E5 subscription. A published custom classifier named Specs is used by an auto-labeling policy and mislabels many files. A colleague suggests editing the sensitivity label's se
- You have a Microsoft 365 E5 subscription. User1 created a custom classifier named Payroll. User2, a Compliance Administrator, must review Payroll's test predictions while User1 is on leave. User2 can'
- Data explorer and Content explorer provide an inventory of classified and labeled items
Use Data explorer or Content explorer to locate items associated with sensitive information types, sensitivity labels, retention labels, and supported trainable classifiers. Start with the classifier or label, choose the data source, and drill into the repository to inspect matching items. Filter Exchange or Teams by a full mailbox address, and SharePoint or OneDrive by site, folder, or file information; CSV export reflects the current focus of the pane rather than an automatically complete tenant report. These views describe the classified-content inventory; use activity or audit records when the requirement is to establish who changed a label and when.
Trap Using a label publishing policy's target-user list as the inventory of labeled files, because publication records eligibility to apply a label rather than which content carries it.
4 questions test this
- You have a Microsoft 365 E5 subscription. The legal team asks how many SharePoint and OneDrive documents currently match the built-in Resumes trainable classifier, and where they are stored. You need
- You have a Microsoft 365 E5 subscription. Each morning, User1 opens Content explorer and must find the same three sensitive information types, two sensitivity labels and one retention label among hund
- You have a Microsoft 365 E5 subscription. A file named Budget.xlsx in Site1 had the Confidential sensitivity label last week but has no label today. Data explorer shows the file's current state only.
- You have a Microsoft 365 E5 subscription. In Content explorer, you select a sensitive information type and drill into the Exchange location to review items for one mailbox that belongs to User1. You n
- Explorer navigation, item listing, and content viewing require different permissions
An administrative role that exposes an explorer page does not by itself grant access to its item list or content. Data Explorer List viewer and Data Explorer Content viewer grant independent permissions through Data Classification List Viewer and Data Classification Content Viewer; Content explorer uses the corresponding Content Explorer role groups. Grant both capabilities when a user must list locations and read content, and apply administrative-unit restrictions when access must be scoped; content-view permission is also needed to reveal potentially sensitive item names.
Trap Assigning Compliance Administrator alone to an investigator who needs document previews, because portal administration and direct access to classified content are separate permissions.
4 questions test this
- You have a Microsoft 365 E5 subscription. User1 is a member of the Data Explorer List viewer role group. In Data explorer, User1 sees each item and its location, but item names that might contain sens
- You have a Microsoft 365 E5 subscription. The security team wants to manage one role group for investigators. It must include the data classification list viewer role together with other Purview roles
- You have a Microsoft 365 E5 subscription that uses administrative units for regions. User1 manages data classification for the Europe region only. User1 must see only Europe items in Content explorer.
- You have a Microsoft 365 E5 subscription. User1 must review sensitive files in Content explorer, which includes seeing each file's location and opening its contents. User1 has the Security Administrat
- Explorer investigations must account for indexing delays and encrypted-content restrictions
Explorer counts can take up to seven days to update, and SharePoint file results can take up to fourteen days, so an immediate count is not a real-time completeness check. Preview and download are disabled for encrypted documents.
Trap Granting broader explorer content permissions to solve an encrypted document's unavailable preview, because the preview restriction is a product boundary rather than missing list access.
5 questions test this
- You have a Microsoft 365 E5 subscription. Users started applying the Internal label to Exchange email three days ago. In Content explorer, the Exchange count for Internal is still lower than expected,
- You have a Microsoft 365 E5 subscription. Nine days ago, users uploaded 5,000 files to a SharePoint site, and some files are encrypted by a label. Content explorer counts don't include the new files y
- You have a Microsoft 365 E5 subscription. Five days ago, an auto-labeling policy applied the Confidential label to many files in SharePoint Online. Content explorer doesn't yet show the new counts for
- You have a Microsoft 365 E5 subscription. Ten days ago, a retention label was auto-applied to Exchange mailboxes and SharePoint sites. Content explorer now shows current counts for Exchange but not fo
- You have a Microsoft 365 E5 subscription. User1 is a member of Content Explorer List viewer and Content Explorer Content viewer. User1 can open most documents in Content explorer, but documents labele
- Explorer match feedback identifies classification errors to guide detector tuning
In Content explorer, review a supported SIT or trainable-classifier match for a SharePoint or OneDrive item and record Match for a true positive or Not a Match for a false positive. Use the classifier's matched-items view or the item's available contextual summary to inspect the detection, and use Withdraw feedback to correct a mistaken submission. Apply the findings to detector tuning rather than treating a feedback selection as an immediate change to its rules. EDM, named-entity, and credential-scanning SITs do not support Match and Not a Match feedback, so check the classifier's feedback capability before choosing this workflow.
Trap Raising the policy's match-count threshold before reviewing disputed items, because changing how many detections trigger a policy does not establish whether those detections are correct.
5 questions test this
- You have a Microsoft 365 E5 subscription. A custom sensitive information type named SIT1 matched a OneDrive file that contains no sensitive data. You open the file in Content explorer and review it on
- You have a Microsoft 365 E5 subscription. You plan to collect Match and Not a match feedback in Content explorer to tune the classifiers used in your DLP policies for SharePoint. You need to identify
- You have a Microsoft 365 E5 subscription. Over a week, analysts mark 200 SharePoint matches of a custom type named SIT1 as Not a match. A DLP rule still blocks the same kinds of files. A manager expec
- You have a Microsoft 365 E5 subscription. You review OneDrive matches for an exact data match sensitive information type named EDM1 in Content explorer. The Match and Not a match options don't appear
- You have a Microsoft 365 E5 subscription. A DLP policy uses a custom sensitive information type and matches both Exchange email and SharePoint files. You need to give Match or Not a match feedback on
- On-demand classification requires a scope and policy-impact review before execution
Before starting on-demand classification for SharePoint or OneDrive, review active policies that could act on refreshed results: apply-label or label-removal policies can change files even while the policy being investigated remains in simulation. Under Information Protection > Classifiers > On-demand classification, create a scan and select locations, classifiers, file extensions, and the file last-modified date range to include the intended historical files. Review View estimation and estimated charges, adjust scope if necessary, and only then select Start classification. Running the scan requires Compliance Administrator membership; inspecting classification results separately requires Content Explorer List Viewer or Content Explorer Content Viewer permissions for the intended view.
Trap Using one auto-labeling policy's simulation state as tenant-wide change isolation during an on-demand scan, because other active policies can act on the refreshed classification.
5 questions test this
- You have a Microsoft 365 E5 subscription. You run an on-demand classification scan of SharePoint that selects only the Credit Card Number classifier. Afterward, a DLP policy based on the U.S. Social S
- You have a Microsoft 365 E5 subscription. You are testing an auto-labeling policy in simulation mode. A separate active policy removes a label from files that match a sensitive information type. You p
- You have a Microsoft 365 E5 subscription. You finished the on-demand classification wizard for a scan named Scan1 that covers 300 SharePoint sites. Finance must approve the expected cost before any fi
- You have a Microsoft 365 E5 subscription that uses several EDM classifiers. An on-demand classification estimate for OneDrive is far higher than expected because previously classified files are rescan
- You have a Microsoft 365 E5 subscription. You create an on-demand classification scan to classify SharePoint files that were last modified in 2022 and 2023. You keep the wizard defaults. The estimatio
- OCR adds image text to existing Purview detection after billing and locations are configured
Enable OCR at tenant level after connecting an Azure pay-as-you-go subscription through Microsoft Syntex billing; deploying Microsoft Syntex itself is not required. In Microsoft Purview Settings, select Optical character recognition and configure the locations and included or excluded groups. Existing sensitive information types, EDM, trainable classifiers, and fingerprint SITs can then recognize extracted image content, with each workload limited to its supported solutions. Only images uploaded after OCR is enabled are scanned, so activation does not provide retrospective coverage of existing images.
Trap Creating a second credit-card SIT specifically for screenshots before enabling image scanning, because OCR supplies extracted text to existing detectors.
4 questions test this
- You have a Microsoft 365 E5 subscription. Yesterday, you enabled OCR for SharePoint. Today, a DLP policy detects SSNs in newly uploaded scanned forms but not in thousands of scanned forms uploaded las
- You have a Microsoft 365 E5 subscription. You enabled OCR for SharePoint sites. A DLP policy uses the built-in Credit Card Number type. A team proposes creating a second credit card type specifically
- You have a Microsoft 365 E5 subscription with Microsoft Syntex pay-as-you-go billing configured. You need OCR to scan images in Exchange and on Windows devices for members of the Finance group only. Y
- You have a Microsoft 365 E5 subscription and an Azure pay-as-you-go subscription. You plan to have DLP policies detect credit card numbers in scanned images in SharePoint and Exchange. You need to com
- OCR eligibility depends on workload-specific size, format, and image dimensions
OCR permits images up to 20 MB in Exchange and Teams and up to 50 MB in SharePoint, OneDrive, and Windows or macOS endpoints. Supported image dimensions range from 50 by 50 to 16,000 by 16,000 pixels, and extraction is limited to the first 2 million characters. Exchange supports selected embedded-image formats with at most 20 embedded images scanned per file, while Teams and endpoints support JPEG, JPG, PNG, BMP, TIFF, and image-only PDFs; check the location's format support before choosing the policy design.
4 questions test this
- You have a Microsoft 365 E5 subscription with OCR enabled for SharePoint. A site contains small JPG thumbnails of ID cards that are 40 × 40 pixels, and larger 1,200 × 800 pixel images. DLP detects IDs
- You have a Microsoft 365 E5 subscription with OCR enabled for Exchange. A user sends a ZIP file that contains 30 scanned invoice images. Only some of the images trigger the DLP policy that should matc
- You have a Microsoft 365 E5 subscription with OCR enabled for SharePoint and Windows devices. Users store screenshots as GIF files in SharePoint and in local folders on Windows 11 devices. DLP detects
- You have a Microsoft 365 E5 subscription with OCR enabled for Exchange. A user emails a 25 MB high-resolution PNG scan of a passport to an external recipient. A DLP policy that detects passport number
- Exchange OCR scope controls scanning but does not provide image policy tips
Exchange OCR scans incoming, internal, and outgoing email by default, but Exchange DLP policy tips are not supported for images. Select Specific sender groups to limit the sender population, or the Exchange advanced option for only externally sent mail to exclude both incoming and internal traffic.
Trap Changing a sensitivity label's publishing audience to reduce Exchange OCR scanning, because label publication does not set the OCR sender or direction scope.
4 questions test this
- You have a Microsoft 365 E5 subscription with OCR enabled for Exchange using the default scope. Costs are high because of images in email from external senders. You need to exclude incoming email from
- You have a Microsoft 365 E5 subscription. OCR must scan images only in email sent by members of the Legal and HR groups, including their internal and outgoing mail. Email from other users and from ext
- You have a Microsoft 365 E5 subscription. You enable OCR for Exchange and keep the default sender scope. Before estimating costs, the finance team asks which email messages will have their images scan
- You have a Microsoft 365 E5 subscription. OCR is enabled for Exchange. A DLP policy detects credit card numbers in PNG attachments and in message text. Users see a policy tip when the number is in the
- Endpoint OCR depends on cloud connectivity, bandwidth, and file-path coverage
Windows and macOS endpoints send images to the cloud for OCR, with a default advanced-classification bandwidth limit of 1,024 MB per device per day. OCR stops scanning images after the device reaches that limit; increase it when the required coverage justifies the additional traffic. Endpoint DLP file-path exclusions also exclude those folders from OCR, and network controls must permit the required blob.core.windows.net endpoints.
Trap Adding another sensitive information type to a policy when image classification stops after heavy device use, because detector selection does not increase the device's cloud-scanning bandwidth.
4 questions test this
- You have a Microsoft 365 E5 subscription. You plan to enable OCR for 2,000 Windows 11 devices and must estimate upload traffic. The default device settings will be kept. You need to identify the defau
- You have a Microsoft 365 E5 subscription. Endpoint OCR is enabled for Windows devices that use a corporate proxy. DLP detects sensitive text in documents, but images are never classified. Devices are
- You have a Microsoft 365 E5 subscription with OCR enabled for Windows devices. Endpoint DLP settings exclude the path C:\Scans to reduce scanning of scanner output. A new policy must detect SSNs in im
- You have a Microsoft 365 E5 subscription with OCR enabled for Windows devices. Engineers on Device1 copy hundreds of screenshots daily. By midafternoon, OCR stops detecting sensitive data in new image
- OCR charges per scanned image rather than per policy that uses its results
Each scanned standalone image is an OCR transaction, and each PDF page is charged separately. The same extracted result can be used by multiple supported Purview policies without an additional scan charge for each policy. Exchange caches eligible repeated small images across the tenant for a moving five-day window, and endpoints maintain a local thirty-day cache; standalone SharePoint and OneDrive images do not use that caching mechanism.
4 questions test this
- You have a Microsoft 365 E5 subscription with OCR enabled for Exchange. All 8,000 users include the same company logo image in their email signatures, sending thousands of messages each day. You need
- You have a Microsoft 365 E5 subscription that uses Endpoint OCR. Over two weeks, Endpoint DLP evaluates the same unchanged screenshot on one Windows device many times. Finance asks how repeated OCR ch
- You have a Microsoft 365 E5 subscription. OCR is enabled for SharePoint. A user uploads a 12-page scanned PDF file. Two DLP policies and one auto-apply retention label policy evaluate the extracted te
- You have a Microsoft 365 E5 subscription with OCR enabled. An image in Exchange is scanned and is evaluated by a DLP policy, an auto-labeling policy and an auto-apply retention label policy. The finan
Implement and manage sensitivity labels in Microsoft Purview
Read full chapterCheat sheet
Sharp facts the exam loves — scan these before test day.
- Sensitivity label administration can be delegated without Global Administrator
Use a Purview role group containing Sensitivity Label Administrator for custom delegation of label and label-policy management, or use an appropriate built-in group such as Information Protection Admins. For read-only configuration access, use Sensitivity Label Reader. These are administrative permissions; users applying a published label in an app do not need the label-administration role.
Trap Assigning Content Explorer Content Viewer to a label-policy author, because permission to inspect classified documents does not confer label configuration rights.
3 questions test this
- You have a Microsoft 365 E5 subscription. Users in the Sales department must apply a label named Confidential to documents in Word. Confidential is published to the Sales group in a label policy. Whic
- You have a Microsoft 365 E5 subscription. You create a custom Microsoft Purview role group named LabelAuditors. Members of LabelAuditors must view sensitivity labels and label policy configuration, bu
- You have a Microsoft 365 E5 subscription. Admin1 must create and edit sensitivity labels and label policies without receiving Global Administrator or permissions outside information protection. Admin1
- Administrative units can bound both delegated label administration and policy eligibility
Assign Microsoft Entra administrative units to individual members of applicable Purview role groups to restrict the populations they manage. When creating label or auto-labeling policies, select administrative units to constrain eligible Exchange and OneDrive users or SharePoint sites. Refine user and group scope as needed, but SharePoint policies apply to all sites associated with the selected units and do not allow individual site inclusions or exclusions. Keep unit membership accurate because it determines the effective boundary even when the policy selects all users or sites within that scope.
Trap Using a sensitivity label's encryption recipient list to limit which division an administrator may manage, because content usage rights do not scope administrative authority.
3 questions test this
- You have a Microsoft 365 E5 subscription. Admin1 is a member of the Information Protection Admins role group. Admin1 must manage label policies only for users in France. Your organization has a Micros
- You have a Microsoft 365 E5 subscription. A restricted administrator assigned an administrative unit named AU-Sales creates a label policy, selects AU-Sales, and keeps the default of all users and gro
- You have a Microsoft 365 E5 subscription. You are a restricted administrator assigned an administrative unit named AU1 that is associated with SharePoint sites by a site query. You create an auto-labe
- An item carries one organizational sensitivity label as persistent metadata
A supported item can carry one sensitivity label from your organization, stored in clear-text metadata that travels with the content. Supported applications use that identity to display the classification and enforce the configured settings even when the file changes location. A sensitivity label can coexist with a retention label because protection classification and retention lifecycle are separate dimensions.
2 questions test this
- You have a Microsoft 365 E5 subscription. Documents in a site named Legal already have a sensitivity label named Confidential. The records team must apply a retention label named Retain7 to the same d
- You have a Microsoft 365 E5 subscription. A file named File1.docx is labeled Confidential in a SharePoint Online site. User1 downloads File1.docx and uploads it to a partner storage service that is no
- A label's selected scopes determine where it can be used and which settings it can configure
Select Files & other data assets for files and Power BI content, Emails for mail, and Groups & sites for supported containers. A scope that is not selected leaves its settings unavailable and prevents the label from being offered for that resource type. Meetings also requires both Files & other data assets and Emails, so an administrator must satisfy the scope dependency before configuring meeting protection.
Trap Republishing a Groups & sites-only label to an Outlook user to make it available for email, because audience changes do not add the Emails scope.
3 questions test this
- You have a Microsoft 365 E5 subscription. You create a label named Finance Data. Analysts in the Finance department must be able to apply Finance Data to Power BI reports, dashboards, and semantic mod
- You have a Microsoft 365 E5 subscription. A label named Project is scoped only to Groups & sites. User1 uses Outlook and must apply Project to email messages. You add User1 to the label policy that pu
- You have a Microsoft 365 E5 subscription. You edit a label named MeetingSecure that currently has only the Groups & sites scope. You need MeetingSecure to protect calendar items, Teams meetings, and c
- A label grouping organizes choices rather than supplying inherited protection settings
Use label groups in the modern scheme, or parent labels and sublabels in the classic scheme, to organize related choices in a two-tier menu. The child labels do not inherit the parent's protection settings; configure each applicable label independently, with color as the documented inheritance exception. A classic parent with published sublabels cannot itself be applied or used as a default, and modern label groups cannot be published as labels. For classic sublabels, select and publish both the parent label and the sublabel. In the modern scheme, label display names must be unique within each group and among standalone labels, so moving a label into a group fails if another label there has the same display name.
Trap Using encryption configured only on the Confidential parent to protect its departmental sublabels, because the sublabels do not acquire those encryption settings.
3 questions test this
- You have a Microsoft 365 E5 subscription. You use parent labels and sublabels. You publish a sublabel named Confidential\Finance in a label policy for the Finance group, but you do not include its par
- You have a Microsoft 365 E5 subscription. A parent label named Confidential applies encryption. Its sublabels, HR and Finance, have no protection settings. Users apply Confidential\HR to documents, an
- You have a Microsoft 365 E5 subscription. You use label groups. A group named Confidential contains a label whose display name is Partners. You try to move a standalone label that also has the display
- Meeting labels enforce Teams options separately from encrypting the invitation
Select Protect Teams meetings and chat on a meeting-capable label to enforce lobby access, presenter and recording permissions, audio/video encryption, automatic recording, video watermarks, and chat-copy restrictions. Invite encryption separately restricts who can read the invitation and meeting link; it does not configure those meeting options. Teams-specific protection depends on Teams Premium licensing and supported Teams clients, because the configured options cannot be enforced for users on unsupported clients. Calendar items require Exchange Online mailboxes and do not support ordinary automatic or recommended labeling, so use manual selection or the meeting-specific default and inheritance settings instead.
Trap Using Do Not Forward on the invitation as the lobby-admission control, because invitation usage rights restrict message reuse rather than deciding who bypasses the Teams lobby.
3 questions test this
- You have a Microsoft 365 E5 subscription. A meeting label named Board is configured with Protect Teams meetings and chat to enforce who can bypass the lobby and who can record. One participant joins a
- You have a Microsoft 365 E5 subscription. Organizers apply a label named Board to Teams meetings. Only invited users in your organization must bypass the meeting lobby. Board currently encrypts meetin
- You have a Microsoft 365 E5 subscription. You configure a label named Exec for meetings. An information bar in the Microsoft Purview portal states that your organization does not have a required licen
- Sensitivity-label scripts manage label definitions separately from publishing policies
Use New-Label and Set-Label for sensitivity-label definitions, and New-LabelPolicy and Set-LabelPolicy for their publishing policies in Security & Compliance PowerShell. Retrieve Guid, Name, DisplayName, and ContentType with Get-Label and target the GUID when modifying a label, because display names need not be unique. For multilingual deployments, supply translated DisplayName and Tooltip entries through Set-Label -LocaleSettings rather than expecting the Office display language to translate administrator-authored text. These operations let scripts change a label's identity-specific settings without confusing the label object with the policy that distributes it.
Trap Using Set-LabelPolicy to translate an individual label's display name, because localized DisplayName and Tooltip entries belong to the label's LocaleSettings rather than its publishing policy.
3 questions test this
- You have a Microsoft 365 E5 subscription. You created a sensitivity label named Label1 by using New-Label. You need to make Label1 available to members of the Sales group by creating a new publishing
- You have a Microsoft 365 E5 subscription. Two sensitivity labels in different label groups both have the display name Confidential. You need to configure an advanced setting on only one of them by usi
- You have a Microsoft 365 E5 subscription. Users in Germany and Spain must see a label named Confidential and its tooltip in their own languages. You use Security & Compliance PowerShell to configure t
- Sensitivity label encryption can use centrally assigned permissions or user-selected permissions
Choose Assign permissions now when every item in the category should use administrator-defined readers and usage rights. Choose Let users assign permissions when collaborators differ per item; supported Office apps can prompt for recipients, while Outlook can use Do Not Forward or Encrypt-Only. Rights-management encryption requires an activated Azure Rights Management service, and the chosen client must support the configured permission mode. A tenant supports at most 500 labels that specify encryption users and permissions even though the overall catalog can exceed 1,000 labels, so keep the user-facing taxonomy small rather than designing toward the catalog maximum.
Trap Creating a new centrally permissioned label for every ad hoc contract recipient combination, because a user-permission mode can express changing collaborators without multiplying labels.
4 questions test this
- You have a Microsoft 365 E5 subscription. Your tenant was created several years ago. You configure a label named Secret to apply encryption by using Assign permissions now and publish it. Users can ap
- You have a Microsoft 365 E5 subscription. Users in Outlook must be able to encrypt individual email messages so that recipients cannot forward, print, or copy them. Recipients differ for every message
- You have a Microsoft 365 E5 subscription. A label named Contracts must encrypt contracts. Each author shares each contract with a different set of external recipients that only the author knows. The s
- You have a Microsoft 365 E5 subscription. You plan one label for each of 700 partner projects. Each label would use Assign permissions now and list the users and permissions for one project. The tenan
- A label's encryption recipients determine content access independently of who can apply the label
Configure the encryption audience explicitly, using supported users or groups, organizational membership, authenticated users, or an external organization's domain as appropriate. Everyone in your organization excludes guest accounts, while Any authenticated users permits a broad audience subject to the configured usage rights. Specifying a domain belonging to a Microsoft Entra tenant includes that tenant's verified domains, and publishing exclusions or non-email-enabled security groups do not become equivalent Azure Rights Management access controls.
Trap Excluding a guest from the label publishing policy to revoke access to an already encrypted file, because publication eligibility does not remove rights granted by the protection configuration.
4 questions test this
- You have a Microsoft 365 E5 subscription. A partner uses Microsoft Entra ID and has two verified domains, contoso.com and fabrikam.com. You add contoso.com to the encryption permissions of a label nam
- You have a Microsoft 365 E5 subscription. A label named Internal uses Assign permissions now and grants Editor permissions to Everyone in your organization. A guest account named Guest2 in your tenant
- You have a Microsoft 365 E5 subscription. A label named Projects uses Assign permissions now and grants Editor permissions to a dynamic distribution group named DDG1. Members of DDG1 can't open docume
- You have a Microsoft 365 E5 subscription. A guest named Guest1 was granted access by the encryption settings of a label named Partner. Guest1 must no longer open Partner documents. You exclude Guest1
- Encrypted-content permissions distinguish editing from exporting or removing protection
Grant the usage rights needed for the intended workflow rather than treating all document access as Full Control. DOCEDIT allows content changes, EDIT permits saving in protected formats, and EXPORT or Full Control supports operations that can remove existing encryption. Authorized Azure Rights Management super users provide a separate recovery and inspection path when ordinary recipients lack those rights.
Trap Assigning a tenant label-administration role as the way to decrypt every protected document, because management permission is not itself a content usage right or super-user grant.
3 questions test this
- You have a Microsoft 365 E5 subscription. A label named Review grants reviewers View, Open, Read and Edit Content, Edit (DOCEDIT) on encrypted Word documents in their current folder. Reviewers can cha
- You have a Microsoft 365 E5 subscription. A compliance investigator who is a member of Information Protection Admins must open every document that labels encrypted for your organization, including doc
- You have a Microsoft 365 E5 subscription. Users have View, Open, Read and Edit Content, Edit on encrypted documents. When they relabel these documents, the new label must be able to replace the existi
- Content expiration and offline access impose different limits on encrypted content
User access to content expires determines when recipients should stop opening an item, while Allow offline access determines how long a cached use license can be used before reauthentication. Labels with Assign permissions now can set offline access to never, always, or a limited number of days; user-assigned permissions use the tenant use-license validity, which defaults to 30 days. Previously authorized readers can retain cached rights until their use license expires, so select the offline interval with access-change responsiveness in mind.
Trap Setting only a document expiration date to require authentication on every opening, because lifetime expiry does not define the use-license renewal interval.
3 questions test this
- You have a Microsoft 365 E5 subscription. A label uses Assign permissions now with Allow offline access set to 14 days. User1 opened a labeled file on a laptop yesterday. You remove User1 from the lab
- You have a Microsoft 365 E5 subscription. A label uses Assign permissions now. Users must be able to open labeled files without a network connection, but they must reauthenticate with the encryption s
- You have a Microsoft 365 E5 subscription. A label named PriceList uses Assign permissions now and is applied to a document that is sent to partners. Partners must be able to open the document without
- Double Key Encryption reserves decryption control for data that can forgo cloud processing
Use Double Key Encryption for highly sensitive content requiring an organization-controlled key in addition to the Microsoft-held key; access to both keys is required to decrypt. Deploy the organization's DKE service before configuring the label, and plan to use supported Windows clients for consumption. SharePoint and OneDrive can store DKE files but cannot process them for Office for the web, coauthoring, search, DLP, or eDiscovery, so ordinary rights-management encryption is the better fit when those cloud capabilities are required. Bring Your Own Key (BYOK) instead provides customer-managed key provisioning and lifecycle for Azure Rights Management and requires an Azure subscription; it does not introduce DKE's separate organizational key service.
Trap Using BYOK alone when Microsoft must be unable to decrypt with its service-side key material, because BYOK does not add the separate organization-controlled DKE service key.
3 questions test this
- You have a Microsoft 365 E5 subscription. You plan to protect a small set of documents by using a new sensitivity label that uses Double Key Encryption. Users will open the documents in Office apps fo
- You have a Microsoft 365 E5 subscription. Regulations require that Microsoft must not be able to decrypt a small set of top-secret documents, even with its own key material. Your organization will hos
- You have a Microsoft 365 E5 subscription. Highly confidential files in SharePoint use a label with Double Key Encryption. The files must now be searchable, be discoverable by eDiscovery, and be co-aut
- Changing a published label's encryption does not affect every previously labeled item in the same way
Adding encryption to a published label protects newly labeled items after the update reaches clients. Existing files in SharePoint and OneDrive with labeling integration enabled acquire the new encryption status when next accessed, but other previously labeled documents and emails generally need the label removed and reapplied to change encryption status. Changes to administrator-assigned users and rights take effect at authentication, subject to the offline use-license boundary; changing user-assigned permission mode applies to newly labeled or relabeled items.
Trap Recreating the publishing policy to force all offline desktop files to adopt newly added encryption immediately, because policy distribution does not rewrite each existing file's protection.
3 questions test this
- You have a Microsoft 365 E5 subscription. A published label named General had no encryption. You edit General to apply encryption. Some files labeled General are in SharePoint with labels enabled for
- You have a Microsoft 365 E5 subscription. A label uses Assign permissions now. You add a partner group to the label permissions so that partner users can open documents already labeled and encrypted l
- You have a Microsoft 365 E5 subscription. A label uses Let users assign permissions with Do Not Forward. You change the label so that it uses Encrypt-Only instead. What happens to email messages that
- SharePoint file-label integration enables service processing of supported encrypted content
Enable SharePoint and OneDrive file-label integration with the Purview portal's Turn on now banner or Set-SPOTenant -EnableAIPIntegration $true; Multi-Geo deployments require running PowerShell for each geo. This allows the services to process supported label-encrypted files that use a cloud-based key for Office for the web, search, eDiscovery, and DLP, rather than treating the contents as unreadable. Existing encrypted files must be edited or downloaded and uploaded again to gain these processing capabilities. File integration is separate from Microsoft Entra container-label enablement and from the Co-authoring for files with sensitivity labels setting used for encrypted-file collaboration in desktop and mobile Office apps.
Trap Using Execute-AzureAdLabelSync to make encrypted cloud documents searchable, because synchronizing container labels does not enable SharePoint's processing of file contents.
3 questions test this
- You have a Microsoft 365 E5 subscription. Encrypted files in a SharePoint site are not returned by search or eDiscovery. A colleague proposes running Execute-AzureAdLabelSync in Security & Compliance
- You have a Microsoft 365 E5 subscription. Your organization uses Microsoft 365 Multi-Geo. SharePoint and OneDrive in every geo-location must be able to process the contents of Office files that are en
- You have a Microsoft 365 E5 subscription. Documents that are labeled with encryption in SharePoint Online cannot be opened in Office for the web, and search does not return their content. Sensitivity
Select Extend protection on download, copy or move for a SharePoint library to protect downloaded unprotected documents with the original SharePoint permissions rather than an independent fixed recipient list. Enable Set-SPOTenant -ExtendPermissionsToUnprotectedFiles $true, file-label integration, and encrypted-file coauthoring, then select a published file label using Let users assign permissions with the Office permission-prompt option. Ordinary recipients must connect to the original SharePoint item to open the downloaded file, so offline access is unavailable and removal of their source access or deletion of the source prevents opening. These labeled files cannot be moved or copied to another site, and moving or copying between libraries in the same site requires permission to create or delete lists.
Trap Using an ordinary administrator-permissioned library default to track later SharePoint access changes on downloads, because its fixed usage-right grants do not perform this original-item permission check.
3 questions test this
- You have a Microsoft 365 E5 subscription. A SharePoint library is configured to extend SharePoint permissions to downloaded files. User1 downloads a protected file from the library and later tries to
- You have a Microsoft 365 E5 subscription. A library in a site named Site1 extends SharePoint permissions to downloaded files. User1 must move a labeled file from that library to a library in a site na
- You have a Microsoft 365 E5 subscription. Unlabeled files downloaded from a library named Lib1 must stay protected with the current SharePoint permissions of the original files, even after those permi
- Document tracking and revocation target a registered ContentID rather than every copy of a file
Track and revoke a protected Office document by its registered ContentID; supported Office apps register local label-protected documents when opened, and password-protected documents are unsupported. After Connect-AipService, use Get-AipServiceDocumentLog to find the ContentID by filename or protection owner and Get-AipServiceTrackingLog -ContentId to inspect successful and denied access. Revoke with Set-AipServiceDocumentRevoked -ContentId -IssuerName, or undo a mistaken revocation with Clear-AipServiceDocumentRevoked using the same values; cached offline rights can continue until their allowed period expires. For documents protected with administrator-defined permissions, SharePoint or OneDrive uploads remove ContentID and downloads receive a new one, so revoking the original identity does not revoke downloaded copies.
Trap Using an Advanced Message Encryption email-revocation command for a registered local Office document, because that workflow targets eligible encrypted messages rather than a document ContentID.
3 questions test this
- You have a Microsoft 365 E5 subscription. A document named Spec.docx is protected with administrator-defined permissions and is stored in a OneDrive account. You revoke the ContentID that Spec.docx ha
- You have a Microsoft 365 E5 subscription. User1 attached two documents named Q1.docx and Q2.docx to one email message, protected the message, and sent it. You revoke access to Q1.docx by using its Con
- You have a Microsoft 365 E5 subscription. You revoked access to a protected document by running Set-AipServiceDocumentRevoked with its ContentID and an IssuerName. The revocation was a mistake, and au
- Sensitivity label content markings depend on item type and application support
Office content markings can add headers, footers, and document watermarks, with variables such as the label or document name. Email and meeting invites support headers and footers but not watermarks. Watermarks allow 255 characters and headers or footers generally allow 1,024, while Excel has a combined 255-character header-and-footer limit that includes formatting codes; service-side auto-labeling does not itself insert these visual markings into documents.
Trap Using encryption alone to meet a requirement for visible handling instructions on printed documents, because restricting access does not insert those instructions into the content.
3 questions test this
- You have a Microsoft 365 E5 subscription. A label named HR encrypts documents. Printed copies of HR documents must show the text "Handle under policy HR-7" on every page so that anyone who sees the pa
- You have a Microsoft 365 E5 subscription. A label adds a header that contains 600 characters, including some formatting. The header appears as expected in Word documents, but the header text cannot be
- You have a Microsoft 365 E5 subscription. A label named Confidential is configured with a header, a footer, and a watermark as content markings. User1 applies Confidential to an email message in Outlo
- Dynamic watermarks personalize the displayed document and require encrypted labels
Dynamic watermarks insert the viewing user's UPN by default and can include customized text, date, and time. They require label encryption, persist in print but not export, and Microsoft recommends setting offline access to Never. Except for documented exceptions such as the Rights Management owner, Outlook attachment preview, and PowerPoint Live, unsupported Office clients deny access rather than silently omitting the watermark, so verify client capability before deployment.
Trap Using a static Confidential watermark for a requirement to identify which reader captured a page, because fixed content marking does not personalize itself for the current viewer.
2 questions test this
- You have a Microsoft 365 E5 subscription. Screenshots of highly sensitive board documents are being shared outside the company. Each page must show the email address of the person who has the document
- You have a Microsoft 365 E5 subscription. A label applies encryption and a dynamic watermark. Some users can open labeled documents in Office on the web, but they cannot open them in an older desktop
- A sensitivity label must be published to become available to its intended users
Create and configure a sensitivity label first, then include it in a label policy targeted to users or supported groups. One label can be reused in several policies, allowing a pilot audience and later organization-wide publication without duplicating the label. Editing an already published label does not require a new policy; allow up to 24 hours for changes to replicate across apps and services. The publishing policy can also supply a custom help-page URL, displayed as Learn More after the available labels in Office apps, to explain label choices beyond individual label tooltips.
Trap Creating an auto-labeling policy solely to populate a user's Sensitivity menu, because menu availability comes from a publishing policy.
4 questions test this
- You have a Microsoft 365 E5 subscription. Group IT contains the IT department, and group Staff contains all other users. A new label named Confidential must be available to both groups at once. IT mus
- You have a Microsoft 365 E5 subscription. A label named Confidential is published to all users in a label policy named Global. You need to change the tooltip and header text of Confidential so that ev
- You have a Microsoft 365 E5 subscription. You create a sensitivity label named Label1 in the Microsoft Purview portal. Users in the Sales department must be able to select Label1 from the Sensitivity
- You have a Microsoft 365 E5 subscription. Users are unsure which sensitivity label to choose for their documents. You must add a link in the Sensitivity menu of Office apps that opens an intranet page
- Default labels provide a starting classification while mandatory labeling requires coverage
A publishing policy can assign separate defaults for supported item types such as documents, email, meetings, containers, and Power BI content. Mandatory labeling requires an applicable label before the supported save, send, or creation operation; the requirement can be satisfied manually, automatically, or by a default. Combine these settings when coverage is required with fewer prompts, while allowing users to choose the classification that accurately fits the content.
Trap Using mandatory labeling alone to guarantee that sensitive documents receive the most restrictive category, because requiring a label does not determine which classification is correct.
3 questions test this
- You have a Microsoft 365 E5 subscription. New Word documents must start with a label named General. New email messages must not receive any default label, but users can still apply labels to email man
- You have a Microsoft 365 E5 subscription. Every document and email message that users create must have a sensitivity label before users can save the document or send the message. Users must be able to
- You have a Microsoft 365 E5 subscription. Mandatory labeling is enabled for documents, and users complain that Word prompts them to choose a label for every new document. You must keep label coverage,
- Users receive labels from all applicable policies and conflicting settings from the highest-priority policy
Sensitivity label policies are ordered with the lowest priority at the top and the highest order number at the bottom. A user in multiple policies receives their combined available labels, while each conflicting setting comes from the highest-priority applicable policy. Reorder the policies when a departmental default or mandatory-label setting must override the organization-wide baseline.
Trap Removing a baseline label from a departmental policy to hide it from a user who still receives the baseline policy, because label availability is combined across applicable policies.
3 questions test this
- You have a Microsoft 365 E5 subscription. User1 is in two label policies: Baseline, order number 0, which sets General as the default label, and Legal, order number 1, which sets Secret as the default
- You have a Microsoft 365 E5 subscription. Label policy Baseline has order number 1 and does not require a label. Policy Finance has order number 0 and requires users to apply a label. Finance users ar
- You have a Microsoft 365 E5 subscription. A label named Public is published to all users in a policy named Baseline. HR users must not see Public. You remove Public from the HR label policy, which inc
- Downgrade justification follows label priority but does not apply to every label change
Configure the label policy to require a justification when users remove a label or replace it with a lower-priority label on files, email, or meetings. Put more restrictive labels lower in the label list so the priority represents the intended sensitivity order. The setting does not apply to container labels or changes between sublabels under the same parent or label group; Office prompts once per app session, while the Information Protection client prompts for each file.
Trap Using a publishing policy's priority number as the sensitivity ranking for downgrade detection, because policy precedence and the labels' own sensitivity order are different lists.
3 questions test this
- You have a Microsoft 365 E5 subscription. A label policy requires justification for label downgrades. In one Word session, User1 downgrades five documents. User1 then downgrades five other files by us
- You have a Microsoft 365 E5 subscription. A label policy requires a justification for changing a label. Users change labels on several items, including documents, SharePoint sites, and sublabels that
- You have a Microsoft 365 E5 subscription. A label policy requires justification for downgrades. Users are not prompted when they change documents from Secret to Internal. The labels list shows Secret
- Unpublishing a sensitivity label withdraws future selection without removing applied labels
Remove a sensitivity label from every publishing policy that offers it to the intended users to withdraw it from their selection menus after policy refresh. Labels already applied to content or containers remain, and an applied container label continues protecting its Teams workspace or SharePoint site. Publication can be restored by adding the label back to a policy; deletion is a separate operation and is blocked while the label remains in any label policy.
Trap Using a SharePoint auto-labeling removal policy to retire a menu choice, because that action changes labels on matching files rather than withdrawing publication to users.
3 questions test this
- You have a Microsoft 365 E5 subscription. You attempt to delete a sensitivity label named Old from the Microsoft Purview portal, and the deletion is blocked. Old was used during an initial testing pha
- You have a Microsoft 365 E5 subscription. A label named Legacy is applied to thousands of documents. You remove Legacy from every label policy so that users can no longer select it. After the policies
- You have a Microsoft 365 E5 subscription. A label named Project is no longer needed. Users must stop seeing Project in their Office apps, but files that already have Project must keep it, and you migh
- Meeting inheritance uses separate settings for shared files and saved artifacts
Configure Inherit label from files shared to meetings separately from Apply meeting label to artifacts, because they control opposite directions of label inheritance. The first setting automatically applies or recommends the highest-priority supported file label published to the organizer for files shared through meeting chat, the Shared tab, or Live share, not screen or window sharing; it can replace a lower manual meeting label but preserves a higher label. The artifact setting applies the meeting label to recordings and transcripts in MP4 files and notes in Loop files when saved to SharePoint or OneDrive, with MP4 labeling support enabled through Set-SPOTenant -EnableSensitivityLabelForVideoFiles $true. Changing the meeting label afterward does not relabel saved artifacts, which require a separate permitted file-label change.
Trap Using the shared-file inheritance option to relabel recordings saved before a meeting's classification changed, because artifact labeling has its own setting and occurs when each artifact is saved.
3 questions test this
- You have a Microsoft 365 E5 subscription. A Teams meeting was labeled Confidential, and its recording was saved to OneDrive with Confidential by using Apply meeting label to artifacts. Afterward, the
- You have a Microsoft 365 E5 subscription. Recordings and transcripts of labeled Teams meetings must receive the meeting sensitivity label when they are saved to OneDrive. Apply meeting label to artifa
- You have a Microsoft 365 E5 subscription. Inherit label from files shared to meetings is enabled. A Teams meeting has the manual label General. File1 is presented by screen share, and File2 is posted
- Outlook can derive an email label from eligible physical attachments
Enable Email inherits highest priority label from attachments in the publishing policy's Default settings for emails to select the highest-priority supported attachment label published to the sender. Attachments must be physical files rather than SharePoint or OneDrive links, and the label must support both files and emails. Inheritance preserves manually labeled email and higher-priority email labels, but can replace lower-priority automatic or default labels. Select Recommend users apply the attachments label instead of automatically applying it when users should confirm the change; without that option, inheritance applies the selected label and its configured encryption automatically.
Trap Assuming a pasted OneDrive sharing link will trigger attachment-label inheritance, because this Outlook policy evaluates physical attachments rather than cloud-file references.
3 questions test this
- You have a Microsoft 365 E5 subscription. Email inherits highest priority label from attachments is enabled without the recommendation option. User1 manually labels an email message Public and then at
- You have a Microsoft 365 E5 subscription. Email inherits highest priority label from attachments was enabled in a label policy last month. User1 pastes a OneDrive sharing link to a document labeled Co
- You have a Microsoft 365 E5 subscription. Email inherits highest priority label from attachments is enabled in the label policy. When users attach labeled documents to unlabeled email messages, they m
- Deleting a sensitivity label changes protection differently across workloads
Deleting an encrypting sensitivity label archives its protection template so previously protected content can still be opened; it does not destroy the template. The archived template prevents creating a new label with the same name; deleting that template risks losing access to content encrypted with it. In SharePoint and OneDrive with file-label integration enabled, opening or exporting a document removes the deleted label's encryption if the services can process it, whereas email and documents outside that integration retain encryption. Deleting a container label removes it and ends enforcement of its configured settings. Label metadata can remain in files after deletion, but losing the label-ID-to-name mapping hides the applied name and can make deleted labels appear as GUIDs in Content explorer or Activity explorer.
Trap Using a familiar protection-template name as proof that a deleted sensitivity label still exists, because archived encryption templates can outlive their label definitions.
3 questions test this
- You have a Microsoft 365 E5 subscription. A label named Project applies encryption and is used on documents in SharePoint, with sensitivity labels enabled for Office files, and on email messages. You
- You have a Microsoft 365 E5 subscription. You deleted a sensitivity label named Restricted that applied encryption. You now try to create a new sensitivity label that has the same name, Restricted, bu
- You have a Microsoft 365 E5 subscription. In Activity explorer, some labeling events show GUIDs instead of sensitivity label names, while events for other labels show names as expected. You need to id
- Client-side label conditions classify content while users edit documents or compose email
Configure Auto-labeling for files and emails on the label to evaluate sensitive information types or trainable classifiers in supported Office clients. Select automatic application or recommendation according to whether users should see a proposed label, and refine SIT conditions with instance counts, confidence, and all-versus-any logic. This path can label a document before it is saved and depends on the Office app's feature support; a service-side auto-labeling policy is the separate choice for unattended processing.
Trap Configuring only a publishing-policy default label for a requirement to recommend classifications based on detected payroll content, because a default is not content-dependent.
4 questions test this
- You have a Microsoft 365 E5 subscription. Analysts draft spreadsheets that contain credit card numbers in Excel for Windows. A label named Confidential must be applied as soon as the numbers are typed
- You have a Microsoft 365 E5 subscription. Users create payroll documents in Word. When Word detects payroll account numbers in a document, users must be prompted to apply a label named Payroll, and th
- You have a Microsoft 365 E5 subscription. A label named Highly Confidential is configured in Auto-labeling for files and emails to apply automatically when Word documents contain credit card numbers.
- You have a Microsoft 365 E5 subscription. Legal staff draft contracts in Word for Windows. A label named Legal must be automatically applied when a document resembles a contract, even if it contains n
- Office auto-labeling conditions using EDM must also include a non-EDM sensitive information type
When configuring a label's client-side sensitive-information conditions with EDM, also specify at least one non-EDM type, such as the corresponding built-in identifier type. An EDM-only configuration turns off that label's auto-labeling setting. Require both types in an all-of group when only reference-confirmed records should trigger labeling; an any-of grouping would also permit the generic type to trigger without EDM confirmation.
4 questions test this
- You have a Microsoft 365 E5 subscription. You create a custom sensitive information type named EDM1 that uses exact data match for customer records. You configure Auto-labeling for files and emails fo
- You have a Microsoft 365 E5 subscription. A label named Customer has client-side auto-labeling conditions that include an EDM type named EDM1 and the built-in type Credit card number. The label applie
- You have a Microsoft 365 E5 subscription. You plan to configure Auto-labeling for files and emails for a label named Patient. The conditions must detect patient records by using an exact data match ty
- You have a Microsoft 365 E5 subscription. Admin1 edits a label named Records. Admin1 removes the built-in Social Security number type from its Auto-labeling for files and emails conditions, and keeps
- Automatic label selection uses sensitivity order with special client-side sibling behavior
When multiple labels qualify, selection normally favors the highest-priority label, which is the one with the highest order number. For an unlabeled file matching sibling sublabels in Office, automatic application is preferred to recommendation before comparing sibling order. If the file already has a sublabel under that same parent, client-side labeling keeps it; service-side policy evaluation instead selects the highest-order qualifying sibling.
Trap Moving a recommended sibling below an automatic sibling to guarantee that Office chooses the recommendation, because automatic-versus-recommended behavior is evaluated before that sibling ordering.
3 questions test this
- You have a Microsoft 365 E5 subscription. A parent label named Confidential has sublabels named Finance and Legal, in that order. A Word document already has Finance applied as a default label. User1
- You have a Microsoft 365 E5 subscription. A parent label named Confidential has two sublabels. Finance is configured for automatic labeling, and Legal, which is positioned below Finance, is configured
- You have a Microsoft 365 E5 subscription. You have four sensitivity labels in this order: Public, General, Confidential, and Highly Confidential. None has sublabels. A document matches the auto-labeli
- Service-side auto-labeling processes cloud files at rest and Exchange mail in transit
Use an auto-labeling policy for saved SharePoint or OneDrive files and email processed by Exchange Online, without depending on an installed Office client. Exchange policy evaluation does not retroactively process mail already at rest in mailboxes. Supported Office and PDF attachments can supply detection evidence, but the policy labels the email rather than assigning the same label to its attachment; encryption inheritance is a separate behavior. For SharePoint and OneDrive, simulation and label application preserve existing modified, modified-by, and date metadata. When the label encrypts a cloud file, its Rights Management issuer and owner are the account that last modified the file.
Trap Using an Exchange auto-labeling policy to relabel all historical mailbox messages, because its Exchange evaluation point is mail transport rather than mailbox-at-rest scanning.
4 questions test this
- You have a Microsoft 365 E5 subscription. You create an Exchange auto-labeling policy named Policy1 that applies a label named Label1 when content contains bank account numbers. User1 sends an unlabel
- You have a Microsoft 365 E5 subscription. A SharePoint Online site named Site1 stores contracts that User1 last edited two years ago. You plan to run an auto-labeling policy named Policy1 against Site
- You have a Microsoft 365 E5 subscription. Users have stored thousands of messages that contain credit card numbers in their Exchange Online mailboxes for several years. You create an auto-labeling pol
- You have a Microsoft 365 E5 subscription. An auto-labeling policy named Policy1 applies an encrypting label named Label1 to files in a SharePoint Online site named Site1. User1 created a file named Fi
- Auto-labeling policies must run simulation and be eligible to turn on before they can apply or remove labels
Run at least one simulation before turning on a service-side auto-labeling policy, and review its matches before enforcement; simulation records expected outcomes without changing labels, can take about 12 hours, and blocks activation if more than 20 million files match, requiring a narrower policy and another run. Before submitting or rerunning simulation through PowerShell, connect with Connect-IPPSSession -EnableSearchOnlySession so the simulation job can be submitted correctly. Results describe one policy and available classification at the time, so assess overlapping active policies and actual enforcement separately; configured activity alerts can still fire during simulation. When selecting Run policy in simulation mode, optionally enable automatic turn-on if the policy is not edited for seven days, rather than requiring a separate manual activation. Duplicating a policy creates a new policy in simulation regardless of the source policy's active state, so the copy must pass its own simulation gate before enforcement.
Trap Assuming a simulation match count proves successful relabeling of all matching files, because evaluation and label-writing enforcement are separate stages.
4 questions test this
- You have a Microsoft 365 E5 subscription. A simulation for an auto-labeling policy named Policy1 shows 8,000 matched files in OneDrive. You turn on Policy1. A week later, your manager asks you to conf
- You have a Microsoft 365 E5 subscription. You run a simulation for an auto-labeling policy named Policy1 that targets all SharePoint sites. The simulation reports more than 25 million matched files, a
- You have a Microsoft 365 E5 subscription. You use Security & Compliance PowerShell to rerun the simulation for an auto-labeling policy named Policy1 after you edit its conditions. The simulation that
- You have a Microsoft 365 E5 subscription. You create an auto-labeling policy named Policy1 for all OneDrive accounts. Management wants Policy1 to start labeling files as soon as possible. You have not
- Service-side labeling requires eligible labels, supported files, and realistic processing scope
The selected label must be published to at least one user; SharePoint and OneDrive encryption requires Assign permissions now with content expiration set to Never, whereas Exchange-only policies also allow Let users assign permissions with Do Not Forward or Encrypt-Only but cannot auto-apply S/MIME-protecting labels. Supported files include DOCX, PPTX, XLSX, and PDFs after tenant PDF support is enabled, while open or checked-out files are ineligible during processing. Plan within 100 policies and a tenant-wide ceiling of 500,000 automatically labeled files per day, not a promised rate; explicit portal targeting allows 1,000 SharePoint sites or 100 OneDrive users or groups, while All is exempt from those selection caps. SharePoint list-item attachments are unsupported, and OneDrive accounts must be associated with their corresponding users for both simulation and auto-labeling. Label-removal policies do not support password-protected files or files protected with external or non-Microsoft encryption, even when simulation identifies matching content.
Trap Using a label that prompts the user applying the label to choose collaborators for unattended SharePoint auto-labeling, because the service needs administrator-defined permissions and nonexpiring content access.
3 questions test this
- You have a Microsoft 365 E5 subscription. Sensitivity labels are enabled for Office files in SharePoint and OneDrive. An auto-labeling policy named Policy1 applies a label to matching Word and Excel f
- You have a Microsoft 365 E5 subscription. You create an auto-labeling policy named Policy1 that targets only Exchange email. Policy1 must apply an encrypting sensitivity label to outgoing messages tha
- You have a Microsoft 365 E5 subscription. You create a sensitivity label named Label1 that applies encryption and lets users assign permissions when they apply the label. You plan to use Label1 in an
- Service-side policies distinguish label replacement from explicit label removal
Choose an apply-label policy to assign or upgrade classification, or the separate SharePoint and OneDrive removal action to clear a selected label, including a manual label, and its label-applied encryption. Automatic application normally preserves manual labels and higher-priority labels while replacing lower-priority automatic or default labels; service-side replacement of a lower-priority manual label requires the explicit policy option. When matching active policies conflict, application wins over removal even if a different label is applied. A matching apply-label policy without the manual-replacement option can also prevent another policy from replacing a manual label.
Trap Raising a label's position alone to ensure that all manually labeled files are replaced by an auto-labeling policy, because replacing manual classifications requires the additional policy option.
3 questions test this
- You have a Microsoft 365 E5 subscription. Policy1 is an auto-labeling policy that removes a label named Draft from OneDrive files. Policy2 is an active auto-labeling policy that applies a label named
- You have a Microsoft 365 E5 subscription. Users manually applied a label named Project to thousands of files in a SharePoint site named Site1. The project has ended, and the files must be left unlabel
- You have a Microsoft 365 E5 subscription. Policy1 is an auto-labeling policy that replaces lower-priority manual labels with Highly Confidential. Its simulation showed manually labeled files as replac
- A library-default auto-labeling policy can extend SharePoint defaults to existing files
Use the auto-labeling policy option that applies SharePoint document libraries' default sensitivity labels to eligible existing files at rest, which the ordinary new-or-edited-file default can leave untouched. This policy selects each library's configured default rather than inspecting content to choose a classification, so it supplies a location-defined baseline rather than content-dependent differentiation. Select specific SharePoint sites rather than All, without administrative-unit scoping; only one such policy is supported per tenant, with up to 10 sites selected at a time. After labeling completes and results are verified, edit that policy to replace the selection with the next batch of up to 10 sites. If a site cannot be added, distinguish a missing library default, which needs configuration, from an inability to verify defaults, which requires checking access to site and library metadata.
Trap Using the general 1,000-site auto-labeling selection allowance for a library-default backfill policy, because this policy type accepts only 10 sites at a time in its single tenant-wide policy.
4 questions test this
- You have a Microsoft 365 E5 subscription. Libraries in 25 SharePoint sites have default sensitivity labels. You need to apply each library default label to the existing files in all 25 sites by using
- You have a Microsoft 365 E5 subscription. Your organization uses Purview administrative units, including one named AU1, for delegated administration. You plan to create an auto-labeling policy that ap
- You have a Microsoft 365 E5 subscription. A document library in a SharePoint site named Site1 has a default sensitivity label named Confidential. Files that users uploaded before the default label was
- You have a Microsoft 365 E5 subscription. You create an auto-labeling policy that applies default sensitivity labels from SharePoint document libraries to existing files. When you add a site named Sit
- Auto-labeling rollout requires licensing and permissions beyond manual labeling
Verify an eligible E5 or P2-tier auto-labeling entitlement rather than assuming that a license supporting manual labeling also permits automatic or recommended labeling. Service-side simulation requires Microsoft 365 auditing, and reading matched source contents additionally requires Data Classification Content Viewer, which Global Administrator does not receive by default. Turning a successfully simulated policy on requires Compliance Administrator or Compliance Data Administrator; content-preview permission is not policy-activation authority. If the auto-labeling surface is absent, verify regional availability as well as the license and administrative assignment before changing the label's detection conditions.
Trap Assigning only Data Classification Content Viewer to an operator who must activate a simulated policy, because source-content visibility does not grant the administrative permission to turn enforcement on.
3 questions test this
- You have a Microsoft 365 E5 subscription. Operator1 has the Data Classification Content Viewer role and reviewed a completed simulation for an auto-labeling policy named Policy1. Policy1 shows Ready t
- You have a Microsoft 365 E3 subscription. Users manually apply sensitivity labels in Office apps. You plan to configure auto-labeling policies for SharePoint and OneDrive, but the Auto-labeling polici
- You have a Microsoft 365 E5 subscription. Audit log search is turned off for the tenant. You create an auto-labeling policy named Policy1 for OneDrive accounts and select Run policy in simulation mode
- Advanced auto-labeling rules expose workload-specific conditions and exceptions
Select Common rules for a shared rule definition across selected workloads, or Advanced rules when Exchange, SharePoint, and OneDrive need different conditions or exceptions. Use Content is shared to distinguish only with people inside my organization from with people outside my organization, and supported attachment or document name, file-extension, and size conditions to refine which items qualify without changing the content detector. Exchange advanced rules can evaluate subjects, headers, senders, and recipients, allowing a message-context requirement without relying only on sensitive-information counts. SharePoint and OneDrive rules can use document properties, but Document property is compares managed-property values as exact strings rather than regular expressions; mapped values containing an ampersand can fail even when the strings agree, so use a consistent alternative classification value without ampersands in the document metadata and rule, then verify simulation matches and actual labeling. For Exchange, Sender domain is accepts up to 600 domain entries in that condition, while FromAddressMatchesPatterns supports at most 10 regular expressions of up to 128 characters each; these are condition- or parameter-specific limits, not combined policy-wide allowances.
Trap Using a regular expression in Document property is to match several SharePoint metadata values, because that managed-property comparison requires exact strings rather than regex matching.
3 questions test this
- You have a Microsoft 365 E5 subscription. One auto-labeling policy must label Exchange email by using subject and sender domain conditions, and label SharePoint files by using only a sensitive informa
- You have a Microsoft 365 E5 subscription. An auto-labeling rule uses Document property is to match the mapped managed property value Billing & payment document. Files that have exactly this value rema
- You have a Microsoft 365 E5 subscription. An auto-labeling policy for SharePoint uses Document property is with the value Proj-.* to match the managed property RefinableString10, which holds values su
- Exchange auto-labeling location scope follows senders rather than recipient membership
Keep Exchange at All included and None excluded when an auto-labeling policy must evaluate incoming messages from external senders, and narrow internal recipients with advanced rule conditions instead. Selecting specific included users or groups exempts external senders, while exclusions exempt messages those users send rather than messages they receive. To encrypt matching externally sent messages, also enable Apply encryption to email received from outside your organization and assign a Rights Management owner. That owner must be one internal user identified by an organization-owned email address, not a mail contact, shared mailbox, or group.
Trap Including only the Finance group in Exchange location scope to encrypt external mail addressed to Finance, because explicit location inclusions select senders and exempt messages sent from outside the organization.
3 questions test this
- You have a Microsoft 365 E5 subscription. An Exchange auto-labeling policy uses an encrypting label and has Apply encryption to email received from outside your organization selected. You must assign
- You have a Microsoft 365 E5 subscription. An Exchange auto-labeling policy labels incoming email from external senders with an encrypting label named Confidential. Matching incoming messages are label
- You have a Microsoft 365 E5 subscription. An Exchange auto-labeling policy has the Exchange location set to All included, and you exclude a user named User1. You need to identify which email messages
- An encrypting auto-label overrides competing Exchange rule-based IRM settings
When an Exchange auto-labeling policy and a mail flow or DLP rule both match, the applied label's encryption takes precedence over the rule's IRM encryption settings. If the applied label does not encrypt, the rule's IRM encryption can be applied alongside that classification label instead. Determine whether the selected label itself supplies encryption before predicting the protection outcome, rather than assuming that every matching rights template accumulates on the message.
Trap Assuming a mail flow rule's broader rights template remains effective beneath a stricter encrypting auto-label, because the matching label's encryption displaces the rule's IRM settings rather than layering the grants.
3 questions test this
- You have a Microsoft 365 E5 subscription. An incoming email message already has IRM encryption that a mail flow rule applied, and it has no sensitivity label. It then matches an Exchange auto-labeling
- You have a Microsoft 365 E5 subscription. An Exchange auto-labeling policy applies a label named General, which does not apply encryption. A mail flow rule that applies IRM encryption also matches the
- You have a Microsoft 365 E5 subscription. A mail flow rule applies a rights template that lets partners read messages. An auto-labeling policy applies Highly Confidential, which encrypts messages for
Associate an existing SharePoint adaptive scope through New-AutoSensitivityLabelPolicy -SharePointAdaptiveScopes when sites must be targeted dynamically or exceed the portal's 1,000 explicitly selected sites. This replaces static enumeration with adaptive membership rather than increasing the portal selection limit. Create the policy and its conditions as separate objects with New-AutoSensitivityLabelPolicy and New-AutoSensitivityLabelRule -Policy.
Trap Using repeated portal site selections to configure a single policy for more than 1,000 explicit SharePoint sites, because the portal selection cap still applies instead of being replaced by adaptive-scope membership.
3 questions test this
- You have a Microsoft 365 E5 subscription. You created an auto-labeling policy by running New-AutoSensitivityLabelPolicy. You now need to define the sensitive information type conditions for SharePoint
- You have a Microsoft 365 E5 subscription. A single auto-labeling policy must target 1,500 SharePoint sites that share a site property. The portal lets you explicitly select up to 1,000 sites. You need
- You have a Microsoft 365 E5 subscription. An auto-labeling policy must automatically include new SharePoint communication sites as they are created, without an administrator editing the policy each ti
- File labeling progress and Exchange labeling verification require different evidence
Use policy-level progress, Labeled items, Labeling failures, and coverage reports to verify SharePoint and OneDrive file enforcement, not Exchange mail; progress updates every 48 hours, so a newly enabled policy can initially show zero. Distinguish successful labeling from Pending, Not yet attempted, and Failed to apply label outcomes; absence from the failure list does not establish success. Coverage by simulation context reports labeling activity after the latest simulation and is available for 30 days, so its counts can differ from all-time labeled totals; rerun simulation to obtain a new coverage context when that window expires. Review each file's Failure reason to distinguish automatically retried transient infrastructure failures from format, existing-protection, or label-configuration failures needing reason-specific administrative remediation, while recognizing that some unsupported files require no action. For recent Exchange results, filter Activity explorer for Sensitivity label applied and check How applied for automatic application, recognizing that the event does not identify the specific auto-labeling policy or rule.
Trap Using an Exchange-only simulation rerun to populate file coverage reports, because those enforcement and coverage views report SharePoint and OneDrive files rather than email.
2 questions test this
- You have a Microsoft 365 E5 subscription. An Exchange auto-labeling policy was turned on yesterday. You need to verify that recent email messages were labeled automatically by the policy. The policy L
- You have a Microsoft 365 E5 subscription. An auto-labeling policy for SharePoint was turned on after a simulation that ran 40 days ago. The View coverage entry for the policy is now unavailable. You n
- A SharePoint library default can upgrade automatic classifications but preserves manual labels
An ordinary SharePoint library default replaces lower-priority automatic or publishing-policy default labels, but preserves manual labels and higher-priority classifications. Configure it as a site administrator in Library settings using a published Files & other data assets label, with file-label integration enabled and library IRM disabled. If the default label encrypts, use administrator-defined permissions with content expiration set to Never, not user-defined permissions or Double Key Encryption. A publishing-policy default never replaces an existing label, and the separate Extend protection on download, copy or move option must remain unselected for this ordinary library-default scenario.
Trap Raising a user's publishing-policy default to overwrite an existing automatic label in a library, because a publishing-policy default does not perform the library default's priority-based replacement.
3 questions test this
- You have a Microsoft 365 E5 subscription. A label named Restricted encrypts content and prompts users in Word to specify permissions. You cannot select Restricted as the default sensitivity label for
- You have a Microsoft 365 E5 subscription. A site admin wants to select a default sensitivity label for a document library named Lib1, but the option to select a default label is unavailable for Lib1.
- You have a Microsoft 365 E5 subscription. Files in a library are automatically labeled General. You need files that users edit in the library to receive Confidential, which has higher priority. You se
- Comparable auto-labeling simulations require preserved results and complete workload evidence
Export the simulation results needed for comparison and check the exported file before editing the policy or restarting simulation, because sample retention does not guarantee earlier-run availability. Simulation displays up to 100 items per site and CSV exports have a 50,000-record ceiling, so displayed or exported rows need not enumerate every policy match. A failed simulation or a workload marked Not available is missing evidence rather than a completed zero-match test, and a partial match count includes only available workload results. For comparable Exchange runs, send and receive the same representative messages during each simulation instead of assuming that earlier test traffic will be evaluated again. Restarting simulation retries evaluation without guaranteeing a fix, so inspect the new status and source results before deciding that testing succeeded.
Trap Assuming retained simulation samples guarantee recovery of earlier-run exports after policy editing, because sample retention and prior-run result availability are separate boundaries.
3 questions test this
- You have a Microsoft 365 E5 subscription. You must compare the simulation results of an auto-labeling policy named Policy1 before and after you edit its conditions. A colleague notes that simulation s
- You have a Microsoft 365 E5 subscription. A simulation for an auto-labeling policy reports 180,000 matched SharePoint files. When you export the matched items to a CSV file, the file contains 50,000 r
- You have a Microsoft 365 E5 subscription. You restart simulation for an Exchange auto-labeling policy after you edit a condition. The first run found 40 matches from test messages sent last week, but
- Recreating an auto-labeling rule requires confirmation of the specific rule-load failure
Contact Microsoft Support when an enabled Exchange auto-labeling policy stops matching without corresponding item-level failures, and recreate a rule only after Support identifies it as failing to load. A rule-load failure prevents evaluation against that rule, unlike a file-level failure after a match, so an empty labeling-failure list does not establish that rule evaluation is healthy. Preserve the affected rule's policy, name, target label, workload and scope, conditions, exceptions, priority, and enabled state, then delete and recreate only that confirmed rule with the same configuration. Plan for interrupted enforcement from that rule during repair and propagation, rerun simulation with newly sent or received Exchange messages, and turn on the policy only after validation before verifying that matching resumes.
Trap Using bulk deletion and recreation of unrelated policy rules to troubleshoot missing Exchange matches, because deleting each rule removes its enforcement without identifying the rule-load fault.
3 questions test this
- You have a Microsoft 365 E5 subscription. Microsoft Support confirms that a rule named Rule2 in an Exchange auto-labeling policy named Policy1 failed to load. Policy1 has five other rules. You will re
- You have a Microsoft 365 E5 subscription. An enabled Exchange auto-labeling policy suddenly stops matching email that it matched last month. The policy has no item-level labeling failures, and its con
- You have a Microsoft 365 E5 subscription. An enabled Exchange auto-labeling policy stopped matching outgoing messages last week, and its Labeling failures view is empty. A colleague says that the empt
- Converting label settings creates a service-side policy from sensitive-information-type conditions only
Use the conversion option at the end of label creation or editing to populate an auto-labeling policy from the label's sensitive-information-type conditions, not its trainable classifiers. Classifier-only labels do not offer conversion, and mixed conditions transfer only the sensitive-information-type portion, so review the resulting detection logic before saving. The generated policy includes all SharePoint, OneDrive, and Exchange locations by default and starts in simulation when saved; edit its scope and conditions when those defaults do not match the intended rollout. Conversion does not check whether file-label integration is enabled for SharePoint and OneDrive, so verify that prerequisite separately before expecting those locations to apply labels.
Trap Assuming conversion preserves a mixed label's trainable-classifier criteria, because the generated service-side policy copies only its sensitive-information-type conditions.
3 questions test this
- You have a Microsoft 365 E5 subscription. You converted label settings into an auto-labeling policy. Its simulation shows matches in OneDrive, but after you turn it on, no OneDrive files are labeled.
- You have a Microsoft 365 E5 subscription. You create an auto-labeling policy by converting a label that uses sensitive information types. The policy must apply only to Exchange email. You review the g
- You have a Microsoft 365 E5 subscription. The Auto-labeling for files and emails conditions of a label use a sensitive info type and a trainable classifier. At the end of editing the label, you select
- Container label settings require Microsoft Entra enablement and label synchronization
Enable sensitivity-label support for Microsoft 365 groups in Microsoft Entra ID, then run Execute-AzureAdLabelSync in Security & Compliance PowerShell to synchronize the labels. Select Groups & sites on the label and publish it to users who need to choose it for supported workspaces. Group owners can change labels for group-connected sites, while a non-group-connected SharePoint site requires a site admin.
Trap Enabling sensitivity labels for Office files in SharePoint as the only prerequisite for labeling Microsoft 365 groups, because file integration and group-label support are separate configurations.
2 questions test this
- You have a Microsoft 365 E5 subscription. You enabled sensitivity labels for Office files in SharePoint and OneDrive. When you create a new sensitivity label, the Groups & sites scope is unavailable,
- You have a Microsoft 365 E5 subscription. A SharePoint communication site that is not connected to a Microsoft 365 group has a sensitivity label named General. The site must be relabeled Confidential.
- Container labels govern workspace access without assigning labels to the files inside
A container sensitivity label can set privacy, guest admission, and SharePoint external-sharing controls, but documents inside do not inherit its item-level label or encryption. Public and Private privacy values set and lock the workspace choice, while None leaves owners able to choose it. The guest-access setting controls adding guests rather than automatically removing existing guests, so review existing membership separately when tightening admission.
Trap Using a private Teams label as the mechanism to encrypt every document uploaded by team members, because workspace access controls do not assign file-level protection.
2 questions test this
- You have a Microsoft 365 E5 subscription. You create a container sensitivity label for teams and sites. The label must apply its guest and sharing controls, but team owners must still be able to choos
- You have a Microsoft 365 E5 subscription. A team has a container label named Restricted that sets its privacy to Private. Management requires that every document uploaded to the team is encrypted. Use
- Container labels can invoke Conditional Access but do not replace its required configuration
For labeled SharePoint sites, choose an unmanaged-device restriction or an existing published authentication context when access must depend on device or authentication conditions. The unmanaged-device option requires the documented app-enforced-restrictions policy and cannot relax a stricter tenant setting. Authentication contexts must be configured and published in Microsoft Entra Conditional Access, and clients that do not support the selected context are denied access.
Trap Assigning a more permissive site label to bypass the tenant's unmanaged-device restriction for one project, because the tenant-level restriction remains the effective lower bound.
2 questions test this
- You have a Microsoft 365 E5 subscription. The tenant is configured for Allow limited, web-only access from unmanaged devices. You apply a label that allows full access from unmanaged devices to a proj
- You have a Microsoft 365 E5 subscription. Labeled SharePoint sites for mergers must require multifactor authentication by using an authentication context. When you edit the label, the drop-down list f
A shared channel inherits the sensitivity label settings of its parent team and cannot replace or remove that inherited label. Container labels can constrain invitations to other teams with Internal only, Same label only, or Private team only controls, subject to compatible privacy and guest settings. These controls govern team invitations rather than invitations to individual users, and only Private team only can potentially remove previously invited teams.
Trap Applying a separate more permissive sensitivity label to one shared channel to allow a partner team, because that channel's label is inherited from its parent team.
2 questions test this
- You have a Microsoft 365 E5 subscription. A team named Team1 has a label that allows only Internal only invitations to shared channels. A shared channel in Team1 must be shared with a partner team, so
- You have a Microsoft 365 E5 subscription. Team1 has a sensitivity label whose shared channel control is set to Internal only. A channel owner in Team1 wants to invite one individual from a partner org
- Container labels can standardize who may share a site and its content
Use the MembersCanShare advanced setting on a sensitivity label to control sharing permissions for the labeled SharePoint site. MemberShareAll allows the broader owner-and-member sharing model, MemberShareFileAndFolder reserves site sharing for owners, and MemberShareNone reserves sharing of files, folders, and the site for owners. Configure this with Set-Label -AdvancedSettings and distinguish it from external-sharing audience controls or the default sharing-link type.
Trap Changing the default sharing-link type to restrict the ability of members to share the site, because a default link choice does not set the sharing-permission model.
2 questions test this
- You have a Microsoft 365 E5 subscription. For sites labeled Project, members and people with Edit permissions must be able to share files and folders, but only site owners can share the site itself. Y
- You have a Microsoft 365 E5 subscription. Sites labeled Highly Confidential must allow only site owners to share files, folders, and the site. You configure the label by using Set-Label in Security &
- Channel meeting protection requires an associated meeting label on the container label
Edit an existing Groups & sites label and associate a configured meeting-protection label to make channel meetings and chats inherit its meeting controls. The association option is available when editing rather than initially creating the label, and the required label scopes include files, emails, and meetings. Users cannot change the associated label inherited by channel meetings and chats. This association supplies meeting and chat protection rather than merely relying on the parent team's container privacy settings.
Trap Reaching for a standalone label on each channel meeting to enforce the channel's baseline, because channel meeting protection is inherited through the container label's configured association.
2 questions test this
- You have a Microsoft 365 E5 subscription. You create a new label with the Groups & sites, Files & other data assets, Emails, and Meetings scopes. While creating it, you cannot find the option Apply a
- You have a Microsoft 365 E5 subscription. All channel meetings and channel chats in teams labeled Confidential must enforce the lobby and recording options of a meeting label named Board, and users mu
- Label-based sharing-link defaults provide a baseline rather than a sharing prohibition
Use Set-Label -AdvancedSettings to configure DefaultSharingScope as SpecificPeople, Organization, or Anyone and DefaultShareLinkPermission as View or Edit for supported labeled sites or documents. Setting DefaultShareLinkToExistingAccess to True overrides both settings and selects people with existing access instead. Users can change the proposed link settings before sharing, so use access restrictions rather than these defaults when broader sharing must be prohibited. When site and document defaults conflict, the more restrictive audience scope wins, with the permissions attached to that selected default rather than independently combining the most restrictive permission.
Trap Assuming a document's View default always overrides a site's Edit default, because a narrower site audience can select the site's default together with its Edit permission.
2 questions test this
- You have a Microsoft 365 E5 subscription. Users must not create Anyone links for documents in sites labeled Restricted. You set DefaultSharingScope to SpecificPeople for the label, but users still cha
- You have a Microsoft 365 E5 subscription. A SharePoint site named Site1 has a label whose default sharing link is scoped to specific people with Edit permissions. A document in Site1 has a label whose
- Power BI labeling requires more than publishing a Purview label to a user
In Fabric tenant settings, enable Allow users to apply sensitivity labels for content and scope it to the intended organization or security groups. Users also need the labels published to them, appropriate information-protection licensing, Power BI Pro or Premium Per User for labeling Power BI items, and Create and Edit permissions on the item. The tenant setting permits labeling capability but does not supply missing item permissions.
Trap Granting only access to the Fabric tenant-labeling setting to a report viewer who must relabel content, because the item still requires Create and Edit rights.
3 questions test this
- You have a Microsoft 365 E5 subscription and Microsoft Fabric with Power BI. User1 has a Power BI Pro license, is in the group allowed by the Fabric labeling tenant setting, and has labels published t
- You have a Microsoft 365 E5 subscription and Microsoft Fabric with Power BI. Sensitivity labels are published to all users, who have Power BI Pro licenses and Edit permissions on their reports. No use
- You have a Microsoft 365 E5 subscription and Microsoft Fabric with Power BI. The tenant setting that lets users apply sensitivity labels is enabled for the entire organization. Only a security group n
- Power BI service permissions govern access while sensitivity labels protect supported exported files
Within the Power BI service, sensitivity labels classify content but do not replace Power BI access permissions or row-level security. Supported exports to Excel, PDF, PowerPoint as an image, and downloaded PBIX files carry the label and its configured file encryption; CSV and other unsupported paths do not. Power BI Desktop enforces encryption on a protected PBIX, so consider both in-service authorization and allowed export paths when designing protection.
Trap Assigning a restrictive sensitivity label to a semantic model as the way to limit which rows a service user can view, because service-level row filtering requires the relevant Power BI security controls.
3 questions test this
- You have a Microsoft 365 E5 subscription and Microsoft Fabric with Power BI. User1 has Viewer access to a report named Report1 in the service. Report1 has an encrypting label that grants User1 no usag
- You have a Microsoft 365 E5 subscription and Microsoft Fabric with Power BI. A Power BI report named Report1 has an encrypting sensitivity label. Users export data from Report1 in several ways. You ne
- You have a Microsoft 365 E5 subscription and Microsoft Fabric with Power BI. Regional managers must see only the rows for their own region in a semantic model named Sales in the Power BI service. Admi
- Power BI label inheritance follows content relationships and preserves stronger classifications
New reports and dashboards inherit the label of their parent semantic model or report, and a label on a published PBIX travels to the resulting service report and model. Downloading a PBIX when the service report and model have different labels selects the more restrictive one. Analyze in Excel also carries the model label and protection to the workbook; refresh can upgrade an inherited label but does not silently replace a manually applied label or downgrade a stronger Excel classification.
3 questions test this
- You have a Microsoft 365 E5 subscription and Microsoft Fabric with Power BI. User1 uses Analyze in Excel on a semantic model named Model1 labeled General, then manually labels the workbook Confidentia
- You have a Microsoft 365 E5 subscription and Microsoft Fabric with Power BI. A semantic model named Model1 is labeled Confidential in the Power BI service. No label policy defines a default label for
- You have a Microsoft 365 E5 subscription and Microsoft Fabric with Power BI. A report named Report1 is labeled General, and its semantic model named Model1 is labeled Highly Confidential, which is mor
- Defender for Cloud Apps label integration requires licensing, connectors, and suitable published labels
Provide both Defender for Cloud Apps and Microsoft Purview licensing, enable the Microsoft 365 app connector, and publish labels whose scope includes files and emails. Enable automatic label scanning in the Microsoft Information Protection section of Cloud Apps settings in the Microsoft Defender portal. Defender for Cloud Apps retrieves the tenant's label list hourly, and can be configured to ignore externally defined labels when only the organization's classifications should be considered.
Trap Adding a Groups & sites-only label to a publishing policy for cloud-file governance, because the integration's label recognition requires the item scopes.
2 questions test this
- You have a Microsoft 365 E5 subscription that uses Microsoft Defender for Cloud Apps. A label named Project is published in a label policy, but Defender for Cloud Apps never recognizes Project on file
- You have a Microsoft 365 E5 subscription that includes Defender for Cloud Apps and Microsoft Purview licenses. Sensitivity labels are published with the Files and Emails scopes. Defender for Cloud App
- Defender for Cloud Apps can label supported originals directly or through file-policy governance
For an individual file, use Cloud Apps > Files and Apply sensitivity label; for matching populations, configure a file policy with the sensitivity-label governance action. Applying labels is supported for suitable Office and PDF files up to 30 MB in Box, Google Workspace, SharePoint Online, and OneDrive. Empty files and libraries requiring checkout cannot be labeled, and password-protected files do not expose readable labels to the service. File-policy application has a safety limit of 100 Apply label actions per app per tenant per day, after which labeling pauses and resumes automatically the next day after 12:00 UTC. Disabling a policy suspends all its pending labeling tasks rather than accelerating the remaining work.
Trap Using the automatic label-discovery checkbox alone to assign a new classification to every matching file, because discovery does not configure a label-application governance action.
3 questions test this
- You have a Microsoft 365 E5 subscription. A Defender for Cloud Apps file policy applies a label named Internal to matching OneDrive files: File1.docx, which is empty; File2.xlsx, which is password pro
- You have a Microsoft 365 E5 subscription. A Defender for Cloud Apps file policy named FP1 applies a label to 5,000 matching files in SharePoint Online. A few hours after FP1 starts, labeling stops whi
- You have a Microsoft 365 E5 subscription that uses Microsoft Defender for Cloud Apps. A security analyst finds one unlabeled Word document in Box that must be labeled Confidential immediately. You mus
- Defender for Cloud Apps label remediation depends on where protection was applied
Defender for Cloud Apps can override unprotected labels applied outside the service but cannot remove them, and it cannot remove protected labels applied outside the service. It also does not override labels it already applied itself. Where protected content needs inspection, configure the documented permission to inspect protected files and choose remediation compatible with the label's origin rather than assuming every label can be replaced or cleared.
Trap Using a second Defender for Cloud Apps file policy to overwrite a label assigned by the first one, because labels already applied by that service are not overridden by its subsequent labeling action.
3 questions test this
- You have a Microsoft 365 E5 subscription. A Defender for Cloud Apps file policy named FP1 applied a label named General to files in Box. A second file policy named FP2 must apply a label named Confide
- You have a Microsoft 365 E5 subscription that uses Microsoft Defender for Cloud Apps. Documents in SharePoint Online carry an unprotected label named PartnerGeneral that was applied outside Defender f
- You have a Microsoft 365 E5 subscription. Users encrypt OneDrive files by applying a label in Word. A Defender for Cloud Apps file policy with content inspection must scan these protected files for se
- Session-policy protection labels the downloaded copy without changing the cloud original
Use the Protect action in a Defender for Cloud Apps session policy with Control file download (with inspection) to label and encrypt a downloaded copy in an eligible Word, Excel, PowerPoint, or PDF format while leaving the cloud original unchanged. Only sensitivity labels configured to apply encryption are offered for this action, and Protect does not overwrite an existing label. The app session must be routed through Conditional Access App Control, with Defender for Cloud Apps and Microsoft Entra ID P1 licensing and the required Purview labeling entitlement in place. When matching session policies conflict, the more restrictive policy wins, so a matching Block prevents download even when another policy would protect it. Select Always apply the selected action even if the data cannot be scanned when the chosen action must also apply to unscannable content, without treating that setting as support for labeling arbitrary file types.
Trap Using a file-policy Apply sensitivity label governance action when only downloaded copies should change, because file-policy governance applies the label to the original cloud file.
3 questions test this
- You have a Microsoft 365 E5 subscription that uses Microsoft Defender for Cloud Apps. Two session policies apply when User1 downloads a file from SharePoint Online through Conditional Access App Contr
- You have a Microsoft 365 E5 subscription that uses Microsoft Defender for Cloud Apps. You create a session policy with Control file download (with inspection) and select the Protect action. The label
- You have a Microsoft 365 E5 subscription. Contractors access a SharePoint Online site from unmanaged devices. Files that contractors download must be labeled and encrypted, but the files stored in the
- Session-labeling validation must exercise the app that actually serves the file
Target the resource app that serves a download separately when needed, because a session policy for a host such as Teams or Exchange does not automatically cover SharePoint or OneDrive. Sign out of existing sessions, reauthenticate to each configured app as an in-scope user, and perform the intended file download. In the Defender portal, open Cloud Apps > Policies > Policy management and select the session policy to check its report for redirected sign-ins and the resulting file action. Confirm both the controlled session and download outcome rather than treating successful host-app sign-in as proof that file protection ran.
Trap Assuming a Teams-targeted session policy controls a file served by SharePoint, because the host app and its resource app require their own applicable policy coverage.
3 questions test this
- You have a Microsoft 365 E5 subscription that uses Microsoft Defender for Cloud Apps. You create a session policy that uses the Protect action for Microsoft Teams. Users download files from the Files
- You have a Microsoft 365 E5 subscription that uses Microsoft Defender for Cloud Apps. You configured a session policy named SP1 to protect files downloaded from OneDrive. A test user signed out, reaut
- You have a Microsoft 365 E5 subscription that uses Microsoft Defender for Cloud Apps. You configure a session policy that protects downloads from SharePoint Online. You are already signed in to ShareP
Implement information protection for Windows, file shares, and Exchange
Read full chapterCheat sheet
Sharp facts the exam loves — scan these before test day.
- The Information Protection client extends Windows labeling without adding an Office add-in
Deploy the Microsoft Purview Information Protection client for File Explorer labeling, the protected-file viewer, file-management PowerShell, or the on-premises scanner. Office labeling uses the built-in Office experience rather than an add-in from this client. The client supports eligible 64-bit Windows and Windows Server versions; ARM64 supports the viewer and file labeler but not the scanner or PowerShell components.
Trap Installing the client as the way to supply sensitivity-label buttons to Office for macOS, because its extension components run on Windows and Office has its own labeling implementation.
5 questions test this
- You have a Microsoft 365 E5 subscription. Users on Windows 11 devices must apply sensitivity labels to PDF files and PNG images by right-clicking them in File Explorer. The solution must use a compone
- You have a Microsoft 365 E5 subscription. A records analyst uses an ARM64 Windows 11 laptop and must run nightly scripts that call Set-FileLabel to label exported PDF files from the Microsoft Purview
- You have a Microsoft 365 E5 subscription. You deploy the Microsoft Purview Information Protection client to Windows 11 devices that run Microsoft 365 Apps. Users report that they can't find an Informa
- You have a Microsoft 365 E5 subscription. You plan to deploy the Microsoft Purview Information Protection client to these devices: Device1: Windows 11 Enterprise, 64-bit Device2: Windows 11 Enterprise
- You have a Microsoft 365 E5 subscription. Several on-premises file shares and a SharePoint Server 2019 farm contain millions of documents. You need to discover sensitive files there and label and encr
- Client deployment requires prerequisite checks and local diagnostic verification
Install the Information Protection client using local administrator permissions, a suitable cloud sensitivity-labeling subscription, and Microsoft Entra authentication. The full installation requires .NET Framework 4.7.2 or later, and its PowerShell module requires Windows PowerShell 4.0 or later. The executable installer can acquire a missing .NET prerequisite and require a restart, but it does not check or install the PowerShell prerequisite, so verify both dependencies during deployment preparation. Confirm successful installation in the install log under %temp% by default, and collect runtime diagnostics from %localappdata%\Microsoft\MSIP or export them to a ZIP file with Export-DebugLogs -FileName; to adjust local diagnostic detail, change HKEY_CURRENT_USER\SOFTWARE\Microsoft\MSIP\LogLevel, which does not change the information sent to Microsoft Purview auditing.
Trap Assigning Information Protection Admins membership as a substitute for elevation on the Windows computer, because tenant administration does not grant local software-installation rights.
6 questions test this
- You have a Microsoft 365 E5 subscription. A help desk technician who is a member of the Information Protection Admins role group tries to install the Microsoft Purview Information Protection client on
- You have a Microsoft 365 E5 subscription. You ran the Microsoft Purview Information Protection client executable silently on Device1 with default options, and you need to confirm from the device that
- You have a Microsoft 365 E5 subscription. Microsoft Support asks you to send all Microsoft Purview Information Protection client log files from Device1 as a single compressed file. You want to collect
- You have a Microsoft 365 E5 subscription. You prepare a deployment checklist for the Microsoft Purview Information Protection client, including its PowerShell module, on older Windows Server computers
- You have a Microsoft 365 E5 subscription. Device1 runs the Microsoft Purview Information Protection client. Its local troubleshooting logs grow quickly, and you must cut them to errors only. Audit dat
- You have a Microsoft 365 E5 subscription. You deploy the Microsoft Purview Information Protection client executable to devices that lack .NET Framework 4.7.2. Your change window must account for every
- Client installation options must match the required components and existing AIP installation
Use the EXE or MSI package for client deployment, and use PowerShellOnly=true with the executable when only the cmdlets are needed. A scanner host requires the full client, so a cmdlet-only installation is insufficient for that role. For a noninteractive upgrade from the older AIP client, first uninstall it or set the AllowMajorVersionUpgrade DWORD to 1 under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\MSIP, acknowledging removal of the old Office add-in; restart File Explorer after installation.
5 questions test this
- You have a Microsoft 365 E5 subscription. Server1 has the Microsoft Purview Information Protection client installed with PowerShellOnly=true because administrators only ran labeling scripts there. Ser
- You have a Microsoft 365 E5 subscription. Users upgrade interactively from the Azure Information Protection unified labeling client to the Microsoft Purview Information Protection client. The setup as
- You have a Microsoft 365 E5 subscription. After you install the Microsoft Purview Information Protection client on Device1 with the executable, the user doesn't yet see the option to apply sensitivity
- You have a Microsoft 365 E5 subscription. Group Policy will silently install the Microsoft Purview Information Protection client on devices that still run the Azure Information Protection unified labe
- You have a Microsoft 365 E5 subscription. Remote Desktop Services hosts had the Microsoft Purview Information Protection client installed with PowerShellOnly=true. Users on these hosts must now label
- Disconnected client support can supply labeling policy but does not enable applying encryption offline
A disconnected Information Protection client can apply labels that do not apply encryption, but applying encryption requires active internet connectivity. Before downloading policy for transfer, Microsoft recommends disabling the download account's EnableAudit advanced label-policy setting with Set-LabelPolicy, because a destination with periodic connectivity can otherwise send that account's name to Microsoft Purview rather than its local user's name. On a connected client signed in as the download account, obtain the required labels and policy settings, export the client logs, and copy the policy XML files from the exported MSIP folder into %localappdata%\Microsoft\MSIP for the disconnected user. After the transfer, restore EnableAudit to True if the download account normally connects to the internet. Reset Settings deletes those copied files, so a disconnected client needs them restored manually before it can resume labeling.
Trap Using a longer protected-document offline use-license duration to let an isolated client encrypt new files, because offline consumption rights do not provide online encryption-service access.
5 questions test this
- You have a Microsoft 365 E5 subscription. An isolated engineering computer uses manually copied policy files. To let engineers encrypt new drawings there, a colleague proposes setting the Confidential
- You have a Microsoft 365 E5 subscription. You exported client logs from a connected computer signed in as the policy download account, and you copied the .xml files from the MSIP folder in the export.
- You have a Microsoft 365 E5 subscription. A laboratory computer that runs the Microsoft Purview Information Protection client can't connect to the internet. You will supply its label policy files manu
- You have a Microsoft 365 E5 subscription. A user on a disconnected computer selected Reset Settings from Help and feedback in the Microsoft Purview Information Protection file labeler, and labeling ha
- You have a Microsoft 365 E5 subscription. A disconnected computer occasionally gets internet access. Its client policy was downloaded by the Entra account Download1, while engineers sign in with local
- The client event-data boundary selects EU storage and processing independently of diagnostic logging
When client events must be stored and processed in the EU, set the HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\MSIP\DataBoundary DWORD to European_Union (2). This selects the event destination rather than changing local diagnostic detail or disabling audit submission.
Trap Using the local LogLevel setting to meet an EU event-residency requirement, because it controls troubleshooting verbosity rather than the destination of submitted events.
5 questions test this
- You have a Microsoft 365 E5 subscription. A colleague created a DataBoundary value as a string containing European_Union under HKLM\SOFTWARE\WOW6432Node\Microsoft\MSIP on devices that run the Microsof
- You have a Microsoft 365 E5 subscription for a company based in Germany. Windows devices run the Microsoft Purview Information Protection client. Events that the client sends must be stored and proces
- You have a Microsoft 365 E5 subscription. Client events from Windows devices that run the Microsoft Purview Information Protection client must be stored and processed in the EU. An engineer proposes s
- You have a Microsoft 365 E5 subscription. You set the DataBoundary registry value to 2 on all Windows devices that run the Microsoft Purview Information Protection client. A data protection officer as
- You have a Microsoft 365 E5 subscription. You are writing a Group Policy Preferences item to configure the EU event destination for the Microsoft Purview Information Protection client on 64-bit Window
- Set-FileLabel can assign a chosen label or classify files from policy conditions
Use Set-FileLabel with -Path and the label's GUID in -LabelId to assign a specific classification to a file or folder tree. Use -AutoLabel instead when content should select a label from configured automatic conditions, and use -PreserveFileDetails when modification details must remain unchanged. A required downgrade justification must be supplied with -JustificationMessage; otherwise affected files can be skipped instead of silently changed.
Trap Running Set-Label to classify files in a local folder, because that Security & Compliance cmdlet configures the label definition rather than applying it to file content.
5 questions test this
- You have a Microsoft 365 E5 subscription. Sensitivity labels are configured with automatic labeling conditions for credit card numbers. A Windows server runs the Microsoft Purview Information Protecti
- You have a Microsoft 365 E5 subscription. Server1 runs the Microsoft Purview Information Protection client. An administrator must classify every document under \\FS01\Legal with the existing Confident
- You have a Microsoft 365 E5 subscription. \\FS01\Projects holds thousands of files, some already labeled by users. With the Microsoft Purview Information Protection client's PowerShell module, you mus
- You have a Microsoft 365 E5 subscription. A records retention process on a file server depends on each file's Date modified value. You plan to label the files on the server by using Set-FileLabel. Lab
- You have a Microsoft 365 E5 subscription. Server1 runs the Microsoft Purview Information Protection client. The Confidential label has a sublabel named Finance. You need to apply Confidential\Finance
- File status reports existing protection while discovery evaluates what the content contains
Use Get-FileStatus to inspect a file's current tenant label, labeling method, Rights Management protection, owner, and issuer. Use Set-FileLabel -WhatIf with optional -DiscoveryInfoTypes to inspect sensitive-information matches without applying a label. Get-FileStatus reports only your tenant's label information and does not treat password protection as Rights Management protection; for SharePoint Online files, use the SharePoint Get-FileSensitivityLabelInfo cmdlet instead.
Trap Interpreting IsRMSProtected=False as proof that a file is readable without a password, because the reported protection status concerns Rights Management rather than every encryption mechanism.
5 questions test this
- You have a Microsoft 365 E5 subscription. You run Get-FileStatus on Plan.docx. The output shows IsRMSProtected : True, but RMSTemplateName shows Restricted Access instead of a template name. A manager
- You have a Microsoft 365 E5 subscription. A workstation runs the Microsoft Purview Information Protection client. Before you label anything, you must see which sensitive information types, such as cre
- You have a Microsoft 365 E5 subscription. You must confirm which sensitivity label is applied to a single Word document stored in a SharePoint Online document library. You have the SharePoint Online a
- You have a Microsoft 365 E5 subscription. Finance protected Budget.docx in Word with Encrypt with Password, and no sensitivity label is applied. Get-FileStatus returns IsRMSProtected False. A colleagu
- You have a Microsoft 365 E5 subscription. A file server named FS1 has the Microsoft Purview Information Protection client installed. You need a report that shows, for every file in \\FS1\Legal, whethe
- Custom permissions can protect a file independently of a fixed label recipient list
Create an ad hoc protection object with New-CustomPermissions to specify recipients, a permission level, and optional expiration, then supply it to Set-FileLabel -CustomPermissions. The object can be used alone or with -LabelId; when combined with a label, the custom permissions replace that label's configured protection settings. The user running the labeling command is normally the Rights Management owner, while -Owner can explicitly select the ownership required for an automated workflow.
Trap Editing a shared label's centrally assigned recipients for a single exceptional file, because that changes a reusable category's configuration rather than giving only that file an ad hoc rights policy.
6 questions test this
- You have a Microsoft 365 E5 subscription. One bid file must be readable by two partner users with Reviewer rights until March 31, after which they lose access. Other files that carry the same Confiden
- You have a Microsoft 365 E5 subscription. A scheduled script runs under a service account and uses Set-FileLabel with custom permissions to protect HR files on a share. The HR manager, not the service
- You have a Microsoft 365 E5 subscription. User1 ran New-CustomPermissions -Users partner1@fabrikam.com -Permissions Viewer -ExpirationDate 12/31 and then protected Design.pdf with Set-FileLabel. User1
- You have a Microsoft 365 E5 subscription. The Confidential label encrypts content for all employees. You run this single PowerShell line: $p = New-CustomPermissions -Users user1@fabrikam.com -Permissi
- You have a Microsoft 365 E5 subscription. Hundreds of documents carry the Legal label, whose encryption grants access to the Legal group. Brief.docx alone must become readable only by the Legal lead a
- You have a Microsoft 365 E5 subscription. External auditors must be able to open and read Audit.xlsx and reply about it, but they must not edit, copy or print the file. You create the protection with
- Remove-FileLabel distinguishes classification removal from protection removal
Use Remove-FileLabel -RemoveProtection to remove encryption while retaining a label, or combine it with -RemoveLabel when both must be removed. Removing a label that uses a protection template also removes that protection, but removing a label with custom permissions leaves its custom protection unless removal is explicitly requested. Supply required justification and sufficient usage rights or an enabled super-user identity before attempting deprotection.
Trap Deleting the sensitivity label in the Purview portal to decrypt a selected local file, because deleting the definition is a tenant-level operation rather than targeted authorized file deprotection.
5 questions test this
- You have a Microsoft 365 E5 subscription. Files in \\FS1\Projects are labeled Confidential, and the label encrypts them. A migration tool must read the files without encryption, but each file must kee
- You have a Microsoft 365 E5 subscription. Report.docx is labeled Internal and was protected with custom permissions created by New-CustomPermissions. The label policy doesn't require justification. Yo
- You have a Microsoft 365 E5 subscription. An employee who left the company encrypted hundreds of project files with custom permissions. An administrator runs Remove-FileLabel -RemoveProtection on them
- You have a Microsoft 365 E5 subscription. The label policy requires users to justify removing a label. You run Remove-FileLabel -RemoveLabel on Strategy.docx from a script, and it returns Skipped with
- You have a Microsoft 365 E5 subscription. You run Remove-FileLabel -RemoveProtection on protected .zip and .7z archives in \\FS1\Archive by using an account that has sufficient usage rights, but prote
- Native file encryption enforces usage rights while generic encryption mainly gates file access
The Information Protection client uses native encryption for supported Office, PDF, text, and image formats, with usage-right enforcement by a compatible app or viewer. For formats not supported by native encryption, generic encryption by default wraps the file as a .pfile and authenticates authorized users before opening, but the intended usage restrictions are displayed rather than technically enforced after release to the native application. Native Office encryption usually preserves the file extension, while protected text and image formats can acquire extensions such as .ptxt or .pjpg.
Trap Selecting generic protection to enforce a no-print requirement inside an arbitrary third-party editor, because that wrapper does not enforce application-level usage rights after authorized opening.
5 questions test this
- You have a Microsoft 365 E5 subscription. A user labels Budget.docx with a label that encrypts content and denies Print, by using the Microsoft Purview Information Protection client in File Explorer.
- You have a Microsoft 365 E5 subscription. Engineers store CAD drawings in a format that doesn't support native encryption. A label that grants View but not Print is applied to the drawings by using th
- You have a Microsoft 365 E5 subscription. Researchers keep meeting notes as plain text. Meg labels Notes.txt as Confidential, an encrypting label, from the right-click menu of the Microsoft Purview In
- You have a Microsoft 365 E5 subscription. A user applies a label that encrypts content to four files by using the Microsoft Purview Information Protection client. You want to know which files will be
- You have a Microsoft 365 E5 subscription. A user on a Windows 11 device that runs the Microsoft Purview Information Protection client right-clicks a Visio 2003 drawing named Design.vsd in File Explore
- Advanced label-based protection can preserve local editing for non-Office file types
On onboarded Windows devices with Endpoint DLP's Advanced label-based protection for all files on devices enabled, applying an encrypting sensitivity label to a non-Office, non-PDF file through the Information Protection File Labeler keeps its original extension, so it stays editable in its standard application. Endpoint DLP enforces only the VIEW, EXTRACT and PRINT usage rights before egress, and encryption is applied when the file leaves the computer. The PowerShell module doesn't recognize this setting: labeling with PowerShell encrypts and changes the file extension.
Trap Removing encryption requirements from the label to preserve a specialist application's local workflow, because device-integrated label protection can separate local usability from egress encryption.
5 questions test this
- You have a Microsoft 365 E5 subscription. Advanced label-based protection for all files on devices is on. User1 copies Report.ptxt, encrypted by the Confidential label that grants Edit, from a USB dri
- You have a Microsoft 365 E5 subscription. Engineers on onboarded Windows 11 devices label .csv and .txt files with an encrypting label by using the Microsoft Purview Information Protection client. The
- You have a Microsoft 365 E5 subscription. Advanced label-based protection for all files on devices is on. On an onboarded device, User1 copies Results.txt, which has an encrypting label, to a USB driv
- You have a Microsoft 365 E5 subscription. Advanced label-based protection for all files on devices is on. On an onboarded device, User1 opens Plan.txt, labeled with an encrypting label that doesn't gr
- You have a Microsoft 365 E5 subscription. Advanced label-based protection for all files on devices is turned on in Endpoint DLP. A user labels Data.csv on an onboarded Windows device with a label that
- Client labeling eligibility depends on file format, location, and password protection
For File Explorer or PowerShell labeling, PDF and JPG files support labels without encryption, whereas XML content can be inspected but requires encryption to receive a label; the scanner's format-eligibility distinction also applies here. WebDAV locations are unsupported, and the client automatically excludes Windows, Program Files, Program Files (x86), ProgramData, and all users' AppData folders, together with executable and system formats such as .exe, .dll, and .sys. A password-protected file cannot be natively encrypted by the client unless it is open in the application applying the encryption.
Trap Using a nonencrypting label on XML to preserve its original extension, because the client supports XML through encryption rather than metadata-only labeling.
6 questions test this
- You have a Microsoft 365 E5 subscription. Users map a partner's document store through a WebDAV drive letter. Labeling files there with the Microsoft Purview Information Protection client fails, altho
- You have a Microsoft 365 E5 subscription. User1 right-clicks Photo.jpg in File Explorer and applies the General label, which doesn't apply encryption, by using the Microsoft Purview Information Protec
- You have a Microsoft 365 E5 subscription. A user selects four files in File Explorer and applies a sensitivity label by using the Microsoft Purview Information Protection client. The client reports th
- You have a Microsoft 365 E5 subscription. User1 right-clicks ten Excel workbooks in File Explorer and applies the Confidential label, which applies encryption, by using the Microsoft Purview Informati
- You have a Microsoft 365 E5 subscription. An application reads Settings.xml from a file share, and the data owner wants the file labeled by using File Explorer and the Microsoft Purview Information Pr
- You have a Microsoft 365 E5 subscription. An administrator runs Set-FileLabel with a sensitivity label that doesn't apply encryption against PDF files in four folders on a Windows 11 device by using t
- A production Information Protection scanner requires a full client, Windows Server, and SQL configuration storage
Deploy the full Information Protection client on a supported 64-bit Windows Server host for production scanning; Server Core and Nano Server are unsupported. The scanner requires a local or remote SQL Server instance with case-insensitive collation, with SQL Server 2016 as the documented minimum and Express recommended only for testing. Plan at least four processor cores, 8 GB RAM, and temporary-file storage appropriate to concurrent file inspection; SQL and scanner capacity must be sized separately.
Trap Using a Windows desktop client with no SQL instance for a production unattended scanner, because the production service and its configuration database have additional host prerequisites.
5 questions test this
- You have a Microsoft 365 E5 subscription. A database administrator wants to host the configuration database for a large Microsoft Purview Information Protection scanner deployment on an existing SQL S
- You have a Microsoft 365 E5 subscription. To save costs, a colleague proposes installing the Microsoft Purview Information Protection client on an always-on Windows 11 desktop, with no SQL Server, to
- You have a Microsoft 365 E5 subscription. You are planning a production deployment of the Microsoft Purview Information Protection scanner to label files on four on-premises SMB file shares. The infra
- You have a Microsoft 365 E5 subscription. A database team must host the configuration database for a new Microsoft Purview Information Protection scanner cluster and lists four existing SQL Server ins
- You have a Microsoft 365 E5 subscription. You are sizing a dedicated virtual machine for a production Microsoft Purview Information Protection scanner node. You want the VM to match the documented sca
- Scanner repository permissions depend on whether it only discovers or also changes files
The scanner service account needs Log on as a service and access to the repositories it scans. Read permission is sufficient for discovery-only scans; classification and protection on file shares require Read, Write, and Modify, while SharePoint Server requires Full Control. When the scanner must inspect or reprotect files encrypted by others, enable the Azure Rights Management super-user feature and grant the scanner account that capability in addition to filesystem access.
Trap Granting SQL db_owner as the remedy for access-denied errors on a file share, because database permissions do not confer repository read or modification rights.
4 questions test this
- You have a Microsoft 365 E5 subscription. The Microsoft Purview Information Protection scanner will scan document libraries on SharePoint Server Subscription Edition and apply sensitivity labels that
- You have a Microsoft 365 E5 subscription. You will run the Microsoft Purview Information Protection scanner in discovery mode only against \\FS01\Finance to report sensitive information types, without
- You have a Microsoft 365 E5 subscription. A content scan job applies a label that reprotects files, but the Microsoft Purview Information Protection scanner fails on files that other users had encrypt
- You have a Microsoft 365 E5 subscription. The Microsoft Purview Information Protection scanner in enforce mode reports access-denied errors when labeling unencrypted Office files on \\FS02\HR. The ser
- The scanner's Windows service identity and delegated cloud identity can be configured separately
A synchronized Active Directory account simplifies running the Windows service and obtaining its cloud label policy, but separate Windows and Microsoft Entra accounts are supported. Use Set-Authentication with the registered app, tenant, and -DelegatedUser to acquire the token and policy, adding -OnBehalfOf when setting credentials for a different Windows execution account. Publish the required labels to the delegated identity and grant admin consent for the app's Content.DelegatedReader, Content.DelegatedWriter, and UnifiedPolicy.Tenant.Read application permissions so unattended authentication supplies the intended policy.
Trap Publishing labels only to the administrator who installed the scanner, because unattended policy acquisition uses the delegated cloud identity rather than whichever user performed installation.
4 questions test this
- You have a Microsoft 365 E5 subscription. The Microsoft Purview Information Protection scanner service runs as CONTOSO\scansvc, which can't be granted Log on locally. You will run Set-Authentication f
- You have a Microsoft 365 E5 subscription. Policy prevents synchronizing the Active Directory account that runs the Microsoft Purview Information Protection scanner service to Microsoft Entra ID, but t
- You have a Microsoft 365 E5 subscription. The Microsoft Purview Information Protection scanner authenticates with Set-Authentication -DelegatedUser scanner@contoso.com. A new label, Restricted, is pub
- You have a Microsoft 365 E5 subscription. For unattended Microsoft Purview Information Protection scanner authentication, you registered an app and added the Azure Rights Management Services permissio
Create the scanner cluster and its content scan job, then install each node with Install-Scanner -SqlServerInstance and -Cluster using the intended shared configuration. Installation normally uses local administrator rights and SQL sysadmin to create the database and grant the service account db_owner; a precreated database is the documented alternative when sysadmin cannot be granted. Supply the Windows service identity as DOMAIN\username at the installer prompt, and use the same cluster name and database when adding scale-out nodes.
Trap Giving every node a different cluster name to make one large scan run faster, because different clusters use separate configuration rather than cooperating on the same cluster workload.
4 questions test this
- You have a Microsoft 365 E5 subscription. You run Install-Scanner -SqlServerInstance SQL1\SCANNER -Cluster Europe, and the installer prompts for the scanner service account. The account is scanneracco
- You have a Microsoft 365 E5 subscription. A SQL Server Sysadmin role was granted to you only until the Microsoft Purview Information Protection scanner installation completed. You will keep configurin
- You have a Microsoft 365 E5 subscription. To scan one large repository faster, you installed three Microsoft Purview Information Protection scanner nodes against the same SQL Server instance with the
- You have a Microsoft 365 E5 subscription. Policy prohibits granting the SQL Server Sysadmin role, even temporarily, to anyone who installs or configures the Microsoft Purview Information Protection sc
- Scanner licensing distinguishes discovery and uniform labeling from content-based automation
Validate scanner feature entitlement separately from client installation and repository or cloud permissions. The service-description matrix includes sensitive-information discovery and applying one label across an on-premises repository in both Azure Information Protection Premium P1 and P2, but automated content-based classification, labeling, and protection requires P2 capability rather than P1. Purview Information Protection for Office 365 does not include those scanner features, so verify the service-plan capabilities included in the organization's subscription before choosing a discovery, repository-baseline, or content-dependent rollout.
Trap Assuming a P1 entitlement for applying a repository-wide default label also licenses content-driven scanner classification, because the feature matrix assigns those two scanner operations to different entitlement levels.
4 questions test this
- Your organization licenses Azure Information Protection Premium P1 but not P2. A content scan job must apply the Confidential label only to on-premises files that contain passport numbers, based on th
- Your organization licenses Azure Information Protection Premium P1 but not P2. You want the Microsoft Purview Information Protection scanner to apply the General label to every file on one on-premises
- Your organization licenses Azure Information Protection Premium P1 but not P2. You want the Microsoft Purview Information Protection scanner to find on-premises files that contain any sensitive inform
- Your organization's only information protection entitlement is Purview Information Protection for Office 365. The full client and the Microsoft Purview Information Protection scanner are installed, wi
- A scanner can run repeatedly without enforcing labels until enforcement is enabled
Start a content scan job with Schedule set to Manual and Enforce sensitivity labeling policy set to Off to obtain discovery reports before making changes. After validating results, set enforcement to On to label and protect, manually run a full rescan to apply labels across previously inspected content, and set Schedule to Always when continuous crawl cycles are required. Relabel files is a separate setting that defaults to Off and should be enabled only when the approved rollout requires replacing classifications rather than only labeling eligible unlabeled content. A scanner systematically crawls repositories rather than providing real-time event interception, so choose both change behavior and crawl frequency deliberately.
Trap Changing Schedule to Always as the only step to apply labels after a discovery pilot, because recurrence and labeling enforcement are independent job settings.
4 questions test this
- You have a Microsoft 365 E5 subscription. A Microsoft Purview Information Protection scanner content scan job enforces labeling. Many files already carry the General label, and the scanner must replac
- You have a Microsoft 365 E5 subscription. Managers want a sensitivity label applied by the Microsoft Purview Information Protection scanner within seconds of a user saving a file to \\FS01\Contracts,
- You have a Microsoft 365 E5 subscription. After a Microsoft Purview Information Protection scanner discovery pilot, a colleague changed only the content scan job Schedule from Manual to Always. A week
- You have a Microsoft 365 E5 subscription. After a discovery pilot, you edit a Microsoft Purview Information Protection scanner content scan job, set Schedule to Always and Enforce sensitivity labeling
- Scanner repository configuration uses explicit local, UNC, or SharePoint Server paths
Add supported local paths, UNC network shares, or SharePoint Server library and folder URLs to a content scan job. Repository paths do not support wildcards, WebDAV, or OneDrive locations, and repository-specific settings can inherit the content scan job defaults or override them. Discovering all SharePoint sites below a root URL requires the scanner's additional farm-level Site Collector Auditor permission rather than only permission to one known document library.
Trap Using a service-side SharePoint Online auto-labeling location to reach an SMB share through its synced OneDrive folder, because the scanner must be given the supported on-premises repository path.
4 questions test this
- You have a Microsoft 365 E5 subscription. Engineering files live on an on-premises SMB share, and some users also sync copies to OneDrive. You must label the files on the share by using the Microsoft
- You have a Microsoft 365 E5 subscription. A Microsoft Purview Information Protection scanner content scan job applies the default label General to its 30 repositories. Files in \\FS03\Legal must get t
- You have a Microsoft 365 E5 subscription. You are adding a repository to a Microsoft Purview Information Protection scanner content scan job so that it scans every file and subfolder in the Projects s
- You have a Microsoft 365 E5 subscription. You add the repository http://sp01 to a Microsoft Purview Information Protection scanner content scan job to discover all SharePoint Server sites and subsites
- Scanner classification can use label conditions, recommended rules, or a repository baseline
For classification based on content, configure automatic label conditions and leave Label files based on content enabled. If the available labels have only recommended conditions, enable Treat recommended labeling as automatic so the unattended scanner can act on them. For a uniform repository baseline, configure a default label at the policy, content-job, or repository level; for discovery without configured label conditions, set Info types to be discovered to All instead of Policy only.
Trap Choosing Policy only during an inventory of all sensitive data when no label has automatic conditions, because that discovery scope is restricted to configured policy evidence.
4 questions test this
- You have a Microsoft 365 E5 subscription. None of your sensitivity labels have automatic labeling conditions. You must use the Microsoft Purview Information Protection scanner to inventory every known
- You have a Microsoft 365 E5 subscription. Labels in \\FS02\Old must be removed from all files by the Microsoft Purview Information Protection scanner, including protection the labels applied. Label fi
- You have a Microsoft 365 E5 subscription. Confidential has an automatic condition for passport numbers. In the Microsoft Purview Information Protection scanner job, a colleague set Label files based o
- You have a Microsoft 365 E5 subscription. The Confidential label has only recommended labeling conditions for passport numbers. The Microsoft Purview Information Protection scanner enforces labeling,
- A scanner's ability to inspect a file does not guarantee it can apply the desired label
The scanner uses installed Windows IFilters to extract content, then applies labels only when that file type supports the required classification and encryption. For example, a TXT file can be inspected but cannot receive a label without encryption; the scanner protects Office and PDF files by default, so protecting additional formats requires the file-protection configuration. ZIP inspection on Windows Server needs the Microsoft Office IFilter, and encrypting the archive requires inclusion through PFileSupportedExtensions; executable and system-file exclusions must also be respected.
Trap Adding TXT to the scan inclusion list as the complete fix for a nonencrypting label that is never applied, because inspection eligibility does not add metadata-only labeling support to that file type.
4 questions test this
- You have a Microsoft 365 E5 subscription. The Microsoft Purview Information Protection scanner inspects .txt files on \\FS07\Exports, but its non-encrypting default label never lands on them. Complian
- You have a Microsoft 365 E5 subscription. The Microsoft Purview Information Protection scanner runs on Windows Server and must find credit card numbers inside .zip files on \\FS02\Exports. Scans repor
- You have a Microsoft 365 E5 subscription. A Microsoft Purview Information Protection scanner job lists .exe and .dll in File types to scan, so that application folders on \\FS04\Apps are classified. T
- You have a Microsoft 365 E5 subscription. The Microsoft Purview Information Protection scanner applies an encrypting Highly Confidential label to matching .docx and .pdf files, but matching .xml files
- Bulk scanner labeling can preserve modification details while setting protection ownership
Content scan jobs preserve Date modified, Last modified, and Modified by by default, allowing classification without rewriting those business metadata values. The default protection owner is the Scanner Account, so choose ownership deliberately when a service account should not become the effective content owner.
Trap Assuming preservation of Modified by also preserves the original protection ownership, because the job's separate Default owner setting assigns protection ownership to the Scanner Account by default.
4 questions test this
- You have a Microsoft 365 E5 subscription. A Microsoft Purview Information Protection scanner content scan job covers 12 repositories with the default owner value. Files labeled in \\FS06\Finance only
- You have a Microsoft 365 E5 subscription. The security team wants rights-owner@contoso.com, rather than the scanner account, to be the owner value for files that the Microsoft Purview Information Prot
- You have a Microsoft 365 E5 subscription. Records managers require that Date modified, Last modified and Modified by stay unchanged when the Microsoft Purview Information Protection scanner labels fil
- You have a Microsoft 365 E5 subscription. A Microsoft Purview Information Protection scanner job keeps its default settings, including Preserve "Date modified", "Last modified" and "Modified by" On, a
- An explicit scanner cache reset requests full file coverage for a one-time scan
Use Start-Scan -Reset to initiate a full scanner cycle that includes previously inspected files, even when policy and content have not changed. The -Reset parameter resets the scanner cache; in the Microsoft Purview portal, Rescan all files requests full coverage instead of an ordinary incremental cycle. Start-Scan requires a running scanner service and a Manual schedule and is ignored when Schedule is Always. Use Stop-Scan to stop a running cycle.
Trap Using Start-Scan without -Reset to rebuild an inventory of unchanged files under an unchanged policy, because an ordinary subsequent cycle inspects only new or changed files.
4 questions test this
- You have a Microsoft 365 E5 subscription. Halfway through a large Microsoft Purview Information Protection scanner cycle, you run Stop-Scan to free server resources for a backup window. The next morni
- You have a Microsoft 365 E5 subscription. You changed the auto-labeling conditions for a Microsoft Purview Information Protection scanner content scan job and need every file inspected again from the
- You have a Microsoft 365 E5 subscription. A Microsoft Purview Information Protection scanner with a Manual schedule completed several cycles. Neither the policy nor the files changed, but auditors nee
- You have a Microsoft 365 E5 subscription. The Microsoft Purview Information Protection scanner service is running, and its content scan job enforces labeling continuously. You run Start-Scan -Reset to
- Scanner status shows current health while local reports preserve per-file results and scan history
Use Get-ScanStatus to distinguish Offline, Idle, Scanning, and Error and inspect node or repository details when a scan stalls. Error means the service can be running but unable to scan, for example because its configuration database is inaccessible. Review summary TXT and per-file CSV reports under %localappdata%\Microsoft\MSIP\Scanner\Reports for the service account; the portal shows only the latest scan, while local reports retain earlier evidence and Set-ScannerConfiguration -ReportLevel controls reporting detail.
Trap Treating a running Windows service as proof that the content scan is processing files, because service startup can coexist with database or repository errors.
4 questions test this
- You have a Microsoft 365 E5 subscription. Get-ScanStatus reports the Microsoft Purview Information Protection scanner cluster status as Error, even though the scanner Windows service is running on eve
- You have a Microsoft 365 E5 subscription. Disk space on a Microsoft Purview Information Protection scanner node is limited, and you want its local scanner reports to record errors only instead of more
- You have a Microsoft 365 E5 subscription. Auditors ask for the results of Microsoft Purview Information Protection scanner cycles from last month, but the admin portal shows only the latest scan. The
- You have a Microsoft 365 E5 subscription. The Microsoft Purview Information Protection scanner service shows Running in Services, yet no files have been labeled for hours. You need to confirm whether
- Message Encryption requires Azure Rights Management and a working Exchange IRM configuration
Activate Azure Rights Management for the tenant and verify AzureRMSLicensingEnabled with Get-IRMConfiguration in Exchange Online PowerShell. If necessary, enable it with Set-IRMConfiguration, then use Test-IRMConfiguration with a tenant sender and recipient to verify template acquisition, encryption, and decryption. An Exchange Online deployment using AD RMS must migrate to Azure Rights Management before using Microsoft Purview Message Encryption.
Trap Installing the Information Protection file labeler on every external recipient's computer to enable encrypted email, because the message service supports recipient portal access without that Windows client.
5 questions test this
- You have a Microsoft 365 E5 subscription that has never used AD RMS. Get-IRMConfiguration shows AzureRMSLicensingEnabled True, but Test-IRMConfiguration -Sender admin@contoso.com -Recipient admin@cont
- You have a Microsoft 365 E5 subscription. You are validating Microsoft Purview Message Encryption with Test-IRMConfiguration so that the output confirms RMS template acquisition, encryption and decryp
- You have a Microsoft 365 E5 subscription. A change ticket asks you to prove, from Exchange Online PowerShell, that the tenant is configured for Microsoft Purview Message Encryption by reading the Azur
- You have a Microsoft 365 E5 subscription. Exchange Online currently uses an on-premises Active Directory Rights Management Services (AD RMS) cluster for IRM. The company now wants to use Microsoft Pur
- You have a Microsoft 365 E5 subscription. The Azure Rights Management service is active in the tenant, but Get-IRMConfiguration returns AzureRMSLicensingEnabled : False. You need Microsoft Purview Mes
- Encrypt-Only allows collaboration while Do Not Forward restricts recipients' reuse
Choose Encrypt-Only when recipients should receive confidential email but may forward, copy, and print it. Choose Do Not Forward when the original recipients should be the authorized audience and forwarding, copying, and printing must be restricted while replies remain possible. Do Not Forward derives its authorized users from that message's chosen recipients, unlike an administrator-defined rights template whose audience is fixed in advance.
Trap Using TLS transport requirements alone to prevent an authorized recipient from printing a delivered message, because transport encryption does not impose client-side usage rights.
5 questions test this
- You have a Microsoft 365 E5 subscription. User1 sends a sensitive message to three people in Marketing by using the Do Not Forward option. One recipient drags the email into a Marketing shared folder
- You have a Microsoft 365 E5 subscription. Messages about a merger must be readable by every current member of the Legal group, even when a sender addresses only some Legal members, and nobody outside
- You have a Microsoft 365 E5 subscription. User1 sends an Encrypt-Only message to an auditor who uses a gmail.com account. The auditor selects the link in the wrapper email and reaches the encrypted me
- You have a Microsoft 365 E5 subscription. User1 sends a pricing proposal to two customers and applies the Do Not Forward option in Outlook. One customer, who uses a Microsoft 365 work account, opens i
- You have a Microsoft 365 E5 subscription. User1 sends a message to external auditors by using the Encrypt option in Outlook on the web, which applies Encrypt-Only. An auditor asks which actions the pr
- Unencrypted Office attachments inherit email encryption while previously encrypted attachments retain their own rights
When a protected email includes unencrypted supported Office documents, those attachments inherit the email's encryption and usage restrictions. The email's sensitivity label identity is not automatically assigned to the attachment, and a document encrypted before attachment keeps its original encryption. Protect a file before attaching it when its intended audience or usage rights must differ from the email; for automatic PDF attachment encryption, enable Set-IRMConfiguration -EnablePdfEncryption $true and use a supported viewer such as Microsoft Edge or the encrypted-message portal.
Trap Changing an email's To list to grant access to an independently encrypted attachment, because the attachment keeps the rights assigned before it joined the message.
4 questions test this
- You have a Microsoft 365 E5 subscription that uses Microsoft Purview Message Encryption. Users attach PDF invoices to encrypted emails, but the PDF files arrive unencrypted while attached Word documen
- You have a Microsoft 365 E5 subscription. You set EnablePdfEncryption to $true. External recipients now receive encrypted PDF attachments with encrypted emails and ask the help desk which apps they ca
- You have a Microsoft 365 E5 subscription. User1 applies the Confidential label, which encrypts content, to an email and attaches an unencrypted Excel workbook named Q3.xlsx. The email goes to a collea
- You have a Microsoft 365 E5 subscription. User1 sends a Do Not Forward email with an unencrypted Excel workbook, Forecast.xlsx, attached to an internal analyst, User2. User2 opens the attachment from
- Mail flow encryption rules act on organizational sending and require Exchange Online routing
Create an Exchange mail flow rule using sender and recipient conditions and the action to apply Message Encryption and rights protection with the intended RMS template. Scope organizational sending explicitly; a rule cannot encrypt inbound mail from an external sender, which is delivered without that requested encryption. In a hybrid deployment, on-premises users can use the service only when their email is routed through Exchange Online, so implement the hybrid mail path before relying on its rules.
Trap Configuring an Exchange Online encryption rule for a hybrid mailbox whose outbound route bypasses Exchange Online, because the message never reaches the service's rule-evaluation path.
5 questions test this
- You have a Microsoft 365 E5 subscription. A mail flow rule encrypts all mail that the Sales department sends to external recipients. A partner at fabrikam.com reads Sales mail only through an automate
- You have a Microsoft 365 E5 subscription. Your organization recently migrated from Active Directory Rights Management Services to the Azure Rights Management service. Existing mail flow rules still en
- You have a Microsoft 365 E5 subscription in a hybrid deployment with Exchange Server. An Exchange Online mail flow rule encrypts all mail sent to external recipients. Messages from on-premises mailbox
- You have a Microsoft 365 E5 subscription. You need a mail flow rule that encrypts every message the members of a group named Finance send to people outside your organization. Messages that Finance mem
- You have a Microsoft 365 E5 subscription that uses Microsoft Purview Message Encryption. You are creating a mail flow rule named Rule1 that must encrypt messages sent to an external auditor at auditor
- Mail flow rules can remove the organization's message protection and optionally its attachment protection
Use the mail flow action to remove Message Encryption and rights protection applied by the organization when an authorized workflow requires decryption. Scope it to organizational messages or replies to messages originally protected by the organization, and add the separate attachment-rights removal action if the entire message and its protected attachments must be unprotected. This is not a general ability to decrypt content protected by unrelated external organizations.
Trap Removing only message-level protection for an integration that must receive editable unprotected Office attachments, because the attachment protection has its own removal action.
6 questions test this
- You have a Microsoft 365 E5 subscription. During a 30-day evaluation, a third-party gateway processes every message your users send, to internal or external recipients, and it can't read protected con
- You have a Microsoft 365 E5 subscription. An approved records system receives copies of encrypted mail from your organization, including Office attachments that users protected before attaching them.
- You have a Microsoft 365 E5 subscription. An approved partner portal ingests mail that your users send and fails on any protected content. Users encrypt some messages with Encrypt-Only in Outlook. You
- You have a Microsoft 365 E5 subscription. A mail flow rule removes Office 365 Message Encryption and rights protection from messages that arrive in the Legal mailbox. A law firm that uses its own Micr
- You have a Microsoft 365 E5 subscription. Users send encrypted mail to external customers, and customers reply from the encrypted message portal. A compliance system that scans incoming mail can't rea
- You have a Microsoft 365 E5 subscription. By using Exchange Online PowerShell, you create a mail flow rule with New-TransportRule for mail sent to an approved integration mailbox. The rule must remove
- Encrypted-message portal access can use social identities or one-time passcodes
Message Encryption supports external recipients through native supported Outlook experiences or the encrypted-message portal for other clients. Use Set-OMEConfiguration -SocialIdSignIn to allow or disallow Microsoft, Google, or Yahoo account sign-in, and -OTPEnabled to control one-time passcodes for the selected configuration. Choose the allowed authentication paths to fit the recipient population rather than requiring every external person to join the sender's Microsoft 365 tenant.
Trap Creating a Microsoft Entra guest account for every Gmail recipient as an unconditional prerequisite for encrypted mail, because the portal supports external authentication methods without that onboarding model.
5 questions test this
- You have a Microsoft 365 E5 subscription that uses Microsoft Purview Message Encryption. Policy now forbids external recipients from signing in to the encrypted message portal with Google, Yahoo or Mi
- You have a Microsoft 365 E5 subscription. On the OME configuration applied to external mail, you run Set-OMEConfiguration with -OTPEnabled $false and -SocialIdSignIn $false. Which recipients will stil
- You have a Microsoft 365 E5 subscription with Advanced Message Encryption. A mail flow rule applies the custom branding template Legal1 to Legal's external mail; other mail uses the default. Only reci
- You have a Microsoft 365 E5 subscription that uses Microsoft Purview Message Encryption. SocialIdSignIn is $false and OTPEnabled keeps its default. A supplier contact with a Gmail address and no work
- You have a Microsoft 365 E5 subscription that uses Microsoft Purview Message Encryption. Fifty partner contacts use Gmail and must read encrypted messages from your users. A colleague plans to invite
- Service-side decryption for the iOS mail app improves readability at the cost of local rights enforcement
The iOS mail app cannot decrypt Message Encryption content itself, and service-side decryption is off by default. Set-ActiveSyncOrganizationSettings -AllowRMSSupportForUnenlightenedApps can deliver a decrypted message copy, but that client can then permit local copy or print operations that the original rights restricted. Server-mediated actions still check rights, attachments remain unsupported in the iOS mail app, and more restrictive OWA or ActiveSync mailbox policies can override the organization setting.
Trap Choosing service-side decryption to preserve the same local copy-and-print controls as a rights-aware Outlook client, because the decrypted local copy is not subject to equivalent client enforcement.
5 questions test this
- You have a Microsoft 365 E5 subscription that uses Microsoft Purview Message Encryption. No ActiveSync settings have been changed from their defaults. A user opens an encrypted message in the built-in
- You have a Microsoft 365 E5 subscription. Executives read mail in the iOS mail app, which can't decrypt Message Encryption. You plan to run Set-ActiveSyncOrganizationSettings -AllowRMSSupportForUnenli
- You have a Microsoft 365 E5 subscription. Some executives read mail in the built-in iOS mail app and can't open messages protected by Microsoft Purview Message Encryption. You decide to let the servic
- You have a Microsoft 365 E5 subscription. You set AllowRMSSupportForUnenlightenedApps to $true. Most users of the built-in iOS mail app can now read encrypted messages on their iPhones, but every user
- You have a Microsoft 365 E5 subscription. You enabled service-side decryption for the iOS mail app. Users of the built-in iOS mail app can now read encrypted messages on their iPhones, but they report
- Encrypt-Only attachment download decryption is configurable separately from message encryption
By default, supported attachments retain their encryption when downloaded from encrypted email through a browser. Set-IRMConfiguration -DecryptAttachmentForEncryptOnly $true enables service-side decryption for eligible Encrypt-Only attachment downloads while leaving the email encrypted. Choose this option only when editable downloaded copies are intended, and distinguish it from Do Not Forward or independently protected attachments whose restrictions must remain in force.
Trap Replacing the entire email's protection with ordinary unencrypted delivery to permit an editable attachment download, because the Encrypt-Only attachment setting can address the download independently.
5 questions test this
- You have a Microsoft 365 E5 subscription. Partners receive Encrypt-Only messages with Excel attachments and download them from a web browser. They need editable copies with no restrictions, and the em
- You have a Microsoft 365 E5 subscription with DecryptAttachmentForEncryptOnly set to $true. User1 encrypts Plan.docx for the Finance group, attaches it to an Encrypt-Only email and sends it. A Finance
- You have a Microsoft 365 E5 subscription that uses Microsoft Purview Message Encryption with default settings. A recipient opens an encrypted message in a web browser and downloads an attached Word do
- You have a Microsoft 365 E5 subscription. You plan to set DecryptAttachmentForEncryptOnly to $true so that recipients can work with attachments from Encrypt-Only mail. Your security officer asks what
- You have a Microsoft 365 E5 subscription. You set DecryptAttachmentForEncryptOnly to $true. When recipients download from a web browser, attachments on Encrypt-Only mail now arrive unprotected, but at
- Advanced Message Encryption provides reusable custom branding configurations beyond the default template
Use Get-OMEConfiguration and Set-OMEConfiguration in Exchange Online PowerShell to inspect or customize the default template's logo, background, introduction, disclaimer, privacy URL, and portal text. With Advanced Message Encryption, use New-OMEConfiguration for additional departmental or regional templates and Remove-OMEConfiguration to retire a custom one. The default template can be modified but not deleted, so distinguish reverting its customization from removing an optional custom template.
Trap Creating multiple sensitivity labels solely to give departments different encrypted-message portal logos, because that presentation requirement belongs to reusable OME branding configurations.
5 questions test this
- You have a Microsoft 365 E5 subscription. An administrator customized the default Microsoft Purview Message Encryption branding template with a logo, disclaimer text, portal text and a purple backgrou
- You have a Microsoft 365 E5 subscription that uses Microsoft Purview Message Encryption. Marketing supplies a new company logo for the default branding template. You plan to run Set-OMEConfiguration w
- You have a Microsoft 365 E5 subscription that uses Microsoft Purview Advanced Message Encryption. A custom branding template named Retail1 is applied by a mail flow rule for a retail brand that the co
- You have a Microsoft 365 E5 subscription that uses Microsoft Purview Message Encryption. The default branding template already shows the corporate logo. The Finance and Legal departments each need enc
- You have a Microsoft 365 E5 subscription that uses Microsoft Purview Advanced Message Encryption. A custom branding template named HR1 is applied by a mail flow rule to encrypted mail that HR sends ex
- Advanced encrypted-email expiration depends on custom branding and external portal access
Configure New-OMEConfiguration or Set-OMEConfiguration with -ExternalMailExpiryInDays between 1 and 730, then select that custom template in a mail flow rule through -ApplyRightsProtectionCustomizationTemplate alongside the chosen rights-protection template. The branded wrapper routes external recipients to the portal, where the expiration is enforced; the wrapper displays the expiry and the portal rejects access afterward. These controls apply to external recipients using the portal rather than internal messages or native inline delivery, so a template must be applied to matching mail as well as created.
Trap Using an Outlook message's ordinary expiration metadata to guarantee that external recipients lose access to encrypted content, because Advanced Message Encryption enforces access expiry through its branded portal configuration.
4 questions test this
- You have a Microsoft 365 E5 subscription that includes Microsoft Purview Advanced Message Encryption. A custom branding template named Partner1 has no expiration and is applied by a mail flow rule to
- You have a Microsoft 365 E5 subscription that includes Microsoft Purview Advanced Message Encryption. External reviewers read Research's encrypted mail in the encrypted message portal and must lose ac
- You have a Microsoft 365 E5 subscription. Contoso applies a custom branding template with a 10-day expiration to encrypted mail sent to suppliers. A supplier calls the help desk because an encrypted i
- You have a Microsoft 365 E5 subscription. A mail flow rule applies a custom branding template with ExternalMailExpiryInDays set to 30 to every encrypted message that User1 sends. User1 sends one encry
- Revoking encrypted mail requires a revocable portal-delivered message and its Message ID
For administrative revocation, obtain the message's Message ID, use Get-OMEMessageStatus to check IsRevocable, then run Set-OMEMessageRevocation -Revoke $true -MessageId and verify the Revoked status. Revocation works for eligible external, link-based branded messages rather than a native inline Outlook experience. A sender can use Remove external access in Outlook on the web for eligible sent mail to a single social-account recipient, while administrators use the supported administrative workflow for eligible messages.
Trap Using ordinary Outlook message recall to revoke an external encrypted portal message, because recall and the portal's continuing access authorization are different mechanisms.
5 questions test this
- You have a Microsoft 365 E5 subscription that includes Microsoft Purview Advanced Message Encryption. Compliance officers must be able to revoke eligible encrypted messages, but they don't use PowerSh
- You have a Microsoft 365 E5 subscription that includes Microsoft Purview Advanced Message Encryption. Yesterday you ran Set-OMEMessageRevocation -Revoke $true for a branded encrypted message that User
- You have a Microsoft 365 E5 subscription that includes Microsoft Purview Advanced Message Encryption. A user reports sending a branded encrypted message containing payroll data to the wrong external a
- You have a Microsoft 365 E5 subscription that includes Microsoft Purview Advanced Message Encryption. User1 sent a branded, link-based encrypted message to an external recipient by mistake. You have i
- You have a Microsoft 365 E5 subscription that includes Microsoft Purview Advanced Message Encryption. User1 sent a custom-branded encrypted message to a single recipient who uses a yahoo.com account.
- Advanced Message Encryption can audit external portal sign-in and message use
Enable encrypted-message portal tracking with Set-IRMConfiguration -EnablePortalTrackingLogs $true and apply a custom branding template to ensure recipients use the portal. The audit records can show external sign-in time and authentication method, reading messages or attachments, attachment downloads, replies, and forwards. Search encrypted message portal activities in Microsoft Purview Audit when proving recipient access rather than merely proving transport delivery.
Trap Using message trace delivery status alone as evidence that an external recipient opened an encrypted attachment, because successful delivery is not a portal content-access event.
5 questions test this
- You have a Microsoft 365 E5 subscription. You enabled portal tracking logs, but auditors find no encrypted message portal activities for several partners who use Microsoft 365 work accounts. The partn
- You have a Microsoft 365 E5 subscription. Portal tracking logs are enabled with Set-IRMConfiguration. A manager asks you to list every time an external recipient read or forwarded encrypted mail from
- You have a Microsoft 365 E5 subscription that includes Microsoft Purview Advanced Message Encryption. Auditors must be able to see when external recipients sign in to the encrypted message portal, rea
- You have a Microsoft 365 E5 subscription that includes Microsoft Purview Advanced Message Encryption. Portal tracking logs are enabled and a custom branding template is applied to external mail. Secur
- You have a Microsoft 365 E5 subscription. Portal tracking logs are enabled and external encrypted mail uses a custom branding template. Legal wants to know which recipient actions the encrypted messag
Implement data loss prevention and retention
Create and configure data loss prevention policies
Read full chapterUnlock with Premium — includes all practice exams and the complete study guide.
Implement and monitor Microsoft Purview Endpoint DLP
Read full chapterUnlock with Premium — includes all practice exams and the complete study guide.
Implement and manage retention
Read full chapterUnlock with Premium — includes all practice exams and the complete study guide.
Manage risks, alerts, and activities
Implement and manage Microsoft Purview Insider Risk Management
Read full chapterUnlock with Premium — includes all practice exams and the complete study guide.
Manage information security alerts and activities
Read full chapterUnlock with Premium — includes all practice exams and the complete study guide.
Protect data used by AI services
Read full chapterUnlock with Premium — includes all practice exams and the complete study guide.