Microsoft Adds a Sovereignty Switch, and Then Flips You Off

Pillar 03 · Residency

Bias declaration. I run SkyeConnex. I build the thing I spend half this article describing, so weigh it accordingly. I also spent years at Microsoft and helped build bits of what became Intune and MS Graph. I like Microsoft 365. I just don’t like defaults that move my data while I’m not looking.

Congratulations, you have a choice

On September 14, Microsoft gave admins in Germany, France, Norway, Sweden and Switzerland a gift. A brand new switch in the Admin Center called “Store Microsoft 365 customer data in-country.”

It ships off.

Leave it off and from December 14, Microsoft may move your Exchange, SharePoint, OneDrive, Teams and Copilot data wherever in the EU it likes. Still inside the EU Data Boundary. Just not at home anymore.

So the sovereignty feature is opt-out. Do nothing and you’ve opted. Microsoft picked the default. Guess who it works for.

The fine print you weren’t sent

All of this lives in Message Center post MC1470878. You can only read it with tenant access. Everyone else got it secondhand from heise, BornCity and a few admins swapping screenshots.

BornCity says the notice never showed up in its own inbox. Readers who went looking found the option greyed out. A sovereignty switch you can see and can’t touch. Very on brand.

Miss the deadline and flip it later? Repatriation can take about six months. Six months. For a checkbox.

The reason Microsoft gives for all this is load balancing. Hold that thought.

The regulator shrugged

heise said it straight. The setting has “no relevance from a data protection perspective.” The North Rhine-Westphalia data protection authority agrees. Under Article 44 GDPR the problem starts at the EU border. Frankfurt to Dublin doesn’t count.

So Microsoft shipped a sovereignty setting and the regulator says it protects nothing. They’re both telling the truth.

The switch picks where the disks sit. It doesn’t pick who holds the keys. Microsoft runs the storage, the service and the key hierarchy in Germany, in Ireland, everywhere. Microsoft is American. The CLOUD Act reaches whatever it has in its possession, custody or control, wherever the rack happens to be bolted down.

Flip it on and your data sits in Germany, readable by the same company under the same law. Leave it off and it sits somewhere else in Europe, readable by the same company under the same law. Different postcode. Same subpoena.

That’s flag-washing. Put a flag on the building and call it sovereignty. The question was always who can be forced to hand your data over. The answer is identical in all five countries, and it lives in Redmond.

The default tells you the rest. If the vendor can move your data across borders to balance its own load, the vendor decides where your data lives. You got a preference. With a deadline. Announced in a notice you probably didn’t get. Plus a six month timeout if you change your mind.

Canada, don’t get smug

We’re not on the list. Don’t celebrate. Our in-country commitment stands on the same three legs Europe’s just wobbled on. A product term the vendor can rewrite. A setting the vendor controls. A notice you might never see.

If a commitment can be redrawn by Message Center post, it was a courtesy all along.

If you’re on the list, before December 14

1. Open the Data Location card. Read your tenant country and committed geography.

2. Find every contract, policy and audit answer that promises in-country storage.

3. Turn the switch on, or leave it off on purpose. Off by accident is the one wrong answer.

4. Screenshot it, date it, file it. Greyed out? Ask support in writing and keep the reply. You’ll want it in March.

Then ask the question nobody in that Admin Center can answer. Where are your keys?

One bit versus a policy

Microsoft gave five countries one bit per tenant. On or off. Set once, by a deadline, six months to undo.

At SkyeConnex we went the other way. Keep Microsoft. It’s very good at running Microsoft 365 and it’s already in every building. Put custody on top.

Geopolicy is per file. You decide which jurisdictions a file may live in, which providers, how its shards spread. A Protected B record in Ottawa and a marketing archive in Toronto get different rules in the same tenant. Encrypted on your side first, then sharded. Enough shards rebuild it. No single provider holds enough to read it, or to be ordered to.

Then the rules change. They always do. New regulation. New contract. A provider you stopped trusting. A grid that got dirtier.

So we run policy defrag. Change the geo rule and the platform walks your existing shards and moves only the ones that no longer comply. It works frame by frame, copying fragments while the source is still alive. Every move lands in the ledger. No Message Center post. No six months.

And you can watch it. Remember defragging a drive? We all sat there watching little blocks shuffle across the screen. Red ones hopping to the end. Blue ones packing in tight. Absolutely no reason to watch. Everybody watched.

Same thing here. Change the rule and the map lights up. Shards that broke the new rule pick up and move. Shards that comply stay put. Your data walks itself back inside the lines you just drew.

Try watching a greyed-out toggle.

Carbon gets the same defrag with one rule. Legal first, carbon second. Carbon never votes on whether a region is allowed. You can’t put a weight on unlawful. Where the law leaves room, the cleaner grid breaks the tie. Change the carbon setting and shards drift toward the cleaner allowed regions. Fragments nobody can read don’t need a passport.

Microsoft lets you pick a flag. We let you write the rule, and keep it true when the rule changes.

Sovereignty by architecture, not by promise. A toggle is a promise with a deadline.

Sources

• heise online, Microsoft 365 data storage location selectable until December (24 September 2026)

• BornCity, Microsoft 365 moves tenant data to another EU country, opt-out required (24 September 2026)

• Senn Tech, Microsoft 365, choose your data location before 14 December (26 September 2026)

• Topedia, New Microsoft 365 data location setting for in-country data storage

• Microsoft Learn, Data Location Card

• itelio, translation of Message Center post MC1470878