No big releases this month, although the sharp-eyed among you might have noticed additional information being reported for Azure Information Protection analytics, which meant an update to the Central reporting for Azure Information Protection article. Not a complete replacement for the document tracking site, but you can now see when a protected document was accessed (successfully, or denied) in your Log Analytics workspace. This information is retrieved from the protection usage logs, which means that this access information isn't restricted to users in your tenant and is independent from specific clients or services.
Most of the other doc updates this month are for corrections and requests for clarifications. 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, August 2019
- Updated the Firewalls and network infrastructure section, with a new method to check whether your firewall might be terminating your TLS connection to the Azure Rights Management service, which will result in a failed connection.
Information added to the SharePoint row in the Prerequisites about how the scanner works when versioning is enabled for SharePoint, and also clarified that the scanner supports document libraries and folders on SharePoint, and not sites or site collections.
- Updated the requirements for the user account installing the RMS connector, with the information that if you're using Azure AD Conditional Access, do not block legacy authentication for this account.