Microsoft Planner: Support for Microsoft Information Protection (MIP) content sensitivity labels
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
- Roadmap
- 523819
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
Schedule dates changed in the text
Date phrases in schedule sentences differ between the versions this installation saw- Seen 13 Jan 2026
mid-December 2025→ late January 2026
Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.
What the notice says
Microsoft’s text, safely structuredUpdated January 13, 2026: We have updated the timeline. Thank you for your patience.
Introduction
Microsoft Planner will soon support Microsoft Information Protection (MIP) sensitivity labels at the content level. This enhancement enables encryption, restricts unauthorized actions such as copying, printing, or exporting plan contents, and adds visual markings like watermarks for clear sensitivity awareness. By enforcing content-level protections, Planner helps organizations prevent data leaks, maintain compliance, and enable secure collaboration without impacting productivity. This update aligns Planner with Microsoft Purview standards for consistent enforcement of security and data protection policies.
This message is associated with Microsoft 365 Roadmap ID 523819.
When this will happen
General Availability (Worldwide): Rollout will begin in early December 2025 and is expected to complete by late January 2026 (previously mid-December 2025).
How this affects your organization
Who is affected: Admins and users of Microsoft Planner across Microsoft 365 tenants.
What will happen
- Planner will support Microsoft Information Protection (MIP) sensitivity labels at the content level.
- Container-level labels (already supported) control who can join a plan and enforce restrictions like guest access and sharing limits.
- Content-level labels (new):
- Block copy, print, and export actions.
- Enforce read-only access for highly confidential plans.
- Restrict duplicating or exporting plans.
- Feature will be enabled by default and progressively available across all tenants by December 15, 2025.
Screenshot 1: Label Picker
Screenshot 2: Label Details
Screenshot 3: Label induced restrictions
What you can do to prepare
- No changes are required for existing labels.
- Review Purview label protection settings (copy/print/export restrictions) and confirm RMS usage rights align with expected Planner behaviors.
- Update governance guidance and user training for label behaviors in Planner.
- Update help and user training for label behaviors in Planner.
Learn more: Learn about sensitivity labels (updates in progress)
FAQ
Question: What label types does Planner support now? Answer: Planner has long supported container‑level labels (Teams/M365 Group/roster access controls). With this release, Planner adds enforcement for content‑level labels (block copy/print/export, read‑only, etc.) on plans and tasks consistent with Microsoft Purview policies and RMS usage rights.
Question: Which plan types are covered and when? Answer: Rollout begins with Roster Plans followed by Group‑backed Plans.
Question: Do I need to change any Purview policies or configurations? Answer: No changes are required for existing labels; however, you should review label protection settings (e.g., copy/print/export restrictions) and confirm RMS usage rights align with expected Planner behaviors. Update governance guidance accordingly.
Question: How does this interact with Loop and Teams meeting notes/TLC? Answer: Loop meeting notes apply a single content label across the page and its components (including Task List components (TLC)). Planner now inherits and enforces those restrictions on the corresponding roster plan, preventing prior sync breaks when restrictive labels were applied.
Question: What happens to guest/external users under different label combinations? Answer: Container labels determine who can be added; content labels determine what actions are permitted. For example, guests can be added when the container allows it, but content‑level restrictions may prevent plan access or actions (copy/export/print).
Question: Who can change a plan’s sensitivity label? Answer: Typically, owners/editors with the appropriate rights can change labels. Permissions are enforced service‑side and reflected in the UI according to RMS usage rights.
Compliance considerations
No compliance considerations identified, review as appropriate for your organization.
What changed
Between archive captures, newest first- Tags
New feature, User impact, Admin impact→ Updated message, New feature, User impact, Admin impact
Updated January 13, 2026: We have updated the timeline. Thank you for your patience. Introduction Microsoft Planner will soon support Microsoft Information Protection (MIP) sensitivity labels … will begin in early December 2025 and is expected to complete by late January 2026 (previously mid-December
2025.2025). How this affects your organization: Who is affected: Admins and users of …- Tags
- · first version seen
Learn more
Links from the notice and their documentation checksRelated public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.