Is Microsoft 365 Copilot sovereign, or does regulated data still leave the building?

No. Microsoft 365 Copilot is not sovereign in the way regulated buyers mean the word. It is a cloud service: prompts and the documents it grounds on through Microsoft Graph are processed inside Microsoft's cloud, not on hardware the customer owns and controls. The EU Data Boundary keeps most of that processing inside Europe, but it does not remove the reach of the United States CLOUD Act, which can compel a US-headquartered provider to hand over data wherever that data physically sits. For a bank, a hospital or a defence supplier, sovereignty means the data and the inference never leave the building, and on that test Copilot does not qualify.

This matters in 2026 because "sovereign" has become a procurement checkbox that vendor marketing answers with data residency alone. Sovereignty is about who can compel access and who can technically reach the data during processing. Regulated buyers are learning to ask the harder question, and the honest answer for any Graph-grounded cloud assistant is that regulated data still leaves the building the moment it is sent for inference.

How does Microsoft 365 Copilot actually process your data?

Copilot works by retrieval augmented generation. When a user asks a question, the service uses Microsoft Graph to find relevant emails, files, chats and calendar items, then sends that grounding data with the prompt to a large language model in Microsoft's cloud. Microsoft states that tenant data is not used to train its foundation models and that traffic stays within the customer's compliance boundary where the EU Data Boundary applies. All of that can be true, yet the regulated content still leaves the tenant's direct control for processing in a shared cloud.

Does the EU Data Boundary make Copilot sovereign?

No. The EU Data Boundary is a residency commitment. It means Microsoft processes and stores in-scope customer data within the European Union and European Free Trade Association region, which reduces cross-border transfer. It does not change corporate nationality, and nationality is what the CLOUD Act turns on. A provider incorporated in the United States is within reach of a US warrant or subpoena for data under its control, even with servers in Amsterdam or Dublin. Residency and sovereignty are different properties, and only one of them is a legal shield.

What did Microsoft confirm to the French Senate in 2025?

In 2025, during testimony to the French Senate, Microsoft confirmed it could not guarantee that data held in its European cloud would never be transferred to United States authorities under the CLOUD Act. This was not a leak or an accusation. It was the provider stating the plain legal position: a US-headquartered company must comply with lawful US demands for data it controls, and no European data centre changes that obligation. For buyers, this is a clear signal that residency inside the EU Data Boundary and immunity from foreign access are not the same thing.

What is the difference between data residency and data sovereignty?

Data residency answers where data is stored and processed. Data sovereignty answers who has jurisdiction over it and who can technically access it. A service can be fully resident in Frankfurt and still be legally reachable from Washington. True sovereignty demands that no foreign law and no third party can compel or effect access, which in practice means the data and the model run on infrastructure the customer owns, inside a perimeter the customer controls, with no path out.

“Residency tells you where the data sleeps; sovereignty tells you who can wake it, and only inference that never leaves operator-owned hardware answers both.”

Which rules make on-premises inference necessary?

Several regimes now push regulated entities towards inference that stays inside their own control:

• US CLOUD Act. Creates the extraterritorial reach that residency cannot cancel.
• GDPR. Restricts transfers of personal data to third countries and expects demonstrable control over processing.
• DORA. In force since January 2025, it makes financial entities accountable for the oversight of their critical ICT third parties.
• NIS2. Extends security and accountability duties across essential and important entities in critical sectors.
• EU AI Act. The high-risk Annex III obligations once due on 2 August 2026 were deferred by the Digital Omnibus to 2 December 2027, with embedded Annex I high-risk duties moving to 2 August 2028 and the Article 50 transparency rules largely unchanged. We read this as a build window, not a reprieve.
• ISO/IEC 42001. The AI management-system standard against which governance can be certified.

What can an auditor actually check?

An auditor cannot inspect the inside of a shared cloud inference call. What an auditor can check is a sealed record, and this is the architectural line that separates a cloud assistant from a Sovereign Intelligence Operating System (a SIOS). Mickai runs offline on operator-owned hardware behind a zero-egress inbound perimeter, so regulated data has no route off the machine. Every action is cryptographically sealed to a post-quantum signed audit ledger using FIPS 204 (ML-DSA), so the record can be verified independently and cannot be quietly altered. Identity is hardware-attested and bound to the same chain, and sensitive decisions can go to cross-model consensus rather than one opaque model. Our approach is protected by 104 filed UK patent applications and approximately 2,340 claims, owned by Mickai LTD and patent pending.

How should a regulated buyer decide?

Ask one question and demand a technical answer: during inference, can any party outside the organisation compel or effect access to this data? For any cloud assistant grounded through a provider's own graph, the honest answer is yes, however small the probability. For inference that runs entirely on hardware the buyer owns, with no egress path, the answer is no by construction. Copilot is a capable assistant for data a buyer is content to process in a shared cloud, but not the right home for data that regulation, contract or national interest says must never leave the building.

Frequently asked questions

Is Microsoft 365 Copilot GDPR compliant?

Microsoft offers contractual and technical measures, including the EU Data Boundary, that support GDPR compliance. Compliance is not the same as sovereignty. GDPR permits certain transfers with safeguards, and the CLOUD Act can still create a lawful access path for a US-headquartered provider, so buyers with strict sovereignty requirements should treat GDPR alignment as necessary but not sufficient.

Can the US CLOUD Act reach data stored in the EU?

Yes. The CLOUD Act can compel a US-headquartered provider to produce data under its control regardless of where the servers physically are. Microsoft confirmed this position to the French Senate in 2025. Storing data inside the EU Data Boundary reduces routine transfer but not the legal reach.

What makes an AI system genuinely sovereign?

A genuinely sovereign system runs on infrastructure the customer owns, inside a perimeter the customer controls, with no path for data to leave during processing. It should provide offline verifiability, a zero-egress inbound perimeter, hardware-attested identity and a tamper-evident audit ledger. If any of those depend on a foreign-controlled cloud, the system is resident, not sovereign.

Is on-premises AI less capable than Copilot?

Capability now depends on architecture and governance more than on cloud scale. A Sovereign Intelligence Operating System can run capable sovereign models on operator hardware, ground them on the organisation's own data and apply cross-model consensus for high-stakes decisions. The trade is not capability for control; it is control gained without surrendering the data.

Does the EU AI Act require sovereign AI in 2026?

Not directly, and the timeline has moved. The high-risk Annex III obligations once due on 2 August 2026 were deferred by the Digital Omnibus to 2 December 2027. The direction of travel towards demonstrable control, logging and human oversight is unchanged, which is why we treat the extra time as a build window, not a reason to wait.