As promised, here is the follow-up post to our earlier announcement about the Windows Azure AD Rights Management preview where you can learn more about how to quickly enable Rights management capabilities within the Office 365 Enterprise preview. And yes, these steps will be simpler/fewer in the final release of Azure AD Rights Management.
I'll let Tejas Patel, our resident expert, give you the inside track here.
Hi, I'm Tejas, a program manager on the Windows Azure AD Rights Management team, and I just want to provide some quick "jump start" steps for how you try out and get a feel for using Windows Azure AD Rights Management.
As Dan mentioned, our service is available as a part of the Office 365 Enterprise Preview. Once you have signed up for the preview, enabling Rights management capabilities within the Office 365 preview just takes a few additional steps.
Today, I'll be discussing how to enable Rights management and then how you can configure Office 2013 Preview to begin using its capabilities.
Quick Start for using Windows Azure AD Rights Management and within Office 2013 Professional Plus
As always, please let us know if there are any questions or feedback. I'll be doing other blog posts later this week to help show you some of the other ways you can use Windows Azure AD Rights Management with the Office 365 preview.
If you're curious what's coming next, here's a look ahead:
Looking forward to trying this out in my org. How do I set this up on my Mac? Are there plans to bake these steps into the Office 365 control panel?
Hi RMS Guru,
Thanks for the post. Regarding your control panel question -- I've since updated the posting to say "And yes, these steps will be simpler/fewer in the final release of Azure AD Rights Management"
Regarding the Mac question: Right now it's not possible. The Azure AD RM service uses 2K RSA keys and the mac client currently only supports 1K RSA keys. It's on the road map but not available at this time. Sorry.
imho the installation is not enterprise aware. our users do not have the option the run any program using elevated rights nor do they have the opportunity to run powershell.
isn't there another deployment solution?
Great to see this new deployment scenario, looking forward to see detail on-prem, hybrid scenarios.
I have seen as well a strong interest in Collab with External parties perhaps using Windows Azure ACS to extend access to other parties to content as well (either for on-prem and Cloud AD RMS scenarios)
I'd like to recommend a capability matrix between all aD RMS scenarios (on prem, and different scenarios in cloud) so can simplify which option is best according to their business needs/product capabilities.
The powershell cmdlets need to be run by Administrators, the cmdlets will be replaced by UI to complete this task. For Office 2013, we will remove the need for users to set the registry keys in a later build.
even if the new offering seems related to Azure AD... when using o365 with on premise active directory and ADFS - still possible to use the o365 rms or do I need to install on premise RMS?
regarding rms guru and the Mac question: I am currently beta-testing the www.rmsviewer.com Mac-viewer and it works great - supports 2k keys because of the concept they use.
Yes, this offering was designed for Office 365, no need to install an AD RMS server. Our service is highly integrated with Office 365 including SharePoint Online and Exchange Online.
As with other Office 365 services, such as Exchange Online, when running in the configuration that you have described (Active Directory and ADFS), you will need to federate and synchronize your directory to Office 365.
I tried the preview today but got stuck with the powershell steps... I don't have access to powershell at my corp. We use mac and linux workstations primarily, and remote powershell is a non-starter. I can't be alone...
After installing Windows Azure AD Rights Management Administration Tools and Utilities, I have tried to import AADRM module but it can't complete. Here is the error: "Import-Module : The specified module 'AADRM' was not loaded because no valid module file was found in any module directory".
I then navigate to \System32\WindowsPowerShell\v1.0\Modules\ folder and it does have AADRM module.
I have tried re-installing Windows Azure AD Rights Management but the command Import-Module AADRM still doesn't work.
We are currently using Office 365 and have enabled E3 licenses to use IRM in Office through Azure. We would like to encrypt a lot of documents using the AD RMS Bulk Encyption tool, however it requires an RMS template. Azure provides two (Confidential, and Confidential Read-only). These work using the tool, but when I try to modify the XML to customize the templates it breaks them and since I don't have access to the AD RMS MMC I cannot generate my own. Does anyone know how I can make this work?
This need more information / answers