A project management dashboard displays task assignments, progress indicators, and a timeline in a browser window.
Microsoft has put a new item on the Microsoft 365 roadmap that Planner users with sprawling projects have been waiting for. It's called "Task Hierarchy for Unified Plans" (roadmap ID 580879). The listing says it will bring nested tasks to Planner so complex work is easier to structure and execute. It's still a plan on paper, so here is what the listing confirms, what it leaves out, and what you can do in the meantime.

A project management dashboard displays task assignments, progress indicators, and a timeline in a browser window. What the roadmap entry says​

The listing's details are short:

  • Product and platform: Planner, on the web.
  • Status: In development.
  • Release ring: General Availability.
  • Cloud instance: Worldwide (Standard Multi-Tenant).
  • Estimated general availability: March 2027.

The cloud instance matters. "Worldwide (Standard Multi-Tenant)" is the standard commercial cloud. The listing doesn't mention GCC, GCC High or DoD tenants. Microsoft's Planner FAQ already says some premium capabilities have been unavailable in those environments, so government admins should not assume this feature will reach them on the same schedule.

Microsoft's roadmap carries its usual caveat. The Microsoft Copilot Roadmap provides estimated release dates and descriptions for commercial features, and all information is subject to change. Treat March 2027 as a planning estimate, not a promise. I could not open the live roadmap entry itself, so the details above come from the listing as submitted.

What the listing doesn't tell us​

The entry is a one-line description, and several questions that matter to administrators and project managers are unanswered:

  • How many levels of nesting will be allowed.
  • Whether parent tasks can be assigned, scheduled or completed independently of their children.
  • Whether dates, status or progress roll up from child tasks to parents. Nothing in the listing says they will.
  • Which plan types and licenses will get the feature: basic plans, premium plans, or both.
  • How the hierarchy will appear in Grid, Board, Schedule, Timeline and Teams views.
  • Whether exports, automation or APIs will support it.

Until Microsoft publishes documentation, anything beyond "nested tasks, web, March 2027, in development" is speculation. Plan around the unknowns rather than assuming answers.

How this fits with what Planner has today​

Planner is Microsoft's unified work-management app. Microsoft's own FAQ describes it as combining the simplicity of To Do, the collaboration of Planner, the power of Microsoft Project and the intelligence of Copilot. The FAQ says the new Planner web experience reached general availability in fall 2024. It also says Project for the web was retired in August 2025, with premium plans moving into Planner.

That history is why a task hierarchy feature is relevant. Planner now has to serve three groups: people with a personal to-do list, teams running shared boards, and project managers who used to live in Project for the web.

Subtasks already exist, with a licensing catch​

Microsoft's FAQ says subtasks and dependencies are available in Planner with a Planner and Project Plan 3 license, and tells users to create a premium plan to get those Project for the web features. A Microsoft Q&A answer from an independent advisor in October 2025 says the same thing from the user's side. It says true hierarchical subtasks are a premium feature, and basic plans show only standalone tasks in board or bucket view. The same answer notes that what many people call subtasks in basic plans are really checklist items, and that these do not appear as cards in Bucket view.

Neither source says whether the new roadmap item is the same as premium subtasks, an extension of them, or something new for basic plans. The listing alone can't settle that, and it would be a mistake to read it as "subtasks for everyone." Licensing is the first thing admins should watch for when Microsoft publishes more detail.

Connected plans: the current approach to big work​

Planner already has a way to handle work that needs its own space: connected plans. Microsoft's support documentation says to use them when a task needs more detailed planning, linking it to another plan so the team can manage the detailed work there. The documented example is a client implementation project with a "Configure integrations" task. That task links to a separate "Integration delivery" plan where the team breaks down the work, assigns owners and manages dates.

This is a link between two plans, not nesting inside one plan. Microsoft's guidance says the main plan and the connected plan track progress independently, so you review progress in the connected plan and update the main task's status yourself.

Connected plans: how to use them now​

Microsoft's steps apply to Planner on the web or in Teams. You start in a basic plan you can edit.

To create a new connected plan:

  1. In your main plan, select More options for the task in Grid view, or open the task details and select More options.
  2. Select Connect to a plan, then New plan.
  3. Choose Create your own plan for an empty plan, or pick a template. Select Continue, and for an empty plan select Create basic plan.
  4. Keep the suggested plan name or enter your own, and review the Share with your group setting and the other plan settings.

To connect an existing plan:

  1. Open the task details in your main plan.
  2. Select More options, then Connect to a plan, then Existing plan.
  3. Pick the plan under Select a plan to connect, then select Connect plan.

Things to know:

  • Premium plans do not appear as an option when you connect an existing plan. The connected plan must be a basic plan you can access.
  • Connected plans keep their own permissions. Someone who isn't a member of that plan's group is notified when they try to open it and can ask the plan owner for access.
  • To connect a task to a different plan, disconnect the current one first.
  • Disconnecting removes the link only. The connected plan and its tasks are not deleted or changed.

To move between plans, select the Planner icon to the left of the task name, or use the connected plan link in the task details pane. To return, use the connected plans indicator at the top of the connected plan and pick the main plan.

Analysis: why this matters, and the caveats​

My reading is that nested tasks are the obvious next step. Connected plans suit large workstreams, but they are heavy for small breakdowns. Not every parent task needs its own plan, with its own members, permissions and progress tracking. A hierarchy inside a single plan could fill that gap. That is my interpretation of the stated goal of clearer structure and easier execution, not a confirmed specification.

There are also reasons for caution:

  • Roll-up behavior is unconfirmed. Hierarchies often invite expectations that parent progress will be calculated from children. The listing does not promise that.
  • Licensing could split users. If the feature lands only in premium plans, it overlaps with what Planner and Project Plan 3 already offers. If it lands in basic plans, it narrows the gap between tiers. Neither is established.
  • Web first. The listed platform is the web. Teams and mobile parity is unaddressed, and Microsoft has said most new Planner capabilities arrive first on desktop and web.
  • Dates slip. Roadmap estimates move, and entries get removed once features ship or are cancelled.

What admins and project leads can do now​

  1. Note the date, then hold it loosely. March 2027 is a target.
  2. Audit your plans. Identify large tasks that currently live as checklists or as separate plans, since those are the likeliest candidates for restructuring.
  3. Use connected plans for genuine workstreams. Don't build a long-term process on the assumption that nested tasks will behave like connected plans.
  4. Check your license mix. Know who has Planner in Microsoft 365, Planner Plan 1, or Planner and Project Plan 3 and 5, because eligibility will probably matter.
  5. Watch the roadmap entry and the Message Center. Details such as nesting depth, permissions and licensing typically appear there as the date approaches.

Bottom line​

Microsoft lists a Planner web feature for nested tasks, in development, targeting March 2027 in the Worldwide standard cloud. It signals that Planner's task structure is getting more capable. It does not yet tell us how deep the nesting goes, who gets it, or how progress will behave. Until it ships, connected plans are the documented way to manage detailed work, and premium plans are where hierarchical subtasks already exist today.

 

References

  1. Planner: Task Hierarchy for Unified Plans Microsoft 365 Roadmap 2026-11-17T18:36:41.967573Z
  2. Microsoft Copilot Roadmap | Microsoft 365 microsoft.com
  3. Use connected plans in Microsoft Planner | Microsoft Support support.microsoft.com