Additional requirements for installing the unified labeling client on enterprise networks
Applies to: Azure Information Protection, Windows 10, Windows 8.1, Windows 8, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
If you have Windows 7 or Office 2010, see AIP and legacy Windows and Office versions.
Relevant for: Azure Information Protection unified labeling client only.
Before you install the Azure Information Protection unified labeling client on your enterprise network, check that computers have the required operating system versions and applications for Azure Information Protection: Requirements for Azure Information Protection.
Then, verify that you have the additional items required for installing the Azure Information Protection unified labeling client.
Not all of these requirements are verified by the installation software.
Microsoft .NET Framework requirements
The full installation of the Azure Information Protection unified labeling client by default, requires a minimum version of Microsoft .NET Framework 4.6.2.
If this framework is missing, the setup wizard from the executable installer tries to download and install this prerequisite. When this prerequisite is installed as part of the client installation, the computer must be restarted.
If you are installing the Azure Information Protection Viewer on its own, you must have a minimum version of Microsoft .NET Framework 4.5.2.
If a minimum version of Microsoft .NET Framework 4.5.2 is missing for the Viewer installation, the installation software does not download or install it.
Disable Exploit protection (.NET 2 or 3 only)
The AIP client is not supported on machines with .NET 2 or 3 that have Exploit protection enabled.
In such cases, we recommend that you upgrade your .NET version.
If you must keep your .NET version 2 or 3, make sure to disable Exploit protection before installing the AIP client.
Windows PowerShell minimum requirements
The PowerShell module for the client requires a minimum version of Windows PowerShell 4.0.
If you're working on an older operating system, you may need to insall PowerShell manually. For more information, see How to Install Windows PowerShell 4.0.
The installer does not check or install this prerequisite for you.
To confirm the version of Windows PowerShell that you are running, type
$PSVersionTable in a PowerShell session.
Screen resolution requirements
Client machines with resolutions of 800x600 and lower can't fully display the Classify and protect - Azure Information Protection dialog box when you right-click a file or folder in the File Explorer.
To install the Azure Information Protection unified labeling client, you must have local administrative permissions on the client computer.
Windows 10 requirements
Computers running Office 2010 require Microsoft Online Services Sign-in Assistant version 7.250.4303.0, which is included with the client installation.
If you have a later version of the Sign-in Assistant, uninstall it before you install the Azure Information Protection unified labeling client.
For example, check the version and uninstall the Sign-in Assistant by using Control Panel > Program and Features > Uninstall or change a program.
Office 2010 extended support ended on October 13, 2020. For more information, see AIP and legacy Windows and Office versions.
For Windows 10 version 1809 only, operation system builds older than 17763.348, install March 1, 2019—KB4482887 (OS Build 17763.348) to ensure the Information Protection bar displays correctly in Office applications. This update is not needed if you have Office 365 1902 or later.
Configure your group policy to prevent disabling AIP
For Office versions 2013 and later, we recommend that you configure your group policy to ensure that the Microsoft Azure Information Protection add-in for Office applications is always enabled. Without this add-in, users won't be able to label their documents or emails in Office applications.
For Word, Excel, PowerPoint, and Outlook, use the group policy setting list of managed add-ins documented in No Add-ins loaded due to group policy settings for Office 2013 and Office 2016 programs.
Specify the following programmatic identifiers (ProgID) for AIP, and set the option to 1: The add-in is always enabled.
For more information, see: