How Windows file servers that use FCI support Azure Rights Management
When you configure Windows Server to use File Classification Infrastructure, this File Server Resource Manager feature can scan local files and determine whether they contain sensitive data. For files that meet this criteria, they are tagged with classification properties that an administrator defines. The File Classification Infrastructure can then take automatic action, according to the classification. One of these actions includes applying information protection by using Azure Rights Management and the deployment of the Rights Management connector (also known as the RMS connector). Office files are then automatically protected by Azure RMS.
To protect all file types, do not use the RMS connector, but instead, run a Windows PowerShell script that uses cmdlets from the Azure Information Protection module.
The classification policies are fully configurable and highly extensible so that you can prevent potential data leakage from unauthorized and authorized users. It can even help to reduce the risk of data leakage by network administrators because you can configure policies that don’t require these administrators to have access to the files.
For instructions to deploy and configure the RMS connector for Office files, see Deploying the Azure Rights Management connector.
For instructions to use the Windows PowerShell script for all file types, see RMS Protection with Windows Server File Classification Infrastructure (FCI).
Now that you understand how applications and services support Azure RMS, you might be interested in comparing Azure RMS with the on-premises version of Rights Management, Active Directory Rights Management Services (AD RMS). For a comparison of features, requirements, and security controls, see Comparing Azure Rights Management and AD RMS.
Send feedback about: