Planner Agent in Microsoft 365 Copilot: action items from meetings and email as tasks

Every IT department, sales team, and project group recognises the pattern. A meeting ends with a list of agreed actions, someone says they will send the action items afterwards, and three working days later most of them have not been followed up. Not because people are forgetful, but because the gap between a verbal commitment and a concrete task in a planner has always required manual effort. Microsoft has now closed that gap. The Planner Agent in Microsoft 365 Copilot is generally available and does exactly this: it listens in on meetings and email, recognises action items, and converts them into tasks in Microsoft Planner.

This is no longer a preview feature. The Planner Agent was broadly rolled out to all Microsoft 365 Copilot licence holders in September 2026, with draft mode as the default working method so that the human always has the final say.

What does the Planner Agent do?

The Planner Agent is an AI agent active within Microsoft 365 Copilot that has access to Teams meeting transcripts, the Outlook inbox, and documents shared in chat or email. After a meeting, the agent analyses the transcript and recognises three types of elements: action items with an owner, deadlines or time indicators, and questions requiring follow-up. Those elements are converted into Planner tasks and staged for approval in the relevant team plan.

The agent works in the background, without participants needing to take any extra steps during the meeting itself. Only after the meeting do the draft tasks appear as interactive cards in the Teams chat. Owners can review, adjust, and approve them in under a minute.

Action items from Teams meetings

The most direct application is processing Teams meetings. When a meeting has been recorded and transcribed, the Planner Agent automatically reads through the transcript. It detects phrases such as 'you are taking that on, right?' or 'this needs to be done by Friday' and links them to the appropriate participant. The result is a set of proposed tasks that appear directly in the Teams chat, including name, description, and a deadline if one was mentioned.

All AI-generated tasks land in draft mode by default. The participant or meeting owner reviews the drafts, adjusts them where needed, and approves them. Only then are they definitively added to the Planner board. This is a deliberate choice by Microsoft: the agent assists, the human decides. For sensitive or complex projects, that is not a limitation but an advantage.

Tasks from email and documents

The Planner Agent does not only work with meetings. It can also be applied to Outlook emails and shared documents. When a client sends an email containing several requests, the agent recognises those requests, converts them into draft tasks, and links them to the appropriate project in Planner. When a colleague shares a Word document with review comments, the open remarks are converted into follow-up tasks for the relevant people.

This makes the agent particularly valuable for customer-facing teams and project managers who need to convert a large volume of loose communication into structured follow-up. The manual translation step between an incoming request and a planned task largely disappears, without losing oversight of the Planner board.

Draft mode: the human approval step

A core principle of the Planner Agent is that all AI actions begin in draft mode. The agent makes a proposal but never autonomously applies changes to a definitive Planner board. This is both a safety measure and a quality consideration. AI models generally understand context well, but nuances or team-internal priorities are not always derivable from a transcript.

The workflow in Teams chat is straightforward: the agent displays the draft tasks as interactive cards, the owner clicks to approve, adjust, or reject, and that is it. The threshold is low enough that it takes considerably less time than taking manual notes, while quality control is preserved.

Configuration and requirements

The Planner Agent is available to users with a Microsoft 365 Copilot licence. That licence is an add-on to an existing M365 licence and requires at least Microsoft 365 Business Standard, E3, or a higher SKU. IT administrators activate the agent through the Copilot settings in the Microsoft 365 Admin Center, where per user group they can configure which Copilot agents are available.

An important consideration: the agent only works with meetings for which a transcript is available. Transcription is disabled by default in Teams. Administrators can enable this via a meeting policy in the Teams Admin Center, or meeting owners can do so per meeting. Anyone who wants to get the most out of the Planner Agent should first ensure that Teams transcription is structurally configured for the relevant meeting groups.

Integration with existing Planner boards

The Planner Agent links tasks to existing plans in Microsoft Planner. IT administrators can configure which plans are available as destinations for the agent. For organisations already actively using Planner or Microsoft To Do, the integration is nearly seamless: tasks land directly in the existing structure, including the right bucket and the right team.

The agent can also create new plans when an action has no existing plan to link to. In that case, the agent proposes a name based on the meeting name or the project mentioned in the transcript. That proposal also appears as a draft first.

How to get started

Three concrete steps for teams that want to deploy the Planner Agent. First, verify that your organisation has Microsoft 365 Copilot licences and for which users they are active. Second, enable Teams transcription via the meeting policy for the relevant groups, because without transcription the agent has no input to process. Third, start with a pilot group of two to three teams that meet frequently and struggle with structured follow-up. Evaluate after two weeks how much manual note-taking work has been replaced and adjust the scope accordingly.

The step from meeting to action used to be a matter of personal discipline. With the Planner Agent, it has become a configuration question. Want help activating Copilot agents in your environment, setting up an efficient Planner structure, or drafting an adoption strategy? Contact Zarioh.