Microsoft is bringing Planner into the new Outlook for Windows, giving users another reason to spend more time in the modern Outlook client instead of Outlook Classic. Windows Latest reports that Planner is beginning to roll out in the new Outlook sidebar, with broader availability expected by the end of August 2026. Microsoft To Do remains the familiar task experience in Outlook Classic, but the practical signal is that Planner is becoming the strategic task surface for Microsoft 365 work.

This is not just a cosmetic sidebar change. It reflects Microsoft’s broader direction for productivity: email, calendar, tasks, Office apps, and Copilot are being pulled into a more unified Microsoft 365 workflow. That direction may be sensible for many cloud-first organizations, but it also creates a planning problem for users and administrators who still rely on Outlook Classic for mature desktop features.

What Microsoft is adding

Planner in the new Outlook is intended to reduce context switching. Users can work with tasks from the same application where they handle mail and calendar activity, rather than jumping between Outlook, To Do, Planner, Teams, and a browser. According to Windows Latest, Microsoft says the integration is based on customer feedback asking for task management to sit closer to daily productivity workflows.

Importantly, Planner in the new Outlook does not require Microsoft 365 Copilot. That should make the rollout relevant to a much wider set of tenants than Copilot-only features. Users who already manage team plans in Planner may find the sidebar convenient, especially when tasks are connected to meetings, messages, projects, or Microsoft 365 Groups.

For organizations, however, the feature also raises information architecture questions. Planner and To Do overlap, but they are not identical. To Do has been widely used for personal task lists and flagged email workflows. Planner is stronger for shared plans, buckets, assignments, and organization-level task coordination. If both tools are available without guidance, users may scatter work across multiple task systems and then lose track of what is authoritative.

What this means for Microsoft To Do

Microsoft To Do is not disappearing overnight, and many users will continue to depend on it. But the direction of travel is clear: To Do appears to be in a quieter maintenance phase, while Planner is receiving more visible placement in the Microsoft 365 experience. For IT teams, the risk is not immediate breakage; it is slow drift.

Slow drift can be harder to manage than a formal retirement announcement. Users may notice that tutorials, support articles, Copilot experiences, and new Outlook features increasingly reference Planner. Meanwhile, Outlook Classic users may remain comfortable with To Do and wonder why the newer task experience is not arriving in their client. That split can create inconsistent training, inconsistent support scripts, and inconsistent expectations across departments.

A practical response is to define task use cases. For example, personal reminders and individual follow-ups may still fit To Do. Team projects, recurring operational checklists, campaign work, and cross-functional assignments may belong in Planner. If your organization uses another work management system such as Jira, Azure DevOps, ServiceNow, or Asana, be explicit about where Planner should not be used.

Outlook Classic is still a special case

The new Planner integration also underscores Microsoft’s posture toward Outlook Classic. Windows Latest reports that Microsoft is not planning to bring Planner to Outlook Classic. Classic Outlook continues to receive maintenance, selected performance improvements, and AI-powered additions, but it is no longer the main destination for non-AI feature growth.

That does not mean every organization should move immediately. Outlook Classic remains important because many users still depend on capabilities that are either missing, different, or less mature in the new Outlook. Examples commonly include advanced mailbox workflows, PST-related scenarios, shared mailbox habits, add-ins, offline expectations, and long-established power-user behaviors.

Microsoft is also improving some Classic Outlook areas. Windows Latest notes a shift for shared calendars from older MAPI-based behavior toward a more modern REST-based model, which should improve sync and performance. That is useful, but it does not change the strategic pressure: Microsoft wants more users in the new Outlook, and feature placement is one way to encourage the move.

Recommended steps for Microsoft 365 admins

First, identify who is actually using Outlook Classic, the new Outlook, Outlook on the web, and mobile clients. Many organizations assume they know, but usage is often fragmented by department. A migration plan based on assumptions will miss critical workflows.

Second, pilot Planner in the new Outlook with users who already understand Planner. Ask them whether the sidebar saves time or simply creates another place to check. Evaluate notifications, task creation from email, plan visibility, and permission behavior. The goal is to validate the workflow, not merely confirm that the icon appears.

Third, publish a simple task management standard. Tell users when to use To Do, when to use Planner, and when to use a line-of-business work tracking system. Without that guidance, adding Planner to Outlook can increase convenience while reducing organizational clarity.

Finally, treat Outlook migration as a workflow project rather than a client swap. If users remain on Outlook Classic because of shared mailboxes, add-ins, archives, or specialized calendar operations, document those blockers. If the new Outlook is good enough for a group, move that group intentionally and train them on Planner at the same time.

Bottom line

Planner’s arrival in the new Outlook is another sign that Microsoft’s productivity roadmap favors the modern Outlook and Microsoft 365 web-connected experiences. The change may be useful, especially for teams that already manage work in Planner, but it also widens the gap between new Outlook and Outlook Classic. Administrators should use this moment to clarify task management standards, pilot the new workflow, and make Outlook migration decisions based on real user requirements rather than pressure from a sidebar icon.

Source: Windows Latest source