Same idea as the full Chief: one place that holds who you are, your business, what's on your plate, how you work, and your voice, loaded into every chat. In Microsoft 365 Copilot, that place is an agent you build yourself. Here is how.
Agent Builder lets you make your own Copilot agent by describing what you want in plain language, no code. You give it instructions and point it at your own files in SharePoint or OneDrive. Do this once and you have a Chief that answers from your world. Labels move around as Microsoft updates, so match the meaning, not the exact word.
This is the easy, no-code route. You describe your agent and Microsoft builds it for you.
Instructions set the standing job and the ground rules. You can type them, or switch to the Configure tab to edit them directly.
Act as my chief of staff. I am [name], [role] at [company]. I own [the 3-5 outcomes you are responsible for]. How to work with me: - Lead with the answer. No preamble and no filler. - Direct, plain, short sentences. Write at an 8th-grade level. - One thing at a time. Do not stack questions. - Draft, never send. Get my okay before anything goes out. - Push back when I am vague or wrong. Ask before you assume. - End with the single next step I should take. My voice: [two or three words, e.g. plain, direct, warm]. Words I never use: [list]. Answer from the files in my knowledge sources. If something is not in them, say so.
This is what your Chief reads from. Put your context files in SharePoint or OneDrive, then point the agent at them. Same five files as the full Chief, one for each part of your world.
Copilot Memory quietly remembers your preferences and context over time, so your Chief gets more personal the more you use it. Finish the agent and put it to work.
The basic agent above is user-buildable, but only if your admin has enabled it. In many tenants Agent Builder is on by default, but your IT department can switch off agent creation, publishing, or the connectors that reach your data. If you do not see New agent, that is why.
The powerful parts of the Chief framework, having the AI write back to your files, run scheduled automations, and connect live to your data, live in Copilot Studio and Power Automate. In a company Microsoft tenant those are governed by IT: an admin has to enable agent creation and connectors, premium licenses or capacity are required, and data-governance (DLP) policies apply. So the advanced build may need approvals you do not control.
The contrast worth knowing: in Claude, this whole system, files the AI writes and maintains, automations, connections, runs at the individual level, no admin gate. In Microsoft, the starter agent is yours, but the compounding parts run through IT.