The item is marked In development. It targets Desktop and Web in the Worldwide (Standard Multi-Tenant) cloud, on the General Availability release ring, with an estimated GA date of January 2027. Microsoft's roadmap says all dates are estimates and subject to change. Features can be removed from the roadmap, postponed or cancelled.
What Microsoft has actually committed to
Here is what the roadmap entry confirms:
- A product backlog where work can be organized and prioritized
- Time-boxed sprints that teams plan in advance
- A current-sprint focus, so the team sees what is in flight now
- Buckets stay as they are, separate from sprint planning
- Scope: Desktop and Web, Worldwide standard multi-tenant cloud, GA estimated for January 2027
The entry does not cover:
- sprint length options
- how tasks move between the backlog and a sprint
- ranking controls for backlog items
- which views or reports come with the feature
- whether existing plans will be converted
- which license unlocks it
Anyone claiming to know those details before January is guessing.
In short: the scope is clear, but the implementation details are not public yet.
Why "separate from buckets" matters
Planner users have long faked sprints with buckets: one column per sprint, plus a "Backlog" column and a lot of dragging. That works until you also want buckets for workstreams, departments or stages. Then the same column has to do two jobs.
Planner's premium plans already moved away from that approach. SharePoint consultant Gregory Zelfond of SharePoint Maven explains that in the past, buckets were used to create Sprints, but now Sprints have a default field on the task card plus their own view. In that premium setup, all tasks on the plan are added to the Backlog "Bucket" by default, and you can also create buckets for Sprints and set Sprint start and end dates. Tasks can then be dragged and dropped from Backlog to Sprint buckets, just like with a "regular" Board.
The roadmap's wording about keeping sprints separate from buckets points the same way for unified plans: buckets describe how a team groups its work, and sprints describe when the work happens. Don't assume the unified version will copy the premium interface, though. Microsoft hasn't published screenshots or a workflow for it yet.
The bigger story: unified plans
This roadmap item is part of a larger change. On November 18, 2026, Microsoft's Planner team, in a post by Ashna Patel, introduced unified plans: one shared foundation that combines features from To Do and from Planner's basic and premium plan types. Premium features are available based on a user's Microsoft Copilot, Planner Plan 1, or Planner and Project Plan 3 license. The post names sprints and backlogs, along with task hierarchy and dependencies, as premium features on the roadmap for unified plans. Goals view, Timeline view and custom fields have already rolled out there.
Key points from Microsoft's announcement:
- Location: Unified plans are available across Outlook, Teams, Planner and Loop, as well as Microsoft Copilot and Cowork. Autopilot support is planned. The sprint feature itself is only listed for Desktop and Web, so don't expect it on every surface on day one.
- Infrastructure: Microsoft is moving to a fully Azure-based service and says it will stop investing in Dataverse-based plans. Unified plans don't need a Dataverse environment or Dataverse storage capacity. Existing premium plans still use Dataverse.
- Premium plans: They remain supported during the transition. Microsoft recommends creating new basic (unified) plans where they fit, and says some scenarios may still need premium plans in the meantime.
- New features: Microsoft says all new Planner features will be built for unified plans. Several recent ones, including task chat, custom templates and Capacity view, won't be available in premium plans.
- To Do: The To Do apps retire on June 30, 2027, as personal task management moves into Planner.
In short: sprints and backlogs are one of the main premium features Microsoft needs to bring to unified plans before premium plans can stop being the default choice for agile teams.
The licensing question
Today, backlogs and sprints are a paid feature. Microsoft's own Planner product page lists Backlogs and sprints among the features in Planner Plan 1, next to task dependencies, reports and Timeline view. ProjectManager's recent overview also notes that Planner Plan 1 costs $10 per user per month, paid yearly, and adds the timeline, calendar and People views, finish-to-start dependencies, milestones, goals and sprints.
Microsoft calls sprints and backlogs a premium feature on the unified roadmap, so it will probably require a Copilot, Plan 1 or Plan 3 license. However, neither the roadmap entry nor the announcement names the specific license for this feature. Check the Planner plans and pricing comparison and the Planner service description when the feature gets close to release.
One thing Microsoft does promise is that collaboration works across license tiers. Its example is a project lead with Planner Plan 1 setting goals while teammates with Planner in Microsoft 365 track and update the related tasks. Whether sprint planning follows the same pattern (licensed leads plan, everyone else works the tasks) isn't confirmed for this feature.
What admins and team leads can do now
- Don't migrate yet. Premium plans remain supported. Microsoft hasn't announced a migration requirement or deadline for existing plans.
- List your sprint workarounds. Find basic plans where buckets are being used as sprints. Those teams will benefit most and will need to decide how to restructure their buckets once sprints become a separate dimension.
- Treat January 2027 as an estimate. Don't schedule a process overhaul or training for a fixed date. Watch roadmap ID 581629 for status changes.
- Check licensing before rollout. Compare assigned licenses against the official feature comparison so nobody is surprised when the feature appears.
- Review your integrations. Microsoft says the first unified task and plan Graph APIs are in beta and is moving toward a single Power Automate connector. Agile tooling built on premium-plan APIs or Dataverse may need changes eventually.
- Look at the To Do retirement too. It's on the same roadmap, and it lands in mid-2027.
Will it replace a dedicated agile tool?
Probably not, and Microsoft isn't positioning it that way. VirtoSoftware describes Planner's existing premium sprint support as a lightweight agile setup rather than a full Azure DevOps replacement, but enough for most business teams. Nothing in the roadmap entry mentions story points, velocity, burndown charts or sprint reports, so software teams already using Azure DevOps or GitHub have no reason to switch.
The target audience is business teams: marketing, HR, operations and IT service teams who want two-week cadences without learning a developer tool. For them, getting sprints into the same plan type that powers Copilot, Cowork and the Planner MCP server matters more than a burndown chart.
Bottom line
Roadmap item 581629 brings backlogs, time-boxed sprints and a current-sprint view to unified plans, and keeps buckets as a separate way to organize work. It's estimated for January 2027 on Desktop and Web. It's still in development, the license isn't specified, and premium plans aren't being retired yet. If your team plans sprints with bucket workarounds, start planning for the change now, but don't commit to a date until Microsoft confirms one.
References
- Planner: Sprints and backlogs in unified plans Microsoft 365 Roadmap · 2026-11-18T18:32:08.027424Z
- Microsoft Planner Premium: Features & Pricing 2027 virtosoftware.com
- Roadmap di IA al lavoro | Microsoft 365 microsoft.com