But if not, RMS for individuals lets users create a free account, or a Microsoft account can be used for applications that support this authentication for Azure Information Protection. Many organizations already have user accounts in Azure AD because they are running Azure services or have Microsoft 365. That means your users can be authenticated even when they are not connected to your internal network and it is easier to share protected content with users from other organizations. That makes this cloud solution quicker to deploy and easier to maintain.Īzure Information Protection uses Azure AD for authentication - for both internal users and users from other organizations. Some of the main differences for Azure Information Protection include: DifferenceĪzure Information Protection doesn't require the additional servers and PKI certificates that AD RMS needs, because Microsoft Azure takes care of those for you. If you know or have previously deployed Active Directory Rights Management Services (AD RMS), you might be wondering how Azure Information Protection compares in terms of functionality and requirements as an information protection solution.

The classic client will be officially retired, and will stop functioning, on March 31, 2022.Īll current Azure Information Protection classic client customers must migrate to the Microsoft Information Protection unified labeling platform and upgrade to the unified labeling client. No further support is provided for the classic client and maintenance versions will no longer be released.

To provide a unified and streamlined customer experience, the Azure Information Protection classic client and Label Management in the Azure Portal are deprecated as of March 31, 2021.

Compare mac email clients