Step 3: Evaluate Information Protection Readiness
Playbook Overview > Get Started > Step 1 > Step 2 > Step 3 > Step 4 > Step 5
Overview⚓︎
The third step in preparing your migration is to evaluate the readiness of your information protection policies to transition to the built-in labeling solution in Office.
Many of the capabilities of the AIP Add-in are already supported in the built-in labeling experience in M365 Apps for Enterprise. Over the next few months, we will continue to deliver improvements and new capabilities in the built-in client.
💡 Tip: Tune-in to the quarterly Office sensitivity labels newsletter to stay up-to-date with what's new and coming soon for information protection in Office apps.
💡 Tip: By enabling the built-in labeling client in M365 Apps, you can continue to use the AIP Scanner, AIP PowerShell, or AIP Classify and Protect.
Checklist⚓︎
- Use Comparison Guide to evaluate the roadmap status of all your AIP Add-in scenarios. The guide provides per-feature status, links to committed roadmaps, and change-management guidelines to help you evaluate each feature's transition.
- Use the generalized recommendations below to help you anticipate your adoption timelines based on a feature's roadmap. Refer to the Comparison Guide for each feature's roadmap.
| Scenario Roadmap | Migration Recommendations |
|---|---|
All scenarios are ✅ Supported or ⬛ Not Needed |
Time Horizon: Now 1. Start your migration today. Got to Step 5 to learn how to enable the built-in labeling client. |
At least one must-have scenario ⭐ In Preview or 🔷 In Development |
Time Horizon: 3-6 months 1. Start planning your migration now. Most of these capabilities will be available in Current Channel in the next 3-6 months. Review each feature's roadmap for specific timelines. 2. Join a preview program to start evaluating these capabilities. 3. Consider whether you will require the ⚙️ AIPException policy to avoid disabling the AIP Addin. |
At least one must-have scenario 🟨 In Planning |
Time Horizon: 6-12 months 1. Consider piloting supported features in a preview program while you prepare for remaining capabilities. 2. Consider whether all your users require 🟨 In Planning features and opportunity to deploy built-in labeling sooner for small population.3. Plan to use the ⚙️ AIPException policy to avoid having the AIP Addin disabled by default. |
At least one must-have scenario ⚫ Not Planned |
Time Horizon: Now 1. Evaluate the AIP Scanner, AIP PowerShell, or AIP Classify and Protect to replace the functionality you were using the AIP Add-in. 2. If you are unable to use built-in labeling for any users because At least one must-have scenario ⚫ Not Planned, contact your Microsoft support team to request a Design Change Request. The product team will evaluate this according to typical backlog triage. |
When you're ready, proceed to Step 4️⃣.