EU AI Act + Microsoft 365 Copilot: The Compliance Plan

There is a date hanging over every European Copilot deployment: August 2, 2026 — when the EU AI Act's core obligations become enforceable for most providers and deployers of AI systems. I keep meeting two extreme reactions in architecture reviews: teams that assume "Microsoft handles it" and teams quietly planning to switch Copilot off. Both are wrong, and both are expensive.

This is the practical division of responsibility — what Microsoft covers, what lands on you as the deployer, and a compliance plan that fits in the months remaining.

What does the EU AI Act actually require from a Copilot customer?

Under the AI Act, your organization is in most cases a deployer of an AI system, not a provider. Deployer obligations center on four things: using the system according to its instructions, ensuring appropriate human oversight, ensuring staff have adequate AI literacy (Article 4 — already in application since February 2025), and meeting transparency duties where AI interacts with people or generates content. The heavier provider duties — model documentation, training-data summaries, systemic-risk assessment for general-purpose AI — sit primarily with Microsoft and the model providers upstream.

That sentence should reduce your panic, not your diligence. "Deployer" is the smaller role, but it is not an empty one — and regulators will ask you, not Redmond, how a decision assisted by Copilot was overseen in your organization.

What does Microsoft cover for you?

More than most compliance teams realize, and it is worth citing precisely:

• Microsoft has stated its commitment to compliance with the EU AI Act across its AI portfolio, building on its Responsible AI Standard — see the compliance commitments in the Microsoft 365 Copilot privacy and security documentation.
• ISO/IEC 42001 certification (AI management systems) covers Microsoft 365 Copilot, Copilot Studio and Microsoft Foundry, independently audited — the certificates are on the Service Trust Portal and documented in the ISO 42001 compliance offering. For your own audit, this is the artifact you attach when asked "is your AI vendor managed responsibly?".
• Transparency documentation exists per product: the Microsoft 365 Copilot application card and the Copilot Studio system card describe capabilities, limitations and safety mitigations — exactly the inputs your AI Act technical file wants.
• Contractual and data-protection foundations: enterprise data protection and the Product Terms' shared-responsibility model, summarized in Microsoft's AI assurance overview.

What stays on your desk (the deployer checklist)

This is the part no vendor can do for you:

1. AI system inventory. You cannot demonstrate compliance for systems you have not listed. Copilot chat, agents built in Copilot Studio, custom Foundry applications, AI features inside third-party SaaS — one register, with owner, purpose and risk notes per entry.
2. Risk classification per use case. Drafting an email is not the same risk class as agent-assisted decisions in HR or credit. The Act's obligations scale with use, not with product name. Most office productivity use is minimal/limited risk — but an agent you built that screens candidates is a different conversation entirely.
3. Human oversight that is real. "A human clicks accept" is not oversight if the human rubber-stamps 200 outputs a day. Define where review is mandatory, who is accountable, and how overrides are recorded.
4. AI literacy evidence. Article 4 has applied since February 2025. Keep records: who was trained, on what, when. A one-hour structured session with your Copilot user base, documented, beats a policy PDF nobody read.
5. Transparency in your own use. Where your agents interact with customers, people must be able to know they are dealing with AI. Build the disclosure into the agent, not into a footnote.
6. Monitoring and incident path. Log Copilot interactions (Purview's AI governance tooling covers auditing and DSPM for AI), and define what happens when an output causes harm or a serious incident: who assesses, who reports, in what timeframe.

The 8-week plan (realistic version)

• Weeks 1–2 — Inventory and triage. Build the AI register. Run a Purview DSPM for AI assessment to see what AI is actually touching your data, including the unsanctioned tools.
• Weeks 3–4 — Classify and gap-check. Map each use case to an AI Act risk class. Use Compliance Manager assessment templates to structure the gap analysis instead of inventing a framework from scratch.
• Weeks 5–6 — Close the deployer gaps. Oversight rules written into agent designs; disclosure added to customer-facing agents; literacy training delivered and recorded; vendor artifacts (ISO 42001 certificate, application cards) filed in your technical documentation.
• Weeks 7–8 — Operationalize. Audit logging verified end to end, incident playbook rehearsed once, quarterly review cycle booked. Compliance that lives in a calendar survives; compliance that lives in a binder does not.

One honest note on timing: the EU's "digital omnibus" discussions have shifted some adjacent deadlines, and national enforcement readiness varies. None of that changes the deployer fundamentals above — inventory, classification, oversight, literacy, transparency, monitoring are the load-bearing work under every scenario, and they take weeks, not days.

Related reading: AI Governance Fundamentals for Enterprise Microsoft 365 · The Microsoft Copilot for M365 Governance Framework

Frequently asked questions

We only use Copilot for documents and meetings. Are we even in scope?

Mostly in the lightest tiers — but Article 4 AI literacy applies to you today, and your inventory still needs to say so. "We assessed it and it is minimal risk" is a compliance position; silence is not.

Does Microsoft's ISO 42001 certification make us compliant?

No — it makes your vendor demonstrably managed, which is one required input. Your deployer obligations (oversight, literacy, transparency in your use cases) cannot be inherited from a supplier certificate.

What about agents we build ourselves in Copilot Studio or Foundry?

The closer you get to building, the closer you move toward provider-like duties for that system. An internal agent automating a consequential decision deserves the full treatment: documented purpose, risk assessment, oversight design, logging. The platform's system card helps, but the use case is yours.

What is genuinely urgent before August 2?

The register, the risk classification, and documented literacy. Those three produce most of what a regulator would ask for first — and they are prerequisites for everything else.