Azure Information Protection client: Version release history and support policy

Applies to: Active Directory Rights Management Services, Azure Information Protection, Windows 10, Windows 8.1, Windows 8, Windows 7 with SP1, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2

The Azure Information Protection team regularly updates the Azure Information Protection client for fixes and new functionality.

You can download the latest GA release version and the current preview version from the Microsoft Download Center. These versions are also included in the Microsoft Update Catalog (category: Azure Information Protection), so that you can deploy the client by using WSUS or Configuration Manager, or other software deployment mechanisms that use Microsoft Update.

Servicing information and timelines

Each general availability (GA) version of the Azure Information Protection client is supported for up to six months after the release of the subsequent GA version. Unsupported versions of the client are not included on this page. Fixes and new functionality are always applied to the latest GA version and will not be applied to older GA versions.

Preview versions should not be deployed for end users on production networks. Instead, use the latest preview version to see and try new functionality or fixes that are coming in the next GA version. Preview versions that are not current are not supported.

Release history

Use the following information to see what’s new or changed for a supported release of the Azure Information Protection client for Windows. The most current release is listed first.


Minor fixes are not listed so if you experience a problem with the Azure Information Protection client, we recommend that you check whether it is fixed with the latest GA release. If the problem remains, check the current preview version.

For technical support, see the Support options and community resources information. We also invite you to engage with the Azure Information Protection team, on their Yammer site.

Versions later than

If you have a version of the client that is later than, it is a preview build for testing and evaluation purposes.

Released: 05/21/2018

The current preview version is and has the following changes since the current GA version of the client.

New features:

  • For the Azure Information Protection scanner:

    • You can specify a file types list to include or exclude from scanning. To specify this list, use Set-AIPScannerScannedFileTypes. After you have specified your file types list, you can add a new file type to the list by using Add-AIPScannerScannedFileType, and remove a file type from the list by using Remove-AIPScannerScannedFileType.

    • You can label files without inspecting the contents by applying a default label. Use the Set-AIPScannerRepository cmdlet, and set the MatchPolicy parameter to Off.

    • You can discover files with sensitive information types without configuring labels for automatic classification. use the Set-AIPScannerConfiguration cmdlet, and set the DiscoverInformationTypes parameter to All

    • By default, only Office document types are protected. Other file types can be protected when you define them in the registry. For instructions, see File API configuration from the developer guidance.

    • By default, the scanner now runs with a low integrity level for higher security in case you run the scanner with an account that has privileged rights. When the service account that runs the scanner has only the rights documented in the scanner prerequisites, the low integrity level is not necessary and is not recommended because it negatively affects performance. You can use an advanced client setting to disable the low integrity level. More information

  • For Get-AIPFileStatus, the output now includes the Rights Management owner and Rights Management issuer, and the date that the content was protected.

Additional changes:

  • For the Azure Information Protection scanner:

    • The ScanMode parameter from Set-AIPScannerConfiguration is renamed to Enforce, with values of Off and On.

    • To use a default label, you no longer need to configure a default label as a policy setting. Instead, just specify this default label with the repository configuration.

  • Removed the "Congratulations!" welcome page and "What's new in Azure Information Protection" page, which displayed for first-time use in Office applications.


Released: 04/17/2018

This version includes the MSIPC version 1.0.3403.1224 of the RMS client.

New features:

  • The Azure Information Protection scanner: The PowerShell module that is included with the client has new cmdlets to install and configure the scanner so that you can discover, classify, and protect files on your on-premises data stores. For instructions, see Deploying the Azure Information Protection scanner to automatically classify and protect files.

  • You can now set different visual markings for Word, Excel, PowerPoint, and Outlook by using an "If.App" variable statement in the text string, and identify the application type. More information

  • Support for the policy setting, Display the Information Protection bar in Office apps. When this setting is off, users select labels from the Protect button on the ribbon.

  • A new advanced client setting (still in preview) to turn on classification to run continuously in the background. When this setting is enabled, for Office apps, automatic and recommended classification runs continuously in the background, instead of running when documents are saved. With this change in behavior, you can now apply automatic and recommended classification to documents that are stored in SharePoint Online. More information

  • A new advanced client setting so that Outlook doesn't apply the default label that is configured in the Azure Information Protection policy. Instead, Outlook can apply a different default label, or no label. More information

  • For Office apps, when you specify custom permissions, you can now browse and select users from an address book icon. This option brings parity to the user experience when you specify custom permissions by using File Explorer.

  • Support for a completely non-interactive authentication method, for service accounts that use PowerShell and that cannot be granted the Log on locally right. This authentication method requires you to use the new Token parameter with Set-AIPAuthentication, and run a PowerShell script as a task. More information

  • New parameter, IntegratedAuth for Set-RMSServerAuthentication. This parameter supports server mode for AD RMS, which is needed for AD RMS to support Windows Server FCI.


Fixes for stability and for specific scenarios that include:

  • For Office versions 16.0.8628.2010 and later (Click-to-Run), the Azure Information Protection bar supports the latest monitor display options that previously might result in the bar displaying outside Office applications.

  • When two organization using Azure Information Protection share labeled documents and emails, their own labels are retained and not replaced by the other organization's labels.

  • For Excel:

    • Support for changing Office themes or Windows themes, which previously caused Excel to not display any data after the theme was changed.

    • Support for cells that contain cross-references, which previously caused text corruption in that cell.

    • Support for typing Japanese, Chinese, or Korean characters, which previously closed a window so these characters couldn't be selected.

    • Support for comments, which previously closed the comment while it was being typed.

  • For PowerPoint: Support for coauthoring, which previously could cause data loss.

  • Files that have a .xml file name extension can now be inspected for recommended or automatic classification.

  • The viewer can now open protected text-based files (.ptxt and .pxml) larger than 20 MB.

  • Prevent Outlook hanging when Outlook reminders are used.

  • Bootstrap succeeds in Office 64-bit, so that you can protect documents and emails.

  • You can now configure a label for user defined permissions for Word, Excel, PowerPoint, and File Explorer and also use the advanced client setting to hide the custom permissions options. More information

  • Fall back to the Calibri font if visual markers in the Azure Information Protection policy are configured for a font name that is not installed on the client.

  • Prevent Office crashes after the Azure Information Protection client is upgraded.

  • For Office apps, improve performance and memory consumption.

  • When you configure a label for user defined permissions and HYOK (AD RMS) protection, the protection no longer incorrectly uses the Azure Rights Management service.

  • For a more consistent management experience, sublabels no longer inherit visual markings and protection settings from their parent label.


Released: 09/18/2017

This version includes the MSIPC version 1.0.3219.0619 of the RMS client.

New features:


Fixes for stability and for specific scenarios that include:

  • Support for generically protecting large files that previously could cause corruption if larger than 1 GB. Now, the file size is limited only by available hard disk space and available memory. For more information about file size limitations, see File sizes supported for protection from the admin guide.

  • The Azure Information Protection client viewer opens protected PDF (.ppdf) files as view-only.

  • Support for labeling and protection of files stored on SharePoint Server.

  • Watermarks now support multiple lines. In addition, visual markings are now applied to a document on the first save only rather than every time a document is saved.

  • The Run Diagnostics option in the Help and Feedback dialog box is replaced with Reset Settings. The behavior for this action has changed to include signing out the user and deleting the Azure Information Protection policy. For more information, see More information about the Reset Settings option from the admin guide.

  • Support for proxy authentication.

Fixes for a better user experience, that include:

  • Email validation when users specify custom permissions. Also, multiple email addresses can now be specified by pressing Enter.

  • The parent label is not displayed when all its sublabels are configured for protection and the client does not have an edition of Office that supports protection.

Next steps

For more information about installing and using the client:


Before commenting, we ask that you review our House rules.