Our technical writer, Carol Bailey, is letting you know whats new and hot in the docs for November.
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 aNovember 2017 (or later) date at the top of the article.
Many of the doc updates this month support the public preview of the Azure Information Protection scanner, which was announcedlast month. On our Yammer site, we’ve seen many people put the scanner through its paces and report back very favorably. Some of the resulting feedback is now incorporated into the documentation and if you also have questions or comments, now is a great time to share those with us!
One of the other important doc updates this month is to the version history page for the Azure Information Protection client. This page has now been extended to include a support statement that GA versions are supported for a period of six months from the date of their release.
As always, we listen to your feedback and try to incorporate it whenever possible.If you have feedback about the documentation, or want to see what others are discussing, head over to our Yammer site.
Whats new in the documentation for Azure Information Protection, November 2017
– Updated the following entry with details about the metadata, to help you configure your DLP rules:How can DLP solutions and other applications integrate with Azure Information Protection?
– This second step of the tutorial is updated for this month’s change to the policy settings. If you very recently got a subscription for Azure Information Protection, to complete the tutorial you will have to change the default for the new policy setting that makes custom permissions available to users.
– Updated the descriptions in the overview of the steps to include which steps can be skipped if you migrate using a “big bang” approach rather than a phased migration. Also updated the post migration tasks, with the renamed Step 11. Complete client migration tasks to include disabling the scheduled task, “AD RMS Rights Policy Template Management (Automated)” for Office 2010.
– Updated for the new policy settings in the Azure portal:
- Display the Information Protection bar in Office apps
- Add the Do Not Forward button to the Outlook ribbon
- Make the custom permissions option available to users
– Updated to clarify which files the scanner can inspect, when files are rescanned, and information about optimizing the performance of the scanner and the factors that can affect the performance. The prerequisites are also updated to include a Windows client operating system for testing purposes, and the new minimum version of SQL Server 2012 (previously, the minimum version was SQL Server 2012 R2).
– Updated to include the support lifecycle statement that the general availability (GA) versions of the Azure Information Protection client are supported for a period of six months from the date of their release. The versions older than this time period are now removed from this page.
– Updated for the new advanced client setting: Label an Office document by using an existing custom property. This page is also updated for the advanced client settings that can now be configured as policy settings in the Azure portal.
– Updated theHow to label files non-interactively for Azure Information Protection section with a note to add the Azure AD account to scoped policies, if needed. At the end of the procedure, added a tip to grant permissions to the apps if running Set-AIPAuthentication is not successful.
– New article for end users if you are currently in the classify-only phase of deployment. These instructions do not include any of the protection configuration steps and options, which is suitable for when you haven’t yet activated protection so users cannot protect documents and emails.
Source: EM+S Blog Feed