Microsoft turned on Researcher in GCC on April 2. Within a week I watched government teams start scoping custom agents to do exactly what Researcher now does out of the box. That instinct, build it yourself, is how the public sector wastes the most time on AI.
What Actually Shipped
On April 2, 2026, Microsoft expanded its agentic Copilot stack into U.S. government clouds. Researcher is rolling out now, starting with GCC (Government Community Cloud). Analyst is live across GCC, GCC-High, and DoD. Agent Builder is available in GCC and GCC-High, and Copilot Studio publishing landed at the GCC level so you can share vetted agents into Teams and Microsoft 365.
Researcher is the one most teams will misread. It runs multi-step research across your work content and produces grounded, source-cited drafts, inside the government cloud compliance boundary. It is not a chatbot. It plans, gathers, and synthesizes, then shows you where every claim came from.
The Decision That Actually Matters
Three tools, three jobs. Match the tool to the job and you skip weeks of build.
Researcher. Use it when the task is “read across a pile of my tenant’s content and give me a sourced synthesis.” Policy comparisons; a background memo assembled from scattered SharePoint and email; a year of meeting notes distilled into a decision brief. Zero build. You point it at content you already have permission to see, and it cites its sources.
Agent Builder. Use it when you want Researcher-style grounding plus a fixed job, packaged so a team gets the same answer every time. You bundle instructions, prompts, and a knowledge source into a reusable agent. No code, no orchestration, no connectors. Think the onboarding assistant or the procurement-policy explainer that ten people share.
Custom Copilot Studio agent. Use it when the agent has to do something, not just read and answer. Multi-system actions, a custom tool or MCP server, a Graph or PowerShell call, a topic tree with branching logic, line-of-business connectors. That is real engineering, and it is the right call only when the simpler two can’t reach.
If Researcher already answers the question, building an agent to answer it is just expensive cosplay.
Where Government Teams Overbuild
The pattern I see constantly: someone needs a “policy assistant,” and the reflex is a full Copilot Studio build with custom topics and a vector index. Half the time Agent Builder with the right knowledge source does it in an afternoon; the other half, Researcher answers the question with citations and no build at all. The custom agent only earns its cost when you need actions, external systems, or orchestration the platform tools can’t express.
GCC sharpens this. Every custom agent you stand up is another thing to govern: data boundaries, Purview labels, conditional access, audit logging, a publish-and-review path. In a regulated environment, the cheapest agent to secure is the one you didn’t build. Out-of-box tools inherit the platform’s compliance posture; your custom orchestration inherits your mistakes.
A Quick Test Before You Build
Ask three questions, in order. One: does Researcher already produce the synthesis I need from content I can already access? If yes, stop. Two: can Agent Builder package the job with a knowledge source and consistent instructions? If yes, stop. Only if the agent must take actions, call external systems, or run custom tools do you open Copilot Studio. Most requests die at question one or two, and that is a feature, not a failure.
Who’s Behind This
I build the third category, custom GCC agents with citation-bound retrieval, MCP tooling, and audit logging, when the job genuinely needs it. I also tell government teams when it doesn’t, because billing you to rebuild Researcher would be a poor way to earn repeat work. Veteran-owned small business, solo by design, so you talk to the engineer who builds it, not an account manager.
If your team is sizing an agent and isn’t sure which of the three you actually need, let’s talk.