As per Carol’s introduction post, she's letting you know what's new and hot in the docs for this month. And July has been a very hot month for us!
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: July 1, 2015 (or later) at the top of the page.
Summary of the documentation available: Getting Started with Rights Management | Configuring Rights Management | Using Rights Management | Administering Rights Management by using Windows PowerShell
With all the new releases coming out that support Rights Management, the documentation page to watch and refresh at the moment is Requirements for Azure Rights Management – you might want to add this to your favorites! For more information about some of the releases, check out our blog posts if you haven't already. For example: Office 2016 for Mac available now with Azure RMS support! and Office for iPad available now with Azure RMS support!
In addition, when Office for Mac 2016 released, we updated the Active Directory Rights Management Services Mobile Device Extension documentation, to let AD RMS customers know that this latest Office version requires our latest version of the mobile device extension. If you're not sure how to confirm whether your installed version supports Office for Mac 2016, we've added instructions how to check.
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, for the mobile device extension, or for Azure RMS, email AskIPTeam@Microsoft.com.
What's New for the RMS Sharing Application Documentation, July 2015
There are no technical changes to the sharing application documentation since the last update (June 2015), except to document a new release for minor fixes. For more information, see Rights Management sharing application: Version release history.
What's New in the Documentation Library for Azure Rights Management, July 2015
The following information lists the topics that contain significant changes since the last update (June 2015).
– In the SharePoint Online and SharePoint Server section, removed the limitation that you cannot share with people outside your organization. With recent changes to SharePoint, you can now share by using a work or school account, or a Microsoft account.
– Although Windows 10 is now added as a supported operating system, the RMS sharing application doesn't yet support this latest Windows release, which is reflected in the Applications section (the Important callout box). This restriction should be resolved very soon! In addition, the Client device capabilities section has multiple updates for the recent releases:
- Office Mobile apps and Siemens JT2Go: JT files are added for Windows 10
- Office for iPad and iPhone is added for iOS (Word, Excel, PowerPoint)
- Office 2016 for Mac is added for OS X (Word, Excel, PowerPoint, and for Email)
– New entry:
- When I share a protected document with somebody outside my company, how does that user get authenticated?
– Updated the following sections:
- Exchange Online: IRM Configuration: Expand this section to now see a typical set of commands that enables Exchange Online to use Azure RMS.
- SharePoint Online and OneDrive for Business: IRM Configuration: Expand this section to now see configuration steps for OneDrive for Business. This section now more clearly delineates the different levels of configuration required and who would usually do this configuration.
– Updated the -ProtectionPassword<SecureString> parameter description, for information about how to specify special characters (such as symbols) for paswords when you use ConvertTo-SecureString. Chances are, if you have a strong password, you will use special characters. If you do not escape these characters when you specify the password or surround them in single (not double) quotes, PowerShell strips them out so the password will fail and you see the error messages Trusted Publishing Domain data is corrupted and The remote server returned an unexpected response: (400) Bad Request.