Azure Information Protection client: Version release history and support policy
Applies to: Azure Information Protection
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.
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.
Versions later than 220.127.116.11
If you have a version of the client that is later than 18.104.22.168, it is a preview build for testing and evaluation purposes.
The current preview version is 22.214.171.124 and has the following changes since the current GA version of the client.
This version includes the MSIPC version 1.0.3403.1224 of the RMS client.
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.
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
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 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.
Support for cells in Excel that contain cross-references, which previously caused text corruption in that cell.
Support for changing Office themes or Windows themes, which previously caused Excel to not display any data after the theme was changed.
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.
This version includes the MSIPC version 1.0.3219.0619 of the RMS client.
Support for the new Office 365 DLP conditions that you can configure for a label. For more information, see Configure conditions for an Azure Information Protection label.
Support for labels that are configured for user-defined actions. For Outlook, this label automatically applies the Outlook Do Not Forward option. For Word, Excel, PowerPoint, and File Explorer, this label prompts the user to specify custom permissions. For more information, see Configure an Azure Information Protection label for protection.
Labels support multiple languages. Beginning with August 30, 2017, the default policy includes support for multiple languages that this version of the client displays to users. For users to see labels in their preferred language from a default policy before this date, and for labels that you configure, see How to configure labels for different languages in Azure Information Protection.
Labels are displayed from the Protect button on the Office ribbon, in addition to displaying on the Information Protection bar.
Native protection for the following Visio file types: .vsdm, .vsdx, .vssm, .vssx, .vstm, .vstx
Support for advanced client configurations that you configure in the Azure portal. These configurations include the following:
For PowerShell, support to label files non-interactively by using the new PowerShell cmdlets, Set-AIPAuthentication and Clear-AIPAuthentication. For more information how to use these cmdlets, see the PowerShell section of the admin guide.
For the PowerShell cmdlets, Set-AIPFileLabel and Set-AIPFileClassification, there are new parameters: Owner and PreserveFileDetails. These parameters let you specify an email address for the Owner custom property, and leave the date unchanged for documents that you label.
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.
This version includes the MSIPC version 1.0.2217.1 of the RMS client.
- New PowerShell cmdlet, Set-AIPFileClassification. When you run this cmdlet, it inspects the file contents and automatically applies labels to unlabeled files, according to the conditions that you specify in the Azure Information Protection policy.
All labeling and classification cmdlets are now supported on computers that are not connected to the Internet but have a valid Azure Information Protection policy.
For consistency, an output parameter from the Get-AIPFileStatus cmdlet is changed from British English (IsLabelled) to American English (IsLabeled). If you have scripts or automated processes that look for this parameter, update the spelling for this parameter.
General fixes for stability that include:
For Outlook: Fixes for crashes, high memory consumption, and display issues for menus.
For Word, Excel, and PowerPoint: Fixes for high CPU usage, display issues when saving large Excel files, or the application stops responding.
Also for these applications, to improve performance for Office 2016 with SharePoint Online and OneDrive for Business, automatic and recommended labeling is applied when the file closes rather than when the file saves (automatically saves or the user chooses to save). Similarly, if the setting All documents and email must have a label is enabled, users are not prompted to select a label until the file closes. The exception is for Word 2016 and Excel 2016 and the user selects the Save As option. Then, this action triggers these labeling behaviors if they are configured.
For more information about installing and using the client:
For users: Download and install the client
Before commenting, we ask that you review our House rules.