Azure Information Protection Documentation Update for March 2019

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


 


Updates this month support the new preview version of the Azure Information Protection client, and Azure Information Protection analytics (still in preview) has a new Recommendations report and a new policy setting to control sending auditing data. Other documentation updates are for clarifications and corrections. 


 


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, March 2019


 


What is Azure Information Protection?


– Added a video that covers the latest updates for unified labeling support for Microsoft 365.


 


How to configure a label for Rights Management protection


– Updates:



  • Clarified the differences for when a label is applied that is configured for Not Configured vs. Remove Protection.

  • Clarified that the expiry option is not always honored by email clients, because of their caching mechanisms.

  • Added a new example configuration for the recently supported scenario of “Just for me“.


 


How to configure a label for visual markings for Azure Information Protection


– Updated the information about the maximum string length for Excel: Excel has a total limit of 255 characters for headers and footers. This limit includes characters that aren’t visible in Excel, such as formatting codes. If that limit is reached, nothing from the string you enter is displayed in Excel. Previously, the documentation reported that the string was truncated.


 


How to configure conditions for automatic and recommended classification for Azure Information Protection


– Clarified that when you configure automatic labeling, unlike the experience in Word, Excel, and PowerPoint, users do not see an information bar that informs them of the automatically selected label before the email is sent. 


 


How to configure the policy settings for Azure Information Protection


– Updated to include the new policy setting of Send audit data to Azure Information Protection analytics. Screenshots for quickstarts and tutorials are also updated for this new policy setting.


 


How to migrate Azure Information Protection labels to Office 365 sensitivity labels


 – Updated the section for clients that support unified labeling to also include services. The Considerations section is also updated for the following:



 


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


– Updated the Optimizing the performance of the scanner section to include information that the construction of regex expressions can affect the scanner performance, with some tips how to write more efficient expressions.


 


Central reporting for Azure Information Protection


– Updated for guidance when and how to use the new policy setting Send audit data to Azure Information Protection analytics, and also a note how to use this setting as a workaround if your workspace is not displaying information when you first set it up. This known issue is expected to be fixed soon and will not be needed when the feature goes into general availability. There’s also information about the new Recommendations report, which is still rolling out to tenants.


 


The client side of Azure Information Protection


– Updated the feature comparison table:



  • Updated the row for the Information Protection bar in Office apps, to clarify that for the unified labeling client, this bar doesn’t support a title or tooltip, and doesn’t display the color of the currently selected label.

  • Added a new row for visual markings that are supported by both the Azure Information Protection client and the Azure Information Protection unified labeling client, but the unified labeling client doesn’t support variables for dynamic values or for different visual markings per app.

  • Updated the row for AD RMS support with the information that on the unified labeling client, the viewer requires the AD RMS mobile device extension.


This page lists some current limitations and features that are not yet available for the unified labeling client (still in preview) but might be included in future releases. However, there are now some features and functionalities that are decided to be not included in future versions, and these are now listed in a new section: Features not planned to be in the Azure Information Protection unified labeling client.


 


Azure Information Protection client: Version release history and support policy


– Updated for the latest preview release information.


– Removed version information for 1.29.5.0 because it is now out of support.


 


Admin Guide: Install the Azure Information Protection client for users


– Updated the prerequisites section for KB 4482887, which is for Windows 10 version 1809 only, operation system builds older than 17763.348: This fix prevents the Azure Information Protection bar from displaying incorrectly in Office apps.


 


Admin Guide: Custom configurations for the Azure Information Protection client


– New advanced client settings for the preview client:



Also updated the section for Don’t protect PDF files by using the ISO standard for PDF encryption to now include reasons why you might need this setting. One potential reason to use this setting is if you need to add protection to signed PDF documents: Signed PDF documents can be additionally protected with the .ppdf format because this protection is implemented as a wrapper for the file.




 

REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

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