Most of the doc updates this month are to support the
recently updated RMS Protection Tool
- with the main page on MSDN being
RMS Protection Cmdlets
. However, we continue to update the core Azure RMS docs for support changes and to answer your questions. There are no significant changes this month to the documentation for the RMS sharing application.
We value customer feedback and try to incorporate it when possible. Although we can't promise to make the docs perfect for everybody, we are committed to continual improvement. If you have any feedback about the docs for the RMS Protection Took, the RMS sharing application, or for Azure RMS, email
What's New in the Documentation Library for Azure Rights Management, March 2016
The following information lists the articles that have significant changes since the last update (February 2016).
Requirements for Azure Rights Management
- Updated support statements for Windows 10 Mobile, and added Outlook for Android in the
client device capabilities table
Activating Azure Rights Management
- Added a new procedure if you're using the new
Office 365 admin center preview
to activate Azure RMS. This activation option is located under
Configuring Custom Templates for Azure Rights Management
- Updated to document the new maximum limit of 500 custom templates (published or archived) that you can save in Azure. If you exceed the 500 limit because you have many archived templates, consider exporting the archived templates. This lets you save them locally (to import later if needed), and you can then delete them from Azure. This limit applies whether you create the templates in the Azure classic portal, or you create or import them by using PowerShell.
Configuring Super Users for Azure Rights Management and Discovery Services or Data Recovery
- Removed the warning that the RMS Protection Tool doesn't support user accounts now that the the
version of the RMS Protection PowerShell module is released. However, for automated scenarios (such as scripts that run when you're not signed in, and use with Windows Server File Classification Infrastructure), you should still use a service principal account.