Microsoft 365 data residency in Switzerland from 14 December 2026

Microsoft 365 data residency in Switzerland now depends on a tenant setting. Since 14 September 2026, eligible commercial tenants whose Default Geography is Switzerland, France, Germany, Norway or Sweden have a setting called “Store Microsoft 365 customer data in-country”, and on 14 December 2026 the choice recorded in each tenant takes effect: where it is Off, Microsoft may begin moving Exchange Online, SharePoint, OneDrive, Teams and Copilot data at rest out of Switzerland to storage elsewhere in the EU Data Boundary. Turning it back On later starts a return move that Microsoft says “can take approximately 6 months”.

This post covers who must decide, where the data goes, Swiss data protection law (the FADP, or nLPD), sector rules, Copilot and a dated checklist. As of 9 October 2026, Microsoft’s documentation, updated on 8 October 2026, still gives 14 December 2026, and it still did when we checked again on 31 October and 7 November 2026.

Microsoft 365 data residency in Switzerland: what changes on 14 December 2026

Microsoft’s Product Terms Data Residency page places the setting on the Data Location Card, under Admin > Settings > Org settings > Organization profile > Data location > Commitments. In German, the label reads “Microsoft 365-Kundendaten im Land speichern”, according to ioz.ch.

• On. Microsoft keeps Core Services data at rest in the Product Terms geography: Switzerland, for a Swiss tenant.
• Off. Microsoft “may store your Microsoft 365 Core Services data regionally within the EU Data Boundary”.

The Core Services are Exchange Online, SharePoint, OneDrive for Business, Teams, Microsoft 365 Copilot and Copilot Chat. Other services, such as Forms and Planner, are outside this commitment and have their own data locations (see Microsoft’s Data Location FAQ).

Documented on Microsoft Learn, not in the Product Terms

The published Product Terms, read on 9 October 2026, still list Switzerland where “Microsoft will store the following Customer Data at rest only within that Geo”, with no opt-out. The Learn page calls itself an overview, says the Product Terms prevail where they differ, and gives the commitment period as “equal to the length of the customer’s agreement with Microsoft (typically 1-3 years)”. Ask Microsoft or your reseller, in writing, which version of the Product Terms your agreement incorporates and whether its in-country commitment runs to the agreement’s end, whatever the setting shows.

Which Swiss tenants have to decide?

Every eligible commercial tenant with a Swiss Default Geography has to decide. Some need a different check:

• ADR, ADR-E and Multi-Geo tenants. Their paid offering already governs residency, so they do not see the setting.
• Tenants that never joined the Legacy Move Program. Microsoft says they “may not be eligible”, that the programme ended on 30 April 2023, and that Advanced Data Residency (ADR) is now the only durable commitment that includes migration.
• Education tenants. The setting is commercial only, and for an EU or EFTA tenant without the ADR for Education add-on, Microsoft’s Office 365 Education terms already allow storage “anywhere within the European Union”.

The default varies too. Microsoft documents Off only for tenants created after 14 September 2026 and sends older tenants to the Message Center. As reported, not verified by us: heise (24 September 2026) and a Borncity reader cite post MC1470878, under which the setting stays disabled unless an administrator acts; the reader’s copy gives Microsoft’s reason as “to help maintain a high-performing service in the EU/EFTA”. ioz.ch (23 September 2026) reports the same without naming the post; empowering.cloud (22 September 2026) reports a variant, MC1470876, defaulting to On. Borncity reported the switch greyed out on 24 September 2026 and apparently fixed on 25 September; readers still found it missing or greyed out on some older tenants, linking this to the Legacy Move Program. Only your own Data Location Card settles it.

Where does the data go if the setting stays Off?

If the setting stays Off, Microsoft 365 Core Services data at rest remains within the EU Data Boundary, subject to the limited transfers Microsoft documents for it. The Data Location Card shows “No Commitment” for the Core Services, but Microsoft says the separate EU Data Boundary commitment “remains in place regardless”. The EU Data Boundary covers the 27 EU states plus Iceland, Liechtenstein, Norway and Switzerland.

Microsoft’s glossary lists Microsoft 365 datacentres for the “European Union/EFTA” region in 13 countries: Austria, Denmark, Finland, France, Germany, Ireland, Italy, the Netherlands, Norway, Poland, Spain, Sweden and Switzerland. The EU Data Boundary page adds Belgium and Greece, announced or operating, and says more may follow. Backups follow the commitment; for a region, the FAQ says they may span “multiple countries or regions”.

Microsoft said on 25 February 2026 that it operates cloud regions near Zurich and Geneva “so customers can keep data within national borders when needed”. The setting decides whether your tenant is committed to them. It changes where data sits, not which company operates the service (see the CLOUD Act and what a foreign authority can reach).

Does EU storage breach Swiss data protection law?

Storing Microsoft 365 data elsewhere in the EU or EFTA does not by itself breach the FADP. Article 16(1) FADP allows disclosure abroad where the Federal Council has found adequate protection, and Annex 1 of the Data Protection Ordinance lists every EU and EEA state, which covers every EU Data Boundary country other than Switzerland. As of 9 October 2026 we found no FDPIC statement on the setting.

The paperwork does change. Article 19(4) requires the controller to tell data subjects the State to which their data is disclosed, and article 12(2)(g) requires the record of processing to name it. With the setting Off, Microsoft names no single State, only the 31-state EU Data Boundary, with Microsoft 365 datacentres listed in 13 of them. Notices, records and client statements saying “stored in Switzerland” need review. Our nLPD page sets out what we give you, as processor, for that record.

Sector rules and contracts to check

• First-pillar and family-allowance bodies. The Federal Social Insurance Office’s eGov Mitteilung Nr. 054 (10 March 2025, updated on 30 May 2026 at the FDPIC’s request) is expressly not a general approval of Microsoft 365. It requires these bodies’ data to be processed and stored only in datacentres in Switzerland, with a Swiss tenant. The text exists in German and French, not English, so the summary is ours. On our reading, leaving the setting Off conflicts with that condition, and because it covers processing, Copilot’s regional inferencing and flex routing belong in the same assessment.
• The federal administration. The same document records the Federal Council’s decision that it may not process particularly sensitive personal data in Microsoft 365 (see Bern’s open-source workplace).
• FINMA-supervised institutions. Circular 2018/3 permits outsourcing abroad if the institution can expressly assure that it, its audit firm and FINMA can exercise and enforce their inspection and audit rights (margin no. 30), and if restructuring or wind-down in Switzerland stays possible, with the necessary information accessible in Switzerland at all times (margin no. 31). A new storage country belongs in the outsourcing inventory (margin no. 14). See FINMA outsourcing.
• Contracts and secrecy. Check client contracts and DPAs that promise Swiss storage, and any professional secrecy duty under article 321 of the Swiss Criminal Code.

Copilot: flex routing, billing and in-country processing

Flex routing can run Copilot inference outside Europe

Microsoft’s flex routing page (29 September 2026) says it is on by default for eligible tenants created after 25 March 2026. When on, “LLM inferencing may occur in the United States, Canada, or Australia during times of peak demand”, and limited pseudonymised data may be stored outside the EU Data Boundary. Office 365 for IT Pros (7 April 2026) reported that post MC1269223 switched it on for existing EU and EFTA tenants from 17 April 2026; readers reported a variant, MC1269219, that left it off. An AI Administrator switches it off under Copilot > Settings > View all > Flex routing during peak load periods; doing so also locks it off for Copilot Studio, Dynamics 365 and Power Platform. See also what stays inside a private AI deployment.

Usage-based billing, moved to early 2027

Microsoft announced in Partner Center that usage-based billing would become the default for new Microsoft 365 Copilot Business licences bought through CSP from 1 December 2026, with an adjustable default limit of 4,000 Copilot Credits per user per month. On 3 November 2026 it moved that date: the rollout “is planned to begin during Microsoft’s FY27 Q3 (January-March 2027)”, the default limit stays at 4,000 credits, and the new timeline applies “across all markets”.

A separate announcement, of 14 October 2026, adds that from 1 December 2026 new Microsoft 365 Copilot and Copilot Business offers can be bought without a qualifying Microsoft 365 base subscription, at the same prices, and replace the current offers, renamed “(add-on)”, for new purchases. The billing announcement, as updated on 3 November, applies usage-based billing to new Copilot Business licences “including standalone offers and bundles”.

Copilot processing in Switzerland: regional, not in-country

Microsoft’s announcement of 4 November 2025 listed Switzerland for in-country Copilot processing in 2026. An editor’s note of 3 April 2026 says EU and EFTA countries will instead get local inferencing “at a regional level”.

What to do before 14 December 2026

Where Microsoft documents a default for new tenants or licences, it is the broader option in all three cases: EU/EFTA-wide storage, inference outside Europe at peak load, and usage-based spending. Keeping the narrower one takes an administrator’s decision.

1. By 23 October 2026, read every tenant. A Global Administrator screenshots the Data Location Card: whether the switch exists, its state, and the Current and Committed Geography.
2. By 30 October 2026, file the notice. Keep your tenant’s Message Center post (reported as MC1470876 or MC1470878) with the screenshots.
3. By 13 November 2026, decide. The DPO, legal, compliance and IT list every obligation naming Switzerland and record the decision, owner and reasons.
4. By 30 November 2026, set it. If Swiss storage is required, a Global Administrator switches it On and checks that the Committed Geography shows Switzerland. If the switch is missing or greyed out, ask Microsoft or your CSP in writing.
5. By 1 December 2026, review Copilot. An AI Administrator decides on flex routing in the Microsoft 365 admin center; disallowing it there also turns it off for Copilot Studio, Dynamics 365 and Power Platform. If you buy Copilot Business through CSP, agree the spending limit with your partner before usage-based billing becomes the default, now planned for January to March 2027.
6. By 14 December 2026, if you accept EU/EFTA storage, update the paperwork. The privacy notice (art. 19(4)), the record of processing (art. 12(2)(g)), the outsourcing inventory and client statements promising Swiss storage.
7. From January 2027, check every quarter. Re-read the Data Location Card, the flex routing setting and the Learn pages.

Data location is a setting now: what to ask any provider

Procurement and data protection officers should ask any provider, in writing, for:

• A location in the contract. And which document governs if contract and documentation differ.
• Consent before a move. Set notice and your written agreement.
• Every copy. Backups, replicas, logs and support exports.
• The way back. How long a return move takes.
• A tested exit. See exit plan and exit strategy.

How Pilae fits

For workloads that must stay in Switzerland by contract rather than by a tenant setting, Pilae runs open-source apps on your premises or on dedicated machines in Pilae Cloud, with Zurich the default for Swiss data (regions). Every machine and backup target is named in your contract and data processing agreement, backups go to a second site in the same jurisdiction, and data is not moved to another country without your written agreement (data residency). Because the apps run on machines you or your contract name, there is no tenant setting to forget and nothing in a US provider’s hands to disclose (CLOUD Act and your data location).

This does not have to mean leaving Microsoft 365. Files, chat, the wiki and sign-in can move to the sovereign workplace one app at a time, with Keycloak federating Entra ID, while mail stays in Exchange Online: Pilae does not operate mail (Microsoft 365 alternative). Copilot can stay for everyday work while confidential material goes to a private assistant whose prompts and files stay on machines you control (Copilot alternative). To plan the split, talk to an engineer.

This post is general information, not legal advice. For the binding texts, see Microsoft’s Product Terms and data residency documentation, the FADP on Fedlex (no official English version), and the rules of your sector.