Updated on 2015-12-01 to work with the release version of the Azure RMS PowerShell cmdlets.
File Classification Infrastructure (FCI) is a built-in feature on Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 that helps IT admins to manage their organization's data on file servers by providing automatic classification processes. Using rules which are constructed with regular expressions, PowerShell, and/or .NET or native modules, FCI can identify sensitive files and perform actions such as encrypting Microsoft Office documents with Rights Management Services (RMS) , expiring files that have passed a defined date limit, or other custom action (defined through a script/program). FCI provides an extensible infrastructure that enables organizations to construct rich end-to-end classification solutions built upon Windows. For more information on FCI please check this blog post .
By default, FCI's built-in tasks can only encrypt Microsoft Office documents with Rights Management Services (RMS). By using a custom FCI task and the Rights Management (Microsoft.Protection) cmdlets, IT admins can apply RMS protection to any file in a file share. Once the files are protected, only authorized users will be able access those files even if they are copied to another location. This blog post covers how to use Azure RMS with your File Server in the case that your File Server is directly connected to the Internet. A follow up blog post will be added demonstrating how to use Azure RMS without connecting your File Server directly to the Internet.
To use Azure RMS with your File Server, you will need to configure an AAD Service Principal which has been authorized on your Azure RMS Tenant and at least one RMS Template. This guide assumes that you have already configured this with Azure RMS; further instructions about how to do this can be found here .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.