As per Carol’s introduction post, she's letting you know what's new and hot in the docs for this month.
Dan (on behalf of the RMS team)
The Documentation Library for Azure Rights Management has been updated on the web and the latest content has Updated: February 1, 2015 (or later) at the top of the topic.
Summary of the documentation available: Getting Started with Rights Management | Configuring Rights Management | Using Rights Management | Administering Rights Management by using Windows PowerShell
Unlike the previous month with the bumper crop of new releases and updates, February has been a fairly quiet month for doc updates. There are no significant updates to the RMS sharing application and the updates we have are mainly to incorporate customer feedback and questions.
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 sharing application, or for Azure RMS, email AskIPTeam@Microsoft.com.
What's New in the Documentation Library for Azure Rights Management, February 2015
The following information lists the topics that contain significant changes since the last update (January 2015).
– Updated the final row in the What problems does Azure RMS solve? table, for the latest certifications that might be needed for compliance or regulatory requirements.
– Updated the section about how to take control of accounts and the sign-up process by using the AllowEmailVerifiedUsers parameter with the Set-MsolCompanySettings cmdlet from the Windows PowerShell module for Azure Active Directory. When this parameter is set to False (and AllowAdHocSubscriptions is set to True) only users who already have an account in Azure AD can sign up for RMS for individuals. This prevents new user accounts from being created automatically during the self-service sign-up process.
In addition, added the Get-MsolAccountSku cmdlet as another check that you can use to see whether your organization has been granted an RMS for individuals subscription. If it has, RIGHTSMANAGEMENT_ADHOC is returned as one of the subscriptions with a pool of active units available.
– Added a new row for file types to clarify that both Azure RMS and AD RMS now support protecting all file types when you use the RMS sharing application.
– Updated the prerequisites to clarify that the connector must be installed on a member server and not a domain controller.
– Updated to add a reference to new video: Azure RMS user experience
Updated for the following:
- Add-AadrmTemplate to clarify that before using this cmdlet, you must first create a rights definition object that specifies the rights that you want to grant and to whom, by using New-AadrmRightsDefinition. The example for this cmdlet is also updated to include the configuration of a departmental template.
- New-AadrmRightsDefinition no longer references the "bundled rights" such as Co-Author and Co-Owner. These are not working as expected so they are removed from the documentation while we investigate the issue.
– New entry:
- Can I prevent users from sharing protected documents with specific organizations?