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
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 section about how to take control of accounts and the sign-up process by using the AllowEmailVerifiedUsers parameter with the
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
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.
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
. The example for this cmdlet is also updated to include the configuration of a departmental template.
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.