What Microsoft Purview licenses are required for Auto-Labeling and Records Information Management?

Question

Can someone clarify the exact licensing needed in Microsoft Purview to enable auto-labeling across Exchange, SharePoint, OneDrive, and Teams, as well as advanced IRM features like disposition reviews and regulatory records? If you have implemented this recently, what licensing path worked for you?

Answer 1

To answer your question, the first thing you need to check is what licensing you already have.

• If you’re on Microsoft 365 E5, then you automatically get everything you need. E5 already includes auto-labeling across Exchange, SharePoint, OneDrive, and Teams, and it also covers all the advanced Records and Information Management features like disposition review and regulatory records.

If you’re on Microsoft 365 E3, then those features are not included by default. You can either stay on E3 and add the E5 Compliance add-on, which unlocks both auto-labeling and advanced records, or you can upgrade fully to E5.

So, the licensing you need depends entirely on your current plan. Once you confirm that, it becomes very clear which path to take.

Answer 2

To enable auto-labeling across Exchange, SharePoint, OneDrive, and Teams, as well as advanced Information Rights Management (IRM) features like disposition reviews and regulatory records in Microsoft Purview, you will need the following licenses:

1. Microsoft 365 E5/A5/G5 or Microsoft 365 E5/A5/G5 Compliance: These licenses provide the necessary capabilities for auto-labeling and advanced IRM features.
2. Microsoft Purview Information Protection (Plan 2): This plan is specifically required for automatic sensitivity labeling across the mentioned services.

Additionally, for users to benefit from the services, they must have the appropriate licenses assigned. For example, a standard/Plan 1 license must be assigned alongside any premium licenses for users to access sensitivity labeling features.

For more detailed information on the licensing requirements, you can refer to the Microsoft documentation on sensitivity labels and licensing guidance.