If you click the link above, you might realize the Azure Information Protection docs have a new design for the top-level page. What's different about it? It has cards to help you find the documentation you're probably looking for, because the chosen articles are currently trending with others. Other services on docs.microsoft.com are sporting the new look for their documentation as well, so let me know if you have any feedback about the new design or the chosen cards or links.
However, the big release for Azure Information Protection this month was a new preview version of the unified labeling client, which includes the scanner. Of course, there are other updates and fixes with this new version of the client, but support for the scanner and with new features easily steals the show. Missed the announcement and breakdown of the new scanner features? See the blog post Unified labeling AIP scanner preview brings scaling out and more! and be sure to read the details in the version history.
We also have an updated support statement: Both the Azure Information Protection client (classic) and the Azure Information Protection unified labeling client are supported on Windows Server 2019, but we also made the clarification that Server Core and Nano Server aren't supported for any Azure Information Protection feature.
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, September 2019
- Updated the Client devices section to include Windows Server 2019 as a supported operating system, with the clarification that for the listed Windows Server versions supported, Server Core and Nano Server are not supported for any Azure Information Protection feature. For example, for the scanner, for the RMS connector, and for the PowerShell modules.
- Updated to include the preview version of the scanner from the unified labeling client. In case you haven't seen this quickstart before, it's a great way to get a taste of what the scanner can do without the complexity of configuring labels or the configuration required for a service account to run unattended.
- Updated to clarify that the checkbox Enable deeper analytics into your sensitive data applies to the classic client only. Information in this article is also updated to include the instructions to use the Publish option in the Azure portal if your labels use the unified labeling store.
- Updated throughout for the scanner, including instructions if you want to upgrade an existing deployment of the scanner from the classic client. In addition, the section for Reset Settings is updated for the files that get deleted when you select this action from the client.
- Revised the section for the LogMatchedContent advanced setting. Previously, the documentation incorrectly stated that unified labeling clients sent content matches for sensitive information types if the checkbox for Azure Information Protection analytics was selected, and you could use the LogMatchedContent setting for a subset of users who shouldn't send this information. Because the checkbox doesn't control this behavior for the unified labeling client, use this setting to enable matched content to be sent from unified labeling clients. This section is now renamed Send information type matches to Azure Information Protection analytics.