Azure Information Protection deployment roadmap for protection only
Applies to: Azure Information Protection, Office 365
Relevant for: Azure Information Protection classic client for Windows. For the unified labeling client, see AIP deployment roadmap for classification, labeling, and protection.
To provide a unified and streamlined customer experience, we are sunsetting the Azure Information Protection classic client and Label Management in the Azure Portal as of March 31, 2021. No further support is provided for the classic client, and maintenance versions will no longer be released.
- The classic client will be fully retired, and will stop functioning, on March 31, 2022.
- As of March 18, 2022, we are also sunsetting the AIP audit log and analytics, with a full retirement date of September 31, 2022.
The content in this article is provided to support customers with extended support only. For more information, see Removed and retired services.
Alternatively, you may be looking for one of the following articles:
Use the following steps as recommendations to help you prepare for, implement, and manage Azure Information Protection for your organization, when you want to implement data protection only.
This roadmap is recommended for customers with a subscription that doesn't support both classification and labels, but does support protection without labels. You must have the AIP classic client installed.
Perform the following steps:
- Confirm that you have a subscription that includes the AIP protection service
- Prepare your tenant to use Azure Information Protection
- Install the Azure Information Protection classic and client configure applications and services for Rights Management
- Use and monitor your data protection solutions
- Administer the protection service for your tenant account as needed
Confirm that you have a subscription that includes the AIP protection service
Verify that your organization has a subscription that includes the functionality and features you expect. Assign a license from this subscription to each user in your organization who will protect documents and emails.
Do not manually assign user licenses from the free RMS for individuals subscription and do not use this license to administer the Azure Rights Management service for your organization.
These licenses display as Rights Management Adhoc in the Microsoft 365 admin center, and RIGHTSMANAGEMENT_ADHOC when you run the Azure AD PowerShell cmdlet, Get-MsolAccountSku.
For more information about how the RMS for individuals subscription is automatically granted and assigned to users, see RMS for individuals and Azure Information Protection.
Prepare your tenant to use Azure Information Protection
Before you begin using the protection service from Azure Information Protection, do the following preparation:
Set up your user accounts and groups for AIP
Make sure that your Microsoft 365 tenant contains the user accounts and groups that will be used by Azure Information Protection to authenticate and authorize users from your organization. If necessary, create these accounts and groups, or synchronize them from your on-premises directory.
For more information, see Preparing users and groups for Azure Information Protection.
Decide how you want to manage your tenant key
Decide whether you want Microsoft to manage your tenant key (the default), or generate and manage your tenant key yourself (known as bring your own key, or BYOK). For additional security, implement "hold your own key" (HYOK) protection.
For more information, see Planning and implementing your Azure Information Protection tenant key.
Install PowerShell for AIP
Install the PowerShell module for AIPService on at least one computer that has internet access. You can do this step now, or later.
For more information, see Installing the AIPService PowerShell module.
Make sure that the protection service is activated so that you can begin to protect documents and emails. If you are deploying in phases, configure user onboarding controls to restrict users' ability to apply protection.
For more information, see Activating the protection service from Azure Information Protection.
Configure optional features as needed
Consider configuring either of the following features, either now or later.
Feature Description Custom templates for protection settings If the default templates are not sufficient for your organization, configure custom templates. For more information, see Configuring and managing templates for Azure Information Protection. Usage logging Configure usage logging to monitor how your organization is using the protection service. For more information, see Logging and analyzing the protection usage from Azure Information Protection.
Install the Azure Information Protection classic and client configure applications and services for Rights Management
Perform the following steps:
Deploy the Azure Information Protection classic client
Install the classic client for users to protect files other than Office documents and emails, and to track protected documents, and provide user training for this client. For more information, see Azure Information Protection classic client for Windows.
Configure Office applications and services
Configure Office applications and services for the information rights management (IRM) features in SharePoint or Exchange Online.
For more information, see Configuring applications for Azure Rights Management.
Configure the super user feature for data recovery
If you have existing IT services that need to inspect files that Azure Information Protection will protect—such as data leak prevention (DLP) solutions, content encryption gateways (CEG), and anti-malware products—configure the service accounts to be super users for Azure Rights Management.
For more information, see Configuring super users for Azure Information Protection and discovery services or data recovery.
Protect existing files in bulk
You can use PowerShell cmdlets to bulk-protect or bulk-unprotect multiple file types.
For more information, see Using PowerShell with the Azure Information Protection client from the admin guide.
For files on Windows-based file servers, you can use these cmdlets with a script and Windows Server File Classification Infrastructure. For more information, see RMS protection with Windows Server File Classification Infrastructure (FCI).
Deploy the connector for on-premises servers
If you have on-premises services that you want to use with the protection service, install and configure the Rights Management connector.
For more information, see Deploying the Azure Rights Management connector.
Use and monitor your data protection solutions
You're now ready to protect your data, and log how your company is using the protection service.
For more information, see:
- Helping users to protect files by using the Azure Rights Management service
- Logging and analyzing the protection usage from Azure Information Protection
Administer the protection service for your tenant account as needed
As you begin to use the protection service, you might find PowerShell useful to help script or automate administrative changes. PowerShell might also be needed for some of the advanced configurations.
For more information, see Administering protection from Azure Information Protection by using PowerShell.