This feature has been available for a while, but its original version required you to have an Azure subscription and storage account. Microsoft is now providing an alternative by introducing the detailed Usage logs we are examining in this article. In addition, there is no automated way of generating them, as even the Azure AD Reporting API does not expose said reports. While those reports are nice to have, they don’t offer much granularity. The available reports provide data for the number of the protected documents that were accessed for the last one month, the number of users that accessed at least one protected document as well as the number of denied requests, a list of the top 1000 users, list of device platforms from which content was accessed, and a list of applications. To view said reports one has to login to the Azure management portal, select the Azure AD entry, then click on Reports. Several reports that summarize the usage of Azure RMS have been available for a while as part of the Azure AD reports feature, accessible via the (classic) Azure Portal for the Azure AD instance corresponding to your Office 365 tenant. When it comes to auditing usage of Azure RMS, two types of logs can be considered: the Admin audit log, which covers every “privileged” operation such as creating new templates or using the Super user feature, and the Usage logs, which cover the consumption of protected content. Obtaining and examining the logs is a simple task and only minimal knowledge of the inner workings of RMS is required, however an unfamiliar reader should consider reading the Azure RMS documentation first. In this article we will focus on the Usage logs, which allow you to audit the consumption of content protected by Azure RMS, as well as perform more detailed analysis as to what devices are used to access content, what IP the content was accessed from and so on.
Rms sharing application full#
The service has been rapidly evolving in the past few months, introducing features such as: the Tracking portal, which gives users the ability to audit the consumption of their protected content and revoke access if needed full multi-factor authentication support across all RMS clients the RMS protection tool, which provides PowerShell cmdlets to bulk (un)protect files and replaces the AD RMS Bulk Protection Tool the Azure RMS usage logs and more. Other news in the RMS Sharing Application are some IT administator custom settings to control the behavior of the app.Azure Rights Management Service (RMS) is an information protection solution, the cloud-based version of AD RMS. When I click OK and choose to open the wordfile in Office Mobile I see the document: When I click on the attached pfile and choose to open it with the RMS Sharing App I get prompted for my RMS credentials (as you can see the RMS sharing app is now localized and shows me a swedish version):Īfter I authenticate my phone shows me the permissions (in swedish) that I am asked to comply wih and I am informed that the usage of this document is logged: This is what the mail with the pfile attachment looks like on my iPhone: If I try to open a nativly RMS-protected Word document (that still has the *.docx file extension) on my iPhone it will not know that it needs to be decrypted first and the Word viewer will show this instead of trying to decrypt the document with the RMS app: When I click Send Now the mail will be sent with the attachment RMS protected. This means that the attached Word-document, even though the fileformat it nativly RMS aware, will use the generic wrapper pfile instead. I’ll change it to allow consumption on all devices. Note: Remember to write the mail first, since the mail will be sent directly when you protect the attachment. When you click the button you will be prompted to configure some options, like the level of permission and if you want to enable content expiration:
This is done by clicking the Share Protected button in the compose mail window: One new feature is that you can protect an attachment in Outlook without protecting the entire mail. It downloads the necessary installation files when it runs. It is now a standalone file called setup.exe that is 407 Kb. The setup files are no longer stored in a zip-file. A new version of the RMS Sharing Application has just been released.
0 kommentar(er)
