Azure Information Protection Documentation Update for October 2019

The Documentation for Azure Information Protection been updated on the web and the latest content has an October 2019 (or later) date at the top of the article.


 


Fast on the heels of last month’s preview version of the Azure Information Protection unified labeling client, came the general availability release this month, with the scanner still in preview.  Even if you installed the previous preview version of the scanner, there are important scanner changes in this release, so I encourage you to carefully check the version history before you upgrade or install this client.


 


Some other things to point out:



  • With everybody talking about Ignite 2019 in Orlando next week, we’ve updated our top 5 recommended sessions and just like last year, I’ll add links when the recordings become available.

  • Now that Office 365 apps with built-in labeling for Windows is becoming more available for users, we’ve updated our comparison information to help you choose between this built-in functionality, the unified labeling client, and the classic client. We’ve also incorporated this choice into an updated table to compare the features across these clients. 


We listen to your feedback and try to incorporate it whenever possible. Let me know if you have feedback about the technical documentation for Azure Information Protection. I also encourage you to head over to our Yammer site to see what others are discussing.


 


What’s new in the documentation for Azure Information Protection, October 2019


 


What is Azure Information Protection?


– Updated the Microsoft Ignite section, removing the top 5 recommended sessions from last year, and replacing them with this year’s top 5 recommended sessions. When recordings become available, you’ll see links added to the sessions.


 


FAQs: Classification and labeling in Azure Information Protection


– Now that Outlook on the web supports built-in labeling, updated How is classification for emails using Azure Information Protection different from Exchange message classification?


 


Requirements for Azure Information Protection


– Updated the Applications section with the information that the Office Mail Merge is not supported for any Azure Information Protection feature.


 


Active Directory Requirements for Azure Information Protection


– Updated the section “Users’ UPN value doesn’t match their email address” with the information that this scenario doesn’t support single-sign on (SSO).


 


Applications that support Azure Rights Management data protection


– Updated the RMS-enlightened applications table, Windows row, Other files types, to include Visio file name extensions for Visio 2016 and later. These are not newly supported file types and have been listed in the admin guides as supported file types, but were not included in this table. 


 


Quickstart: Get started with Azure Information Protection in the Azure portal


– Updated to include publishing the Global policy with default labels in the Azure portal, so that they’re available for the classic client. 


 


Refreshing templates for users and services


– Updated to add a new section, Office 2019 for Mac and Office 2016 for Mac: How to force a refresh for templates.


 


How to migrate Azure Information Protection labels to unified sensitivity labels


– The section Copy policies is back now that this functionality is rolling out to all tenants in public preview. In addition, the table for settings not supported in the admin centers includes a new row for the protection setting of “any authenticated user”, with the guidance to configure this setting in the Azure portal until it’s available to select from the admin centers.


 


Central reporting for Azure Information Protection


– Removed the known limitation that custom information types were not always displayed now that this functionality is supported by the current release of the unified labeling client. Also removed Access and AccessDenied as event functions. These activities for protected documents are included as values for the Activity field. Similarly, InformationTypesMatches is removed as an event function, with the match included in the value for DiscoveredInformationTypes.


 


Deploying the Azure Information Protection scanner to automatically classify and protect files


– Updated throughout to include the preview version of the scanner from the current GA version of the unified labeling client. Additionally:



 


The client side of Azure Information Protection


– Updated to incorporate comparison information about built-in labeling for Office, with a redesign of the feature comparisons table.


 


Azure Information Protection unified labeling client – Version release history and support policy


– Updated for the new general availability release, version 2.5.33.0 which includes full details of what’s supported for the preview version of the scanner, and other changes for the client.


 


Admin Guide: Using PowerShell with the Azure Information Protection unified client


– Updated procedure for the preview version of the unified labeling client (and scanner) to create a registered app in Azure: To create and configure the Azure AD applications for Set-AIPAuthentication  Note that this procedure has changed since the last preview version of the scanner, now that Set-AIPAuthentication supports the DelegatedUser parameter.


 


Admin Guide: Custom configurations for the Azure Information Protection unified labeling client


– New advanced settings that you configure with PowerShell



Additionally, new configuration support for disconnected computers.


 


Azure Information Protection client: Version release history and support policy


– Updated for the new general availability release, version 1.54.33.0.  The section for version 1.41.51.0 is removed now that it’s out of support and this version is added to the table of releases that are no longer supported.


 


AzureInformatioProtection PowerShell module:



 

Leave a Reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.