It comprises a set of RMS applications that work on all your common devices, a set of software development kits, and related tooling.
Azure RMS is also known as the Microsoft Rights Management suite. Azure RMS can can coexist along with on-premises. Although Azure RMS is built on this framework it is not the same.
#Rms sharing app windows
RMS has been around for quite awhile in the on-premises world attached with Windows Server under Active Directory RMS (ADRMS). It uses encryption, identity, and authorization policies to help secure your files.
To continue this post I have included information and configuration steps around Azure RMS and IRM in Office 365. As the move to O365 continues we need to know what we can and cannot do to protect our data. I don’t believe this is a common scenario but I believe this is an important use case to know as I could not find this unsupported scenario documented anywhere. Basically that external user was granted permission in SharePoint Online but that permission does not pass through to Azure RMS unless they use an O365 account. It fails because no Org ID actually is given permission (the permission is given to the Live ID). Then Office explicitly looks for an Org ID token that has right to open it, which is by design. When Office client opens the document, it needs to connect to the Azure RMS server using an Org ID. The reason that this is happening is because when a Live ID (non-O365 user) downloads a document from a SharePoint Online (SPO) protected library, SPO protects the doc with IRM by giving permission to your Live ID.
#Rms sharing app full
The only way to allow that external user to access the document is to change permission directly on the document itself using the “Change Permission” option in the yellow notification bar in the full Word client. You can request updated permissions from ” No matter what you choose here you will never be able to access the document. If that document is downloaded and then opened the user will receive and error stating “You do not have credentials that allow you to open this document. It can be viewed in the browser and the IRM policy can be viewed as working. Test Document 1 is in an IRM protected library and shared with an account. If a standard Live ID is used the document will be able only be able to be viewed in the browser. I have confirmed this scenario with Microsoft as being unsupported. What I found out was that:Īn IRM protected document that is shared to an external user, will not be able to be viewed after it is downloaded, unless they used an Office 365 ID to access the document. The situation revolved around a document that had an IRM policy applied to it and was shared with an external user. I have began working with IRM policies in Office 365 more often recently and ran into a situation that surprised me.
0 kommentar(er)
