Copilot Studio for US Government customers
This article is for US government customers who are deploying Copilot Studio as a part of a Copilot Studio Government Community Cloud (GCC) plan. It provides you with an overview of features that are specific to these plans.
Government plans are designed for the unique needs of organizations that must meet US compliance and security standards.
We recommend that you read this article and Microsoft Copilot Studio overview.
The Copilot Studio US Government Service Description serves as an overlay to the general Copilot Studio Service Description. It defines the unique commitments and differences compared to the general Copilot Studio offerings that are available to our customers since December 2019.
Microsoft Copilot Studio US Government plans and environments
Licensing for Copilot Studio US Government plans is the same as for public cloud. They're available through the Volume Licensing and Cloud Solution Provider purchasing channels. For more information, see Assign user licenses and manage access.
The Copilot Studio GCC environment is compliant with the Federal requirements for cloud services, including FedRAMP High.
In addition to the features and capabilities of Copilot Studio, organizations that use Copilot Studio US Government plans benefit from the following unique features:
- Your organization's customer content is physically separated from customer content in non-US-Government plans for Copilot Studio.
- Your organization's customer content is stored within the United States.
- Access to your organization's customer content is restricted to screened Microsoft personnel.
- Copilot Studio US Government complies with all certifications and accreditations that US Public Sector customers require.
GCC High environment
Beginning February 2022, eligible customers can choose to deploy Copilot Studio US Government to the GCC High environment.
Microsoft designed the platform and our operational procedures to meet the requirements aligning with the DISA SRG IL4 (Defense Information Systems Agency Security Requirements Guide Impact Level 4) compliance framework.
This option enables and requires the customer to use Microsoft Entra ID for Government for customer identities. By contrast, GCC uses the public Microsoft Entra ID.
For the US Department of Defense contractor customer base, Microsoft operates the service in a manner that enables these customers to meet International Traffic in Arms Regulations (ITAR) commitment and Defense Federal Acquisition Regulation Supplement (DFARS) acquisition regulations, as documented and required by their contracts with the US Department of Defense. DISA has granted a Provisional Authority to Operate.
Customer eligibility
Copilot Studio US Government plans are available to:
- (1) US federal, state, local, tribal, and territorial government entities, and
- (2) other entities, which handle data that is subject to government regulations and requirements and where use of Copilot Studio US Government plans is appropriate to meet these requirements, subject to validation of eligibility.
Microsoft's validation of eligibility includes:
- Confirmation of handling data subject to ITAR
- Law enforcement data subject to the Federal Bureau of Investigation's (FBI) Criminal Justice Information Services (CJIS) Policy
- Other government-regulated or controlled data
Validation may require sponsorship by a government entity with specific requirements for the handling of data.
Entities with questions about eligibility for Copilot Studio US Government should consult their account team. Microsoft revalidates eligibility when it renews customer contracts for Copilot Studio US Government plans.
Differences between customer data and customer content
Customer data, as defined in the Online Service Terms, means all data provided to Microsoft by, or on behalf of, customers using an online service. This includes all text, sound, video, image files, and software.
Customer content refers to a specific subset of customer data that has been directly created by users. This could include for example content stored in databases through entries in the Dataverse entities (for example, contact information). Content is generally considered confidential information, and in normal service operations, isn't sent through the Internet without encryption.
For more information on how Copilot Studio protects customer data, see the Microsoft Online Services Trust Center.
Data segregation for Government Community Cloud
When provisioned as part of Copilot Studio US Government plans, the Copilot Studio service is offered in accordance with the National Institute of Standards and Technology (NIST).
In addition to the logical separation of customer content at the application layer, the Copilot Studio US Government service provides your organization with a secondary layer of physical segregation for customer content. This segregation is achieved by using infrastructure that is separate from the infrastructure used for commercial Copilot Studio customers. This type of usage includes using Azure services in Azure's Government Cloud. To learn more, see Azure Government.
Customer content located within the United States
The Copilot Studio US Government service runs in datacenters physically located in the United States. It stores customer content at rest in datacenters physically located only in the United States.
Restricted data access by administrators
Access to Copilot Studio US Government customer content by Microsoft administrators is restricted to personnel who are US citizens. These personnel undergo background investigations in accordance with relevant government standards.
Copilot Studio support and service engineering staff don't have standing access to customer content hosted in the Copilot Studio US Government service. Any staff who requests temporary permission elevation which would grant access to customer content must first have passed the following background checks.
| Microsoft Personnel Screening and Background Checks 1 | Description |
|---|---|
| U.S. citizenship | Verification of U.S. citizenship |
| Employment history check | Verification of seven (7) year employment history |
| Education verification | Verification of highest degree attained |
| Social Security number (SSN) search | Verification that the SSN the employees provides is valid |
| Criminal history check | A seven (7) year criminal record check for felony and misdemeanor offenses at the state, county, and local level and at the federal level |
| Office of Foreign Assets Control list (OFAC) | Validation against the Department of Treasury list of groups with whom U.S. persons aren't allowed to engage in trade or financial transactions |
| Bureau of Industry and Security list (BIS) | Validation against the Department of Commerce list of individuals and entities barred from engaging in export activities |
| Office of Defense Trade Controls Debarred Persons list (DDTC) | Validation against the Department of State list of individuals and entities barred from engaging in export activities related to the defense industry |
| Fingerprinting check | Fingerprint background check against FBI databases |
| CJIS background screening | State-adjudicated review of federal and state criminal history by state CSA appointed authority within each state that has signed up for the Microsoft CJIS IA program |
| Department of Defense IT-2 | Staff who request elevated permissions to customer data or privileged administrative access to DoD SRG L5 service capacities must pass DoD IT-2 adjudication, based on a successful OPM Tier 3 investigation. |
1. Applies only to personnel with temporary or standing access to customer content hosted in Copilot Studio US Government (GCC and GCC High)
Certification and accreditation
Copilot Studio US Government plans are designed to support the Federal Risk and Authorization Management Program (FedRAMP) accreditation at a High Impact level. FedRAMP artifacts are available for review by federal customers who are required to comply with FedRAMP. Federal agencies can peruse these artifacts in support of their review to grant an Authority to Operate (ATO).
Note
Copilot Studio is authorized as a service within the Azure Government FedRAMP ATO.
For more information, including how to access the FedRAMP documents, review the FedRAMP Marketplace.
Copilot Studio US Government plans have features designed to support customers' CJIS Policy requirements for law enforcement agencies.
Copilot Studio US Government and other Microsoft services
Copilot Studio US Government plans include several features that allow users to connect to, and integrate with, other Microsoft enterprise service offerings such as Power Apps and Power Automate US Government.
Copilot Studio US Government services run within Microsoft datacenters in a manner consistent with a multitenant, public cloud deployment model. However, client applications are limited to the web-user client and aren't available in Microsoft Teams. Government customers are responsible for managing client applications.
Copilot Studio US Government plans use the Office 365 customer administrator UI for customer administration and billing.
The Copilot Studio US Government service maintains the actual resources, information flow, and data management. For purposes of FedRAMP ATO inheritance, Copilot Studio US Government plans use Azure (including Azure for Government) ATOs for infrastructure and platform services, respectively.
If you adopt the use of Active Directory Federation Services (ADFS) 2.0 and set up policies to help ensure your users connect to the services through single sign-on, any temporarily cached customer content will be in the United States.
Copilot Studio US Government and third-party services
Copilot Studio US Government plans provide the ability to integrate third-party applications into the service through Power Automate Cloud Flow, which uses Connectors and Skills. These third-party applications and services might involve storing, transmitting, and processing your organization's customer data on third-party systems that are outside of the Copilot Studio US Government infrastructure. As a result, these third-party applications and services aren't covered by the Copilot Studio US Government compliance and data protection commitments.
Important
Review the privacy and compliance statements provided by the third parties when assessing the appropriate use of these services for your organization.
Governance considerations can help your organization bring awareness about the capabilities available across several related themes, such as architecture, security, alert and action, and monitoring.
Copilot Studio US Government and Azure Services
The Copilot Studio US Government services are deployed to Microsoft Azure Government. Microsoft Entra ID isn't part of the Copilot Studio US Government accreditation boundary. However, the services rely on a customer's Microsoft Entra ID tenant for customer tenant and identity functions. This includes:
- Authentication
- Federated authentication
- Licensing
When a user of an organization employing ADFS attempts to access the Copilot Studio US Government service, the user is redirected to a login page hosted on the organization's ADFS server.
The user provides credentials to their organization's ADFS server. The organization's ADFS server attempts to authenticate the credentials using the organization's Active Directory infrastructure.
If authentication is successful, the organization's ADFS server issues a SAML (Security Assertion Markup Language) ticket that contains information about the user's identity and group membership.
The customer's ADFS server signs this ticket using one half of an asymmetric key pair and then sends the ticket to Microsoft Entra ID via encrypted TLS (Transport Layer Security). Microsoft Entra ID validates the signature using the other half of the asymmetric key pair and then grants access based on the ticket.
The user's identity and group membership information remain encrypted in Microsoft Entra ID. In other words, only limited user-identifiable information is stored in Microsoft Entra ID.
You can find full details of the Microsoft Entra ID security architecture and control implementation in the Azure System Security Plan (SSP).
The Microsoft Entra ID account management services are hosted on physical servers managed by the Microsoft Global Foundation Services (GFS). Network access to these servers is controlled by GFS-managed network devices using rules set by Azure. Users don't interact directly with Microsoft Entra ID.
Microsoft Copilot Studio US Government service URLs
You use a different set of URLs to access Copilot Studio US Government environments, as shown in the following table. The table also includes the commercial URLs for contextual reference.
| Commercial | US Government (GCC) | US Government (GCC High) |
|---|---|---|
| copilotstudio.microsoft.com | gcc.powerva.microsoft.us | high.powerva.microsoft.us |
| flow.microsoft.com | gov.flow.microsoft.us | high.flow.microsoft.us |
| make.powerapps.com | make.gov.powerapps.us | make.high.powerapps.us |
| flow.microsoft.com/connectors | gov.flow.microsoft.us/connectors | high.flow.microsoft.us/connectors |
| admin.powerplatform.microsoft.com | gcc.admin.powerplatform.microsoft.us | high.admin.powerplatform.microsoft.us |
| admin.powerplatform.microsoft.com | gcc.api.powerva.microsoft.us | high.api.powerva.microsoft.us |
For those customers that implement network restrictions, ensure access to the following domains is made available to your end users' access points:
GCC customers
- .azure.net
- .azure.us
- .azure-apihub.us
- .azureedge.net
- .crm9.dynamics.com
- .microsoft.com
- .microsoft.us
- .microsoftonline.com
- .usgovcloudapi.net
- .windows.net
Refer to the IP ranges for AzureCloud.usgovtexas and AzureCloud.usgovvirginia to enable access to Dataverse instances that users and administrators may create within your tenant.
Connectivity between Copilot Studio US Government and Public Azure Cloud services
Azure is distributed among multiple clouds. By default, tenants are allowed to open firewall rules to a cloud-specific instance, but cross-cloud networking is different and requires opening specific firewall rules to communicate between services. If you're a Copilot Studio customer and you have existing SQL instances in Azure public cloud which you need to access, you must open specific firewall ports in SQL to the Azure Government Cloud IP space for the following datacenters:
USGov Virginia
USGov Texas
Refer to the Azure IP Ranges and Service Tags - US Government Cloud document, focusing attention on AzureCloud.usgovtexas, and AzureCloud.usgovvirginia. Also note that these are the IP ranges required for your end users to have access to the service URLs.
Copilot Studio US Government feature limitations
Some of the features available in the commercial version of Copilot Studio aren't available to Copilot Studio US Government customers. The Copilot Studio team is actively working on making these features available to US Government customers and will update this article when these features become available.
| Feature or capability | Available in GCC | Available in GCC High |
|---|---|---|
| Copilot Studio Analytics 1 | ✖ No |
✖ No |
| Copilot Studio Microsoft Teams app experience | ✖ No |
✖ No |
| Teams channel in the Copilot Studio web app | ✔ Yes |
✖ No |
| Transfer to agents | ✔ Yes |
✖ No |
1. Alternatively, you can create Custom Analytics using a Power BI dashboard (blog).
Requesting support
Having a problem with your service? You can create a support request to get the issue resolved.
More information: Contact Technical Support