- [Instructor] One of the fairly common server roles
that takes advantage of federated identity
is the Rights Management Service role.
This is an on-premises server role
that can be used to protect the content
of your company's data and even email.
RMS uses federated identity to recognize users
and applies RMS templates to secure content
inside of files and emails.
There are already ways to secure entire documents in place
through sharing permissions and the like.
What RMS adds is protection
over the content inside the document.
Using RMS templates you can disable buttons
and supported applications.
You can turn off save as and other buttons
that might allow content to leave your network.
You can even shutdown the forward option
on protected emails to prevent sensitive information
from being moved outside the organization.
This role is not new to Windows Server 2019.
It installs, configures, and runs the same
as it did in Windows Server 2016 and earlier.
The reason I wanted to bring it up in this course
is right in line with the changes I mentioned
for Active Directory Federation Services.
The use of the cloud in hybrid environments
has changed a few things
about how users access protected content.
If you're currently protecting content
stored in Azure spaces,
you're likely using Azure Information Protection
instead of RMS.
The Azure tools are designed
to better handle the nature and volume of requests
as well as providing security
that aligns with cloud computing practices.
This is important for companies that use RMS
to protect content of files
that are meant to be shared throughout
and possibly outside of the company.
Microsoft has for some time now
supported a client application
for Windows, Mac, and mobile platforms
designed to grant access to RMS protected client.
This rights management sharing application
reads RMS security details and works with RMS
to grant appropriate privileges to the content.
With the combination of RMS
and Azure Information Protection being used,
Microsoft has to make a choice
on how to best support this type of sharing
because AIP is not RMS.
What they came up with is a new application.
The RMS sharing application
is going to be out of support as of 2019.
A new AIP client application has been introduced
that does support RMS connections.
If your company has been using the RMS client for awhile
to access protected client from a partner organization
or if you're using RMS to share with people
outside your directory, it may be time to make the shift
to that new client application.
It may even be time to look at Azure solutions
to see what other benefits you could gain
by implementing this cloud solution
to protect your proprietary data.