Copilot Flex Routing and the EU Data Boundary: What Changed in April 2026 and What to Switch Off

Flex Routing is Microsoft's mechanism for handling demand spikes on Copilot's EU infrastructure. When the usual EU processing capacity is under load, Flex Routing can send the LLM inference call to a data centre outside the EU Data Boundary instead of queuing it. A Copilot response your European staff normally expect to be processed inside the EU may, under load, be processed somewhere else.

"Under load" is doing a lot of work in that sentence. Microsoft does not publish a live figure for how often this triggers (a number I would also like to see), so the honest position is that it can happen, not that it constantly does.

Before 17 April 2026, EU Data Boundary coverage for Copilot read, in practice, closer to a flat guarantee for EU tenants. Since that date, Flex Routing exists as a named, admin-controlled setting layered on top of the Data Boundary, and it is on by default in most tenants.

Two independent write-ups that cover the mechanics in technical detail, changepilot and innfactory, both describe the same change: a real, documented routing behaviour, not a rumour making the rounds in Microsoft 365 admin forums.

Nobody sent out a press release when this landed (Microsoft rarely does for admin-level routing changes), which is exactly why it tends to surface in the middle of a rollout rather than before one. A data protection officer asks a precise question about where processing happens, and the honest answer now has a clause attached to it that did not exist a few months earlier.

The EU Data Boundary already covers Copilot as an in-scope service for EU customers, following the Preferred Data Location of the user who wrote the prompt in normal operation. I have written that part up in more depth, including exactly where prompts are stored at rest, on the Copilot GDPR and EU Data Boundary page. Flex Routing sits on top of that normal operation as the exception, not a replacement for it. When capacity allows, processing stays where the Data Boundary rules already put it. Under load, it does not.

Copilot data residency in Europe does not need a task force or an external audit to verify. It needs 1 specific question, put to whoever holds admin access: is Flex Routing switched on for our tenant right now, and do we know why.

Anthropic-provided models available inside Copilot are excluded from the EU Data Boundary, regardless of the Flex Routing setting. That exclusion is separate, it was already true before 17 April 2026, and Flex Routing does not change it either way. Admins decide independently whether third-party models power their Copilot experiences at all.

Keep these 2 facts apart when you brief a compliance team (I have watched them get merged into one worry more than once). Flex Routing is about where Microsoft's own models process a request under load. The Anthropic exclusion is about a different provider entirely, and it applies whether Copilot is busy or quiet.

None of this should derail a rollout. It should get 1 line on an agenda before the rollout starts: has someone checked the Flex Routing setting, and does the answer match what employees, a works council, or a compliance team have already been told. That question fits naturally into the kind of live online Copilot training for European companies I run, where the admin questions tend to come up in the first 10 minutes anyway.

Training and data residency usually get treated as 2 separate jobs, owned by 2 separate people who rarely sit in the same meeting. In practice they answer to the same audience. The people asking "where does our data go" in a Copilot session are, more often than not, the same people who will ask a works council or a customer the same question a month later. Answering it once, clearly, saves everyone the second version of that conversation.

Copilot, GDPR and the EU Data Boundary · Copilot Training for European Companies · Live Online Copilot Workshops

Sources: changepilot and innfactory both publish technical write-ups of the Flex Routing mechanics referenced above.