Organizational Copilot does not have a universal “EU / United States / Custom” dropdown that guarantees every prompt, response, log, and connected service stays in a chosen region. Administrators need to check storage commitments, inference routing, and model or agent exceptions separately. This guide reflects Microsoft’s documentation checked on October 14, 2026.
1. Start with the service and the type of data
Identify the exact product, tenant cloud, sign-up geography, subscription, and enabled features. Microsoft Copilot for work, consumer Copilot, Copilot Studio, and Security Copilot do not share one universal location control. Microsoft’s organizational documentation is transitioning from the Microsoft 365 Copilot name to Microsoft Copilot; product names in licensing and admin screens may differ.
Separate these questions:
- Data at rest: Where are stored interaction records, source files, and other committed data kept?
- Data processing: Where can the model process the prompt and grounding content?
- Other data flows: Which subprocessors, agents, web searches, diagnostics, or support operations are involved?
Microsoft’s data-residency overview distinguishes stored data from processing. Neither a document’s original country nor the network endpoint observed on a PC proves where every AI operation occurs.
2. Check the real data-location view and storage commitments
In the Microsoft 365 admin center, go to Settings → Org settings → Organization profile → Data location. The Data Location Card documentation describes Current Geography and Committed Geography. Record both, the service, and the check date. The card displays selected services; Copilot Chat is not currently shown even though it can have storage commitments.
The card is not a general AI-processing-region selector. Microsoft documents a separate in-country storage setting for certain eligible commercial tenants in France, Germany, Norway, Sweden, and Switzerland, with exclusions for paid residency offerings. Its presence and effect depend on eligibility. Do not enable or disable it as a substitute for reviewing processing requirements.
Copilot residency commitments differ across Product Terms, Advanced Data Residency, and Multi-Geo. In the documented Multi-Geo scenario, the interacting user’s Preferred Data Location determines storage of the interaction; an absent or invalid value falls back to the tenant’s primary provisioned geography. That does not mean the source document moves with the interaction. Check each workload and migration status rather than assuming one setting relocates all data.
3. For eligible EU/EFTA tenants, review flex routing
The EU Data Boundary comprises EU and EFTA countries; the United Kingdom is not included simply because it is in Europe. Eligibility follows the documented tenant conditions. Microsoft says tenants that purchased Multi-Geo are not in scope for the Microsoft 365 EU Data Boundary, so do not describe Multi-Geo as an automatic enhancement of that commitment.
Eligible tenants have a real flex-routing control. An AI Administrator can review Copilot → Settings → View all → Flex routing during peak load periods. Allowing it permits some inference outside the EU Data Boundary at peak demand. If your approved policy requires declining that routing, choose Do not allow flex routing through the organization’s change process.
Microsoft documents flex routing as enabled by default for eligible tenants created after March 25, 2026; administrators of older tenants should check their actual setting. The setting concerns inference, not a migration of stored interaction history. Limited pseudonymized operational data has separate transfer provisions. Availability also differs for tenants that purchased or used Multi-Geo, and the related Power Platform setting has its own documented interaction with this control. Do not assume a missing control is a licensing fault or will appear after waiting 24 hours.
4. Review model exceptions and retain an evidence record
Turning off flex routing is not a blanket certification for every enabled AI model. Microsoft’s Anthropic subprocessor documentation says these models are excluded from the EU Data Boundary and applicable in-country processing commitments. Review Copilot → Settings → View all → AI providers operating as Microsoft subprocessors with the authorized administrator.
The Microsoft 365 apps setting for Anthropic has its own scope and interaction with the global provider setting. Inspect both the permitted users and relevant app experience; do not infer a tenant’s actual configuration from a general default. Also review enabled agents’ terms and web-search data flows using Microsoft’s organizational Copilot privacy guidance.
Keep a dated record of the tenant, product, committed data categories, observed settings, enabled providers, documented exceptions, and any unresolved support question. Confirm the applicable Product Terms and contractual commitments with your organization’s privacy and legal owners before handling regulated data. These checks support a review; they do not themselves guarantee legal compliance or complete data sovereignty. There is no verified universal 30-minute activation time or Defender log that proves all Copilot processing stayed in a selected region.