Kanban boards inside Microsoft Teams: the options and their trade-offs
If your team already works in Microsoft Teams and wants a kanban board there, the built-in answer is the Planner app. With a Microsoft 365 licence that includes Planner, anyone can create a basic plan with a Board view: columns called buckets, cards with assignees, due dates, checklists, labels, and files. That covers a plain kanban board at no extra cost. What it does not cover on the standard licence is backlogs and sprints, a Timeline (Gantt) view, sub-tasks, and the ability to create dependencies. Those need Planner Plan 1, listed on Microsoft's pricing page at $10.00 per user per month, paid yearly, as checked on October 8, 2026. The other route is a separate board tool connected to Teams, which makes sense when the board's audience is not the same as the team's membership.
The pages that rank for this query are mostly a Microsoft article, a third-party marketplace listing, and forum threads where people ask for something Planner does not do. This page puts the licence boundary, the channel membership question, and a working setup in one place, so a small team can decide in one sitting.
What the Planner board gives you on a standard licence
Microsoft's admin documentation lists the subscriptions that include Planner: Microsoft 365 Business Basic, Microsoft 365 Business Standard, Office 365 E1, E3, and E5, and Microsoft 365 A1. It also states that if the current subscription does not include Planner, the only way to get it is to switch to a subscription that does. The page is at Microsoft Planner for admins.
With that licence, users create what Microsoft calls basic plans, which have four views: Grid, Board, Schedule, and Charts. The plan comparison on Microsoft's Planner pricing page lists the included features as task creation with files, checklists, and labels; My Day, My Tasks, and Assigned to me; basic and custom templates; the four views; and the ability to view task dependencies and custom task fields.
The wording on that last point matters. On the standard licence, dependencies and custom fields can be viewed. Creating them is listed under Planner Plan 1.
What the Board view actually is
In a Planner plan, columns are buckets. The team names them, so they can follow the stages of the work (To do, Doing, Review, Done) rather than a fixed set of statuses. Each task also carries a progress status that is separate from the bucket it sits in.
That separation is useful, and it is also the source of a common mess. If a card sits in Done while its progress says "in progress", the Charts view and the board disagree. Small teams avoid this by deciding once which one is authoritative, usually the bucket, and marking a task completed only when it reaches the last bucket.
The name change that confuses older guides
Microsoft's admin page records that in April 2024 the Tasks by Planner and To Do app was renamed Planner, and Project Plan 1 was renamed Planner Plan 1. On September 18, 2024, Project Plan 3 and Project Plan 5 became Planner and Project Plan 3 and Planner and Project Plan 5. Guides and screenshots from before those dates use the old names for the same things.
What the licence decides, in one table
Most teams discover the licence boundary the day someone asks for a Gantt chart or a sprint view. The table below summarizes Microsoft's pricing page as of October 8, 2026.
| Tier | Price listed | Plan type | What it adds for kanban teams |
|---|---|---|---|
| Planner in Microsoft 365 | Included in eligible Microsoft 365 plans | Basic plans | Grid, Board, Schedule, Charts views; checklists, labels, files; view dependencies and custom fields |
| Planner Plan 1 | $10.00 per user per month, paid yearly | Premium plans | Sub-tasks, backlogs and sprints, create task dependencies, Calendar, Timeline (Gantt), and People views, goals, milestones, custom task fields |
| Planner and Project Plan 3 | $30.00 per user per month, paid yearly | Premium plans | Task history, Assignments view, portfolios, baselines and critical path, dependencies with lead and lag, Project desktop |
The pricing page also offers a one-month free trial of the paid plans, with a credit card required, and states that after paid service begins there is a seven-day window to cancel for a prorated refund.
Reading the table for a small team
A plain board is free with the licence most organizations already hold. If what the team needs is columns, assignees, due dates, and labels, the standard Planner board is enough, and adding another tool brings more cost than benefit.
The upgrade decision is about three specific needs. Teams running sprints with a backlog need Plan 1. Teams that need a Gantt view tied to the same tasks need Plan 1. Teams that need sub-tasks with their own owners need Plan 1. At $10.00 per user per month, a six-person team pays $720 a year for those features.
Microsoft's admin page also notes that premium capabilities are not available in GCC High or DoD tenants, which settles the question early for organizations in those clouds.
How a board in a channel ties to team membership
When you add a Planner plan as a tab in a Teams channel, the plan belongs to that team. Its members are the team's members. This has consequences worth thinking through before the board is set up.
The useful side
Nobody maintains a second list of people. A new team member sees the board; someone who leaves loses access. Discussion can happen in the channel next to the tab, and notifications arrive in the app people already watch all day.
The awkward side
A board's audience is often not the team's audience. A project with two people from marketing and one outside contractor does not match a team of twenty-five. The options are to create a separate team for three people, which multiplies teams quickly, or to keep the board in the large team and accept that most members see work that is not theirs.
External people raise a policy question before a product question. Guests can be added to a team only if the organization's guest settings allow it, and those settings belong to the Microsoft 365 administrator. Agencies and consultancies whose boards routinely include client contacts should ask that question first, because the answer decides whether a Teams-based board is workable at all.
A rule of thumb
If the board's members are the same as an existing team's members, the Planner tab is the simplest option. If the board needs a different set of people, especially outsiders, a board tool with its own membership and per-project permissions is usually less friction than rearranging Teams.
Setting up a Planner board that stays accurate
Most complaints about the built-in board come from a plan created in a hurry. Four decisions prevent most of them.
Name buckets after stages, not topics
The temptation is to use buckets as categories: Website, Marketing, Admin. A task can be in only one bucket but can carry several labels, so categories belong on labels. Buckets should be the stages work passes through, so a card moving left to right means progress and a card that has not moved for a week stands out.
Keep the stage list short
Four or five buckets cover most small teams: To do, Doing, Review, Done, and optionally Blocked. Each extra bucket is another place for a card to sit unnoticed.
Set a limit on work in progress by agreement
Planner does not enforce a cap on how many cards can sit in a bucket. Kanban works better with one. Teams can agree a number, for example no more than two cards per person in Doing, and check it at the weekly review. The board makes overload visible; the agreement makes it actionable.
Archive the Done column on a schedule
A Done bucket that grows forever slows down the board and hides recent wins. Moving or clearing completed tasks every week or at the end of each sprint keeps the board focused on current work.
When a separate board tool fits better
The built-in board is the right default for many teams. A separate tool is worth considering in a few specific situations.
The board needs people outside the organization. If clients or freelancers must see or update cards, a tool with per-workspace or per-board membership avoids changing tenant guest policy for each engagement.
The team needs Gantt, calendar, and board views of the same tasks without a per-user add-on. Some board tools include timeline and calendar views in their free or base plans. Compare that against the $10.00 per user per month for Planner Plan 1 at your team size.
Chat about a task should stay with the task. Teams channels hold conversation well, but the link between a channel message and the card it discusses has to be maintained by hand. Tools with comments and mentions on each card keep the history in the card.
The team is moving off Trello. A tool that imports Trello's JSON export with checklists, attachments, and comments saves days of copying. The Trello comparison and the Trello import page describe how one tool handles this.
Keeping Teams in the loop
Choosing a separate board does not have to mean leaving Teams out. Many board tools publish a Teams app or connect through automation services such as Zapier. A common pattern is to post a message in the project channel when a card moves to Done or when someone is assigned. The integrations page shows what that setup looks like with webhooks and automation tools.
Keep the number of automated messages small. A channel that receives a post for every card edit trains people to mute it, and then the one message that matters is missed too. Two triggers are usually enough: a card reaching Done, and a person being assigned. Everything else can be checked on the board itself during the weekly review.
A decision you can make this week
Three questions settle the choice for most small teams.
- Do the board's members match an existing team? If yes, start with the Planner tab. If no, look at a tool with its own membership.
- Do you need sprints, a Gantt view, or sub-tasks? If no, the standard licence covers you. If yes, price Planner Plan 1 against tools that include those views.
- Will outsiders use the board? If yes, check the tenant's guest policy before designing anything.
Whatever the answer, run the board for two weeks with four or five buckets and an agreed work-in-progress limit before adding anything else. The structure of the board matters more than the product hosting it.
What to change first
Rename your buckets to stages and add a work-in-progress limit this week. If the board needs outside members, Gantt and calendar views, and chat on each card without a per-user add-on, Pinateca is free for up to five people and ten boards.
Q1. Is there a free kanban board in Microsoft Teams?
Yes, if your Microsoft 365 subscription includes Planner. Microsoft lists Business Basic, Business Standard, Office 365 E1, E3, E5, and Microsoft 365 A1 as including it. Basic plans have a Board view with buckets, labels, checklists, and assignees at no extra cost.
Q2. Does Planner in Teams have a Gantt chart?
Not on the standard licence. Microsoft's pricing page lists the Timeline (Gantt) view under Planner Plan 1, which was $10.00 per user per month, paid yearly, when checked on October 8, 2026.
Q3. Can I run sprints in Microsoft Planner?
Backlogs and sprints are listed as Planner Plan 1 features. On the standard licence, teams often represent a sprint with a bucket or with due dates and labels, and clear the Done bucket at the end of each sprint.
Q4. Can people outside my company see a Planner board in Teams?
Only if they are added to the team as guests, which depends on your organization's guest access settings. If outside collaborators are a regular need, check the policy with your Microsoft 365 administrator before building the workflow around Teams.
Q5. Can a board tool other than Planner post updates into Teams?
Many board tools offer a Teams app or connect through automation services such as Zapier or webhooks. A typical setup posts a message to a channel when a card is completed or assigned, so the team sees changes without opening the board.