Domain 1 of 3 · Chapter 3 of 3

Implement information protection for Windows, file shares, and Exchange

Where the Information Protection client fits

Picture a legal department's file server full of PDFs, scanned TIFF images and old Office 97-2003 documents, all of which the Information Protection client can label without encryption[1], yet none of which built-in Office labeling will ever touch because nobody opens them in an Office app. The Microsoft Purview Information Protection client[1] extends sensitivity labels beyond the labels built into Microsoft 365 apps and services, runs on Windows only, and replaces the Azure Information Protection (AIP) unified labeling client; the rest of this topic calls it the Information Protection client.

The labels themselves still come from the Microsoft Purview portal. The Microsoft SC-401 study guide skills measured[2] lists 'Configure protection settings and content marking for sensitivity labels' under Implement and manage sensitivity labels in Microsoft Purview and 'Translate sensitive information requirements into built-in or custom sensitive info types' under Implement and manage data classification; sensitive information types (SITs) drive automatic labeling. This topic covers the three places those labels and their encryption must reach without Office: individual Windows files, on-premises repositories, and Exchange Online email.

One model for the whole topic

Every file or message protected in this topic is encrypted by the Azure Rights Management service, which the Azure Information Protection service description calls the data protection technology for Microsoft Purview Information Protection[3]. The model is the same everywhere: Purview defines the label, Azure Rights Management supplies the encryption, and the client, or its scanner for repositories, applies labels to files while Exchange Online applies the same encryption service to email.

The four client components

The client installs these components, per Microsoft Learn's component table[1]:

Component What it does
Information protection file labeler Applies sensitivity labels and encryption from File Explorer
Information protection viewer Opens files that are encrypted
Microsoft Purview Information Protection PowerShell module Adjusts sensitivity labels on files, and installs and configures the scanner
Information protection scanner Discovers, labels and encrypts files on data stores such as network shares and SharePoint Server libraries

There is no Office add-in in this client[1], because that functionality is replaced by the sensitivity labels built into Office. Installing the client therefore never adds labeling buttons to Office on any platform; Office labels with its own built-in implementation.

Where the content lives decides only email (Exchange Online) versus files (the client). For files, the component follows how labeling runs: the scanner labels files on data stores[1] and runs unattended[4], the PowerShell module labels files from scripts, and a user labels in File Explorer with the file labeler.

Platform support

The client supports the 64-bit versions of Windows and Windows Server[1] covered by the Microsoft Lifecycle Policy, including Windows Enterprise multi-session. On ARM64 the viewer and file labeler are supported, but the scanner and PowerShell are not[1], so a script-based or scanner-based design needs a machine that isn't ARM64.

Deploying the Information Protection client

A client rollout succeeds or fails on prerequisites, and the installer checks only some of them, so plan them before you pick a package.

Prerequisites

Keep the two runtime checks apart: the executable can fetch a missing .NET Framework, but nothing installs a missing PowerShell version for you.

Choosing a package

There are two installers, an .exe and an .msi[1]. The executable supports a silent full install and a silent cmdlets-only install; the .msi is the version Microsoft documents for central deployment, for example with Microsoft Intune. A cmdlets-only install suits a labeling script but not a scanner host, because the scanner prerequisites say you must install the full client for the scanner, not just the PowerShell module[5].

Silent installs with the executable (from Microsoft Learn's install steps)

# Full client, no prompts
PurviewInfoProtection.exe /quiet
# PowerShell cmdlets only: fine for scripts, not valid for a scanner host
PurviewInfoProtection.exe PowerShellOnly=true /quiet

Upgrading from the AIP client

An interactive install that detects the AIP unified labeling client upgrades it after you acknowledge that the AIP Add-in for Office will be removed[1]. A non-interactive upgrade (Microsoft Update Catalog, Group Policy or scripting) requires you to either uninstall the AIP client first or create the AllowMajorVersionUpgrade DWORD[1] under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\MSIP, where 1 silently allows the upgrade and uninstalls the AIP Office add-in and 0 blocks the upgrade.

Confirming the install

After installing, restart any instances of File Explorer[1], then confirm success in the install log, which is created in the %temp% folder by default; search it for Installation completed successfully.

The takeaway: match the package to the role (the full client for a scanner), verify both runtimes yourself, and settle the AIP upgrade path before any silent rollout.

Registry settings for the client's own data

Two registry settings change what the client does with its own data, and they are easy to confuse because both sound like logging: one sets local troubleshooting detail, the other sets where events are sent.

Local diagnostic logs

Client and scanner log files are written to several folders, including %localappdata%\Microsoft\MSIP[1], and they are intended for troubleshooting by Microsoft Support. To hand them over, run the Export-DebugLogs cmdlet or use Export Logs in the file labeler's Help and Feedback dialog[1]; the logs are exported as a single compressed file.

The local detail level is the HKEY_CURRENT_USER\SOFTWARE\Microsoft\MSIP\LogLevel value[1]: Off, Error, Warn, Info (the scanner's default), Debug, or Trace (the default for clients). This registry setting doesn't change the information that is sent to Microsoft Purview auditing.

The EU data boundary

EU customers can have the client send its data to the EU to be stored and processed[1] by setting the HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\MSIP\DataBoundary DWORD, the key that specifies where events are sent: 0 is Default, 1 is North_America and 2 is European_Union.

The takeaway: LogLevel decides how much the client writes locally for support; DataBoundary decides where its events go. An EU residency requirement is met with DataBoundary set to 2, never by lowering LogLevel.

Supporting disconnected computers

By default the client connects to the internet to download sensitivity labels and label policy settings from Microsoft Purview[1], so a computer that can't connect needs those policy files copied in by hand. One limit decides whether the procedure helps at all, so it comes first: the client requires an active internet connection to apply encryption, so the disconnected computers solution is supported only for labels that do not apply encryption[1]. An isolated computer can classify new files but cannot encrypt them, and no offline setting on an already protected document changes that.

The transfer procedure

The figure below traces six consolidated stages in order:

  1. Choose or create a Microsoft Entra user account[1] that will download the labels and policy settings for the disconnected computer.
  2. For that account, turn off sending audit data with the EnableAudit advanced setting through Set-LabelPolicy in Security & Compliance PowerShell[1]. Microsoft recommends this because a disconnected computer that does get periodic connectivity would send logging information that includes the download account's name, which can differ from the local account in use.
  3. On a connected computer with the client installed, sign in with that account and download the labels and policy settings[1].
  4. From that computer, export the log files, for example with Export-DebugLogs.
  5. From the MSIP folder in the compressed export, copy every file with an .xml extension into %localappdata%\Microsoft\MSIP on the disconnected computer[1].
  6. If the download account usually connects to the internet, set EnableAudit back to True.

Keeping it working

If a user selects Reset Settings in the file labeler's Help and feedback, the action deletes the policy files and leaves the client inoperable[1] until you replace the files manually or the computer connects and downloads them. A scanner server without internet connectivity follows a separate procedure built on offline content scan jobs[5] (a content scan job holds the scanner's repositories and their scan settings; see Designing the content scan job below), which can still apply labels based on imported policies.

The takeaway: disconnected support moves policy to the computer, not encryption capability.

1. Choose a download account2. Turn off EnableAudit for it3. Download policy as that user4. Export logs (Export-DebugLogs)5. Copy the MSIP .xml files to%localappdata%\Microsoft\MSIP6. Restore EnableAudit if neededResult: labels withoutencryption only
The six-step policy transfer for a disconnected Information Protection client, from Microsoft Learn's disconnected computers procedure.

What the client can label and encrypt

Whether a file can carry a given label depends on two things the label designer does not control: the file's type and where the file lives. The figure below turns the type rules into the questions to ask for any file.

Labels without encryption

Only some types can be labeled without encryption. The documented list[1] includes PDF, Microsoft Project, Publisher and XPS files, common images such as .jpg, .png and .tiff, Adobe Photoshop, Digital Negative and Autodesk Design Review files, and the Office file types, including the 97-2003 formats. A type outside that list, such as .txt or .xml, can be labeled only by a label that also encrypts it; the client's native encryption table[1] shows .txt becoming .ptxt and .xml becoming .pxml.

Native versus generic encryption

The client supports encryption at two levels[1]:

  • Native encryption is the default for text, image, Office (Word, Excel, PowerPoint) and PDF files. Users must authenticate before the content renders, and the usage rights the content owner set are enforced when the content opens in the viewer (text and image files) or the associated application (everything else).
  • Generic encryption is the default for every other file type the client labels (the excluded system folders and file types listed below are never labeled). The file is encapsulated as a .pfile, authentication decides whether the user may open it, and opening is audited, but the usage rights are only displayed to inform authorized users and are not enforced.

A no-print requirement on an arbitrary engineering file type therefore cannot be met with generic encryption: once an authorized user opens the file, nothing enforces the rights. Generic protection of non-Office formats (PTXT, PJPG and PFILE) is also a separately licensed feature in the Azure Information Protection service description[3], included in Azure Information Protection Premium P1 and P2 but not in Purview Information Protection for Office 365. That feature name is a licensing label broader than the client's native versus generic split: the client's native encryption table[1] lists .ptxt and .pjpg as natively encrypted text and image files, while .pfile is the file type generic encryption uses. Azure Information Protection Premium P1, Azure Information Protection Premium P2 and Purview Information Protection for Office 365 are licensing plans, the columns of that service description's feature table, not software: the description says subscriptions enable AIP service plans and treats Azure Information Protection as part of Microsoft Purview Information Protection[3], so the AIP name survives in plan names after the AIP client was replaced.

File name extensions after encryption

Natively encrypted Office files keep the same file name extension[1]. Natively encrypted text and image files get a new extension (.txt becomes .ptxt, .jpg becomes .pjpg) and become read-only, and generically encrypted files always get the .pfile extension, so a generically encrypted accounts.zip becomes accounts.zip.pfile. Microsoft warns that firewalls, web proxies or security software that act on file name extensions might need reconfiguring for the new extensions.

Limits on what the client can protect

To protect files critical for computer operations, the client automatically excludes the Windows, Program Files, ProgramData and all users' AppData folders[1] from classifying and labeling, along with file types such as .exe, .dll, .sys, .bat, .msi and .tmp, among others. WebDAV locations aren't supported for the listed file types. A password-protected file can't be natively encrypted by the client[1] unless it is currently open in the application that applies the encryption; you most often see this with password-protected PDF files.

Keeping files editable with Endpoint DLP

For file types other than Office and PDF, the Endpoint DLP setting Advanced label-based protection for all files on devices[1] changes the timing of encryption when labels are applied with the Information Protection File Labeler, not PowerShell: DLP enforces only VIEW, EXTRACT and PRINT permissions before the file leaves the computer (egress), and encryption is applied only at egress. The local file name extension therefore doesn't change, and users keep viewing and editing in their standard application.

The takeaway: check the file type first. It decides whether a label can stand alone, whether usage rights are enforced, and whether the extension changes.

Does the labelapply encryption?NoYesType can be labeledwithout encryption?Type supports nativeencryption?YesNoYesNoLabeled, noencryptionNative: rightsenforcedCannot be labeledGeneric .pfile:rights shown only
How the Information Protection client's file-type rules decide between labeling without encryption, native encryption and generic .pfile encryption.

Managing files with PowerShell

The client's PowerShell module turns File Explorer actions into scriptable cmdlets, which is how an administrator labels a whole folder tree, inventories what is already labeled, or removes protection under policy.

Settle a name collision first. Set-FileLabel, Get-FileStatus and Remove-FileLabel act on files and come from the client's module, whereas New-Label, Set-Label and Set-LabelPolicy are Security & Compliance PowerShell cmdlets that configure labels and label policies[1], for example their advanced settings. Within the client PowerShell module, use Set-FileLabel to apply labels to file content.

Applying a chosen label

Set-FileLabel sets a sensitivity label for one or more files[6], and it also encrypts them when the label applies encryption. Its -Path takes a local path, a network path or a SharePoint Server URL, with no wildcards and no WebDAV. Its -LabelId takes the label's ID (a GUID), which the portal doesn't display; get it with Get-Label | Format-Table -Property DisplayName, Name, Guid in Security & Compliance PowerShell, and when a label has sublabels, specify the sublabel's ID only. When the label encrypts, the Rights Management owner of the files is the user who ran the command[6] (an account that can always access the content, whatever its expiry date[7]), and -Owner specifies a different owner for the label or protection.

If the label policy requires justification for lowering a classification or removing a label, supply -JustificationMessage; without it, a file that triggers justification is skipped and keeps its current label[6], so a higher classification is never silently overwritten.

Label every unlabeled file in a share (Microsoft Learn example 1)

# Find files that have no label, then apply the label with this ID
Get-FileStatus -Path \\Finance\Projects\ |
    Where-Object {$_.IsLabeled -eq $False} |
    Set-FileLabel -LabelId d9f23ae3-4321-4321-4321-f515f824c57b

This listing pipes Get-FileStatus (described below) into Set-FileLabel; IsLabeled is the Get-FileStatus property that reports whether a file already has a label.

Letting the content choose the label

With -AutoLabel, Set-FileLabel runs in auto-labeling mode[6] and sets labels according to the conditions configured for automatic labeling; a file whose content matches no condition is skipped with no label applied. It doesn't overwrite an existing label unless you add -Force, and -PreserveFileDetails leaves the Date modified value of local or network files unchanged.

Inspecting files without changing them

Two inspection questions need two different tools:

  • What protection does this file already have? Get-FileStatus[8] returns whether the file is labeled, the label name and ID, how and when it was labeled (LabelingMethod, LabelDate), whether it is protected by Rights Management (IsRMSProtected) and with which template, and the Rights Management owner and issuer; custom permissions show as "Restricted Access" instead of a template name. It returns label information from your own tenant only, and password-protected files always report a protection status of False, so IsRMSProtected False does not prove a file opens without a password. For files stored in SharePoint Online, use the SharePoint Online Get-FileSensitivityLabelInfo cmdlet instead.
  • What sensitive data does this file contain? Run Set-FileLabel in its WhatIf parameter set[9] (a cmdlet's unique combination of parameters, one set per run). Its syntax for that set[6] is Set-FileLabel [-Path] <String[]> [-PreserveFileDetails] [-WhatIf] [-DiscoveryInfoTypes <String[]>]. In a PowerShell syntax diagram[10], square brackets mark an optional parameter, brackets around the name alone, as in [-Path], mean the name may be omitted when the values are presented in the correct order, and <String[]> takes one or more strings. A discovery run is the Set-FileLabel run with -WhatIf, which the reference lists as mandatory in the WhatIf parameter set[6] although its syntax brackets it, and it may add -DiscoveryInfoTypes. -WhatIf shows what would happen if the cmdlet runs and the cmdlet is not run, so no label or protection is applied; -DiscoveryInfoTypes names the SITs to discover, All or entity IDs, and the run returns the matched types.

Custom permissions for one file

When one file needs rights that no label provides, build an ad hoc protection policy object with New-CustomPermissions[11] (-Users, -Permissions for a permissions level such as Reviewer, and an optional -ExpirationDate) and pass it to Set-FileLabel -CustomPermissions, alone or together with -LabelId. Combined with a label, the custom permissions replace the label's configured protection settings[6] for that file only, so the shared label's recipient list stays unchanged for everyone else. After the expiration date the specified users lose access, but the owner and a super user can always access the file[11]; a super user holds Full Control of content your tenant encrypts, through an Azure Rights Management feature that is off by default[12].

Removing labels and protection

Remove-FileLabel[13] treats the label and the protection as separate things:

  • -RemoveLabel removes the label. If that label protected the file with a template, the protection is removed too; if the file was protected with custom permissions, only the label is removed.
  • -RemoveProtection removes protection and leaves any label in place. You must have sufficient usage rights or be a super user for your organization.
  • Use both switches to remove the label and custom protection together, adding -JustificationMessage when the policy requires a reason.

Removing protection from container files (.zip, .rar, .7z and .pst) is disabled by default and must first be enabled with Set-LabelPolicy.

In short: Set-FileLabel applies, Get-FileStatus reports existing protection, a discovery run reports content, and Remove-FileLabel separates label removal from protection removal.

Scanner prerequisites

The information protection scanner[14] runs as a service on Windows Server and discovers, classifies and protects files on UNC paths for network shares (SMB, and NFS in preview) and on SharePoint Server document libraries and folders. A production deployment rests on four prerequisites: the host, the configuration database, the service account, and the license.

The host

Production scanning needs a Windows Server computer[5] running a supported 64-bit version, with 4 core processors, 8 GB RAM and about 10 GB of free disk space on average for temporary files, because the scanner creates temporary files for each file it scans, four files per core. Server Core and Nano Server aren't supported, and any other Windows version the client supports is allowed only for testing or evaluation outside production. The host also needs the full Information Protection client, not the PowerShell-only installation[5].

The SQL Server configuration database

The scanner stores its configuration in a SQL Server instance, local or remote, with case-insensitive collation[5]. SQL Server 2016 is the minimum version for the Enterprise, Standard and Express editions, and Express is recommended for test environments only. Microsoft recommends hosting SQL Server and the scanner service on different machines except in small deployments, so size the database server separately; the documented sizing formula is 100 KB + <file count> *(1000 + 4* <average file name length>), and its worked example allocates 2 GB of disk for 1 million files with an average file name length of 250 bytes.

The service account

The scanner needs a service account to run the service and to authenticate to Microsoft Entra ID[5]; in the default configuration it is an Active Directory account synchronized to Microsoft Entra ID, and so also the scanner account, the account you specify in Set-Authentication's DelegatedUser parameter[5]. The two names part only when the Windows identity and the Microsoft Entra identity differ (see The delegated cloud identity below). The service account's rights grow with what the scanner will do:

Need Requirement
Run the service Log on as a service, granted automatically during installation
Install and configure Log on locally, which you can remove once scanning works
Discovery mode only Read on the repositories
Classify and protect on file shares or local files Read, Write and Modify
Classify and protect on SharePoint Server Full Control
Reprotect or remove protection on encrypted files Super user for the Azure Rights Management service, with the super user feature enabled
Discover all sites under a SharePoint URL Site Collector Auditor rights at farm level

An access-denied error on a share is therefore a repository-permission problem; the SQL db_owner role the account holds governs the configuration database, not the files.

The license

Licensing, a separate check, uses the plans named under generic encryption above. In the Azure Information Protection service description[3], scanner discovery of on-premises files matching any SIT and applying one label to all files in an on-premises repository are included in Azure Information Protection Premium P1 and P2; automated classification, labeling and protection of on-premises files by the scanner, like configuring conditions for automatic and recommended classification, is P2 only. Purview Information Protection for Office 365 includes none of these scanner features, and the AIP P1 standalone offer is no longer available to new customers as of January 2024. The scanner prerequisites also list a license for information protection for the service account[5].

The takeaway: a 64-bit Windows Server host with the full client, a case-insensitive SQL Server database, a service account with rights matched to the scanner's job, and a license, where P1 covers an inventory or a uniform repository label but content-driven labeling needs P2.

Installing the scanner

Installation follows a fixed order in Microsoft Learn[4]: configure the scanner settings, install the scanner, get a Microsoft Entra token for it, then configure it to apply classification and protection. The figure below adds the discovery run that sits between the last two steps.

The scanner cluster and content scan job

In the Microsoft Purview portal, you first create a scanner cluster[4], whose name identifies the scanner instance during installation, upgrades and other processes, and then a content scan job that defines the repositories to scan (designed in the next section).

Install-Scanner

Sign in to the server with an account that has local administrator rights and permission to write to the SQL Server master database[4], open PowerShell as an administrator, and run Install-Scanner -SqlServerInstance <name> -Cluster <cluster name>. At the prompt, enter the service account as an on-premises Windows identity in DOMAIN\username form, not a UPN, because the installer uses that format to resolve the SID, grant Log on as a service, configure the service's Run As account and grant SQL permissions.

The installing account normally holds the SQL Sysadmin role, which lets setup create the scanner configuration database and grant the service account the db_owner role[5]. Where Sysadmin can't be granted even temporarily, a Sysadmin creates the database beforehand (named AIPScannerUL_<cluster_name> when you specify your own cluster name), and db_owner is assigned to the service account and to the accounts that install and configure the scanner.

Scaling out with nodes

A scanner cluster can hold several nodes: you deploy multiple nodes by using the same cluster name and database[14] for Install-Scanner, for faster scan times and broader scope. Different cluster names on one SQL instance give each scanner its own configuration database, and the performance guidance says scanners that should run in parallel must all be installed with the same cluster name[4].

The delegated cloud identity

To run unattended, the scanner needs a Microsoft Entra token[4]: register an app, give it the Azure Rights Management Service application permissions Content.DelegatedReader and Content.DelegatedWriter and the Microsoft Information Protection Sync Service application permission UnifiedPolicy.Tenant.Read, grant admin consent, and then run Set-Authentication.

Acquiring the scanner's token (Microsoft Learn example, values replaced with placeholders)

$pscreds = Get-Credential CONTOSO\scanner   # the Windows account that runs the service
Set-Authentication -AppId "<app ID>" -AppSecret "<client secret>" -TenantId "<tenant ID>" -DelegatedUser scanner@contoso.com -OnBehalfOf $pscreds

-DelegatedUser names the scanner account, and the scanner applies the labels configured for that account[5], so publish the scanner's labels to the delegated user, not to whichever administrator ran setup. The Windows identity and the cloud identity can differ: when the service account can't be synchronized, use a local Windows or Active Directory account for the service and specify the Microsoft Entra user in DelegatedUser[5], adding OnBehalfOf when you run the command under any user other than the scanner account. The token is valid for one year, two years or never[4], matching the client secret's expiry, and you repeat the procedure when it expires.

In short: one cluster name groups the nodes, DOMAIN\username runs the service, and the delegated user decides which label policy the scanner receives.

1. Create a scanner clusterand a content scan job2. Install-Scanner with theSQL instance and cluster3. Register the app, then runSet-Authentication4. Discovery scan(Enforce Off, Schedule Manual)5. Enforce On, rescan all files,then Schedule Always
Information protection scanner deployment order, following Microsoft Learn's configure-and-install steps with the discovery cycle before enforcement.

Designing the content scan job

A content scan job holds the settings that decide what the scanner touches and how; the repositories you add belong to the job and inherit its settings unless you override them.

Repositories

Add repositories as explicit paths[4]: a local path such as C:\Folder, a UNC path such as \\Server\Folder, or a SharePoint Server library or folder URL. Wildcards, WebDAV locations and OneDrive locations are not supported as repositories. Each repository's remaining settings stay at Content scan job default, which means the repository inherits the content scan job's settings, until you override them. Giving only the SharePoint server's root URL discovers all sites and subsites below it, which requires Site Collector Auditor rights at farm level[5], one of the service account rights listed under Scanner prerequisites above. Files already saved in SharePoint Online or OneDrive are labeled by a service-side auto-labeling policy[15] instead, a feature covered in Implement and manage sensitivity labels.

Schedule, enforcement and relabeling

The initial content scan job[4] keeps Schedule at Manual, sets Enforce sensitivity labeling policy to Off, keeps Label files based on content at On, keeps Default label at Policy default, and keeps Relabel files at its default of Off; those defaults make the scanner run once, in reporting-only mode[4]. Moving to production means changing Schedule to Always and Enforce to On, and the two settings do different jobs:

Changing Schedule alone therefore produces continuous reporting with no labeling. Because the scanner doesn't discover and label in real time but systematically crawls the data stores[14], crawl frequency is a scheduling decision, not an event-driven one. Leave Relabel files Off unless the rollout must replace existing labels rather than only label unlabeled files. With it On, Allow label downgrade set to Off keeps the scanner from replacing a label with a lower-priority one, and label priority is set by the order of the labels list in the Microsoft Purview portal[16]. Sublabels are the exception for this check: sublabels under the same parent share the parent label's priority, so switching between them isn't a downgrade and Allow label downgrade = Off won't block relabeling to a lower priority sublabel[4], even though the list orders one below the other.

What the job looks for

File details and ownership

By default the job preserves "Date modified", "Last modified" and "Modified by", and its Default owner setting is Scanner Account[4], which Microsoft Learn's Set-ScannerContentScan example writes as -DefaultOwner <account running the scanner>[4], that is, the service account. Preserving Modified by keeps business metadata intact but says nothing about who owns the protection: that is the separate Default owner setting, so set it deliberately when the service account should not be the default owner of content the scanner protects.

The takeaway: pilot with Manual and Enforce Off, choose Policy only or All for the discovery breadth you need, then turn Enforce On and Schedule Always as two separate decisions.

How the scanner decides what it can label

Every file the scanner reaches goes through the same three-step scanning process[14], which the figure below traces together with the final check on the file type:

  1. Include or exclude. The scanner skips files excluded from classification and protection, such as executable and system files, and applies any file lists you defined with File types to scan. By default it also excludes .msg, .rtf and .rar on top of the client's excluded types[1].
  2. Inspect and label. Supported files are inspected with the Windows IFilters installed on the computer[14], the same filters Windows Search uses for indexing, and labeled using your labels' conditions; in discovery mode they are only reported.
  3. Label files that can't be inspected. For file types that can't be inspected, the scanner applies the default label from its label policy or the default label configured for the scanner.

Inspection does not guarantee labeling

The scanner can't label a file[14] when the label does not encrypt and the file type doesn't support labeling without encryption, or when the label applies encryption but the scanner doesn't protect that file type. By default it encrypts only Office file types, and PDF files when they're protected with the ISO standard for PDF encryption. So a .txt file can be inspected, but it can't receive a label that doesn't apply encryption; it can receive a label that encrypts once .txt is included in the types the scanner protects. Adding .txt to the files the job scans fixes inspection, not label support.

To protect more types, set the PFileSupportedExtensions advanced setting[4] on the label policy that applies to the account downloading labels for the scanner, which for an internet-connected scanner is the scanner account set with -DelegatedUser.

Protect .xml and .tiff in addition to Office and PDF files (Microsoft Learn example 2)

# "Scanner" is the name of the label policy published to the scanner's delegated user
Set-LabelPolicy -Identity Scanner -AdvancedSettings @{PFileSupportedExtensions=ConvertTo-Json(".xml", ".tiff")}

Setting the value to "*" instead makes the scanner protect all file types, as the client does.

ZIP archives

On Windows Server, the scanner needs the Microsoft Office IFilter installed to scan .zip files for SITs[1], and labeling and encrypting a matching archive also needs the .zip extension specified in PFileSupportedExtensions. The archive then gets generic encryption and a new name; Microsoft's example turns accounts.zip into accounts.zip.pfile.

The takeaway: whether the scanner can read a file and whether it can label that file are separate checks, and each has its own fix.

1. Skip excluded files(system types, job file lists)2. Inspect with IFilters,label by conditions3. Default label for filesthat cannot be inspectedLabel applied only if thefile type supports it
The information protection scanner's three-step scanning process from Microsoft Learn, ending with the file-type check that decides whether a label lands.

Operating the scanner

Once the content scan job exists, daily operation means starting cycles, forcing full rescans when needed, and reading status and reports.

Starting and stopping cycles

Start a cycle with Scan now in the portal or with Start-Scan[18], which starts a one-time cycle only when the scanner service is already running and the schedule is set to Manual; with the schedule set to Always, Start-Scan is ignored. That is consistent with the Always setting described in the content scan job section: the scanner then starts each new cycle by itself, so there is nothing for Start-Scan to start. Stop a running cycle with Stop scan in the portal or the Stop-Scan cmdlet[17].

Full rescans

The first cycle inspects every file, and subsequent cycles inspect only new or modified files[17]. To force a full pass, run Start-Scan -Reset[18], which resets the scanner cache so the scanner scans all files even if they were scanned before and the policy hasn't changed, or select Rescan all files in the portal; after a full scan completes, the scan type returns to incremental.

The Start-Scan reference describes a policy change as triggering a full scan, and the scanner management guide reconciles that: the automatic full rescan on changed settings belongs to earlier scanner versions, and version 2.8.85.0 or later skips it[17]. On current versions, after switching Enforce from Off to On, run a full rescan yourself so the labels apply across content that was already scanned.

Status

Get-ScanStatus[19] reports the cluster's status:

Status Meaning
Offline The service isn't started
Idle The service is running but not currently scanning
Scanning The service is running and is scanning files
Error The service is running but an error prevents it from scanning, for example it can't access the configuration database

Use the NodesInfo variable for per-node detail, or -Verbose for file counts and per-repository status (Skipped, Pending, Scanning, Finished). A started Windows service is therefore not proof that files are being processed: Error is exactly a running service that cannot scan.

Reports

After a cycle, the scanner writes reports to %localappdata%\Microsoft\MSIP\Scanner\Reports[17]: .txt summary files (time taken, files scanned, files matching information types) and .csv files with per-file detail, up to 60 reports per scanning cycle. Scanners send data to Microsoft Purview Information Protection every five minutes, but the admin portal displays the last scan only, so results of earlier scans come from these local reports. The report folder location or name can't be changed (a directory junction can redirect it), and the documented junction example points at the service account's profile. Report detail is set with the ReportLevel parameter of Set-ScannerConfiguration.

The takeaway: Start-Scan and Rescan all files control coverage, Get-ScanStatus shows health right now, and the local reports keep the history the portal drops.

Turning on Message Encryption

Microsoft Purview Message Encryption lets your organization send and receive encrypted email with people inside and outside the organization[20], including Outlook.com, Yahoo! and Gmail users; it replaces Office 365 Message Encryption (OME), which was deprecated. It is an online service built on the Azure Rights Management service[20], the same encryption service that protects labeled files.

The one prerequisite

The only prerequisite is that the Azure Rights Management service is activated in your tenant[21]; Microsoft 365 then activates message encryption automatically, and the service itself is activated automatically for most eligible plans. A tenant that uses Active Directory Rights Management Services (AD RMS) with Exchange Online must migrate to the Azure Rights Management service first[21], because Message Encryption is not compatible with AD RMS.

Verifying in Exchange Online PowerShell

The documented verification[21] uses Exchange Online's Information Rights Management (IRM) cmdlets[22] to confirm the one prerequisite took effect:

  1. Run Get-IRMConfiguration and confirm AzureRMSLicensingEnabled is $True, meaning Exchange Online can connect directly to Azure Rights Management, which enables Message Encryption[22]; if it isn't, set it with Set-IRMConfiguration.
  2. Run Test-IRMConfiguration -Sender <address> -Recipient <address> with any users' addresses in your tenant; a passing result shows RMS templates acquired, encryption verified, decryption verified and IRM verified.
  3. If the test fails with Failed to acquire RMS templates, set LicensingLocation from Get-AipServiceConfiguration and InternalLicensingEnabled with Set-IRMConfiguration, then rerun the test.

Existing mail flow rules that use the previous OME version must be updated, or your users keep receiving encrypted mail in the previous HTML attachment format[21]. External recipients need no Information Protection client; they get native Outlook or the encrypted message portal[20].

The takeaway: activate Azure Rights Management, verify it with the IRM cmdlets, and update previous-version OME rules.

Rights options for encrypted email

Every encrypted message carries one rights choice: Encrypt-Only, Do Not Forward or a rights management template. The three differ in who may read the message and in what happens to its attachments.

Encrypt-Only, Do Not Forward and templates

Do Not Forward and a template that withholds the Forward right both stop forwarding, so the real difference is who else can read. With the template, a recipient could drag the message to a shared location where anyone in the template's group can open it[7]; with Do Not Forward, only the original recipients and the email owner can view it. Microsoft's rule of thumb: use Do Not Forward when only the sender's chosen recipients should see the information, and a template when rights belong to a group the administrator specifies independently of whom the sender addresses.

Attachments

By default, when a message is encrypted, unencrypted Office documents attached to it inherit the same encryption settings[23]. For Encrypt-Only, one Set-IRMConfiguration setting can change this inheritance[23] (see Attachment downloads in a web browser below). The message's sensitivity label is not inherited by the attachment, although a label could be applied automatically when a user in the same tenant opens the document. A document that was already encrypted before it was attached always keeps its original encryption[23], so changing the message's recipients gives no one access to it.

The inherited rights follow the option. For Do Not Forward, attached documents get Edit Content, Edit; Save; View, Open, Read; and Allow Macros[7]; for Encrypt-Only, recipients can save, edit, copy and print the document from Office apps, but only into file formats that support Rights Management encryption, so it can't be saved without the original encryption. When an attachment needs a different audience or different rights from the message, encrypt the file before attaching it.

PDF attachments are encrypted automatically only after you enable it with Set-IRMConfiguration -EnablePdfEncryption $True[7]; the PDF then inherits the message's permissions, and recipients read it in Microsoft Edge or in the encrypted message portal.

The takeaway: pick the option by sharing intent, and remember that attachments inherit encryption, not the label, and never override encryption a file already had.

Mail flow rules for message encryption

Mail flow rules (also known as transport rules) let an Exchange Online administrator encrypt outgoing email and remove encryption from messages coming from inside the organization or from replies to encrypted messages it sent[24], using the Exchange admin center or Exchange Online PowerShell.

Encrypting

An encryption rule in the Exchange admin center starts with The sender is located > Inside the organization[24], adds conditions such as a specific recipient or The recipient is external/internal > Outside the organization, and takes the action Modify the message security > Apply Office 365 Message Encryption and rights protection. Despite the old name, this action enables encryption using Microsoft Purview Message Encryption[24]; the deprecated version is the separate action Apply the previous version of OME. It takes an RMS template from the list of default templates and options plus your custom templates[24], that is, the previous section's rights options, with Encrypt-Only listed as Encrypt. Message Encryption also encrypts replies from recipients of encrypted email[20].

Two scope limits decide whether a rule can ever take effect:

Removing encryption

For an authorized workflow that needs decrypted mail, create a rule with The sender is located > Inside the organization (for mail going out) or The recipient is located > Inside the organization (for replies coming in), and the action Remove Office 365 Message Encryption and rights protection applied by the organization[24]. Add the optional, separate action Remove attachment rights protection applied by the organization when the attachments must be unprotected too; message-level removal alone leaves protected attachments protected. Both actions remove only protection that your organization applied, as their names state, so they are not a way to decrypt content protected by another organization.

The takeaway: rules act on mail your organization sends or receives replies to, only on mail routed through Exchange Online, and they treat message and attachment protection as separate actions.

What external recipients experience

How a recipient opens a protected message depends on who they are and which client they use, and three administrator settings tune that experience.

Native Outlook or the encrypted message portal

Microsoft 365 users who read mail in Outlook clients get a native reading experience[20], even when they aren't in the sender's organization; supported clients include Outlook desktop, Outlook for Mac, Outlook mobile and Outlook on the web. Recipients on Gmail or Yahoo accounts get a wrapper mail that directs them to the encrypted message portal, and users of other email clients also use the portal. A mail flow rule that applies a custom branding template can force all external recipients into the portal[25]; a branding template is an OME configuration[26] that sets the wrapper and portal presentation, not a rights management template (see Advanced Message Encryption controls below). Nobody has to join your tenant to read the message.

Portal sign-in options

A recipient with a social ID (a Google, Yahoo or Microsoft account) can sign in to the encrypted message portal with it, and Set-OMEConfiguration -SocialIdSignIn $false turns that off[25]. A recipient who doesn't use Outlook, whatever the account, receives a limited-time web-view link that includes a one-time passcode, controlled by Set-OMEConfiguration -OTPEnabled. Both settings belong to a branding template (the -Identity you pass); despite their OME names, these cmdlets brand Microsoft Purview Message Encryption messages[26], so with Advanced Message Encryption each custom branding template can enable or disable one-time passcodes and social IDs separately[26].

The iOS mail app

The iOS mail app can't decrypt messages protected with message encryption[25], and service-side decryption isn't enabled by default, so its users see a message that they don't have the rights to view. Running Set-ActiveSyncOrganizationSettings -AllowRMSSupportForUnenlightenedApps $true makes the service send a decrypted copy that the device stores. That copy keeps the usage-rights information, but the app doesn't apply client-side usage rights: the user can copy or print the message even without those rights. Actions that need the Microsoft 365 mail server, such as forwarding, are still refused without the right, although a user can work around Do Not Forward by forwarding from a different account in the app. Attachments to encrypted mail can't be viewed in the iOS mail app either way, and an OWA or ActiveSync mailbox policy with -IRMEnabled set to False overrides the organization setting for that mailbox.

Attachment downloads in a web browser

By default, attachments to encrypted mail stay encrypted when users download them from a web browser[25]. Setting Set-IRMConfiguration -DecryptAttachmentForEncryptOnly $true makes the service send a decrypted copy of the file while the message itself stays encrypted; as with the iOS mail app, the browser doesn't apply the retained usage rights, but server actions such as forwarding are still checked. The Encrypt-Only guidance[7] frames this setting as the way to change Encrypt-Only's attachment inheritance when you don't need to keep the document's encryption after authentication: when recipients open the message, the document isn't encrypted. That is a far narrower change than sending the whole message unencrypted.

The takeaway: identity, client and applied branding decide native or portal delivery, the branding template's settings decide how portal users sign in, and the two service-side decryption settings trade local rights enforcement for readability.

Advanced Message Encryption controls

Microsoft Purview Advanced Message Encryption adds more flexible control over external recipients' access to encrypted email[27]: multiple branding templates, expiration, revocation, and encrypted message portal access logs. Expiration, revocation and the access logs work only for email sent to external recipients who read it through the portal[27], and a mail flow rule that applies a custom branding template forces recipients to receive a wrapper mail that directs them to the encrypted message portal[25], as the figure below shows.

Branding templates

As Native Outlook or the encrypted message portal above notes, a branding template is not a rights management template: the latter decides who may read the message and with which rights, while a branding template[26] sets the wrapper and portal presentation, expiry and sign-in options. Every tenant has a default branding template, which you inspect and change with Get-OMEConfiguration and Set-OMEConfiguration[26]: introductory text, disclaimer text, the privacy statement URL, portal text, the logo and the background color. You can modify the default template but not remove it; returning it to its original values means setting the text values to "" and image values such as the logo to $null. With Advanced Message Encryption you can also create custom branding templates with New-OMEConfiguration and delete them with Remove-OMEConfiguration[26], for example one per department, product or region. A different portal logo per department is therefore a branding-template job, not a reason to create more sensitivity labels.

A branding template does nothing until a rule applies it. Create a mail flow rule with the action Modify the message security > Apply custom branding to OME messages[26]; the message must be encrypted, and the encryption rule should have a higher priority than the branding rule so that it is processed first.

Expiration

Create or update a custom template with -ExternalMailExpiryInDays, which accepts any value from 1 to 730 days[28], and apply it with a mail flow rule. The recipient sees the expiration date in the wrapper email, and trying to open an expired message shows an error in the portal. You can set expiration only for email to external recipients, and only when you use custom branding. In PowerShell, a rule can apply the rights option and the branding template in one step through New-TransportRule with -ApplyRightsProtectionTemplate and -ApplyRightsProtectionCustomizationTemplate[25]:

Expiring external mail through a custom template (Microsoft Learn commands; the rule and template names are illustrative)

# Custom branding template whose portal access expires after 7 days
New-OMEConfiguration -Identity "Expire in 7 days" -ExternalMailExpiryInDays 7
# Rule that encrypts organization mail and forces the branded portal wrapper
New-TransportRule -Name "Expiring external mail" -FromScope "InOrganization" -ApplyRightsProtectionTemplate "Encrypt" -ApplyRightsProtectionCustomizationTemplate "Expire in 7 days"

Revocation

Admins and senders can revoke an encrypted message only if the recipient received a link-based, branded encrypted email[29]. Branded here means a custom branding template was applied: Advanced Message Encryption revokes only messages that users receive through the portal, "in other words, email that has a custom branding template applied"[27], and a custom branding template is what guarantees that tracking and revocation are available[29], so do not count on revoking a Gmail or Yahoo recipient's link-based message unless one was applied. The experience depends on the recipient identity type[29]: Microsoft 365 and Microsoft account recipients get an inline experience in supported Outlook clients, which can't be revoked, and Gmail, Yahoo and other types get the link-based experience. A custom branding template can override that split and force all external recipients to use the encrypted message portal[25], Microsoft account holders included. A sender revokes from the Sent folder of Outlook on the web with Remove external access, for a message sent to a single recipient on a social account such as Gmail or Yahoo. An administrator follows three steps:

  1. Get the Message ID, for example from Message Trace or the Message encryption report in the Microsoft Purview portal.
  2. Run Get-OMEMessageStatus -MessageId "<message id>" and confirm that IsRevocable is True.
  3. Run Set-OMEMessageRevocation -Revoke $true -MessageId "<message id>", then confirm Revoked: True with Get-OMEMessageStatus.

After revocation, the recipient gets the error "The message has been revoked by the sender" when accessing the message through the encrypted message portal. The check happens in the portal, which is why only portal-delivered messages are revocable.

Portal access logs

Turn on the access log with Set-IrmConfiguration -EnablePortalTrackingLogs $true[30], and apply a custom branding template to protected mail sent to external recipients so the portal experience is enforced. The log records external user sign-in time and authentication method, reading messages or attachments, attachment downloads, and replies and forwards; search it in Microsoft Purview Audit under encrypted message portal activities. These portal events, not delivery status, are the evidence that an external recipient opened the content.

The takeaway: expiration and revocation depend on custom branding forcing portal delivery to external recipients; without portal delivery those access controls cannot apply.

1. New-OMEConfiguration(optional expiry in days)2. Mail flow rule: encryptand apply the template3. External recipient getsa wrapper with a portal link4. Portal enforces expiry andrevocation, and logs access
Why Advanced Message Encryption controls need custom branding: the template forces external recipients into the encrypted message portal, where expiry, revocation and logging happen.

Email rights options: Encrypt-Only vs Do Not Forward vs rights management template

Decision pointEncrypt-OnlyDo Not ForwardRights management template
Who is authorizedAuthenticated recipients, who may also forward itOnly the recipients the sender chose (a dynamic list)Users the administrator listed in advance (a static list)
Forward, print, copyAllowed; recipients get every right except Save As, Export and Full ControlBlockedWhatever rights the template grants
Unencrypted Office attachmentsInherit the encryption; recipients can still save, edit, copy and print themInherit restricted rights: Edit Content, Edit; Save; View, Open, Read; Allow MacrosInherit the same encryption settings as the message
Pick it whenMail must stay encrypted but recipients still share and reuse itRecipients must not share the message beyond the original recipientsA fixed group must have access regardless of whom the sender addresses

Decision tree

Is the content an emailin Exchange Online?NoYesUnattended bulkon-prem labeling?Expiry, revocationor portal audit?YesNoYesNoInformationprotection scannerAdvanced MessageEncryptionScript labels formany files?Message Encryption(rights option)YesNoPowerShell module(Set-FileLabel)File Explorerfile labeler

Sharp facts the exam loves — give these one last read before exam day.

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

References

  1. https://learn.microsoft.com/en-us/purview/information-protection-client
  2. https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/sc-401
  3. https://learn.microsoft.com/en-us/office365/servicedescriptions/azure-information-protection
  4. https://learn.microsoft.com/en-us/purview/deploy-scanner-configure-install
  5. https://learn.microsoft.com/en-us/purview/deploy-scanner-prereqs
  6. https://learn.microsoft.com/en-us/powershell/module/purviewinformationprotection/set-filelabel
  7. https://learn.microsoft.com/en-us/purview/rights-management-usage-rights
  8. https://learn.microsoft.com/en-us/powershell/module/purviewinformationprotection/get-filestatus
  9. https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_parameter_sets
  10. https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_command_syntax
  11. https://learn.microsoft.com/en-us/powershell/module/purviewinformationprotection/new-custompermissions
  12. https://learn.microsoft.com/en-us/purview/encryption-super-users
  13. https://learn.microsoft.com/en-us/powershell/module/purviewinformationprotection/remove-filelabel
  14. https://learn.microsoft.com/en-us/purview/deploy-scanner
  15. https://learn.microsoft.com/en-us/purview/apply-sensitivity-label-automatically
  16. https://learn.microsoft.com/en-us/purview/sensitivity-labels
  17. https://learn.microsoft.com/en-us/purview/deploy-scanner-manage
  18. https://learn.microsoft.com/en-us/powershell/module/purviewinformationprotection/start-scan
  19. https://learn.microsoft.com/en-us/powershell/module/purviewinformationprotection/get-scanstatus
  20. https://learn.microsoft.com/en-us/purview/ome
  21. https://learn.microsoft.com/en-us/purview/set-up-new-message-encryption-capabilities
  22. https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/set-irmconfiguration
  23. https://learn.microsoft.com/en-us/purview/encryption-sensitivity-labels
  24. https://learn.microsoft.com/en-us/purview/define-mail-flow-rules-to-encrypt-email
  25. https://learn.microsoft.com/en-us/purview/manage-office-365-message-encryption
  26. https://learn.microsoft.com/en-us/purview/add-your-organization-brand-to-encrypted-messages
  27. https://learn.microsoft.com/en-us/purview/ome-advanced-message-encryption
  28. https://learn.microsoft.com/en-us/purview/ome-advanced-expiration
  29. https://learn.microsoft.com/en-us/purview/revoke-ome-encrypted-mail
  30. https://learn.microsoft.com/en-us/purview/audit-log-encrypted-messages