Agents Developers Build

Four build paths, and the one question that separates them: whether the agent can answer with access the person asking does not have. Copilot Studio environments, data policies, maker credentials, authentication, and channels; Agents Toolkit packages; custom engine agents on Azure Bot Service; Foundry.

In GCC High

Every row below is a documented claim until a tenant check turns it into an observation. The basis column says which, and when.

Control	GCC High	Basis
Copilot Studio	Different Available at high.powerva.microsoft.us; client applications are limited to the web client.	Documented 2026-10-05
Copilot Studio: Teams and Microsoft 365 Copilot channel	Not available	Documented 2026-10-05 (also "Copilot Agents extend M365": No)
Copilot Studio: event triggers and autonomous agents	Not available	Documented 2026-10-05
Copilot Studio: code interpreter	Not available	Documented 2026-10-05 ("Sovereign clouds aren't currently supported.")
Copilot Studio audit logging in Purview	Undocumented The prerequisites list a tenant that is not a FedRAMP tenant.	Documented 2026-10-05
Copilot Studio: Control maker credential options	Undocumented	Documented 2026-10-05 (no cloud named)
Pro-code declarative agents (Microsoft 365 Agents Toolkit)	Different Microsoft's pages disagree on support; an administrator uploads the package; custom actions are unsupported.	Documented 2026-10-05 (listed as supported); Documented 2026-10-05 ("Support for GCC High and DoD environments is not yet available")
Custom engine agent in Teams (Azure Bot Service)	Different Azure Bot Service runs in Azure Government; Teams is the only channel in GCC High; no route into Microsoft 365 Copilot is documented.	Documented 2026-10-05
Foundry Agent Service	Different Azure Government, US Gov Virginia and Arizona; no SharePoint, web search, agent-to-agent, or hosted agents; FedRAMP High is Forecasted.	Documented 2026-10-05

#	Where to look	Microsoft documents	If the tenant disagrees
2	Copilot Studio (GCC High), on a test agent: the Channels page, for a Teams and Microsoft 365 Copilot entry; and Microsoft 365 admin center, Agents, All agents, Requests, for Copilot Studio submissions	"Copilot Agents extend M365" and the Teams and M365 Copilot channel are No in GCC High	Copilot Studio agents can reach Copilot: that build path gains the channel and its own requirements.
10	Power Platform admin center (GCC High), Manage, Environments, an environment, Settings, Product, Features: the Copilot Studio agents section, for Control maker credential options	The control exists; no cloud is named	Confirms the maker-credential guardrail. Absence leaves makers able to run tools on their own credentials.
11	Microsoft 365 admin center, Agents, All agents: an Add agent action that uploads an agent package	An administrator publishes a coded agent by uploading its package; Microsoft's pages disagree on Agents Toolkit support for GCC High	Confirms the route to users for pro-code agents.
12	Purview (GCC High), Audit: Copilot Studio activities in the Activities list	Audit logging for Copilot Studio lists a tenant that is not a FedRAMP tenant as a prerequisite	If the activities are listed, changes to Copilot Studio agents are audited in GCC High.