As a Microsoft Certified Trainer working with enterprise customers across Europe, I’ve seen firsthand the compliance challenges that emerged when Microsoft announced flex routing on April 7, 2026. Flex routing allows large language model (LLM) inferencing for Microsoft 365 Copilot to occur outside the EU Data Boundary during periods of peak demand .
This is the processing step where the AI model executes your prompt to produce an output—summarizing content, answering questions, or generating insights.
What caught many administrators off guard is that flex routing is enabled by default for eligible tenants created after March 25, 2026, with existing tenants requiring verification in Message Center. For organizations subject to GDPR, NIS2, or DORA regulations, this represents a significant shift from Microsoft’s previously cautious approach to EU data boundary features.
The setting affects Microsoft 365 Copilot, Copilot Chat, and Copilot experiences in Dynamics 365, Power Platform, and Copilot Studio. While Microsoft assures that data at rest continues to reside within the EU Data Boundary and remains encrypted in transit, limited pseudonymized data may be stored outside the boundary for security and operational purposes. This creates a compliance decision point that every EU/EFTA administrator must address before April 17, 2026 when routing changes take effect.
Technical Configuration: Admin Center and PowerShell
Admin Center Configuration
The flex routing setting lives in two administrative locations and understanding their hierarchy is critical. The Microsoft 365 admin center controls settings for Microsoft 365 Copilot and Copilot Chat, while the Power Platform admin center manages Dynamics 365, Power Platform, and Copilot Studio. Importantly, the Power Platform admin center honors the Microsoft 365 admin center setting unless the Power Platform setting is more restrictive.
To verify or modify your tenant’s flex routing configuration through the admin center, navigate to the Microsoft 365 admin center as an administrator with the AI Administrator role. The setting is located under Copilot > Settings > Flexible inferencing during peak load periods. Here you’ll find two options:
• Allow flex routing during periods of peak load (default for new tenants)
• Do not allow flex routing
Setting changes are honored within one week of modification.
PowerShell Verification
For administrators managing multiple tenants or seeking automation, while Microsoft has not published official PowerShell cmdlets specifically for flex routing configuration, the setting can be verified through the Microsoft 365 admin center API endpoints.
Note: The admin center UI provides the most reliable method for configuration verification. Refer to the official Microsoft Learn documentation [1] for the latest administrative procedures.
Best Practices from the Field
In my experience deploying these controls across multiple customer environments, I recommend documenting your decision in your organization’s compliance registry and scheduling quarterly reviews, as Microsoft may adjust default behaviors or add new controls as the feature matures.
Compliance Implications for Regulated Organizations
From a compliance perspective, flex routing introduces scenarios that challenge existing data processing agreements and regulatory frameworks. Organizations in specific sectors face heightened scrutiny:
• Public sector entities with strict data sovereignty requirements may find that LLM inferencing outside the EU violates procurement agreements or national security policies .
• Critical infrastructure operators subject to NIS2 Directive requirements cannot accept uncontrollable routing decisions for systems processing sensitive operational data .
• Healthcare and financial services organizations bound by sector-specific data residency mandates may violate regulatory obligations if inferencing occurs outside approved jurisdictions .
• Municipalities and state authorities with explicit no-third-country-transfer policies face direct conflicts with flex routing’s design [4].
The challenge extends beyond GDPR Article 44 transfer requirements. While Microsoft maintains encryption and pseudonymization, the ambiguity around what constitutes ‘limited pseudonymized data’ and ‘operational purposes’ creates documentation gaps for Data Protection Impact Assessments . As one compliance analyst noted, the shift from Microsoft’s previous off-by-default approach for EU boundary features to flex routing’s on-by-default stance marks a significant policy change [2].
My recommendation: if your organization operates in regulated sectors or has explicit data residency commitments, disable flex routing immediately and document the decision. The performance benefits during peak demand do not outweigh compliance risks for most regulated entities.
Eligibility and Multi-Geo Considerations
Flex routing eligibility depends on your tenant’s sign-up location and licensing configuration. The feature is available exclusively for customers with a sign-up location in a country or region within the EU or EFTA . You can verify your tenant’s country or region in the Microsoft 365 admin center under organization profile settings. However, there’s a critical exception: customers who have purchased multi-geo capabilities will not have access to the flex routing setting, even if their tenant is listed as being in an EU or EFTA country or region [1]. This exclusion exists because multi-geo customers already have explicit controls over data residency through their geographic data storage configurations. For multi-geo deployments, data residency is governed by the satellite geography assignments rather than the flex routing mechanism. Understanding your tenant’s eligibility status is the first step before attempting configuration changes—attempting to modify a setting that isn’t available for your tenant type will result in configuration errors.
Flex Routing Eligibility Matrix
| Tenant Type | Flex Routing Available | Configuration Location | Default Setting |
|---|---|---|---|
| EU/EFTA new tenants (created after March 25, 2026) | Yes | Microsoft 365 Admin Center | Enabled |
| EU/EFTA existing tenants | Yes | Microsoft 365 Admin Center | Disabled (opt-in required) |
| Multi-geo tenants | No | N/A | N/A (governed by satellite geography) |
| Non-EU tenants | No | N/A | N/A (data processed in default region) |
