Update: As of December 2017, all documentation updates are now posted on our Tech Community blog: https://aka.ms/AIPblog
Our technical writer, Carol Bailey, is letting you know what’s new and hot in the docs for October.
Gagan (on behalf of the Information Protection team)
The Documentation for Azure Information Protection has been updated on the web and the latest content has an October 2017 (or later) date at the top of the article.
The doc updates this month continue to support the release announcements from Ignite 2017, with new and supporting documentation for the Azure Information Protection scanner, and additional information for Azure AD conditional access. The migration guide is also updated for new scripts that are now on the Download Center.
As always, we listen to your feedback and try to incorporate it whenever possible. If you have feedback about the documentation, you can contact us by emailing AskIPTeam@Microsoft.com.
What’s new in the documentation for Azure Information Protection, October 2017
– Updated the Resources for Azure Information Protection section, for a link to the end user adoption guide, and an update for the Ignite 2017 sessions.
– Updated the supported applications table, for Office Mobile for Android, which now supports editing protected documents in addition to viewing them. Also updated the supported solutions table with a new entry for Forcepoint DLP.
– New entries:
- I see Azure Information Protection is listed as an available cloud app for conditional access—how does this work?
- What’s the difference between labels in Azure Information Protection and labels in Office 365?
– Updated for the new scripts on the Download Center, with revised guidance for Mac computers.
– Updated the Rights included in the default templates section, for templates that are created after October 6, 2017.
– Added a new section for examples, which includes how to configure a label to send a protected email to a Gmail account, how to grant controlled access to users in another organization, how to add external users to an existing label, and how to configure a label for email that supports less restrictive permissions than Do Not Forward. Let us know of additional examples that you would find useful.
– Updated for the following:
- An important note that automatic classification and user-defined permissions should not be configured for the same label.
- New section, How automatic or recommended labels are applied. This new section makes it easier to distinguish the differences in behavior for the general availability (GA) version of the client, and the current preview version of the client that is also used with the scanner. Note that the scanner requires conditions to be configured as automatic.
– New article, step-by-step instructions to install, configure, and run the Azure Information Protection scanner. The scanner is now in public preview and announced at Ignite.
– Removed the preview disclaimer, now that this feature is generally available.
– Updates include:
- Instructions to install the client for users are moved to their own page: Install the Azure Information Protection client for users
- For custom configurations, the Enable recommended classification in Outlook option incorrectly had the preview disclaimer removed last month, and is now reinstated.
- For document tracking, added a note to explain why you might not see the Admin icon, and how to alternatively switch to Administrator mode by using a direct link.
- For file types supported, for native protection, added file name extensions for Visio. This support was introduced with the latest GA version of the client. This section is also updated with the information that for text-based files, the Azure Information Protection viewer has a maximum supported file size of 20 MB.
- For file types excluded, added two new sections: Files that cannot be protected by default, and Limitations for container files, such as .zip files.
– The online help for this module is updated for the cmdlets that support the Azure Information Protection scanner.