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 for Azure Rights Management has been updated on the web and the latest content has a May 2016 (or later) date at the top of the page.
Well, what isn’t new this month for our docs?! It’s been an exciting month as we began our transition off TechNet to the new documentation site, docs.microsoft.com. Behind the scenes, we’ve been working hard on this since the beginning of the year, so it’s great to be able to share it with you. Many thanks to our volunteers from Support (Sandor Teglasy, Uwe Wizovsky, Steve Light, Eddie Bowers) who helped to review this before it went live. Miss the announcement? You can read it here: Introducing docs.microsoft.com
Azure RMS, as part of the increasingly popular Enterprise Mobility Suite, was one of the first services chosen to move to this new documentation site and help blaze the trail for other services and products. The new publishing site supports some new functionalities such as a light and dark theme, estimated reading time, social media support, side notes and customer posts, and customer contributions. It doesn’t support all the functionality that we had on TechNet, such as expand/collapse sections and support for large tables. These differences often meant rearranging the information, for example, longer articles are now split into multiple shorter articles, and some of the tables are now presented as lists.
So that the old TechNet links don’t break, we’ve redirected the English pages (“en-us” in the URL) to either the equivalent article on the new publishing site, or the most relevant article. Because the international articles are not yet translated for the new site, these remain on TechNet until that process is complete. Then they will also be redirected.
For the time being, the PowerShell reference help (for Azure RMS and RMS Protection) will remain on MSDN but one of the opportunities this new publishing site brought was bringing together the IT Pro and developer documentation under a single table of contents. Whereas the audiences for these used to be very separate and distinct, these days the lines are more blurred, and this new site provides an opportunity to integrate the technical documentation for the service as a whole, rather than by audience. The sharp-eyed among you will realize we also included the RMS client documentation, which previously had its own node on TechNet because it applies to AD RMS as well as Azure RMS.
Rather like Azure RMS itself, the new documentation site is still evolving and changes will very much be governed by customer feedback. So don’t hold back, tell us what you think! What you like, what you don’t like, what changes you want to see implemented. But as much as the RMS team loves hearing from you, we ask that you send these comments straight to the team responsible for implementing any changes, by posting and voting on the feedback page that is specifically for this purpose: https://aka.ms/sitefeedback.
However, if you have feedback about the information itself, rather than how it is presented, continue to send that feedback to us so that we can incorporate it for doc updates: Email AskIPTeam@Microsoft.com.
What’s New in the Documentation for Azure Rights Management, May 2016
The following information lists the articles that have significant technical changes since the last update (April 2016). Articles that have the same technical information but presented differently for the new publishing site, are not listed. If you have problems finding information on the new publishing site, let us know and we will help you locate it while the search engines index these new pages.
– Updated the RMS for individuals section, to explain that you might see this subscription listed in the Office 365 admin portal as Rights Management Adhoc and automatically assigned to users. Do not manually assign this license to users and do not use this license to administer Azure RMS for your organization. For example, do not attempt to use this license to activate or deactivate Azure RMS.
– Updated to explain how search can be integrated with applications and services that support Azure RMS.
– Updated with the information that in addition to adding external users to templates by using PowerShell, you can also do this in the Azure classic portal if these users are created as an Exchange Online mail contact or as an Office 365 contact, and then added to a mail-enabled group that you then select in the portal.
However, in testing this, we encountered problems with external users opening emails protected with these templates when they were using Outlook Web Access (but not when opening them with Outlook 2013). Our test results did not show any problems with external users opening documents protected with these templates. We will continue to investigate this but because you cannot know in advance whether the external users will use the Outlook Web App to read their email, you might want to restrict use of this template configuration to documents only.
– Updated to reflect an engineering review of the current rights and their descriptions:
- Edit Content, Edit (DOCEDIT): Removed the additional information sentence “In Office applications, this right also allows the user to save the document.”
- Save As, Export (EXPORT): The description more explictly states “For Office documents, the file can be saved without protection.”
- Forward (FORWARD): Explictly states that not relevant for documents, only email messages.
- View Rights (VIEWRIGHTSDATA) and Change Rights (EDITRIGHTSDATA): Removed.
– Updated the description of the file-name field, to clarify that some applications do not yet support displaying the actual file name, but instead, display a GUID. Applications that use the latest RMS client SDK (such as the RMS sharing application) do display the actual file name.
– Updated the RMS client settings section, to correct the registry entries for federated authentication. Previously, they incorrectly had https values instead of http, and were missing the registry key for a 32-bit MSIPC-based application running on a 64-bit version of Windows.