Office 2016 for Mac available now with Azure RMS support!
First published on CloudBlogs on Jul 15, 2015
Today we're very excited to announce RMS (aka IRM) support in the new Office 2016 for Mac. Yair Cohen is a Program Manager on the team and he’ll talk about the release in more detail.
Follow us on twitter (
) and join in our RMS peer community at
Dan (on behalf of the RMS team)
Hi guys, this is Yair. Last week Office 365 announced general availability of the
new Office 2016 for Mac
As part of our commitment to enable Information Rights Management (IRM) in Office on all platforms,
we are excited to announce that Office 2016 for Mac has Azure RMS support.
Office for iOS will also enable Information Rights Management (IRM), and other platforms will follow later this year.
Office 2016 for Mac is powered by the cloud so you can access and share your documents on OneDrive, OneDrive for Business and SharePoint at anytime, anywhere. With Azure RMS, you can also secure and control your documents wherever they go.
The new Outlook, Word, PowerPoint and Excel for Mac support
Azure RMS and AD RMS
, which means that users can now send and receive IRM emails, as well as open and create IRM documents, and share them within and outside their organization.
download the Office apps today
and try them yourself!
If your organization uses Azure RMS, you are all set. Just sign in with your organizational account and open or create IRM protected emails and documents.
If your organization uses AD RMS, your admin will need to install the new Mobile Device Extension package as described
. This is because Office IRM depends on the new RMS SDK 4.1, which uses OAuth 2.0 to authenticate users. Note that even if you already have Mobile Device Extension installed in your org, your admin would still need to install the new version update that was released today and includes a few important fixes for Office 2016 for Mac.
As always, we encourage you to send us your feedback to
Ask the RMS Info Protection Team
Yair on behalf of the RMS team
Click on the image to read the full article in Office blogs: