Share via

Announcement: Windows Azure RMS Documentation Library Update for February 2014

  • Article

Note: This is a cross blog post from our TechNet RMS Blog. (https://blogs.technet.com/b/rms/)

Hi everybody

As per Carol’s introduction post, she's letting you know what's new and hot in the docs for this month.

Reminders: Follow us on twitter (@TheRMSGuy) and join in our our new RMS peer community at www.yammer.com/AskIPTeam.

Cheers,  

   Dan (on behalf of the RMS team)

 

The Documentation Library for Windows Azure Rights Management has been updated on the web and the latest content has Updated: February 1, 2014 at the top of the topic.

Summary of the documentation available:

In addition, there are the Rights Management sharing application guides (also applicable to AD RMS):

Because there was a new release of the sharing application this month, changes for these are also listed in this post. 

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 Windows Azure RMS, email AskIPTeam@Microsoft.com.

 

What's New for the RMS Sharing Application Documentation, Februrary 2014

Rights Management sharing application administration guide

- Updated the enterprise installation instructions:

  • The deployment scenarios are clarified and updated to reflect the changes in the new release.
  • The procedures and verifications are updated for the simpler install instructions and users no longer have to have local administrative permissions.

Rights Management sharing application user guide

- Updated the Dialog box options topic for a new section, What's the difference between generic and (built-in) native protection?

FAQ for Microsoft Rights Management Sharing Application for Windows

- New section added for Common Issues: Limitations for Office 2010 and Windows Azure RMS

 

What's New in the Documentation Library for Windows Azure Rights Management, February 2014

The following information lists the topics that contain significant changes since the last update (January 2014).

RMS for Individuals and Windows Azure Rights Management

- New topic that explains how the free subscription to Windows Azure RMS works, and how the administrator can take control of the directory and accounts that are created in Windows Azure Active Directory.  This supplements the blog post that Tejas previously published: Introducing Microsoft Rights Management for individuals.

Comparing Windows Azure Rights Management and AD RMS

- Added a new section, Cryptographic controls for signing and encryption. This addition makes it easy for people who are looking for security-specific information to confirm that Windows Azure RMS always uses SHA 256 (2048 bits) for signing, and AES 128 for encryption.

Information and Support for Windows Azure Rights Management

- New topic that lists additional links and resources for Windows Azure RMS, such as how to provide feedback about the documentation and how to search just the Windows Azure RMS documentation by using a scoped search query - very useful!  You'll also find RMS-specific links to Yammer, forums, and the new Curah! site where you'll find curated content (including Dan's top 10 links).  If you create your own curations on this site for Windows Azure Rights Management, add the "Azure RMS" tag and others will see them when they click the link in this topic.

Terminology for Windows Azure Rights Management

- New topic that lists terms and abbreviations that are either specific to Windows Azure Rights Management, or have a specific meaning when used in the context of Windows Azure Rights Management.  With all the new features we've been adding and the new terms (and abbreviations) that often accompany new functionality, we thought a list like this would be helpful.  Let us know if you find this useful and if you think there are entries missing that could help other customers.

Planning and Implementing Your Windows Azure Rights Management Tenant Key

- Updated to move the information about the ongoing operations to a new topic, Operations for Your Rights Management Tenant Key, where the lifecycle operations are now in two separate sections for Microsoft-managed, and customer-managed. This reorganization of the (same) information makes it easier to find the information that’s relevant for your chosen tenant key topology, without having to read or scroll through information about the other topology.

In addition, the pictures in this topic were updated and a new picture added that shows the tenant key operations for a customer-managed topology, so that it’s easier to compare and contrast with the Microsoft-managed (BYOK) topology.

One technical change was made to the Choose your tenant key topology section: The addition of a note that as an additional protective measure, Windows Azure RMS uses separate security worlds for its data centers in North America, EMEA, and Asia.

Deploying the Windows Azure Rights Management Connector

- Updates for this topic include the following:

  • Newly supported scenario of file servers that use File Classification Infrastructure (FCI) to classify and apply policies to documents in a folder. For more information, see the Configuring a file server for File Classification Infrastructure to use the connector section.
  • The addition of an architecture overview diagram, to show the various components involved when you deploy the connector.
  • Changes to the file names that now match the current file names on the Download Center.

Known Issues for Windows Azure Rights Management

- Removed from the Windows Azure Rights Management documentation library and will be permanently deleted in a future publication.  This topic contained entries for Windows PowerShell that are now either resolved, or moved to another topic where it is relevant to another procedure.  For example, the procedure to discover Object IDs is moved to Adding, Listing, or Removing Role-based Administrators for Windows Azure Rights Management because you might need this information for when you add or remove a role-based administrator.