Microsoft has introduced a “flexible routing” option for customers in the European Union and the European Free Trade Association using Copilot. This feature allows, during periods of peak demand, language model inference to be processed outside the EU data boundary to ensure a more stable experience. Simply put: when there are load spikes, part of the processing for a Copilot request may be handled at data centers in the United States, Canada, or Australia.
This measure does not affect all customers nor does it operate the same way across all services, but it requires Microsoft 365, Power Platform, and Dynamics 365 administrators to review their configurations. For regulated organizations, legal departments, compliance officers, and security teams, this is no minor adjustment. The question is no longer just whether Copilot is available in Europe but where the inference runs when demand exceeds local capacity.
What is Microsoft Copilot’s flexible routing?
Microsoft defines inference as the step where an AI model processes an instruction to generate a response. This can be a document summary, answering a question, assisting with drafting an email, or an action within a Copilot experience.
With flexible routing enabled, this inference can leave the EU data boundary during times of high demand. Microsoft affirms that data remains encrypted in transit and at rest, and that data at rest continues to be stored within the EU data boundary, except for limited pseudonymized data that can be stored outside for operational and security reasons.
This nuance is important. Microsoft is not saying that all content of a European tenant will be permanently stored outside Europe. Instead, the setting allows model processing to be temporarily executed in another region when additional capacity is needed. This technical distinction may be relevant, but it does not eliminate compliance questions for companies with strict residency commitments, contractual controls, or international data transfer assessments.
The feature applies to customers with tenant registration in EU or EFTA countries or regions. It is not available to customers who have purchased multi-geographic capabilities, even if the tenant is registered in a European country. Microsoft recommends administrators check the tenant’s country or region from the Microsoft 365 admin center.
Enabled by default for eligible new tenants
One of the most sensitive points is the default setting. Microsoft states that flexible routing is enabled by default for eligible tenants created after March 25, 2026. For existing tenants prior to that date, administrators should consult the Message Center to find out the default configuration applied to their organization.
This makes review an immediate task for IT teams. It is not enough to assume that, being in Europe, all Copilot inference will always stay within the EU data boundary. Nor is it sufficient to rely on a corporate policy drafted months earlier, because the configuration may depend on the tenant’s creation date and the specific service.
In Microsoft 365, the setting is managed from the Admin Center by a user with the AI Administrator role. The path Microsoft provides is Copilot > Settings > View all > “Flexible routing during high load periods”. From there, the feature can be enabled or disabled.
The Microsoft 365 Admin Center setting applies to both Microsoft 365 Copilot and Copilot Chat. For Dynamics 365, Power Platform, and Copilot Studio, the configuration is managed from the Power Platform admin center. Microsoft clarifies that Power Platform respects the Microsoft 365 setting unless Power Platform’s own setting is more restrictive.
If an organization chooses not to enable flexible routing, the LLM inference remains within the EU data boundary even during demand spikes. Microsoft affirms that in such cases, their data processing and residency commitments for Microsoft 365 continue to apply.
Why this matters to European companies
The change comes amid ongoing discussions about digital sovereignty, cloud dependency, and AI in the enterprise sector. Many European organizations have adopted Microsoft 365 Copilot precisely because it integrates within an established corporate platform with identity controls, security, auditing, and compliance. However, generative AI adds a new layer: prompts, retrieved context, and responses may involve sensitive information.
For an industrial company, a legal firm, a financial entity, a public administration, or a healthcare organization, the location of processing can be part of their risk analysis. Although data is encrypted and Microsoft implements protective measures, allowing inference outside the EU data boundary may require internal assessment, contractual review, and documented decision-making.
Not all organizations will reach the same conclusion. Some will prioritize service continuity and user experience during load peaks, while others may prefer to restrict processing within the European boundary, even if that impacts performance at certain times. The key is for the decision to be deliberate, not based on an default value that no one reviewed.
Microsoft documentation also notes that with flexible routing enabled, inference may occur in the United States, Canada, or Australia during peak times. For compliance teams, this specific list of locations is useful for evaluating legal frameworks, transfer agreements, internal policies, and sector-specific obligations.
What should administrators do?
The first step is straightforward: verify the actual tenant configuration. Administrators should log into the Microsoft 365 admin center with the appropriate role and review whether flexible routing is permitted. Then, they should document the decision, especially in organizations with data residency policies or regulatory requirements.
The second step is to coordinate Microsoft 365 with Power Platform. A tenant may have Copilot in productivity apps and, at the same time, Copilot experiences in Dynamics 365, Power Platform, or Copilot Studio. If each team only reviews their own console, the configuration might be incomplete.
It is also advisable to involve security, legal, privacy, and procurement teams. The setting is not solely technical; it affects contracts, vendor assessments, processing records, risk analysis, and internal communication. In large organizations, it makes sense to incorporate this review into the broader Copilot adoption process rather than leaving it as an isolated task for the administrator.
The final recommendation is to periodically review the Microsoft 365 Message Center. Copilot features evolve rapidly, with many updates first announced as administrative notices. In an environment where AI relies on distributed computing capacity, residency and processing policies may change more frequently than with traditional cloud services.
Flexible routing does not inherently make Copilot unsafe. However, it is important to remember that data sovereignty in AI is not solely a regional choice. It also depends on where inference is run, what data traverses, how it is encrypted, what exceptions are permitted, who can modify the settings, and how decisions are documented.
Frequently Asked Questions
What is Microsoft Copilot’s flexible routing?
It is an option that allows the inference of language models to be processed outside the EU data boundary during periods of high demand to ensure a smoother experience.
Where can inference be processed if enabled?
Microsoft states that during demand spikes, inference may occur in the United States, Canada, or Australia.
Is it enabled by default?
Yes, for eligible tenants created after March 25, 2026. For earlier tenants, Microsoft recommends checking the Message Center to see the default setting applied.
How can an administrator disable it?
From the Microsoft 365 admin center, with an AI Administrator role, navigate to Copilot > Settings > View all > “Flexible routing during high load periods” and select the option to disable it.