If your company runs on Microsoft 365, the setup you build in Copilot has somewhere further to go than the equivalent on any other platform. A Notebook you assemble for your own weekly work can become an agent, go through IT review, and end up in a catalogue where every office installs it the way they would install anything else.
Table of Contents
Most coordinators never find out that path exists, so a good setup stays where it was made and dies with the person who built it. I want to walk through the whole thing: what a Copilot Notebook actually holds, what to put in one for crew work, how the step from Notebook to agent works, what the approval process involves, and where the ceiling sits for a company that does not have a large IT function.
What a Copilot Notebook is
A Notebook is a container holding the references and working material for an ongoing piece of work, which lets Copilot reason across all of it at once rather than taking one file at a time and losing the connections between them. Ask whether a date change creates a crew conflict and it can consider the schedule, the assignments and the phase sequence together instead of making you paste three documents first.
Two things about availability are worth knowing before you plan any of this around it. Microsoft extended Notebooks to Copilot Chat users in June 2026, beyond the Microsoft 365 Copilot users who previously had them, making shared notebook collaboration considerably more available across a team. In July it added Markdown, TXT and RTF files as supported references, with Markdown following in August, which matters for anyone whose site documentation is not sitting in Office formats.
The more eye-catching capabilities need a caveat that vendor-adjacent write-ups tend to skip. When Microsoft announced the April 2026 wave of Copilot updates, which covered referencing SharePoint content and OneNote notebooks, generating Word documents or PowerPoint presentations from notebook content, sharing a notebook with a Microsoft 365 Group, and mind-map views, it described that set as rolling out in preview to users signed up for the Frontier program. Treat those as direction of travel and build this quarter’s work on what your own tenant already has.
What belongs in a crew planning notebook
| What to reference | Why it earns a place |
|---|---|
| Phase sequence for active jobs | The thing you re-explain constantly, and it holds steady for months |
| The manpower report format the GC asked for | Demonstrating the format beats describing it, and it stops you rewriting output |
| Current crew assignments | What most questions are actually about, though see the staleness note further down |
| Standing site constraints and access rules | Written down once at mobilization and referred to constantly afterwards |
| The labor curve from the estimate | Lets you ask where the current plan has drifted from what was bid |
| Certification and licence status for gating scopes | Stops the notebook proposing a crew that cannot legally perform the work |
The pattern is the same one that governs any saved setup: material that changes slower than you will realistically maintain it belongs in the Notebook, and this week’s specific change belongs in the prompt where you can see what you gave it.
From a notebook to an agent the company installs
1. Build and use the Notebook first
Use it for a few weeks before you consider anything downstream, because what you are really doing is finding out whether the references are the right ones and where the output still needs your hand, and that is far cheaper to discover while the thing is still yours alone.
Give it a situation you already handled and compare what it produces against what you actually sent, which tells you three things at once: whether it holds your format, whether it invents anything, and whether it flags the gaps you would have flagged yourself.
Example test prompt: “The GC has pulled the level 3 rough-in on Halston forward by two weeks. Draft the manpower notice in our format, flag any crew this puts in conflict across jobs, and list anything you had to assume.”
Where the output is wrong the fix is almost always a reference or an instruction rather than a cleverer prompt, and corrections made at that level hold for everyone who uses it later rather than needing to be retyped each time.
2. Turn the setup into an agent with Agent Builder
Agent Builder is where a configured setup becomes something with a name and an identity that other people can run without knowing how you built it. The instructions carry the same weight here as anywhere else in this series, and the refusals matter more once other people will be relying on it.
Example agent instructions: “You produce the weekly manpower notice for our mechanical crews across active commercial jobs. Follow the format in the referenced example exactly. Group hours by phase and area. Flag any crew assigned to overlapping jobs at the top of the output, before anything else. Never estimate an hours figure that was not provided. Never state that a certification is current unless it appears in the referenced status list. If a required input is missing, list it as outstanding and continue rather than filling the gap.”
3. Submit it for administrator review
Since April 2026, Agent Builder can submit an agent for administrator review and approval before it is published to the organisation’s Agent Store. Microsoft’s stated purpose is to let organisations scale distribution of high-quality internal agents while keeping IT admin control.
Once approved, the agent appears in the Agent Store under a section called “Built by your org,” where people across the company can find it and install it. The thing a coordinator built in Denver goes through a review and then sits in a catalogue, under a heading saying the company made it, and the Phoenix office installs it like anything else.
Worth knowing what the reviewer is actually looking at, because it shapes how you should write the thing. They see the instructions you wrote, which means the refusals and the terminology are the parts under scrutiny rather than the polish of the output. An agent whose instructions plainly say what it will not do is far easier to approve than one whose instructions read as a general encouragement to be helpful, so writing for the reviewer and writing for quality turn out to be the same exercise.
None of the other major platforms go this far. A Claude Project can be shared with your team, a ChatGPT Project with contributors, a Gemini Gem like a file in Drive, and all three stop at the same place, which is other people using your setup rather than the company publishing it to itself.
4. Answer three questions before you submit anything
All three are considerably cheaper to answer up front than to discover afterwards, and the first one stops more projects than the other two put together.
- Who can approve an agent, and do they know that is now part of their job? Submitting for review requires somebody who owns the Microsoft 365 admin centre and has time to look.
- What does your tenant actually have today, as against what the release notes describe? Preview capability is not a plan.
- Who owns the agent after it is published? An approved agent with no owner ages exactly as badly as an unapproved one.
5. Watch whether anyone uses it
Microsoft added an Agent 365 Dashboard in July 2026, letting leaders track agent usage and adoption across the organisation with drill-down by individual agent. Publishing something and never checking whether it gets installed is how companies end up with a catalogue of agents nobody opens, and the dashboard is the cheapest available answer to that.
Where this falls short
The path assumes an IT function, which is the honest constraint. Plenty of mid-market specialty contractors run on one IT generalist or an outsourced provider, and “submit for administrator review” then means emailing somebody who has never opened Agent Builder and has no reason to prioritise it. That is a reason to find out who that person is early rather than a reason to dismiss the capability.
There is a Microsoft-shaped boundary too, since none of this applies if your company runs on Google Workspace, where the tooling and the ceiling are both different.
What you get without reaching the full path matters more than the ceiling does, because most readers will not reach it this year. A shared Notebook already solves the smaller half of the problem: the setup stops living in one account, a second person can open it, and the thing survives a holiday. That alone justifies the afternoon, and treating the Agent Store as the entry point rather than the ceiling is how people talk themselves out of starting at all.
Approval also does not make the underlying information current, which is the limit worth being clearest about. An agent can pass review, sit in the Agent Store under your company’s name, and be installed by every office, and it will still answer from the documents it was pointed at rather than from the live state of who is on which crew this week. Rigour about how a tool gets published and freshness of the data underneath it are separate problems, which is the difference between an approved assistant reading a document and the kind of agents that work from live workforce data covering team assembly, assignment matching and change digests.
Opinion: approval is the feature, not the friction
The review step reads like bureaucracy and it is the most valuable part of the whole path. A shared setup nobody senior has read is a liability waiting for the wrong week, because private tools do not get checked and unchecked instructions accumulate quiet bad habits.
It also solves a problem specialty contractors have independent of AI. When offices plan workforce in silos they build their tools in silos too, so four offices each spend an afternoon solving the same problem slightly differently and none of the four versions can be improved centrally. A published agent is the version, and improving it improves it everywhere at once.
The sequence that works is the ordinary one that governs what makes a rollout actually stick with any tool: one person who likes it, then a small group, then the company, with review happening at the point where the consequences of getting it wrong justify the step. Most setups never need to reach the Agent Store, and the ones that do will be obvious because people keep asking for them.
