To use Microsoft Planner in Teams, add Planner as an app for personal and shared task work, or add a specific plan as a tab in a channel. A channel tab gives the team one place to create or attach a plan, organize work into buckets, assign owners, and review progress alongside the conversation where the work is managed.
Choose a basic plan for shared tasks, buckets, assignments, dates, filters, grouping, and Charts. Evaluate a premium plan when the team needs capabilities such as Timeline with Gantt and task dependencies, and confirm the required license before setup. The Planner app can show several task sources and plan types, so the controls available depend on the plan that is open.
Planner is being consolidated across Microsoft 365. App labels, channel support, plan choices, and views can vary by tenant policy, license, geography, and rollout stage. Some users may still see the legacy name Tasks by Planner and To Do.
What Planner in Teams does, and which plan to choose
The Planner app appears in the Teams app menu and can bring together personal tasks, shared basic plans, premium plans, and related task sources. A Planner tab places one plan in a channel. Use the tab when a group needs to review the same work in the context of its channel conversations.
| Need | Starting point | Check before choosing |
|---|---|---|
| Shared task list and board | Basic plan | Confirm access and group membership |
| Timeline with Gantt and dependencies | Evaluate premium | Confirm the required license and feature availability |
| Tasks from several sources | Planner app | Check which plan and task source is open |
Basic plans cover common shared task coordination. Premium plans add capabilities such as Timeline with Gantt and dependencies, subject to licensing and availability. Microsoft’s Planner app administration guidance for Teams explains organizational availability, policies, and the current app scope.
Choose the plan type from the work requirement, not from the view you happen to want. Basic is a practical starting point for shared task coordination; premium should be justified by a documented need such as dependencies or Timeline with Gantt.
Check access before adding Planner
If Planner is missing or a user receives a permission error, check the cause in this order. First confirm that the Planner app is allowed by the organization’s Teams app policy. Then confirm the user’s account and applicable entitlement, membership in the Microsoft 365 group associated with the plan, sharing of the plan with the relevant group, and support for the target channel type.
Group ownership alone may not provide the membership needed to create, view, or edit a plan. If the app policy or tenant availability is the problem, ask the Teams administrator to resolve it. For group membership or plan sharing, ask the Microsoft 365 group owner or administrator. Microsoft provides specific troubleshooting guidance for Planner tab permission errors.
Mobile Teams has more limited Planner functionality. Microsoft notes that mobile users may see plans that have been added as channel tabs, so test the experience on the devices the team actually uses.
Add Planner as a Teams channel tab
Use the native Planner tab workflow to create a plan or attach an existing one. Before starting, identify the intended channel, decide whether the team needs a basic or premium plan, and check that an existing plan is shared with the channel or its associated group. If it is not selectable, resolve sharing or access rather than creating a duplicate.
Microsoft’s current procedure for adding Planner as a Teams tab describes creating a new plan or selecting an existing plan. Prefer this native route over pasting a plan link into a Website tab. Private and shared channel support, menu labels, and plan choices can depend on tenant configuration and rollout.
Set up buckets, tasks, owners, and dates
Use buckets to represent workflow stages or workstreams, not as a second copy of every task attribute. For a delivery team, buckets such as To do, In progress, and Done make a Board review straightforward. Use labels for cross cutting categories such as department or request type, and use priority fields for urgency.
Give each task an action oriented title and enough description or checklist detail to make the next step clear. Assign an accountable owner and set a due date when there is a real commitment. Agree on what completion means before work is distributed.
In a shared plan, a task with multiple assignees is still one task record. Microsoft documents that completing it marks it complete for the other assignees too. If several people are assigned, name one person in the team convention to coordinate completion, and record that responsibility in the task details when it matters.
- Define what each bucket means and who moves tasks between stages.
- Set a rule for assigning one accountable owner or coordinating multiple assignees.
- Use due dates for actual deadlines, not as a substitute for priority.
- Describe the condition that counts as done for recurring task types.
- Check that the people responsible for the work can access the plan.
Document these conventions in the plan description or a channel post so new contributors can apply them consistently. Keep group membership and task assignments aligned with the people who need to act on the work.
Track work with views, filters, Charts, notifications, and To Do
Choose a view for the question the team needs to answer. Use Board for a stage based review, Grid to scan or edit task details, Schedule or Calendar to review dates, and Charts for a visual summary. View names and availability can vary by plan and Planner experience.
Charts can show task status, bucket progress, priority, and member availability. Treat those as summaries, not automatic bottleneck detection or formal capacity planning. Filters narrow the tasks you see, while grouping organizes the view by fields such as bucket, assignment, due date, priority, labels, or status. Neither operation changes the underlying plan. Microsoft’s plan organization and view guide describes current view, grouping, and filtering options.
Enable relevant assignment and due date notifications, then check that Teams notification settings and tenant policies allow delivery. Notification timing and delivery channels can vary between current and legacy experiences.
A user’s Planner assignments can appear in Microsoft To Do’s Assigned to me list when the Planner connection and list are enabled. This is an assignment focused view, not a full copy of Planner. Use Planner for fields and actions that are not exposed in To Do. See Microsoft’s guides to Planner notifications and Planner tasks in Microsoft To Do.
Automate only stable handoffs
Keep plan setup and task organization manual until the team has stable plan destinations, bucket rules, ownership mappings, and task definitions. The Microsoft Planner Power Automate connector supports basic plans, with documented task and bucket actions and task related triggers. It does not support premium plans. Microsoft documents a trigger polling interval of one poll every 360 seconds, so a connector trigger is not the same as an instant user notification.
Hypothetical example: An approved request in an existing intake system becomes a task in a known basic plan. The intake system’s trigger is specific to that system and is not a Planner feature. The flow validates the approved request, maps its known destination and owner, and uses the Planner connector’s task creation action. Optional AI may summarize supplied request text into a draft description, but it should not choose the plan, bucket, assignee, or deadline.
| Stage | Input or AI job | Validation | Action or fallback |
|---|---|---|---|
| Trigger | Approved intake record | Confirm source event and source object ID | Start the flow; send malformed records to intake review |
| Normalize | Known plan, bucket, owner, title, and date mappings | Confirm the destination is a basic plan and identifiers exist | Build the connector request; reject unknown mappings |
| Optional AI | Summarize supplied request text | Compare the draft with the source and validate a fixed schema | Use the summary only for description; route ambiguity or sensitive content to a reviewer |
| Write and record | Planner task creation response | Check required fields and title length before submission | Store the Planner task ID and source identifiers; retry transient failures under an explicit policy |
{
"source_system": "approved_intake",
"source_object_id": "REQ-1042",
"destination_plan_id": "configured-basic-plan-id",
"destination_bucket_id": "configured-bucket-id",
"task_title": "Review supplier onboarding request",
"assignee_user_ids": ["approved-owner-id"],
"due_date": "2026-11-04",
"workflow_version": "1"
}The values above are illustrative, not a Microsoft provided template. Before creating a task, validate that the configured plan is basic, the plan and bucket IDs exist, the owner is in the approved mapping, required fields are present, and the title is within the connector’s documented 255 character limit.
Store the returned Planner task ID alongside the source record ID. For duplicate prevention, define a unique task key such as source_system + source_object_id + destination_plan_id + workflow_version in the integration’s own data store. Enforce it with a database uniqueness constraint and transactional upsert or conflict handling. A search followed by task creation is not safe when two runs can occur simultaneously. If the intake source can redeliver events, track its event ID separately from the task level key.
Use deterministic rules for known plan IDs, bucket mappings, and owner directories. Reserve AI for drafting a summary from supplied text, then validate it before writing. If the plan is premium, the destination is uncertain, or the source contains sensitive content, stop the write and send the item to a human owner.
The intake process owner should review invalid mappings, ambiguous requests, sensitive content, duplicates, and connector failures. The Microsoft 365 administrator handles access or entitlement issues. Microsoft’s Planner connector reference lists supported actions, triggers, plan scope, polling, and connector constraints.
For custom development, Microsoft Graph supports basic Planner plans and tasks, not premium plans. Consult the Planner API overview before designing an integration. Graph or the connector should not be treated as a universal event or automation layer for premium plans.
Know the limits and resolve common failures
Microsoft’s limits page lists 3,000 active tasks, 9,000 total tasks, 200 buckets, and 400 plans owned by a user or group for the covered plan types. The page excludes To Do lists and premium plans in the Planner app and warns that limits may change. Verify the scope before applying these figures to a rollout.
The same limits page lists 20 assignees per task, while a current end user support workflow describes assigning up to 11 people. Treat this as a documentation scope discrepancy, not as a universal Teams interface promise. Test the actual tenant and workflow before setting a team rule.
Do not assume that Planner lacks Gantt functionality. Microsoft documents Timeline with Gantt and dependencies for premium plans, subject to licensing. Conversely, task history should not be treated as a compliance grade audit log. If formal audit controls are required, verify the relevant Microsoft 365 audit capability and plan type. The reviewed documentation does not establish a general Planner recycle bin or recovery workflow, so confirm deletion handling before relying on a recovery assumption.
If a plan cannot be found, return to the access check that failed: app policy, account and entitlement, group membership, plan sharing, or channel support. Do not create a second plan until the group owner or administrator confirms that the original plan is inaccessible or unsuitable.
When basic Planner is not enough
Write down the requirement the current plan cannot meet. If it is Timeline with Gantt or task dependencies, evaluate premium Planner and confirm the required license. If the gap is formal auditing, resource management, time tracking, or a required integration, verify whether a Microsoft 365 capability meets it before comparing other systems.
Test a representative workflow, its permission model, reporting needs, failure handling, and total licensing impact before migrating. Teams that have identified requirements unmet by Planner can also consider ClickUp consulting as one evaluation option. Compare it against the specific workflow and governance requirements rather than assuming any product is universally better.