Microsoft 365 Copilot for Project Management: Planner, Teams and Loop

Microsoft 365 Copilot helps a project manager in four places, each documented by Microsoft today. Copilot Notebooks keep one piece of work’s files, meetings and instructions together. Copilot connectors bring other systems into Copilot’s answers. Planner Agent, which Microsoft used to call the Project Manager agent, turns goals into tasks, works tasks you assign it and writes status reports inside Planner. And Copilot in Teams, Loop and Outlook recaps meetings, summarizes pages and condenses long threads. It is strongest when your work already lives in Microsoft 365. What it does not give you is a board that assistants outside Microsoft 365 can work on as named members. For that you connect one, which Microsoft supports through an MCP tool in a Copilot Studio agent.

Copilot Notebooks: one home per piece of work

Microsoft’s guide to getting started with Copilot Notebooks↗ (opens in a new tab) describes a notebook as an AI-powered workspace for the content that matters to one task: Copilot chats, files, pages, meeting notes and links, with custom instructions, shared with your team in real time. You can add a SharePoint site or a OneDrive folder as a reference, so a notebook can follow the project’s own document library rather than copies. Notebooks work in the Microsoft 365 Copilot app and in OneNote, and Microsoft notes some features are still rolling out.

• References that earn their place: the charter, the current plan, the stakeholder list with who decides what, the last few status reports, and the meeting recaps.
• References that go stale: exported task lists and spreadsheets of who is doing what. Point Copilot at the live plan instead.
• Instructions: the audience for updates, the length, the date style, and what to do when a fact is missing.

You support the project manager for the Website Relaunch project.
Status updates go to the client's marketing director: plain English,
no internal jargon, 200 words at most.
Dates are US style (October 14, 2026).
Never invent a date, owner or number. If the references do not say,
write "unknown" and list it under Questions.
When I add a meeting recap, sort it into decisions, actions (one
owner each) and open questions before doing anything else.

Copilot connectors: reaching systems outside Microsoft 365

Microsoft’s Copilot connectors overview↗ (opens in a new tab) describes two kinds. Synced connectors index outside content, such as Jira, Confluence, ServiceNow or Google Drive, into Microsoft Graph so Copilot can search it. Federated connectors use MCP to fetch data live without indexing it. Both respect the source system’s permissions. Today federated connectors are read-only, and Microsoft says write actions arrive starting in early October 2026. Admins set connectors up in the Microsoft 365 admin center.

For a project manager the useful pattern is the same as with any assistant: read freely, write with approval. Let Copilot search the tracker and the wiki, and keep changes to records behind a person.

Planner Agent: the job the Project Manager agent used to do

Many guides still describe the Project Manager agent. Microsoft now calls it Planner Agent. According to Microsoft’s Planner Agent FAQ↗ (opens in a new tab), it is generally available, works in basic and premium plans shared with a Microsoft 365 group, and is reached from Planner on the web, Teams and Copilot chat. It does three things:

• Works tasks you assign it. Its output appears in a Loop component in the task, where you and the team review, edit or ask it to try again. Microsoft says it is best at tasks with text or image output.
• Writes status reports from the plan’s structure, progress, assignments and recent activity.
• Generates tasks from a goal and relevant files, in premium plans only.

Each person who interacts with it needs a Copilot license; colleagues without one can still work on the plan. Premium plans need a Planner license as well. In premium plans, Planner Agent chat is what Microsoft previously called Copilot in Planner. Admins can switch both off, or limit them to a security group, as Microsoft’s admin guide to turning off Planner Agent↗ (opens in a new tab) explains. How Planner works as a board, and its limits, is in Microsoft Planner as a kanban board.

Teams, Loop and Outlook: meetings, pages and threads

In a Teams meeting, Copilot summarizes key points, including who said what, suggests action items and answers questions during or after the meeting. Microsoft’s page on Copilot in Teams meetings↗ (opens in a new tab) is clear about the catch: to ask Copilot about a meeting after it ends, the meeting must have been transcribed. The intelligent recap, with AI notes and follow-up tasks, comes with a Copilot license or Teams Premium.

• Loop: Copilot drafts pages, brainstorms, and summarizes a page or recaps what changed, which suits a shared project page the whole team edits.
• Outlook: Copilot summarizes a long thread with citations to the messages, drafts replies, and can start a meeting invitation from a thread.
• Teams chats and channels: Copilot summarizes what you missed, with the main points, action items and decisions.

Drafting plans and status updates

Drafting is where Copilot saves the most time, as long as the facts come from something real. In Copilot chat or a notebook, point it at the sources, give the audience and the length, and forbid it from filling gaps.

Using the Planner plan, this week's meeting recaps and the files
below, draft this week's status update for the client.
- Three sections: Done this week, Next week, Needs a decision.
- Under 200 words. Plain English.
- Every item must come from these sources. If a date or owner is
  missing, write "not yet set" rather than guessing.
- End with a list of anything you left out and why.

The same shape drafts a plan from a brief, a risk list from a plan, or an agenda from open questions. A library of these is in prompts for project management with AI.

Where Copilot alone stops

• Licenses per person. Planner Agent, Copilot in Loop and the meeting recap each need licenses Microsoft lists by name; teammates without them see the output but cannot use the feature.
• Recall depends on transcription. A meeting nobody transcribed cannot be asked about afterward.
• Connectors read before they write. Federated connectors are read-only until Microsoft’s write actions arrive, and Copilot Chat does not write back to outside systems without action connectors or agents.
• Assistants outside Microsoft 365 are outsiders. Claude, ChatGPT or a coding agent reach Planner only through the Microsoft Graph API, which covers basic plans, not premium, and acts with a person’s or an app’s permissions rather than as a member with its own role.
• Status is only as fresh as the input. An update drafted from last week’s export is last week’s status, written confidently.

None of this is a flaw. For a team that lives in Microsoft 365, Planner with Planner Agent may be all the board it needs. The gap appears when several different assistants, and the people behind them, need to work on one list and be told apart.

Connecting a board through a Copilot Studio agent

Copilot reaches a board that has a remote MCP server through an agent built in Copilot Studio, which Microsoft includes for authenticated users with a Microsoft 365 Copilot license (with limits its licensing page spells out). Microsoft’s guide to connecting an agent to an existing MCP server↗ (opens in a new tab) gives the steps, supports the Streamable HTTP transport only, and notes that admins can instead register a server centrally, through Agents 365 and the Microsoft 365 admin center:

1. In Copilot Studio, open the agent’s Tools page, select Add a tool, then New tool, then Model Context Protocol.
2. Enter a server name, a clear description, and the server URL. For fenbs that is https://fenbs.ai/api/mcp.
3. Choose OAuth 2.0, then Dynamic discovery. fenbs publishes the OAuth discovery and dynamic client registration endpoints that option looks for.
4. Create a new connection, sign in to fenbs, tick what the agent may do, and select Add to agent. Turn off any tools the agent does not need.
5. Publish the agent and connect it to the Teams and Microsoft 365 Copilot channel, so people can use it there.

Power Platform data policies that govern connectors govern MCP servers too, so if an option is missing, ask your admin.

What Copilot can do on fenbs

fenbs is a task board where people and AI assistants are members with roles. Once connected, the agent should start with fenbs_whoami and fenbs_get_context, which gives it the team’s rules from the Decisions and rules page first, then the AI context notes every assistant reads. It files features, enhancements and bugs with fenbs_create_item, each with a note for the problem, a plan, and a priority from 1 to 10 where 1 is the most urgent, and moves them through To Do, Next Up, In Progress and Completed. Each sign-in gets an access token that lasts an hour and refreshes, and you can revoke it in Settings at any time. Every change appears in History under the assistant’s name, acting for the person who signed in. fenbs has no due dates, sprints or assignee field, and no Teams tab, so dates and owners go in the task note.