Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Version: 11.3.0

Microsoft 365 Copilot on GCC High

Overview​

The HYPR AgentPass™ Microsoft 365 Copilot connector can reach Microsoft 365 Copilot in a Microsoft GCC High tenant, as well as in the commercial cloud. GCC High is a separate, network-isolated Microsoft cloud, with its own sign-in, Microsoft Graph and Power Platform endpoints. Tokens issued in one cloud are not accepted in the other.

Each Microsoft 365 Copilot connector records the Microsoft cloud its tenant lives in. Every Microsoft endpoint the connector uses follows from that setting. One gateway can therefore serve a commercial tenant and a GCC High tenant side by side, with each connector reaching only the hosts of its own cloud.

The connector works on GCC High as it does on the commercial cloud. Access is bring-your-own-license, each request uses a per-user delegated token, and the gateway applies the same policy, approval and audit controls. The differences are:

  • Where the apps are registered, and where consent is granted
  • Which hosts the gateway calls
  • Which Copilot surfaces Microsoft offers in that cloud
note

This guide covers only what differs for a GCC High tenant. Read it alongside Connecting Microsoft 365 Copilot and Microsoft Entra Setup for Microsoft 365 Copilot, which describe the connector and its app registrations in full.

Before You Begin​

Have these in place before you configure the connector:

  • A Microsoft 365 GCC High tenant, with Microsoft 365 Copilot licenses assigned to your users
  • Microsoft Entra ID for Government identities. GCC High tenants sign in against the US Government identity service, not the commercial one
  • Access to the Azure Government portal at https://portal.azure.us, with permission to create app registrations and grant tenant-wide admin consent in that tenant
  • Authority to grant admin consent in the GCC High tenant. Consent granted in a commercial tenant does not carry over
  • Network egress from the gateway to the Microsoft US Government hosts listed in Network Requirements
Work in the GCC High tenant itself

Register the applications, grant consent and assign licenses in the GCC High tenant. A GCC High connector accepts only identities and consent from that cloud. App registrations or consent completed in a commercial tenant are not usable.

Register the Applications in Azure Government​

The connector needs the same two Microsoft Entra app registrations as on the commercial cloud: a confidential middle-tier app that performs the On-Behalf-Of exchange, and a public single-page application that signs users in to the Agent Portal.

Follow Microsoft Entra Setup for Microsoft 365 Copilot end to end, with these substitutions.

Step in the Entra setupOn a GCC High tenant
Open the Azure portalUse the Azure Government portal at https://portal.azure.us, not portal.azure.com
Choose the directorySign in to your GCC High tenant with a Microsoft Entra ID for Government account
Add the delegated Microsoft Graph permissionsThe permission names are identical. Add them as delegated permissions, as on the commercial cloud
Grant admin consentGrant it in the GCC High tenant
Register the Agent Portal redirect URIUnchanged: your gateway's public origin plus /portal/, registered as a single-page application
Grant the Power Platform permission for Copilot Studio agentsAdd the delegated CopilotStudio.Copilots.Invoke permission, and grant admin consent in the GCC High tenant

Everything else about the registrations is the same as on the commercial cloud: the single-tenant account type, the exposed access_as_user scope, the authorized-client-application entry and the client secret.

Copilot Studio agents need consent in GCC High

Copilot Studio agents require the delegated CopilotStudio.Copilots.Invoke permission, with admin consent completed in the GCC High tenant. Without it, registered agents cannot be reached, and the Agent Portal shows a consent notice instead of a reply.

For Microsoft's description of the US Government cloud environments and how they differ, see Understand Microsoft US Government cloud environments.

Set the Connector's Microsoft Cloud​

Each Microsoft 365 Copilot connector records which Microsoft cloud its tenant lives in. The connector's sign-in host, Microsoft Graph host, Microsoft Graph scope and Copilot Studio hosts all follow from that one setting, so you enter no Microsoft hostnames by hand.

  1. Create the connector as described in Create the Connector.
  2. On the connector form, set Microsoft cloud to US Government — GCC High. The default is Commercial (worldwide).
  3. Enter the tenant ID, client ID and client secret from the middle-tier app.
  4. Enter the public app's client ID as Portal app (client) ID, and the Exposed API scope.
  5. Leave Graph scopes blank to use the default for the connector's cloud.
  6. Click Create Connector.

A connector with no cloud recorded uses the commercial cloud. Existing connectors keep working unchanged, and need no attention when you upgrade.

Set the cloud before users sign in

Set the cloud when you create the connector, before your users sign in to the Agent Portal. Microsoft does not accept a token from one cloud in the other, so a connector pointed at the wrong cloud cannot sign anyone in.

You can change the cloud later in the connector's edit drawer. Changing it re-derives the Microsoft Graph endpoint, unless a custom host is set.

Agent Portal Sign-In​

Agent Portal sign-in on GCC High needs nothing extra. The portal takes its Microsoft sign-in address from the connector. Once the connector's cloud is GCC High, users sign in against the US Government identity service automatically. No user or administrator setting is involved.

Feature Availability on GCC High​

Microsoft offers a slightly different set of Copilot surfaces in GCC High than in the commercial cloud. This table lists what each connector surface depends on, and what Microsoft makes available there.

CapabilityAvailability on GCC HighMicrosoft source
Chat with Microsoft 365 Copilot in the Agent PortalAvailablecopilotRoot: post conversations
Attach OneDrive files to a messageAvailableMicrosoft Graph national cloud deployments
Earlier Copilot conversations in the history listAvailableaiInteractionHistory: getAllEnterpriseInteractions
Chat with Microsoft Copilot Studio agents you registerAvailable. This is the primary way a GCC High user reaches a custom agentUS Government customers — Microsoft Copilot Studio
The agent list in the Agent PortalAvailable. The list shows Microsoft 365 Copilot plus the Copilot Studio agents your administrators register, and is the same on both cloudsUS Government customers — Microsoft Copilot Studio
Copilot agents delivered through Microsoft Teams or the Microsoft 365 Copilot appNot offered by Microsoft in GCC High. Those agent channels are unavailable in that cloud, which is why registered Copilot Studio agents are the route to custom agentsUS Government customers — Microsoft Copilot Studio
Policies, approvals, budgets, audit trail and Request LogAvailable. These are gateway capabilities, independent of the Microsoft cloud—

Microsoft notes that feature availability and release timing in the US Government clouds can lag the commercial cloud. For the current position, see Understand Microsoft US Government cloud environments.

Network Requirements​

A GCC High connector reaches Microsoft on the US Government hosts only. If your gateway's outbound traffic is filtered, allow these GCC High hosts over HTTPS (TCP 443).

PurposeCommercial cloudGCC High
Microsoft Entra sign-in, token exchange and signing keyslogin.microsoftonline.comlogin.microsoftonline.us
Microsoft Graph: Copilot chat, OneDrive files, conversation history and agent listsgraph.microsoft.comgraph.microsoft.us
Power Platform: Copilot Studio agent conversations*.environment.api.powerplatform.com*.environment.api.high.powerplatform.microsoft.us
Power Platform service endpointapi.powerplatform.comapi.high.powerplatform.microsoft.us

Allow the Copilot Studio host as a wildcard. Each Power Platform environment has its own subdomain beneath environment.api.high.powerplatform.microsoft.us, so one fixed hostname is not enough.

Your users' browsers reach the Agent Portal on your own gateway origin, and the portal signs users in against login.microsoftonline.us. If you filter browser traffic as well as gateway traffic, allow that host for your users too.

For Microsoft's full list of national-cloud service roots, see Microsoft Graph national cloud deployments.

What Your Users See​

On GCC High, the Agent Portal offers the same experience as on the commercial cloud. Users sign in with their Microsoft work account, chat with Microsoft 365 Copilot, attach their OneDrive files, pick up earlier conversations, and chat with the Copilot Studio agents you register.

Tell your users about two differences:

  • The agent list is what you register. The Agent Portal agent list shows Microsoft 365 Copilot plus the Copilot Studio agents you registered, as on the commercial cloud. Microsoft's own Teams and Microsoft 365 Copilot agent experiences are not part of GCC High, so registered agents are the full catalog there.
  • Copilot Studio agents are the route to custom agents. Microsoft does not offer the Teams or Microsoft 365 Copilot channel for agents in GCC High. Agents you register on the connector are how your users reach your organization's custom agents.

For the full user walkthrough, see Chatting in the Agent Portal.

Verify​

Check each of these before you hand the portal to users:

  • The app registrations exist in your GCC High tenant, created in the Azure Government portal.
  • The connector app's Microsoft Graph permissions show Granted for your tenant in that tenant.
  • The connector's Microsoft cloud is set to US Government — GCC High.
  • A Copilot-licensed GCC High test user can sign in to the Agent Portal, and the chat returns a reply.
  • If you registered Copilot Studio agents, a test user can start a conversation with one.
  • Your outbound filtering allows every host in Network Requirements.