Enterprise Mobility and Security Blog

RSS

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 Azure Rights Management has been updated on the web and the latest content has Updated: October 1, 2014 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

Plus, the Rights Management sharing application guides (admin guide and user guide) and FAQs (for Windows and mobile platforms).

This month, we also updated the Active Directory Rights Management Services Mobile Device Extension for a link to the accompanying downloadable white paper and scripts, and an update to the supported clients list so that Mac OS X version 10.8 (Mountain Lion) is now the mimimum supported version for Mac computers.

In addition, we want to draw your attention to a new section, How does Azure RMS work? Under the hood, in the newly revised topic, What is Azure Rights Management?  Based on the customer questions we've been hearing, this new section includes a high-level example of how Azure RMS protects a secret cola formula without sending the data to the cloud (a common misconception), a section to answer security-related questions about key lengths and algorithms, and a walkthrough section that shows step-by-step flows of how Azure RMS works.  Many thanks to those who helped to review this topic and provide feedback that we've now incorporated – folks from the field and from the Active Directory Documentation Advisory Council. We love feedback that helps to make the docs more useful for others!

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.

There are no significant doc updates this month for the RMS sharing application.

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

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

What is Azure Rights Management?

– New section, How does Azure RMS work? Under the hood, which helps to answer those nitty-gritty details that your security team might ask or have concerns about, that you might want to know to better understand the technology, or if you're just curious.

Requirements for Azure Rights Management

– Updated for the following:

  • Added information to the Azure AD directory section that if you have mobile devices or Mac computers that authenticate on-premises by using AD FS or a similar authentication provider, you must use Windows Server 2012 R2 or later for AD FS, or an authentication provider that supports the OAuth 2.0 protocol.
  • The Client device capabilities table for the latest support statements, which reflect the new release of the RMS sharing app. With the new Office support by using protected PDF documents for mobile devices, we've replaced the previous PDF column with a Protected PDF column.

Activating Azure Rights Management

– Updated to reflect recent changes in the Office 365 admin center. Deactivating Azure Rights Management is similarly updated.  The Office 365 admin center had a few changes this month and our apologies if you had problems finding how to activate Rights Management when there was a delay in updating the instructions to match.

Frequently Asked Questions for Azure Rights Management

– Added the new question "Where can I find supporting information for Azure RMS?" to include useful links that relate to Azure RMS – such as service level agreements, certifications, auditing information, and privacy.