Support statements are also updated throughout for Office 2019 - for the Azure Information Protection client (applies also to the Azure Information Protection unified labeling client), and to the RMS client if you are protecting documents and emails directly with the Azure Rights Management service, rather than using labels. References to out-of-support products, Windows Phone 8.1 and Windows RT are also removed. Remember that January 31 is end of support for the Rights Management sharing application for Windows, so expect this documentation to also be removed soon and the download page removed from the Microsoft Download Center.
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, January 2019
- Updated the Applications section to clarify that the Office 365 apps that are not ProPlus and can support protection come with Office 365 Business and Microsoft 365 Business subscriptions. The Office team has recently posted information that some customers have been experiencing problems applying protection with these Office 365 apps, but are working on a fix. If you think this might apply to you, see Some Office 365 Business users unable to apply IRM protection.
The prerequisites section now lists 8 GB of RAM rather than 4 GB of ram for the Windows Server computer that runs the scanner.
The section How files are scanned is revised to logically walk through the different process steps that the scanner takes, and details about inspecting file types other than Office documents and PDFs is now moved to a new section in the admin guide, File types supported for inspection.
A new tip that might explain why scanning doesn't complete, typically for a data repository in production that has a large number of files on SharePoint that has been hardened by an admin. This scenario produces a very distinctive error message in the logs to help you identify the root cause.
- New article, specifically to accommodate the changes for the new preview version of the client (and scanner). Changes include the ability to have multiple configuration databases on the same SQL Server instance and configuration from the Azure portal before you install (or upgrade) the scanner. The List of cmdlets for the scanner section lists the reduced number of cmdlets that are supported for the scanner, now that configuration for data repositories and file types is moved to the Azure portal.
- Updated the Upgrading the Azure Information Protection scanner section, for recommended upgrade instructions for the preview version. Customers who don't follow this recommended path often have problems with a scanner profile mismatch, which means that their scanner can't download the scanner settings configured in the Azure portal.
The Changing the default protection level of files section is also updated with the information that if you have 64-bit Windows, you must also update the registry path for 32-bit Windows. Some components of the client always operate in 32-bit mode. After making the registry edits, for PowerShell, you must start a new session.