Project management within Microsoft Teams: the 2026 setup

You can run real project management inside Microsoft Teams, and as of 2025 the right tool to do it with is Planner, not the old patchwork of Tasks, Project for the web, and Roadmap. Microsoft consolidated all of that into one app, and most guides you will find still describe the retired version. Here is the honest take: Teams plus Planner is a genuinely good home for project work if your company already lives in Microsoft 365, because the board sits next to the chat where the work actually gets discussed. But the board only stays accurate if the decisions made in your meetings reach it, and that last step is where almost every Teams project setup quietly falls apart. This guide shows the correct 2026 setup, what each piece costs, the exact clicks, and how to close the meeting-to-task gap.

What changed: Planner is now the one tool

If you read an article from 2023 or 2024, it probably tells you to add a "Tasks by Planner and To Do" tab, or to use the Project app or the Roadmap app for bigger work. Most of that is gone. In August 2025, Microsoft retired Project for the web and removed the Project and Roadmap apps from Teams, folding everything into the new Planner. Project Online is on the way out too: end of sale was October 1, 2025, and full retirement is September 30, 2026.

So in 2026 there is one app to learn. The new Planner brings together the simple personal lists of Microsoft To Do, the shared boards of classic Planner, and the heavier scheduling power that used to live in Project. It runs as a tab inside any Teams channel, and it also has a standalone web and desktop app. If an old tab in your Teams says it can no longer open a project or roadmap, that is expected. You re-pin it as a Planner tab.

What it costs (and where the free line really is)

This is the part marketing pages blur. Basic Planner is free with any paid Microsoft 365 business, enterprise, or education plan. That covers task boards, the Grid, Board, Schedule, and Charts views, My Day, and My Tasks. For a lot of teams, that is genuinely enough.

The moment you want a Gantt timeline, task dependencies, sprints, custom fields, team workload, or goals, you cross into Planner Premium, which is a paid per-user license on top of your Microsoft 365 plan.

A few cost traps worth naming. The headline "free" only holds if everyone on the project already has a paid Microsoft 365 seat; Planner basic is not a standalone free product the way Trello's free tier is. Premium is per user, so the price scales with how many people need timelines and dependencies, not how many projects you run. And there is a separate, often-confused bill: AI meeting recap. Intelligent recap and AI notes are part of Teams Premium ($10/user/month, billed yearly) or Microsoft 365 Copilot ($30/user/month), not Planner. Buying Planner Premium does nothing for your meeting summaries, and buying Copilot does nothing for your Gantt charts. They are different products with different invoices.

Structure your projects before you touch a board

The most common Teams mistake is creating boards before you create structure. Teams gives you teams (a container) and channels (rooms inside it). Get that mapping right first, or your project work scatters and nobody can find it.

A clean default that works for most companies:

• One team per client, department, or major program. This is the boundary for membership and access.
• One channel per project or workstream inside that team. Standard channels for things everyone in the team should see; private channels for sensitive work like budgets or a specific client.
• One Planner tab per channel, holding the plan for that project. Keep it one plan per channel so the board and the conversation stay in sync.

Do not create a separate team for every tiny project. Teams sprawl is real, and a member who belongs to forty teams stops checking any of them. Channels are the cheaper, lighter unit; reach for a new channel before a new team.

Run the work: buckets, assignees, dates, and views

Once the board is live, the daily mechanics are simple, and the discipline matters more than the features. Inside a plan you create tasks, group them into buckets (your columns: think "Backlog," "In progress," "In review," "Done," or phase names like "Discovery," "Build," "Launch"), and on each task you set an assignee, a due date, a priority, and a checklist of sub-steps.

Three rules separate a board people trust from a board people ignore:

• Every task has exactly one owner. Not a group, not "the team." One name. Shared ownership means no ownership. If you struggle to make tasks land with a single person, our guide on how to delegate tasks effectively is worth a read.
• Every task has a due date. A task with no date is a wish. Use the Schedule (calendar) view to catch the ones you forgot to date.
• The board reflects reality, not hope. Move cards as work actually progresses. A board that says everything is "In progress" for three weeks is a board nobody is updating.

For views, basic Planner gives you Grid (a list), Board (kanban), Schedule (calendar), and Charts (status breakdown). Premium adds the Timeline (Gantt) view, which is the one people picture when they think "project management," along with dependencies so a delayed task pushes the ones that rely on it. If your projects are simple, ongoing, and bucket-driven, you may never need the timeline. Buy Premium when you actually have sequenced, deadline-driven work, not before.

The gap that rots every Teams board

Here is the failure mode nobody warns you about. You set up the team, the channels, the Planner boards, the buckets. For two weeks it looks great. Then it goes stale, and you blame the team for "not updating Planner." The real cause is upstream: the decisions, owners, and deadlines that should become tasks get made in meetings, and they never make the trip from the call into the board.

This is the same point we make in our broader best project management tools comparison: a project board is only as accurate as the last person who updated it, and the things worth tracking get decided on calls. If logging them is a manual chore done from memory after the meeting, it does not happen. Teams makes this worse in a subtle way, because the meeting, the chat, and the board are all in the same app, so it feels like the information should just flow between them. It does not. Teams does not turn what was said in a meeting into Planner tasks on its own.

There are two honest ways to close the gap.

Option one, the Microsoft-native path. Use Teams Collaborative notes during the meeting. Inside the notes you can create tasks and assign them with an @mention, and assigned tasks flow into the assignee's task tools. This works, but it depends on a human typing the tasks live, in the right format, while also paying attention to the meeting. If you want the steps, see how to use Microsoft Teams meeting notes.

Option two, automatic capture. Record and summarize the meeting so action items get extracted for you, then move them into Planner. For Teams calls, Microsoft's own intelligent recap (Teams Premium or Copilot, priced above) does this. For Google Meet, where a lot of cross-company and client calls actually happen, Scribbl captures the recording, transcript, summary, and action items for free from the browser with no bot joining the call, and Pro and Team plans extend that to Zoom and Microsoft Teams. The goal either way is the same: stop relying on memory, and make the action items land in writing so a human only has to file them, not reconstruct them.

Native or third party: how to decide

If your whole company is on Microsoft 365 and your projects are internal, staying native (Teams plus Planner) is usually the right call. The data stays in your tenant, IT already manages it, and there is no new tool to buy or train people on. Reach for a dedicated project tool like Asana, monday.com, or Jira when Planner's model genuinely does not fit how your team thinks about work, for example heavy sprint engineering (Jira) or client-facing visual dashboards (monday.com).

Whichever side you land on, the capture problem does not change. A Jira backlog rots from stale meeting decisions exactly the same way a Planner board does. Pick the tool that fits, then fix the meeting-to-task path. For agency-specific structure, agency project management tools goes deeper on running client work, and for the discipline of juggling several at once, see how to manage multiple projects.

A clean 30-minute setup

If you want to stand this up today, here is the order that avoids rework:

1. Decide your team-and-channel map on paper first (one team per client or department, one channel per project).
2. Create or reuse the team, then add the project channels.
3. In each project channel, add a Planner tab and create one plan.
4. Build your buckets (your workflow columns) before adding any tasks.
5. Add tasks, and for each one set a single owner and a due date. No exceptions.
6. Decide your capture method now, not later: native Collaborative notes typed live, or recorded recaps you file afterward. Write it into your team norms so it is not optional.

That last step is the one teams skip, and it is the one that determines whether the board still tells the truth in a month.

Frequently asked questions

Is project management in Microsoft Teams free?

The basic version is free if everyone already has a paid Microsoft 365 plan. That gives you Planner boards, buckets, assignees, due dates, and the Grid, Board, Schedule, and Charts views, which is enough for many teams. You only pay once you need Premium features like a Gantt timeline, task dependencies, sprints, or custom fields, which start at $10 per user/month billed yearly (as of 2026-06-13). Note that AI meeting recap is a separate cost (Teams Premium or Copilot), not part of Planner.

What happened to Tasks by Planner, the Project app, and Roadmap in Teams?

They were consolidated. In August 2025 Microsoft retired Project for the web and removed the Project and Roadmap apps from Teams, merging everything into the new Planner. Project Online retires fully on September 30, 2026. If an old tab in your Teams says it can no longer open a project or roadmap, that is expected behavior. Re-pin the work as a Planner tab using the + sign at the top of the channel.

Can Microsoft Teams turn meeting discussions into tasks automatically?

Not fully. Teams Collaborative notes let a person create and assign tasks with an @mention during the meeting, and those flow to the assignee. AI recap (Teams Premium or Copilot) generates a list of suggested action items for you. But neither one writes tasks straight into a Planner board without a human moving them over. The reliable pattern is to capture action items in writing during or right after the call, then file them, rather than reconstructing them from memory later.

Should I use Teams and Planner or a tool like Asana or Jira?

Stay native if your company is on Microsoft 365 and your projects are mostly internal: the board lives next to the chat, IT already manages it, and there is nothing new to buy. Move to a dedicated tool when Planner cannot model your workflow, for example Jira for sprint-heavy engineering or monday.com for visual, client-facing dashboards. Our best project management tools comparison breaks down who each tool is honestly for.

How do I keep our Planner board from going stale?

Three habits. Give every task exactly one owner and a real due date. Move cards as work actually progresses, not in a Friday catch-up scramble. And close the meeting-to-task gap: decide on a capture method (live Collaborative notes or recorded recaps you file afterward) and make it a team norm so action items reliably reach the board. Stale boards are almost always a capture problem, not a tool problem.

The bottom line

Microsoft Teams plus the new Planner is a capable project home in 2026, especially if you are already paying for Microsoft 365. The setup is straightforward: map your teams and channels, add one Planner board per project channel, give every task an owner and a date, and upgrade to Premium only when you genuinely need timelines and dependencies. The piece that decides whether it works is not in the product at all. It is whether the decisions made in your meetings reliably become tracked tasks. Fix that, with native notes or with recorded recaps, and your board will still be honest a month from now. Skip it, and no amount of buckets will save you.