Copilot in Microsoft Planner - from “blank plan” to “let’s go” in one prompt


You know that moment when a project idea is solid… but the plan is not? You’ve got the goal, the deadline, the stakeholders—and then you hit the dreaded empty plan and wonder which bucket to build first, what tasks you’re forgetting, and how you’re going to make it look organized before the kickoff.

This spotlight helps with exactly that: Copilot in Microsoft Planner (preview). It’s a built-in assistant that can generate a full plan (goals, buckets, tasks, and sometimes subtasks) from a simple prompt, and it can also help you add tasks/goals later or answer questions like “What’s due this week?” as the work evolves.


What it is (and what it’s actually good at)

Microsoft describes Copilot in Planner as a way to streamline planning, management, and tracking, so teams can create structure faster and stay informed while executing. 
In practical terms, Copilot in Planner is best at: 

  • Jumpstarting a plan with buckets, goals, and tasks based on what you type. 

  • Adding new tasks / goals / buckets when scope shifts (because it will).

  • Answering basic plan questions like upcoming work, due dates, and plan status.

  • Using your accessible content as context—especially when you attach files directly in the prompt. 


Why it matters (aka: fewer sticky notes, fewer “what did we miss?” meetings)

Most teams don’t struggle with doing work—they struggle with turning goals into a clean work breakdown that everyone can follow. Copilot helps you get a first draft plan in place quickly, so your team can spend kickoff time improving the plan instead of inventing it from scratch. 
And once the plan is live, Copilot can help you stay on top of progress and changes by surfacing what’s behind or what needs attention—without you playing “human dashboard.”


🚨 Quick licensing callout (read this before you get excited)

Licensing for Copilot in Planner has been… let’s call it “dynamic,” so here’s the cleanest way to explain it to your users.

✅ What you need (the safe, future-proof answer)

To use Copilot in Planner, you should plan for users to have both:

  • Project and Planner Plan 3 or Project and Planner Plan 5, AND

  • a Copilot for Microsoft 365 (Microsoft 365 Copilot) license. 

Why “both”? Several licensing updates reported for early August 2025 indicate that access to Copilot in Planner will require a dedicated Microsoft 365 Copilot license, aligning Planner with the broader Copilot licensing model. 

❌ What will not give you access

  • Planner Plan 1 (Planner Premium) does not provide access to Copilot in Planner. 

  • Copilot for Microsoft 365 alone will not unlock Copilot-in-Planner features for users who don’t meet the Planner/Project licensing requirements. 

  • Even Planner Plan 1 + Copilot for Microsoft 365 still won’t provide access to Copilot in Planner.


How to use it: getting started (without the guesswork)

Below are the three most common “on-ramps” you’ll use: Create a new planCreate new goals, and Create new tasks—with the key detail that Copilot requires a Premium plan experience.

 

1) Create a new plan (Premium plan required)

Copilot isn’t available in Basic plans—so if someone creates the plan the “old” way (Basic), they’ll wonder why the Copilot button never shows up. 

Create a Premium plan in Planner

  1. Open Microsoft Teams and launch the Planner app. 
    • In Teams, select View more apps (…) → search Planner → select Add (and pin it if you want quick access). 
  2. Select New plan (lower left). 
  3. In the Create new window, choose Premium (this is the step that unlocks Copilot features). 
  4. Enter a plan name, choose whether to pin it, and optionally select a group to assign it to.
  5. Select Create.
  6. In your new plan, select Copilot in the top right to open the Copilot pane.

Quick troubleshooting tip

If you don’t see the Copilot icon:

  • The plan may be Basic, or
  • the user may not have the right licensing assigned.

 

New plan options in Microsoft Teams with the Premium plan highlighted, showing various project templates below.

2) Create new goals (with Copilot)

Goals are a great way to anchor a plan around outcomes (not just a long list of to-dos). Copilot can generate goals and place them directly into the Goals tab. 

Steps: Generate goals

  1. Open your Premium plan in Planner (Teams). 
  2. Select Copilot (top right). 
  3. Type a prompt such as:
    • “Create goals to grow my career in software development.” 
  4. Select Send—Copilot generates goals and adds them to the Goals tab.

Small trick that makes a big difference: use “/”

In the prompt box, type / to attach a file or reference people so Copilot can ground your goals in real content (like a project charter, requirements doc, or meeting notes).

 

 

3) Create new tasks (with Copilot)

Once you have goals (or even if you don’t), Copilot can generate tasks and add them into your plan based on what you ask. 

Steps: Generate tasks

  1. Open an existing Premium plan
  2. Select Copilot (top right). 
  3. Enter a task prompt, for example:
    • “Add tasks for generating over 100,000 impressions on a social media post.”
  4. Select Send—Copilot adds suggested tasks to the plan. 

Follow-up move

After tasks are added, you can connect them to goals, group them into buckets, and refine assignments/dates—Copilot gets you the structure, and you make it accurate for your team.

 

Project task list with assignments and progress, showing tasks grouped by development phases.

 


Real-world scenarios where Copilot in Planner shines

Here are a few situations where this feature earns its keep—without turning your plan into “AI soup.”

 

1) Fast kickoff planning

You’ve got a kickoff in 30 minutes and need something better than a blank canvas. Copilot can generate a first-pass plan with goals, buckets, and tasks from a natural-language prompt. 

Tip: Start broad, then drill into one bucket with a follow-up prompt so you don’t end up with 200 tasks on day one. (Copilot supports iterating on the plan as it evolves.)

 

2) Turning outcomes into action (marketing, launches, campaigns)

If you know what success looks like but need the steps, Copilot can help translate targets into tasks—like the example prompt to generate tasks toward impressions goals.

Tip: Attach your campaign brief using / so tasks reflect your channels, approvals, and deliverables.

 

3) Progress and workload check-ins without the meeting

Copilot can answer basic plan questions like what’s due soon and help identify what’s behind or where workload is concentrated. 

Tip: Use it as a “pre-meeting summary” generator: ask what’s due this week, what’s overdue, and where the bottlenecks are—then walk into your standup prepared


Project Manager playbook: where Copilot in Planner really earns its keep

Copilot in Planner is at its best when you’re doing classic PM moves: kickoff planning, scope change control, status reporting, and risk triage. Microsoft frames Copilot’s value around planning, managing, and tracking—generating goals/buckets/tasks, helping you adjust as scope changes, and answering questions about progress, due dates, and workload. 

Below are scenarios + prompts written specifically for PM workflows.

 

Scenario 1: Kickoff planning — “Give me a credible WBS in 5 minutes”

Use when: You’ve got a charter or a one-page brief, and you need a first-pass plan that looks like a plan—not a napkin sketch.

Best prompt (copy/paste):

Create a project plan for [project name]. Include buckets for Initiation, Planning, Execution, Testing/Validation, Deployment, and Closeout. 
 

Add goals for scope, schedule, and adoption. Include tasks for stakeholder alignment, requirements, design, build, test, training, comms, and go-live readiness.
 

Assume a [X]-week timeline and include key milestones.

Copilot can generate the initial plan structure (buckets, goals, tasks) from prompts like this. 

PM tip: Attach your charter or requirements doc using / so the plan aligns to real deliverables instead of generic steps. Copilot can use files you have access to, and anything you attach is always used as context.

 

Scenario 2: Build a phase gate plan — “Make the gate checklist so I don’t forget the boring-but-critical stuff”

Use when: You’re running a release, implementation, migration, or rollout with stage gates (Go/No-Go).

Best prompt:

Create a phase gate checklist for moving from Build to Test, and from Test to Deploy.
 

Include tasks for entry/exit criteria, sign-offs, change management, rollback planning, security review, and readiness approvals.
 

Group tasks into buckets by gate.
 

Copilot supports generating and adding tasks/buckets/goals based on prompts, and can build a plan outline. 

PM tip: After the checklist is created, ask:

What tasks are due this week, and what could block the next phase gate?

Copilot can answer plan questions like what’s due and what’s behind.

 

Scenario 3: RAID log starter — “Spin up risks/assumptions/issues/dependencies from the project context”

Use when: You need a RAID log but don’t want to open yet another spreadsheet.

Best prompt:

Based on this plan, suggest an initial list of project risks, assumptions, issues, and dependencies.

Create a bucket for each (Risks, Assumptions, Issues, Dependencies) and add tasks for monitoring and mitigation activities.

Copilot can create buckets/tasks and help teams track changes and issues as the plan evolves. 

PM tip: Your first RAID draft will be “pretty good,” not perfect. Your win is speed. Then refine with the team in kickoff.

 

Scenario 4: Scope change — “We just got a new requirement… rebuild the plan without chaos”

Use when: Stakeholders add scope mid-flight (because of course they did).

Best prompt:

We have a scope change: [describe change].

Add the necessary tasks and buckets, identify what existing tasks are impacted, and suggest an updated sequencing approach.

Also propose a goal that tracks the scope change delivery.

Microsoft explicitly calls out using Copilot when it’s time to triage issues, expand scope, or make changes—adding goals, identifying tasks behind, and keeping the plan organized. 

PM tip: Follow with:

Which tasks are now most at risk of missing the deadline, and what are mitigation options?

Copilot is designed to answer plan status questions and help keep you informed as you execute.

 

Scenario 5: Weekly status reporting — “Give me the update I’d write anyway”

Use when: You’re preparing for steering committee or sponsor updates.

Best prompt:

Give me a status summary for this plan: 

- overall progress

- key accomplishments since last week

- upcoming milestones in the next 2 weeks

- top risks/issues

- tasks that are overdue or at risk

Copilot can answer questions about progress, priorities, due dates, and what’s behind within the plan. 

PM tip: This is where Copilot saves real time. You still apply judgment, but you stop re-building the same narrative from scratch each week.

 

Scenario 6: Workload balancing — “Who’s overloaded and what can we reassign?”

Use when: You’re seeing slippage and suspect the work is unevenly distributed.

Best prompt:

Who has the highest workload in this plan? 
Suggest which tasks could be reassigned without breaking dependencies or timelines.

Microsoft calls out workload insights (identifying who has the highest workload) and tracking tasks behind as core ways Copilot helps manage work. 

PM tip: Use this as a conversation starter—not an auto-reassign trigger. It’s a fast way to spot imbalance before it becomes burnout.

 

PM-grade prompt patterns (that consistently produce better plans)

These aren’t “AI prompts.” These are good PM instructions that happen to work well with Copilot.

 

1) The “constraints first” pattern

Create a plan for [project]. Constraints: deadline [date], team size [#], key stakeholder approvals [list], environments [dev/test/prod]. 

Include tasks and milestones that reflect these constraints.

Copilot builds plans based on the details you provide and can generate full plan elements (goals/buckets/tasks). 

 

2) The “deliverables drive tasks” pattern

Deliverables: [list]. 


Create goals for each deliverable and tasks needed to produce, review, approve, and publish each one.

Copilot can create goals and suggested tasks tied to those goals in a premium plan.

 

3) The “expand one bucket” pattern (prevents task explosions)

Add more detailed tasks inside the bucket [name], including subtasks for validation and stakeholder sign-off.

Copilot supports iterating on existing plans—adding tasks/buckets/goals as needed. 

 

Tips & tricks (so it feels polished, not generic)

  • Write prompts like a mini project brief: outcome + audience + timeline + key workstreams. Copilot’s plan generation is only as good as the direction you give it. 
  • Use “/” to attach files. This is the fastest way to reduce generic output and get tasks that match your real deliverables. 
  • Remember where Copilot-in-Planner lives: Copilot in Planner skills are available inside Planner (Teams and the new Planner web experience as it rolls out), even if you have other Copilot experiences elsewhere.

 

PM tips & tricks (so Copilot feels like an assistant—not a novelty)

  • Always start with a Premium plan. If a plan is Basic, users won’t see Copilot in the plan experience. 
  • Use “/” to attach the charter, requirements, or RACI. Attached files are always included as context, and Copilot can also search for relevant files you already have access to. 
  • Ask Copilot for a plan, then ask it questions. “What’s due this week?” and “What’s behind?” are natural next steps once the structure exists. 
  • Treat outputs as a first draft. Copilot accelerates structure and summarization; PM judgment still owns dependencies, dates, and reality.

 

Wrap-up

Copilot in Planner (preview) is a strong addition to the work management toolbox because it tackles the slowest part of planning: turning “we should do this” into a structured plan people can actually execute. It can generate goals, buckets, and tasks from a prompt, help you evolve the plan as requirements shift, and answer basic status questions so you aren’t constantly hunting for what’s due and what’s stuck. 

The one thing you don’t want to skip is the licensing conversation. For a smooth rollout—and to avoid the frustrating “Why don’t I see Copilot?” moment—set expectations clearly: Planner Plan 1 (Planner Premium) doesn’t include Copilot in Planner, and Copilot for Microsoft 365 alone won’t unlock Copilot-in-Planner features. The path is to ensure users have Project & Planner Plan 3 or 5 plus Copilot for Microsoft 365. If you line up licensing first, the rest is the fun part: letting teams go from idea → plan → action in minutes, and spending their time refining the work instead of reinventing the structure.

 

External Links

 

FAQ: Copilot in Planner (preview)

Q1) What is Copilot in Planner (preview)?

It’s an AI-powered assistant inside Microsoft Planner that helps teams plan and execute work by generating plans, goals, buckets, and tasks—and keeping you informed as projects progress. 

Q2) What can Copilot in Planner do?

Microsoft lists these core skills:

  • Generate a full plan (tasks/subtasks, buckets, goals—some elements may be limited to titles during MVP)
  • Generate and add tasks, buckets, and goals to an existing plan
  • Answer basic questions about a plan (example: “What tasks are due this week?”) 

Q3) Where do I find Copilot in Planner?

Open the Planner app in Teams, open a Premium plan, and select Copilot from the plan’s top menu to open the Copilot pane. 

Q4) Why don’t I see the Copilot icon in my plan?

The most common reason is that the plan was created as Basic (Copilot isn’t available there), or the user doesn’t have the required licensing. 

 

Q5) How does Copilot in Planner use my work data?

Copilot can look for relevant files you already have access to and use them as context; you can also attach specific files directly by typing / in the prompt box. 

Q6) How is Copilot in Planner different from Copilot for Microsoft 365?

Copilot in Planner skills are available when you’re using Copilot inside the Planner app experience; Copilot for Microsoft 365 can also help answer questions about your individual tasks (including private tasks and tasks across plans), but it’s not the same as the in-Planner Copilot feature set.

Q7) What languages are supported?

Copilot in Planner supports prompts in Chinese (Simplified), English, French, German, Italian, Japanese, Portuguese (Brazil), and Spanish, with more planned.

Q8) How do I report a bug or request a feature?

Microsoft suggests using thumbs up/down feedback in the Copilot pane, sending feedback directly in Planner in Teams, or using the Planner Feedback Portal.