Study Guide · SC-401

SC-401 Cheat Sheet

417 entries · 9 chapters · 3 domains

Implement information protection

Implement and manage data classification

Read full chapter

Cheat 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Custom classifier training requires separate positive and negative seed collections

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
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
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
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
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
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
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
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
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
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
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
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

Implement and manage sensitivity labels in Microsoft Purview

Read full chapter

Cheat 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
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
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
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
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
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
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
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
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
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
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
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
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
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
Extended SharePoint protection keeps downloaded documents tied to the original item's permissions

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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
PowerShell auto-labeling can target adaptive SharePoint membership instead of enumerated sites

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
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
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
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
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
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
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
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
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
Teams shared channels inherit the parent label and expose team-invitation controls

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
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
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

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
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
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
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
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
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
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
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
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

Implement information protection for Windows, file shares, and Exchange

Read full chapter

Cheat 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Scanner scale-out uses nodes installed into the same cluster and database

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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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

Implement data loss prevention and retention

Create and configure data loss prevention policies

Read full chapter
  • DLP protection must cover each workload or inline traffic path
  • Multilocation DLP policies share supported conditions but retain workload-specific actions
  • Exchange DLP evaluates new mail rather than rescanning mailbox history
  • On-premises DLP requires a scanner and acts on repository permissions or file placement
  • Fabric DLP requires supported workspace data rather than arbitrary reports or connections
  • A DLP template is a configurable starting point for a documented protection requirement
  • Supplied DLP policies can generate credit-card detections without a custom policy
  • Managed cloud apps DLP controls data in motion with activity-specific conditions
  • Unmanaged cloud-app rules scope inline restrictions with their own conditions
  • Confidence and instance count independently control sensitive-information matches
  • Label conditions use existing classification rather than assigning a label
  • Nested condition groups preserve the intended boundaries of DLP exceptions
  • External access restrictions can preserve internal collaboration
  • Contextual DLP conditions target workload metadata or inspection failures
  • Exchange DLP action selection distinguishes delivery workflows from message modification
  • DLP administration can be delegated without Global Administrator access
  • Administrative units bound both DLP policy management and incident visibility
  • Managing DLP permissions requires role-management authority
  • DLP location scope selects workload instances independently of communication conditions
  • A safe DLP rollout tunes scope, state, and actions independently
  • Cloud DLP overrides combine a blocking action with user feedback
  • DLP incident-report configuration controls administrative evidence and severity
  • Alert aggregation measures repeated events rather than the size of one disclosure
  • DLP notification surfaces have different formatting and delivery limits
  • Client policy-tip settings can hide notifications without removing DLP protection
  • Adaptive DLP rules consume changing insider risk levels
  • Adaptive Protection setup and DLP rule administration require different permissions
  • Adaptive Protection quick setup creates separate endpoint and messaging policies
  • Adaptive endpoint DLP needs advanced classification or a file-type condition
  • A risk-only adaptive rule can restrict sharing without requiring sensitive content
  • DLP collision resolution depends on the policy engine
  • Explicit stop-processing controls apply to Exchange and Teams DLP rules
  • Endpoint DLP combines the most restrictive actions across matching rules
  • Enforced endpoint policies take preference over simulated policies with identical actions
  • Exchange DLP actions determine whether subsequent rules can be processed
  • Instances-based DLP requires a connected cloud-app environment
  • A Purview policy scoped to Instances creates its Defender for Cloud Apps counterpart
  • Purview Instances conditions differ from native file-policy metadata filters
  • Migrating a file policy creates a replacement that must be validated before cutover
  • Cloud Discovery access is insufficient to configure native file protection
  • Dedicated non-Microsoft connected-app policies require a separate DLP configuration
  • File-policy folder scope and owner-group scope target different dimensions
  • Cloud file inspection combines content thresholds with masked evidence
  • File-policy governance is separate from alert notification limits
  • Native cloud file monitoring depends on an active file policy

Unlock with Premium — includes all practice exams and the complete study guide.

Implement and monitor Microsoft Purview Endpoint DLP

Read full chapter
  • Endpoint DLP supports Windows and recent macOS rather than Android endpoints
  • Defender onboarding can be reused for Purview device monitoring
  • Windows Endpoint DLP readiness includes identity, client health, and service connectivity
  • Purview device-management operations require supported Microsoft Entra roles
  • macOS Endpoint DLP onboarding depends on existing MDM management and Defender deployment
  • Supported browser integration enables domain-aware endpoint enforcement
  • Unallowed browser controls block sensitive-file access rather than inspecting each destination
  • Endpoint enforcement requires both the user and device to be in scope
  • Endpoint rule actions must match the actual data-transfer channel
  • Endpoint action modes determine whether users are stopped and whether they can justify proceeding
  • Paste-to-browser rules evaluate the pasted text independently of the source file
  • Scan-failure conditions protect files that lack complete content inspection
  • Endpoint document-attribute conditions can target files without a sensitive-text match
  • File-type and file-extension conditions require separate endpoint rules
  • Clipboard blocking preserves in-file Office editing while restricting transfers to other files
  • Recall snapshot restrictions require a supported Windows endpoint architecture
  • Restricted-app access controls are evaluated before subsequent file activities
  • Restricted app groups provide same-rule exceptions to broader application restrictions
  • Application allowlisting uses an explicit Allow group and a block for other apps
  • Auto-quarantine prevents repeated access attempts by cloud-sync applications
  • Endpoint file-path exclusions disable both monitoring and protection for the excluded paths
  • Endpoint detector selection must account for label origin and classification prerequisites
  • Network-share coverage extends endpoint inspection to files opened from shares
  • Disabling classification removes content inspection for selected supported extensions
  • Ordinary endpoint classification depends on local file creation, modification, or classified-file reads
  • Service-domain mode determines which upload destinations receive DLP restrictions
  • Sensitive service domain groups provide action-specific website controls
  • Printer groups distinguish approved print destinations from the general print action
  • Removable USB groups permit device-specific copying exceptions
  • Network-share groups allow approved copying without excluding files from inspection
  • Windows endpoint network exceptions select activity actions by connection context and priority
  • Website-group match types determine target scope and supported browser actions
  • Just-in-time protection covers files with missing or stale policy evaluation
  • JIT fallback decides what happens when classification fails
  • JIT-specific exclusions preserve ordinary Endpoint DLP classification and protection
  • Deploy endpoint policies before enabling JIT protection
  • JIT holds can end in a resumed operation, a retry, or the configured fallback
  • Always audit file activity provides endpoint visibility before a policy match
  • Activity explorer supports filtered endpoint investigation over up to 30 days
  • Endpoint activity events and rule-match events provide complementary evidence
  • Offline Windows endpoints continue to enforce existing protections
  • Endpoint evidence collection requires both storage setup and rule-level activity selection
  • Always-on diagnostics collects support traces rather than investigator-readable file evidence
  • Device configuration health does not establish that endpoint policies have synchronized

Unlock with Premium — includes all practice exams and the complete study guide.

Implement and manage retention

Read full chapter
  • Retention labels express item-specific exceptions to container-wide retention
  • Retain-only, delete-only, and retain-then-delete serve different lifecycle requirements
  • The retention start point must match the business event being measured
  • Record declaration adds restrictions that an ordinary retention label does not provide
  • A label's expiry action can end restrictions or begin a different lifecycle rule
  • SharePoint list items require retention labels with attachment-specific inheritance
  • Retention settings govern proactive lifecycles while eDiscovery holds preserve a specific investigation
  • Data Lifecycle Management and Records Management expose different label-authoring needs
  • Retention label names and core settings must be chosen before saving
  • One retention label applies at a time without a configurable priority order
  • A record label cannot be deleted while items still use it
  • Retention Management grants lifecycle authoring without requiring item-content access
  • Sequential disposition stages require separate approvals rather than unanimity within one stage
  • Disposition assignment and content-preview permissions must be granted separately
  • Disposition outcomes can advance review, restart it later, or replace the lifecycle rule
  • Disposition auto-approval advances overdue reviews and can authorize final disposal
  • Retention labels provide item-action audit evidence that retention policies do not
  • Adaptive scopes suit large or changing retention populations
  • Adaptive scope type determines both query syntax and selectable locations
  • Targeting only inactive mailboxes requires an adaptive user scope
  • Adaptive scope authoring requires Scope Manager and validated source attributes
  • Static-to-adaptive retention migration requires a validated replacement policy
  • Publishing makes retention labels available without applying them to every item
  • SharePoint default labels apply through container inheritance without overwriting manual labels
  • Outlook folder defaults and rules can apply published retention labels
  • Published labels need workload processing before users can select them
  • Auto-apply retention labels use supported content detectors rather than every DLP detector
  • Historical auto-labeling coverage depends on the condition and workload
  • Query-based auto-application uses the search index and explicit property predicates
  • Retention auto-apply simulation predicts matches without being a mandatory activation gate
  • Cloud-attachment auto-application preserves a copy of the shared file version
  • Retention auto-apply queries require supported managed properties rather than custom aliases
  • Eligible cloud-attachment sharing events determine retained versions and retention restarts
  • Adaptive Protection lifecycle preservation uses a fixed service-managed retention policy
  • Retention obligations are resolved before deletion dates
  • Explicit deletion settings take precedence before the earliest deletion date breaks ties
  • Policy lookup identifies assigned policies for an exact user, site, or group
  • Teams retention must cover messages and their separately stored files
  • An empty static inclusion list reverts to all instances for an enabled location
  • Preservation Lock prevents weakening a retention policy even by administrators
  • Retention distribution errors should be distinguished from normal propagation time
  • Releasing a retention policy does not remove retention labels already applied
  • Mailbox retention locations separate user mailboxes, groups, and public folders
  • Archiving a SharePoint site preserves its retention obligations but restricts interactions
  • A retention archive action changes file storage without releasing compliance preservation
  • Releasing an inactive mailbox's policy has different effects for explicit and implicit targeting
  • SharePoint retention applies to files through their supported storage location
  • Deleting a retained Microsoft 365 group preserves its resources but removes group-based site access
  • Teams call-log cleanup requires a separate PowerShell-managed retention policy
  • SharePoint compliance copies and recycle-bin content require different recovery tools
  • Mailbox compliance copies remain separate from user-visible message folders
  • Recovering an inactive mailbox converts it while restoring copies its content
  • Inactive mailbox restoration requires unique source identity and correct target mapping
  • Inactive mailbox recovery has boundaries for auto-expanding archives and hidden app data
  • Departure recovery depends on retention established before the account is deleted
  • Label-only retention honors version limits that retention policies and holds suspend

Unlock 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 chapter
  • Insider Risk Management Admins configure policies without opening alerts or cases
  • Insider risk content access requires investigator permissions
  • Administrative units restrict insider risk investigations but do not support every global task
  • A priority user group can restrict who reviews evidence about its members
  • The HR connector imports mapped CSV events through an authenticated ingestion process
  • Physical badging signals need HR data to identify access by departing employees
  • Patient data misuse detection combines healthcare activity with employee profile data
  • Custom insider risk indicators consume preprocessed detections rather than raw telemetry
  • Native cloud indicators require their source apps to be connected in Defender for Cloud Apps
  • Security-violation policies require Defender for Endpoint alert sharing
  • Defender alert triage-status filters determine which security activities reach insider risk
  • Username pseudonymization protects display identities rather than every evidence surface
  • Insider risk activation and past activity detection cover different sides of a trigger
  • Insider risk analytics can assess exposure before policies exist
  • Unallowed domains raise insider risk scores while global exclusions suppress scoring
  • Global insider risk alert-volume settings change the lower-severity mix
  • Global exclusion matching must cover the intended destinations and content attributes
  • Global indicators collect activity while policy indicators score activated users
  • Device indicator visibility is bounded by onboarding and collection policies
  • Analytics-based indicator thresholds adapt scoring to actual user activity
  • Built-in insider risk indicators must match the source and eligibility of the signal
  • Indicator variants tailor an existing built-in detection rather than import a new signal
  • Risk score boosters raise activity risk for contextual reasons beyond an event count
  • Conversation-related risk signals require source-specific indicator configuration
  • Insider risk OCR extends policy scoring to eligible images rather than forensic clips
  • Departure-related theft calls for a different template from general data leakage
  • Priority-user templates use curated groups while risky-user templates address employment stressors
  • DLP alerts need separate configuration for insider risk activation and scored evidence
  • Risky browser usage scores website visits that may violate acceptable-use requirements
  • Risky Agents policies evaluate agent behavior rather than only a human user's AI use
  • Insider risk policy membership can be static or adaptive within an administrative boundary
  • Priority content increases risk relevance without automatically excluding other activity
  • Replacing an insider risk policy requires preserving its investigation and Adaptive Protection dependencies
  • Policy health identifies configuration and shared-capacity causes of missing insider risk scoring
  • Sequence detection evaluates an ordered chain rather than unrelated event totals
  • Cumulative exfiltration compares aggregate sharing with organizational and peer norms
  • Forensic evidence capture requires an explicit user request and approval
  • Forensic evidence needs supported Windows Enterprise devices and the Purview client
  • Specific-activity and continuous forensic capture serve different evidence needs
  • Forensic capture duration, daily uploads, and offline storage have separate controls
  • Revoking forensic capture authorization leaves existing clips under separate disposal controls
  • Missing forensic evidence can reflect delivery problems, client failure, or exhausted ingestion capacity
  • Adaptive Protection quick setup creates a baseline while custom setup reuses policy choices
  • Adaptive Protection assigns Elevated, Moderate, and Minor levels from policy insights
  • Adaptive Protection separates the activity lookback from how long a risk level persists
  • Adaptive Protection sends insider risk levels to the control suited to the required protection
  • Confirming an insider risk alert starts or extends a case for one user
  • Resolving an insider risk case records a lasting outcome and starts its cleanup lifecycle
  • Manual scoring can activate selected users before a normal policy trigger occurs
  • Case contributors receive temporary access to one insider risk investigation
  • Insider risk notices educate the case user without closing the case
  • Power Automate provides integrated insider risk workflows for selected cases and users
  • Escalating an insider risk case to eDiscovery enables a legal investigation workflow
  • Office 365 Management Activity API alert export has its own enablement and record filters

Unlock with Premium — includes all practice exams and the complete study guide.

Manage information security alerts and activities

Read full chapter
  • Audit Premium benefits require licensing the user whose activity is recorded
  • Multiyear audit retention needs both the add-on entitlement and a retention policy
  • Exchange search-query auditing must be enabled explicitly on the user's mailbox
  • Audit search permissions must be granted for the interface used
  • Audit searches use exact operation filters and UTC dates rather than unrestricted content search
  • Portal audit searches are bounded jobs rather than continuous collection feeds
  • A PowerShell audit investigation must exhaust result pages rather than trust one response
  • Detailed audit comparisons require expanding the exported AuditData JSON
  • Administrative-unit scoping limits the audit records an investigator can retrieve
  • Disabled unified audit ingestion is corrected with the tenant ingestion switch
  • Audit retention defaults depend on the activity's identity and workload
  • Custom audit retention policies win by priority rather than by longest duration
  • Audit-retention selectors determine how broadly a policy matches
  • Audit retention administration requires Organization Configuration rather than search access alone
  • Security and Compliance PowerShell manages audit retention settings unavailable in the portal
  • Activity explorer shows recent handling events rather than a content inventory
  • Information Protection Analyst supports Activity explorer review without administrative breadth
  • Activity explorer match details explain detection while filter menus are not exhaustive inventories
  • Reusable Activity explorer filter sets focus label investigations within supported workloads
  • DLP alert response combines event validation with tracked ownership and disposition
  • DLP alert permissions do not automatically reveal the matched sensitive content
  • An alert can outlive the mailbox email available for direct download
  • A user activity report can investigate collected signals without an insider risk policy assignment
  • Insider investigations require the evidence view suited to the investigative task
  • Insider risk reports distinguish program effectiveness from an individual investigation
  • Defender XDR can classify DLP signals as behaviors instead of incident-producing alerts
  • Defender DLP incidents correlate security context and expose workload-specific remediation
  • DLP advanced hunting uses audit activity to expand beyond the triggering event
  • Advanced alert policies require an eligible subscription and policy-management authority
  • Insider risk data sharing adds user context to Defender and DLP investigations
  • Defender insider-alert resolution uses classification to determine the Purview outcome
  • Insider risk hunting separates alerts, entities, behaviors, and activity events
  • File-policy evidence identifies who can access sensitive cloud content
  • Cloud file governance actions remove different kinds of exposure
  • The Governance log verifies remediation separately from alert generation
  • Authorizing a verified safe file suppresses future native file-policy matches
  • eDiscovery case access and search-related roles are distinct authorization requirements
  • eDiscovery searches retrieve in-place content from selected mailbox and site sources
  • KeyQL fields and properties determine which evidence an eDiscovery query matches
  • eDiscovery statistics and samples validate relevance without representing a complete export
  • Search permissions filters impose eDiscovery boundaries beyond a single search's source selection
  • Premium eDiscovery processing requires data-user entitlement for enhanced collection and indexing
  • Creating a compliance search defines it but does not execute or export it
  • eDiscovery decryption requires RMS Decrypt and supported encrypted content

Unlock with Premium — includes all practice exams and the complete study guide.

Protect data used by AI services

Read full chapter
  • Copilot DLP uses a dedicated location to exclude eligible labeled grounding content
  • Sensitive-prompt blocking and web-search blocking protect different processing boundaries
  • Copilot can exclude external email by sender metadata without blocking mailbox access
  • Administrative-unit-scoped Copilot DLP follows the prompt user rather than the content owner
  • Copilot policy-tip customization changes only the compliance link destination
  • Endpoint DLP can warn or block sensitive submissions to third-party AI websites
  • Unmanaged AI-app policies in Edge rely on synchronized browser and Intune configuration
  • Copilot's use of label-encrypted content depends on the requesting user's usage rights
  • Copilot label inheritance can raise protection on newly generated destination content
  • Encryption method determines whether Copilot can use protected content
  • Restricted Content Discovery limits SharePoint discovery rather than changing permissions
  • Restricted site access requires both content permission and membership in an allowed group
  • Copilot file protection requires item labels rather than container labels
  • Communication Compliance reviews inappropriate AI prompts and responses as separate matches
  • AI retention policies preserve captured interaction copies in hidden user-mailbox storage
  • eDiscovery retrieves AI conversation content while Audit establishes the activity trail
  • DSPM AI insights depend on auditing and the licenses for the monitored experience
  • Copilot in Fabric and Security Copilot require explicit collection to capture conversation content
  • Enterprise AI visibility requires the service's supported integration and applicable billing
  • Collection rules select source-supported audit events rather than enforcement actions
  • Foundry policy enforcement requires supported user context in addition to Purview onboarding
  • Third-party AI visit discovery and endpoint transfer controls need their respective browser components
  • Edge AI protection can restrict unprotected browsers for the users in policy scope
  • DSPM management and AI read-only roles serve different responsibilities
  • Reading AI prompt and response bodies needs a separate content-viewer permission
  • Insider context in DSPM remains protected by Insider Risk Management permissions
  • Restricted DSPM administrators cannot create organization-wide one-click policies
  • Extend insights creates discovery policies rather than immediate blocking controls
  • Risky AI usage policies score AI behavior rather than only recording policy violations
  • AI network visibility depends on an integrated network partner and collection choices
  • AI protection baselines distinguish paste-and-upload controls from inline Edge prompt blocking
  • DSPM recommendations create ordinary policies that are administered in their owning solutions
  • DSPM labeling recommendations and regulatory guidance address different readiness gaps
  • Enterprise AI prompt blocking requires app-scoped DLP and an application that honors the policy
  • Default DSPM assessments prioritize heavily used sites while custom assessments target a chosen scope
  • Item-level risk assessments use an authorized application to remediate overshared SharePoint items
  • Fabric risk assessments need their own registered-app and admin-API configuration
  • Assessment result tabs guide repository-level oversharing remediation
  • DSPM AI event types distinguish navigation, interactions, sensitive content, and enforcement matches
  • AI monitoring separates service inventory and trends from the availability of conversation bodies

Unlock with Premium — includes all practice exams and the complete study guide.