Currently marked as "In development" with a targeted General Availability window of October 2026 for Worldwide (Standard Multi-Tenant) cloud environments across Desktop, Web, and Teams and Surface Devices, the V2 roadmap entry outlines six major areas of improvement for managing tasks directly inside Copilot Chat. While roadmap dates and feature descriptions are always estimates subject to change before launch, contrasting these planned upgrades against Microsoft Support's documented current limitations reveals exactly where the first-generation chat agent hits a wall—and why project leads and IT administrators should pay close attention.
What Is Planned in the V2 Roadmap Update
The core premise of Planner Agent in Copilot Chat is straightforward: let users create, update, and manage both personal tasks and shared basic plans without having to leave their chat window and open the standalone Planner app. It surfaces priorities, deadlines, and at-risk work alongside interactive task cards so teams can keep projects moving inside their daily workflow.
Building on the initial summer rollout, Roadmap ID 573168 lists six planned improvements for the V2 iteration:
- Expanded Context and Larger Plan Support: Improved context handling paired with support for larger plans.
- Model Upgrades and Better Grounding: Higher-quality responses driven by underlying model upgrades, refined system prompts, and stronger enterprise grounding.
- Speed and Stability: Greater reliability and reduced latency for more consistent, responsive chat interactions.
- Broader Task Assignment Support: Expanded task management capabilities that specifically include wider support for assigning tasks.
- User Experience Refinements: Interface enhancements designed to make managing tasks and plans inside Copilot Chat more intuitive.
- Scheduled Task Catch-Ups: New proactive capabilities, specifically introducing scheduled task catch-ups.
Notice what is missing from Microsoft's roadmap entry: hard numbers and granular specifications. Microsoft does not specify which underlying AI model upgrades are being wired into the V2 agent, what the exact task-count threshold is for "larger plans," or how "scheduled task catch-ups" will be configured and delivered. Will a catch-up behave like a recurring prompt in Copilot Chat, or will it trigger an adaptive card summary on Monday mornings? Until the rollout moves from development into production tenants, those operational details remain unannounced.
Why V2 Matters: Examining Current Version 1 Constraints
To appreciate why "broader task assignment support" and "larger plans" are headlining the V2 roadmap, you have to look under the hood of the current implementation. Based on general industry knowledge of enterprise task management, a project assistant that can create a task but cannot hand it off to a colleague is only doing half the job.
According to Microsoft Support's official Frequently Asked Questions documentation for Planner Agent in Copilot, the current chat experience has strict guardrails around what it can and cannot touch:
| Feature Area | Current Documented V1 State (Microsoft Support) | V2 Roadmap Direction (ID 573168) |
|---|---|---|
| Supported Plan Types | Private tasks, Personal Basic Plans, recently opened Meeting Plans, and recently opened Shared Basic Plans. (Premium plans are not supported in this chat experience.) | Continues targeting personal tasks and shared basic plans, adding support for larger plans and better context handling. |
| Editable Task Fields | Task name, Progress, Start date, Due date, Priority, Plan name, New task notes, Buckets, and Goals. | Expands task management with broader task assignment support (Assignments are currently listed as non-editable in the V1 FAQ). |
| Unsupported Edits | Assignments, Checklists, Attachments, Labels, My Day, Existing task notes, Delete, and Undo actions. | No explicit mention of checklists, labels, or deletion in the V2 summary; focus is on assignments and UX enhancements. |
| Scale & Performance | Optimized for focused prompts on specific plans; Microsoft advises breaking large planning activities into smaller requests. | Targets greater reliability, reduced latency, and larger plan support. |
| Follow-Up Workflows | On-demand Q&A and draft reviews via interactive task cards. | Introduces scheduled task catch-ups. |
In the current version, if you ask the agent in Copilot Chat to modify task properties, Microsoft Support notes that editing is restricted to basic metadata like Name, Progress, Due date, Start date, Priority, and Plan name (alongside buckets, goals, and new task notes in the broader FAQ). Crucial collaborative fields—most notably Assignments, checklists, labels, attachments, and existing task notes—cannot currently be edited through the Planner Agent chat interface. Furthermore, delete and undo actions are unsupported, requiring users to open Microsoft Planner directly to clean up mistakes.
Similarly, when dealing with large-scale planning operations today, Microsoft Support explicitly advises users to work with a single specific plan and break large activities into smaller, focused requests. The plan picker in Copilot is also currently restricted to searching and filtering recently opened basic plans. By targeting larger plans, deeper context handling, and broader assignment support in V2, Microsoft is directly addressing the friction points that force power users to abandon the chat pane and jump back into the full Planner interface.
One Name, Two Experiences: Navigating Microsoft's Naming Maze
If you manage a Microsoft 365 tenant, you have likely noticed that Microsoft loves reusing product names until administrators need a flowchart just to explain licensing. "Planner Agent" is a prime example. Microsoft Support documentation actually describes two related but distinct experiences that share the Planner Agent branding:
- Planner Agent in Copilot Chat (The Target of Roadmap 573168): This is the conversational experience inside Microsoft 365 Copilot Chat (accessible via the web, desktop, or Teams by adding the agent from the Agent Store or invoking
@Planner Agent). It focuses on personal tasks and shared basic plans, uses interactive task cards to preview changes in draft mode before you approve them, and currently does not support Premium plans. - In-Plan Planner Agent (Project Manager Agent Capabilities): As detailed in separate Microsoft Support documentation for accessing Planner Agent directly inside a plan, there is also an in-plan collaborator experience available in both basic and premium plans. That in-plan agent acts like a team member that can have tasks assigned to it, execute work, generate tasks from goals, and write status reports. Access requires a Microsoft Copilot license, with certain premium capabilities tied to Planner Plan 1, Planner and Project Plan 3, or Planner and Project Plan 5 licensing.
Keeping this distinction clear is vital when reading the V2 roadmap. Item 573168 is specifically upgrading the Copilot Chat experience for personal tasks and shared basic plans—bringing stronger assignment handling and scheduled catch-ups into the central chat window rather than forcing users into individual project boards.
Enterprise Grounding, Security, and How to Prepare
What about the roadmap's promise of "higher-quality responses through model upgrades, refined prompts, and better grounding"?
According to Microsoft Support's documentation on enterprise grounding for Planner Agent in Copilot, the agent already pulls context from across your Microsoft 365 environment to identify action items, commitments, and follow-up work. Supported grounding sources currently include:
- Emails (including flagged emails)
- Word, Excel, PowerPoint, PDF, and other supported files stored in SharePoint and OneDrive or uploaded directly into a chat
- Teams chats and channel messages
- Meetings and meeting transcripts
- People and organizational relationship data
- Images contained within supported content
From a security and compliance standpoint, Microsoft Support states that Planner Agent only accesses content that the signed-in user already has permission to view within Microsoft 365. Furthermore, because AI models can occasionally misinterpret a casual remark in a meeting transcript as a binding project deadline, the agent presents generated tasks, plans, and updates in draft mode inside interactive task cards. Users can review, edit, approve, or reject those proposed updates before anything is written to an actual plan.
For Windows users and Microsoft 365 administrators preparing for the V2 improvements, here is the practical takeaway:
- Verify Your Access Path: Users with a Microsoft 365 Copilot license can test the current baseline by opening Microsoft Copilot for Work on the web, desktop, or Teams, selecting All agents in the left rail to add Planner from the Agent Store, or simply typing
@Planner Agentin Copilot Chat. Note that Microsoft Support also documents native Planner capabilities directly in standard Copilot "New chat" sessions without invoking a separate agent, so users may encounter overlapping task-management workflows. - Keep Human-in-the-Loop Habits: Even with V2's promised model upgrades and better grounding, always inspect the interactive task cards in draft mode before approving bulk task creations or plan edits.
- Treat October 2026 as a Target Window: Because Roadmap ID 573168 was just published on October 14, 2026, and remains in "In development" status for a targeted October 2026 General Availability release, rollout timing across Standard Multi-Tenant clouds could easily stretch or shift as final testing wraps up.
If Microsoft delivers on reduced latency, larger plan capacity, and the ability to actually manage task assignments directly inside Copilot Chat, the V2 update will close several of the most glaring gaps in the initial release—turning Planner Agent from a handy personal to-do helper into a far more capable team dispatcher.