Planner Agent can draft the parts of a weekly status report that come from tasks, such as progress, achievements, milestones and next steps. The delivery lead should update the tasks first, then set the RAG status themselves and add the asks and risks the plan can't hold. This is Cliff's judgement, from two decades of IT delivery experience.
The facts come from Microsoft's support page and a public archive copy of MC1506735, checked 20 October 2026, and say nothing about how good the reports are. Microsoft doesn't say how the agent decides the overall status it summarises. General availability is expected to finish by mid-November 2026, and that date could slip.
If Planner Agent could read a risk log or email alongside the plan, or showed which task each line came from, more of the report could be handed over. Reports whose overall status matched the call an experienced delivery lead would make, across many real projects, would loosen the rule on the RAG status.
Let Planner Agent draft the weekly status report from your plan, then make the red, amber or green call yourself. That call, the RAG status, is a judgement about the whole project, and the agent only sees tasks. Update the tasks before you press Generate, and once the draft lands, add the decisions you need from your readers and any risk that lives outside Planner.
The facts below come from Microsoft's support page on Planner Agent status reports and a public archive copy of Message Center post MC1506735, both checked 20 October 2026. What to keep and what to hand over is my judgement, from two decades of IT delivery experience.
If your weekly status starts from meeting notes rather than a Planner plan, see Package a weekly status playbook as a Claude Skill.
What the agent builds the report from
MC1506735 says Planner Agent builds the report from plan data: tasks, owners, due dates, status, buckets and recent activity. It arranges that into sections you can choose, such as an executive summary, progress, risks and blockers, achievements, milestones and next steps, and Microsoft says the summary covers overall status too. The other inputs Microsoft lists are your own settings, such as reporting period, tone, length, audience and extra instructions, plus any file you attach as a template. Microsoft also says the agent only reads plans you already have permission to see, and doesn't edit the plan or its tasks.
The setup has a floor. Microsoft's support page says the plan must be shared with a Microsoft 365 Group and hold at least 10 tasks, and it can be a basic or premium plan as long as Planner Agent is turned on for it. Generating a report needs a Microsoft 365 Copilot licence. Colleagues without one can open and edit a report, but can't generate a new one. Microsoft Support also says, in a note on the same page, "The status report feature is not supported for named orgs." The page doesn't define named orgs, so check with your Microsoft 365 admin if you're not sure whether that covers your organisation.
You can start from the Reports tab in Planner in Teams, where the draft opens in a Loop canvas, or from Planner Agent in the Microsoft 365 Copilot app. MC1506735 says a finished report can go out as a Copilot Page shared by link, or be exported to Word or PDF.
On timing, MC1506735 says general availability starts worldwide in late October 2026 and is expected to finish by mid-November 2026. That's Microsoft's expectation, and rollout dates do slip. If the Reports tab isn't there, your organisation may not have it yet, or an admin may have blocked the agent, which Microsoft says can be done for the whole organisation.
Update the plan before you press Generate
The report can only be as current as the plan at the moment you generate it. If two tasks finished on Tuesday and are still marked in progress, I'd expect the report to call them in progress, in the same tidy prose as every other line. A stale plan gives you a confident report that happens to be wrong, and nothing in the wording tells you which lines are out of date.
So update first. Close what's finished and move the dates that have moved. If work is happening that isn't a task yet, add it now, because the agent can't report on what the plan doesn't hold. Then set the reporting period to Last week, so the report covers the same window your readers expect. Microsoft's own tip is that reports work best on plans that have been tracked for a while.
The pattern I'd watch for is a report that stays green for weeks while the same dependency sits unresolved in the notes underneath. Every line is true. The overall colour isn't.
What stays with you after the draft
Treat any overall status the draft offers as a suggestion, and set the RAG yourself. Every task can be on track while the project is in trouble, because the sponsor has gone quiet or the go-live date depends on a team that isn't in the plan. A red that reflects that comes from you knowing it, and the agent can't know it from the plan.
My own rule ties the colour to the date. Amber means we can still hit the date, but only with a decision or help from outside the team. Red means we can't hit it without moving the date or cutting scope.
The decisions you need from your readers belong near the top of the report, and the plan won't supply them. A plan holds tasks, and a decision you need from a steering group isn't a task unless you've made it one. Write the asks yourself, saying who you need each one from and by when.
Risks need the same treatment. The risks and blockers section can only draw on what's in Planner. A risk that sits in an email thread or in your own head won't appear unless you put it there, so add those by hand and say where each one is tracked.
Check every line against a task
Before anyone reads it, go through the report with the plan open. Every line about progress or next steps should point to a task you can find, with the owner and date the report gives it. If a line doesn't trace to a task, cut it or make it a task. The parts you added yourself won't trace to a task, so make sure each one says who decided it or where it's tracked.
Microsoft's support page says reports are stored in a SharePoint folder and the Loop view has a See who has access option, so check that list too before the draft is finished.
Before you generate your next weekly report, update the plan, then write the RAG line yourself before anyone else sees the draft.
Sources
Microsoft Support, Generate automatic status reports with Planner Agent. Inputs, plan requirements, licence, the named orgs limit, Reports tab, Loop canvas and storage. Checked 20 October 2026.
Microsoft 365 Message Center Archive (mc.merill.net), MC1506735: Microsoft Planner: AI-generated status reports in Planner Agent, a public archive copy of the Message Center post published 13 October 2026. Plan data used, licence, exports and rollout dates. Checked 20 October 2026.