Which Devices Support the Purview Information Protection Client?
Implement and manage sensitivity labels in Microsoft Purview
Implement information protection for Windows, file shares, and Exchange
Answer
Install the Microsoft Purview Information Protection client on Device1 and Device2 only; users apply labels to images and documents through File Explorer by selecting Classify and protect.
HOTSPOT
You have a Microsoft 365 5 subscription that contains the devices shown in the following table.
You publish Microsoft Purview Information Protection sensitivity labels.
You plan to deploy the information protection client to the devices. The solution must ensure that the labels can be applied to sensitive images and documents.
On which devices can you install the information protection client, and what should users use to apply labels? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Community Insight
The exam tests the client's OS/architecture support matrix and the end-user labeling entry point, with the trap being that x86 Windows 10 is unsupported while ARM64 supports the viewer and file labeler.
This SC-401 hotspot asks which devices can host the Microsoft Purview Information Protection client and how users label sensitive images and documents. The correct deployment is Device1 and Device2, with labels applied through File Explorer's Classify and protect option.
Learners often assume every Windows device in the table is supported, or that ARM64 is excluded because the scanner is unsupported; the question only needs labeling, so ARM64 remains valid while x86 does not.
Community Discussion (15 comments)
kollyp2000
👍 2
Devices: Device1 and Device2 only Use: File Explorer Devices: the chipset is the trap Learn’s supported operating systems for the Purview Information Protection client: “Windows 11, including Windows 11 Enterprise multi-session” “Windows 10 (x64)” Windows Server 2019 and 2016 It also adds: “ARM64 is supported for the viewer and file labeler, but isn’t supported for the scanner or PowerShell.” Source: Extend sensitivity labeling on Windows: Requirements Device OS / chipset Supported? Device1 Windows 11 x64 Yes Device2 Windows 11 ARM64 Yes. The file labeler works on ARM64, and that’s the component this question needs Device3 Windows 10 x86 No. Windows 10 is supported as x64 only
646e337
👍 4
Device1 and Device2 are the only ones that can support the client. The client is not supported x86 builds, so Device3 is not supported. ARM64 architecture supports the client being installed and labeling files, but does not support the scanner (which is not needed in this question). So Device2 is supported for the client. The client provides File Explorer integration, so users will use the File Explorer to apply labels to files.
CuDeBila
👍 2
Device 1 & 2 | File explorer https://learn.microsoft.com/en-us/purview/information-protection-client?tabs=devices%2Cinstall-client-exe%2Cclassification-file-types%2Cexcluded-folders#requirements-for-deploying-the-information-protection-client
B73
👍 3
Device 1 only: The following operating systems support the Microsoft Purview Information Protection client: Windows 11, including Windows 11 Enterprise multi-session Windows 10 (x64) (Handwriting isn't supported in the Windows 10 RS4 build and later) Windows Server 2019 Windows Server 2016 ARM64 is supported for the viewer and file labeler, but isn't supported for the scanner or PowerShell. File Explorer: The Information Protection client extends labeling to many file types, including images and other files. Users apply labels through File Explorer (right-click → classify and protect). This is specifically why the client is installed: to allow labeling of files that are not supported by Office apps, such as images.
rvln7
👍 4
The following operating systems support the Microsoft Purview Information Protection client: Windows 11, including Windows 11 Enterprise multi-session Windows 10 (x64) (Handwriting isn't supported in the Windows 10 RS4 build and later) Windows Server 2019 Windows Server 2016 ARM64 is supported for the viewer and file labeler, but isn't supported for the scanner or PowerShell. https://learn.microsoft.com/en-us/purview/information-protection-client?tabs=devices%2Cinstall-client-exe%2Cclassification-file-types%2Cexcluded-folders#requirements-for-deploying-the-information-protection-client
MultiCloudIronMan
👍 1
Device Compatibility: Device1 (Windows 11, x64) and Device3 (Windows 10, x86) support the Microsoft Information Protection (MIP) client, which enables labeling of documents and images. Device2 (Windows 11, ARM64) is not supported by the classic MIP client. ARM64 support is limited and may require alternative solutions like built-in labeling in Office apps. Label Application Method: The Microsoft Purview portal allows users to manually apply sensitivity labels to documents and images, especially when using the unified labeling platform. Other options like File Explorer or Microsoft Word are limited to file types and may not support image labeling directly.
novaCapta
👍 4
ARM64 is supported for the viewer and file labeler. https://learn.microsoft.com/en-us/purview/information-protection-client?tabs=devices%2Cinstall-client-exe%2Cclassification-file-types%2Cexcluded-folders#requirements-for-deploying-the-information-protection-client
Eltooth
👍 3
Device 1 & 3 File Explorer
Blabla532
👍 3
x86 is not supported by Purview client. Device 1 and 2
gabbinu
👍 7
Given answers are correct. The Purview Information Protection (AIP/MIP) client installs only on Windows x86/x64 (not ARM64), so it supports Win11 x64 and Win10 x86, but not Win11 ARM64. To label images and non-Office files, users apply the label via the client’s File Explorer right-click (“Classify and protect”).
Jideakin
👍 2
No, the answer is wrong. ARM64 is supported for labeler, just not for scanner. https://learn.microsoft.com/en-us/purview/information-protection-client?tabs=devices%2Cinstall-client-exe%2Cclassification-file-types%2Cexcluded-folders#requirements-for-deploying-the-information-protection-client
Gtc_
👍 4
Device 1 and file explorer
Gtc_
👍 1
Device 1 & 3, my mistake in typing this.
Gtc_
👍 1
https://learn.microsoft.com/en-us/purview/information-protection-client?tabs=devices%2Cinstall-client-exe%2Cclassification-file-types%2Cexcluded-folders#requirements-for-deploying-the-information-protection-client
NeerajSap
👍 1
This question is about the Microsoft Purview Information Protection client (Unified Labeling client). The client is supported on Windows 10 and Windows 11, but not on ARM64 devices. From the table: Device1 = Windows 11, x64 ✅ Supported Device2 = Windows 11, ARM64 ❌ Not supported Device3 = Windows 10, x86 ✅ Supported To apply labels to files and images, users can use File Explorer integration provided by the Information Protection client (right-click labeling).
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Microsoft Purview Information Protection client supports Windows 11 including multi-session, Windows 10 x64, Windows Server 2019, and Windows Server 2016; ARM64 supports the viewer and file labeler but not the scanner or PowerShell. Device1 is Windows 11 x64 and Device2 is Windows 11 ARM64, so both can install the client for labeling. Device3 is Windows 10 x86, which is not in the supported OS list because Microsoft lists Windows 10 x64 only. The requirement is to apply labels to images and documents, which is exactly the file labeler and File Explorer integration. Users right-click in File Explorer and choose Classify and protect to apply a sensitivity label, and the scanner is not needed, so the ARM64 limitation does not disqualify Device2.Why Other Candidate Answers Are Wrong
"Device1 only" is tempting because ARM64 has scanner and PowerShell limitations, but the question does not require the scanner; ARM64 viewer and file labeler support is sufficient. "Device1 and Device3" fails because Windows 10 x86 is not supported by the client. "Device2 and Device3" fails for the same x86 reason and also ignores the clearly supported Device1. Choosing Office apps or PowerShell as the user-facing labeling method is wrong for sensitive images and non-Office documents; the client provides the File Explorer entry point for those file types.Community Comment Notes
Community answers disagree, and gabbinu's popular comment claims ARM64 is excluded and Windows 10 x86 is supported, which conflicts with Microsoft's current requirements page. rvln7 and novaCapta cite the official support details, with novaCapta noting "ARM64 is supported for the viewer and file labeler." kollyp2000 and B73 land on Device1 and Device2, and kollyp2000 identifies the chipset as "the trap." Eltooth's Device1 and Device3 selection illustrates the common x86 error, so the documented OS list should override the vote count.Official Reference
Exam Strategy
Read the device table by both OS version and processor architecture before choosing client installation targets. Separate the labeling requirement from scanner and PowerShell features, because ARM64 supports the viewer and file labeler even though it lacks scanner support. For the labeling-method dropdown, prefer the end-user File Explorer integration over administrative tools.
Frequently Asked Questions
Which Windows architectures support the Microsoft Purview Information Protection client for labeling images?
Windows 11 x64 and ARM64 are supported for the viewer and file labeler; Windows 10 x86 is not listed, and ARM64 does not support the scanner or PowerShell.
Do users need the AIP scanner to label sensitive images on a device with the Purview client?
No. The scanner is a separate discovery tool; on the device, users label files and images through File Explorer's Classify and protect menu.