Agentic workflows inside GCC High
Microsoft 365 Copilot became generally available in GCC High at the end of 2025, and agents have moved quickly since. If you are planning work in that environment, the question is not whether agents exist there. It is which kinds you can actually use, which ones are still only in the commercial cloud, and what that difference means for the work you are designing.
Varmoda’s cleared teams build inside these boundaries every day, and they see the same pattern. Agents that help a person as they work are available today and worth using. Agents that run on their own are not. The gap is closing, but it is still real. A program that assumes it has the same features as the commercial cloud will design something it cannot launch.
The confusion is understandable. Microsoft announces a capability, the press covers it, and a program assumes it will arrive everywhere at once. It does not. The commercial cloud gets it first, GCC High follows some months later, DoD later still, and the classified environments later again, if at all. Every one of those steps is a separate approval, not a switch somebody flips.
That matters because the cost of getting it wrong is not a missing feature. It is a design built around something that was never going to be there, discovered late, when the schedule has no room left in it. Varmoda has been brought in to unpick that more than once.
What follows is the current state of play, what Varmoda’s teams build inside it today, and how to leave room for the capabilities that are still coming.
What is available, and what is not
| Pattern | GCC High | What it means in practice |
|---|---|---|
| Assistive Copilot on tenant data | Available | Summarize, draft and search across mail, files, chat and meetings, using only what the person is already allowed to see. |
| Declarative agents, scoped | Available | An agent fixed to a set of instructions and a set of documents. It cannot reach anything outside what it was given. |
| Declarative agents with Actions | Available | Generally available in GCC High and DoD since mid-2026, on desktop and web. An agent can now take an action rather than only answer. |
| Autonomous and event‑triggered agents | Not available | Triggers and autonomous agents are marked unavailable for both GCC and GCC High. Nothing runs unattended on a schedule or an event. |
| Computer‑use agents | Not available | Generally available in the commercial cloud, with the government clouds left out of that release. |
IL5, IL6 and the defense environments
GCC High is not the whole picture. Varmoda’s defense work runs across three separate environments, and the rules for agents are different in each one. Treating them as the same place is the fastest way to build something that will never be approved to run.
| Environment | Impact level | What Varmoda’s teams plan for |
|---|---|---|
| GCC High | IL4, for sensitive but unclassified work | Agents that help a person, including ones that can take an action. None that start themselves, none that drive a screen, and no Microsoft 365 Copilot connectors. |
| DoD | IL5 | The same kinds of agent, in the most tightly separated environment, and the slowest to receive new features. Agents that can take an action arrived here at the same time as GCC High. |
| Secret and above | IL6 and classified | A separate approved cloud with its own sponsorship and its own approval to operate. Microsoft does not publish which features it has, so Varmoda treats every agent feature as unavailable until the program confirms it through its own approval channel. |
What IL5 changes about the design
IL5 is for sensitive government information that needs more protection than IL4 gives it. The DoD environment exists to provide that extra separation. Varmoda’s experts plan for three things that follow from it.
- New features arrive months behind the commercial cloud, so a feature that is only promised is never built into the plan.
- Fewer outside tools can connect, so the design is built around what is approved, not around what the documentation says exists.
- The official who approves the system, not the product roadmap, decides when a feature can be switched on.
What IL6 changes about the design
IL6 handles classified information up to Secret, and getting approved there is a different process entirely. It needs sponsorship from the Defense Counterintelligence and Security Agency, cleared staff, and its own approval to operate.
Varmoda tells programs working at IL6 to assume nothing carries over from the unclassified side. The design built for GCC High or DoD can move across, but each agent feature inside it has to be checked and approved again, one at a time. Varmoda’s teams build the work so the part that does the thinking can be swapped out, because at IL6 it often has to be.
Varmoda’s test is the same at every level. If the work needs an agent to start itself, reach the open internet, or click through a screen, it does not belong in a government cloud today. If it needs an agent to gather, think about and draft from what the organization already holds, it does.
The three constraints that shape every design
No unattended execution
Agents cannot start themselves in GCC High or DoD. Every one of them runs because a person asked it to. That rules out the idea people usually draw first: an agent that watches a queue, picks up a case, works it and closes it overnight.
What is left is still worth having. The agent sits one click inside a person’s work, does the gathering and the drafting, and hands back a result the person checks and approves.
In Varmoda’s experience this loses less than it first seems. The step where a person checks the work is usually the step that matters for compliance, and it is far easier to show an approving official a human sign-off than a log of jobs that ran by themselves.
Web grounding is off by default
To guard against data spillage, web grounding is disabled by default in GCC High. Agents answer from tenant content, not from the open internet. If the work quietly assumed the agent could look something up online, it needs a real source inside the boundary instead: a document library, a list, or a business system reached through an approved connection. Varmoda’s teams list those sources while designing, rather than finding the gap during testing.
Connectivity is narrower than commercial
This limit is the one people most often get wrong. Microsoft 365 Copilot connectors, which pull outside content into Copilot’s answers, are not yet available in GCC High. Power Automate connectors are a different thing and they do work in the US Government clouds, which is how most of the joining up actually gets done.
Getting an agent to its users is narrower too. Several of the ways agents are normally shared through Teams are not available in GCC High, so how people will reach the agent has to be planned rather than assumed.
Where agentic workflows earn their place
These are the patterns Varmoda’s teams have put into production inside the boundary.
- Response and submission drafting. An agent scoped to a past-performance library, a solutions archive and a requirements document produces a first draft in minutes rather than days. The writer edits rather than starts.
- Policy and authorization support. Pointed at the system security plan, the control list and past assessment findings, an agent answers control questions and shows the document it came from, which is the next thing an assessor asks for.
- Service desk knowledge. An agent over resolved tickets and runbooks gives a technician the known-good procedure without a search through four repositories.
- Program and status reporting. An agent that reads the plan, the risk log and the week’s correspondence assembles a status draft the program manager corrects and sends.
All four save the same two things: the time spent hunting for information and the time spent writing a first draft. A person still owns the decision. That is what the government clouds support today, and it is what holds up when an inspector general asks who approved what.
Where they do not
Anything that requires the agent to act without supervision: monitoring that fixes problems by itself, overnight queue processing, cases that open themselves when something happens, or scheduled checks between two systems.
These are real problems, but they are automation problems, not agent problems. In GCC High and DoD, Varmoda solves them with Power Automate, Azure Functions or the tools the agency already has, and saves the agent for the step where judgment and writing are genuinely needed.
Mixing the two up is the most common and most expensive mistake Varmoda’s teams get called in to fix. A program buys an agent platform to solve a scheduling problem, finds that the trigger it needs does not exist in its cloud, and spends three months rebuilding what a simple flow would have done in two weeks.
How Varmoda plans for the gap closing
Where this is heading is clear. Agents that can take an action arrived in GCC High and DoD a little over six months after Copilot itself, and the government clouds have followed the commercial cloud rather than drifted away from it. Varmoda builds for today’s limits while keeping the pieces easy to swap.
- Keep the agent’s instructions and its sources in version control, separate from whatever starts it, so a manual launch can become an automatic one later without a rewrite.
- Put the human approval step in deliberately, as a control rather than as a workaround. It stays useful after the constraint lifts.
- Keep the connection to other systems in Power Automate rather than inside the agent, so the data route is already approved and already logged.
- Ask what is available in this particular cloud and at this particular level at every design review. Matching the commercial cloud is a date, not a given, and IL5 and IL6 each have their own.