Azure Information Protection Documentation Update for November 2019

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.

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

 

Of course, the focus for this month was Ignite 2019 in Orlando. If you missed the excellent recap that Nir Hendler provided, you'll find it here: Microsoft Information Protection - Ignite 2019 recap.

 

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

 

What is Azure Information Protection?

- Updated the Microsoft Ignite section to add links to recordings for our top 5 recommended sessions.

 

Frequently asking questions for Azure Information Protection

- Updated What types of data can Azure Information Protection classify and protect? The answer is updated with the newly announced preview release to support .pdf, .xls, and .ppt file types from Power BI.

 

Client devices that support Azure Information Protection

- Updated the Mobile devices section for the new minimum supported version of Android 6.0.

 

Applications that support Azure Rights Management data protection

- Removed the list of supported RMS-enlightened solutions and replaced it with a link to current information, Microsoft Ignite 2019 – Microsoft Information Protection solutions Partner ecosystem showcase.

 

Configuring usage rights for Azure Information Protection

- New section, Automatically encrypt PDF documents with Exchange Online.  Announced at Ignite, you can now automatically encrypt unprotected PDF documents when they are attached to an encrypted email. The document inherits the same permissions as those for the email message. To enable this configuration, set EnablePdfEncryption $True with Set-IRMConfiguration.

 

Configuring the Azure Information Protection policy

- Updated the section Label information stored in emails and documents to remove the semicolon from the end of the metadata for emails. The semicolon can cause problems for Exchange mail flow rules for Outlook on the web and for iOS. The semicolon is also removed from Exchange Online mail flow rules for Azure Information Protection labels and the classic client customization Integration with Exchange message classification for a mobile device labeling solution.

 

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

- Added the new SQL Server requirement for case insensitive collation. In addition:

Central reporting for Azure Information Protection

- Updated to remove the additional step that was needed to publish labels from the Unified labeling pane in the Azure portal after you configure your workspace for Azure Information Protection analytics, and then whenever you made changes to your labels. With an update on the backend, this additional step is no longer needed.

 

The client side of Azure Information Protection

- Added the different policy refresh timings for the scanner to the detailed comparisons table for the clients.

 

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

- Removed release information for version 2.0.778.0 when it went out of support on the first of November. Version 2.0.779 is now the minimum version supported for the unified labeling client. 

 

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

- New advanced setting that you configure with PowerShell

 

Admin Guide: File types supported by the Azure Information Protection unified labeling client

- Updated File types that are excluded from classification and protection with the information that unlike the classic client. .msg files are not automatically excluded. If these file types are labeled (classified and generically protected), the file can't be opened. As a workaround, remove the label. Because of this issue, we don't recommend that you remove the .msg file type for the scanner.

 

User Guide: Classify and protect with the Azure Information Protection unified labeling client

- With the new public preview to enable sensitivity labels for Office files in SharePoint and OneDrive, amended the warning that if the label you select applies protection to a document, the protected document might not be suitable to be saved on SharePoint or OneDrive. Similar warnings in the documentation about loss of SharePoint functionality have also been updated for this preferred solution. 

 

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.