Your agency licensed Microsoft 365 Copilot. On April 2, the Analyst agent went live in your GCC (Government Community Cloud) tenant alongside it. It is, statistically, sitting there untouched. You are paying for a data scientist who never gets assigned a ticket.
Most managers who licensed Copilot think of it as a writing assistant that lives in Word and Outlook. Analyst is a different animal, and because nobody announced it to your staff, nobody is using it.
What Analyst Actually Is
Analyst is a code-backed data analysis agent. Microsoft frames it as a virtual data scientist: you hand it structured or unstructured data, it writes and runs secure Python against that data inside the compliance boundary, and it returns visualizations, pattern detection, and written summaries built for decisions and briefings.
Read that again. It writes and runs code. It is not autocompleting a sentence; it is doing the analysis a junior analyst would do, on data you point it at, without leaving your tenant.
What People Think It Does, and What It Doesn’t
Two wrong assumptions kill adoption. First, people think it is a Power BI replacement. It is not; it is the thing you point at a messy export before you have built a dashboard, when you just need to know what is in the data. Second, people think it replaces their analysts. It does not; it does the grunt work, the pivot tables and the first-pass charts, so your analyst spends their time framing the question instead of formatting cells.
You did not buy a chatbot. You bought a data analyst and left it sitting in the parking lot.
How to Turn It On
Capability is not the gap; activation is. A GCC admin enables agents in the Microsoft 365 admin center. Once enabled, users reach Analyst in the Microsoft 365 Copilot app or by @mention. Your tenant’s agent governance and data policies may gate which users see it, which is a configuration decision, not a missing feature, and worth confirming before you tell a room full of people to go try it.
Two Things It Is Good At Right Now
Budget analysis. Drop in the line-item export, ask it to find variance against the last cycle and flag anything that moved past a threshold you set. It returns the chart and the three sentences you would put under it in a briefing, in about the time it takes to find an open conference room.
Incident pattern detection. Point it at a ticket or incident export and ask what is recurring. It clusters the data, surfaces the patterns a human skims past at volume, and tells you which category is quietly eating your team’s week.
Why GCC Makes This Worth Doing Right
Analyst runs inside Microsoft’s FedRAMP-authorized GCC boundary. The Python executes in a sandbox, it honors your Purview sensitivity labels and Entra permissions, and the data does not leave the tenant. The commercial instinct of “just upload it to some tool” dies in a government environment; this is the compliant version of that instinct, which is exactly why it belongs in your workflow instead of shadow AI someone is already using on the side.
Who Is Behind This
I am Jacob, a U.S. Navy veteran and the engineer behind Puget Sound AI, a veteran-owned small business (VOSB). I build and deploy this kind of workflow inside government GCC environments, then hand it to your staff with documentation so it survives after I leave.
If you licensed Copilot and your team forgot Analyst exists, that is an adoption problem with a short fix. Let’s talk.