(Updated) Connect Teams meeting to existing Planner Plans
Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.
Rollout
- Ends
- 1 Mar 2027
- Roadmap
- 561490
- Platforms
- Desktop, TeamsAndSurfaceDevices
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
- Microsoft's start date
- 15 Jun 2026
- Last changed by Microsoft
- 12 Oct 2026
- First seen here
- 19 Oct 2026
- Versions seen
- 1
What the notice says
Microsoft's text, with its sections, lists and tables; source markup removedUpdated October 12, 2026: We have updated the timeline. Thank you for your patience.
Introduction
We are introducing a new capability that allows users to connect Microsoft Teams meetings to existing Microsoft Planner plans.
Currently, Teams meetings automatically create separate Planner plans for meeting-related tasks, which can result in tasks for the same initiative being spread across multiple plans. This update enables users to link meetings to an existing plan so tasks can be tracked in a single location, improving organization and continuity across ongoing work.
This message is associated with Roadmap ID 561490.
When this will happen
- Targeted Release (Worldwide): We will begin rolling out in late December 2026 (previously late September) and expect to complete by end of January 2027 (previously end of September 2026).
- General Availability (Worldwide): We will announce via Message center when we are ready to proceed.
How this affects your organization
Who is affected
- Users who create or participate in Microsoft Teams meetings and use Microsoft Planner
- Organizations with Teams, Planner, and Loop enabled
What will happen
- Users will be able to link a Teams meeting to an existing Planner plan.
- Tasks created during meetings can be added to the selected existing plan.
- If no plan is selected, meetings will continue to create a new Planner plan.
- This feature will be available by default.
- Facilitator (the meeting task automation capability) can create tasks in the selected plan.
- Users can manually create tasks if Facilitator is disabled.
- No changes to existing plans or previously created plans.
Learn more: Facilitator in Microsoft Teams meetings | Microsoft Support
What you can do to prepare
- No action is required.
- You may want to:
- Ensure that Teams, Planner, and Loop are enabled in your tenant.
- Review whether Facilitator should be enabled for automated task creation scenarios.
- Update internal documentation or task management guidance if applicable.
- Inform helpdesk staff and users about this new option for organizing meeting tasks.
Compliance considerations
| Question | Explanation |
|---|---|
| Does the change alter how existing customer data is processed, stored, or accessed (e.g. documents, emails, chats, etc.), if so how and to what extent? | Tasks created in Teams meetings can now be stored in an existing Planner plan instead of a new auto-generated plan, changing how task data is organized across plans. |
| Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data, if so summarize changes? | Facilitator can create and associate tasks with user selected Planner plans when enabled. |
| Does the change include an admin control and, can it be controlled through Entra ID group membership? | Availability depends on enabling Teams, Planner, Loop, and optionally Facilitator in the tenant. |
| Does the change allow a user to enable and disable the feature themselves? | Users can choose whether to link a meeting to an existing plan or continue using the default behavior. |
What changed
Between the versions this installation saw, newest firstThis installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
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.
- Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.