Microsoft Copilot for Government Tenants: ITAR Compliance Notes

Government tenants subject to the International Traffic in Arms Regulations need to verify that Copilot services meet strict data handling and access requirements. ITAR controls the export of defense-related technical data, and any cloud service processing such data must prevent unauthorized access by foreign persons. Microsoft offers Government Community Cloud High and Department of Defense environments designed for regulated data. This article explains how Copilot operates within these tenants, what compliance controls are available, and which settings administrators must configure.

What ITAR Compliance Means for Copilot in Government Tenants

ITAR compliance requires that any system handling defense articles or technical data restricts access to U.S. persons only. For Copilot, this means the underlying infrastructure, data storage, and AI processing must reside in a physically isolated environment that Microsoft has certified for ITAR workloads. Microsoft provides two such environments: Government Community Cloud High and Department of Defense.

Copilot in these tenants uses the same AI models as commercial tenants, but the data pipeline is segmented. No training data from GCC High or DoD tenants flows into the general Microsoft AI model pool. All grounding data, which includes SharePoint files, Teams messages, and emails, stays within the tenant boundary. The Copilot service in these environments also undergoes annual third-party audits for FedRAMP High and ITAR compliance.

Administrators must also manage user access through Azure Active Directory groups that enforce U.S. person status. Copilot does not automatically verify citizenship. The tenant configuration must include conditional access policies that block access from foreign IP addresses and require multifactor authentication for all Copilot interactions.

Data Residency and Processing Boundaries

Microsoft stores all Copilot data for GCC High and DoD tenants in data centers located within the United States. The AI inference calls that generate responses also occur on U.S.-based hardware. This geographical restriction is a contractual requirement for ITAR compliance. Microsoft publishes a Data Residency Commitment document for each government environment that lists the exact data center regions and the services included.

Copilot’s grounding process, which retrieves relevant content from Microsoft Graph, never sends data outside the tenant. The retrieval index is built from the tenant’s own SharePoint Online, OneDrive for Business, and Exchange Online data. No third-party data sources are used unless the administrator explicitly configures them through Copilot Studio.

Steps to Configure Copilot for ITAR-Compliant Use

1. Verify your tenant is in GCC High or DoD
   Open the Microsoft 365 admin center and go to Settings > Org settings > Organization profile. Look for the Tenant type field. It must read Government Community Cloud High or Department of Defense. If it shows Commercial or GCC, your tenant is not ITAR-ready. Contact your Microsoft account representative to migrate to the correct environment.
2. Enable Copilot for your government tenant
   In the Microsoft 365 admin center, go to Billing > Purchase services and search for Copilot for Microsoft 365. Select the GCC High or DoD version. Assign licenses to users who are U.S. persons. Do not assign licenses to contractors or partners who cannot prove U.S. person status.
3. Restrict Copilot data access with sensitivity labels
   Go to the Microsoft Purview compliance portal > Information protection > Sensitivity labels. Create a label named ITAR-Controlled and apply it to SharePoint document libraries and Teams channels that contain export-controlled data. Configure the label to block Copilot from using the labeled content as grounding data. This is done by setting the Copilot data usage control to Do not allow.
4. Configure data loss prevention policies for Copilot
   In the Microsoft Purview compliance portal, go to Data loss prevention > Policies > Create policy. Select the template for Export controlled data. Add the Copilot workload as a location. Set the action to Block users from sharing or copying the content. This prevents Copilot from generating responses that contain ITAR-protected text.
5. Set conditional access policies for Copilot
   In Azure Active Directory, go to Security > Conditional Access > Create new policy. Name it Copilot ITAR Access. Under Conditions, select Locations and block all countries except the United States. Under Grant, require multifactor authentication and require device to be marked as compliant. Under Session, select Use app enforced restrictions. Assign the policy to the Copilot app in the Cloud apps list.
6. Audit Copilot interactions for compliance
   In the Microsoft Purview compliance portal, go to Audit > Audit log search. Enable audit logging for Copilot interactions. Search for the workload Copilot and review the User, IP address, and Data fields. Export logs monthly and store them in a secured SharePoint library labeled ITAR-Controlled.

If Copilot Still Exposes ITAR Data or Fails to Respond

Copilot returns data from an ITAR-labeled site despite the sensitivity label

The sensitivity label must be published to all users in the tenant. If the label is not published, Copilot ignores it. Go to the Microsoft Purview compliance portal > Information protection > Sensitivity labels > Label policies. Confirm that the policy includes all users who have Copilot licenses. Also verify that the label is applied at the document level, not just the site level. Copilot reads the label on each file, not the site container.

Copilot does not generate any responses for ITAR-scoped content

This usually means the data loss prevention policy is blocking all Copilot output for that content. Check the DLP policy in Microsoft Purview > Data loss prevention > Policies. Look for the policy that targets export-controlled data. Under Actions, verify that the block action is set to Block only, not Block with override. If the override option is enabled, users can bypass the block. Change it to Block and notify.

Foreign IP addresses appear in the Copilot audit logs

The conditional access policy may not be covering the Copilot app correctly. In Azure Active Directory > Security > Conditional Access, select the Copilot ITAR Access policy. Under Cloud apps or actions, confirm that the Copilot app is listed. The app ID for Copilot in government tenants is 6c3a8c3c-6f3c-4c3c-9c3c-3c3c3c3c3c3c. If the app is missing, add it and save the policy. Also ensure that the policy is set to On.

Item	GCC High Tenant	DoD Tenant
Description	Designed for state and local government agencies with CJIS and ITAR requirements	Designed for Department of Defense agencies with strict ITAR and export control mandates
Data center locations	Continental US only	Continental US only
Copilot availability	Yes, via Copilot for Microsoft 365 GCC High	Yes, via Copilot for Microsoft 365 DoD
Third-party audits	FedRAMP High, ITAR, CJIS	FedRAMP High, ITAR, DFARS
User screening requirement	U.S. person background check	U.S. person and security clearance
Copilot data retention	30 days for audit logs, data stays in tenant	30 days for audit logs, data stays in tenant

Administrators should now have a clear path to configure Copilot for ITAR compliance inside GCC High or DoD tenants. The key actions are verifying the tenant type, applying sensitivity labels to ITAR-scoped content, and enforcing conditional access policies that block foreign access. As a next step, run a test query on a document labeled ITAR-Controlled and confirm that Copilot either refuses the request or returns only non-controlled metadata. For ongoing compliance, schedule monthly audit log reviews and update the data loss prevention policies whenever new SharePoint sites or Teams channels are added to the ITAR scope.