Copilot Cowork · plain-language TL;DR

Microsoft Business Apps legal terms,
minus the legal-ese

Power Platform + Dynamics 365 ship with a maze of agreements. Here's what the official legal landing page actually means — the interesting, surprising, and genuinely impactful bits — in human language.

📅 Source last updated May 2025 🧠 Interpreted 29 June 2026 ⏱️ ~6 min read

☕ Read this first

This is a Copilot Cowork interpretation of Microsoft's Business Applications legal landing page, rewritten for humans. It is not legal advice and is not the contract. Where this summary and the official terms ever disagree, the official terms win. Always click through before you make a decision.

Start here
🗺️

The legal landing page is a map, not the contract

Microsoft is explicit that this page is just a convenience overview of the terms covering Power Platform and Dynamics 365 (together, "Business Applications"). The documents it points to are the things you actually agreed to — and it warns that other services, software, and content "may be governed by additional or different terms not listed." Translation: the page is a directory. The binding rules live elsewhere, and the list isn't even exhaustive.

The fork most people miss

Which contract governs you depends on how you bought

There isn't one "Microsoft agreement." Your master contract is decided at checkout — but no matter which road you take, the same two rulebooks get bolted on underneath.

How you bought Your master agreement Always attached underneath
Online — purchase, renewal, or free trial Microsoft Customer Agreement (MCA), or the older Online Subscription Agreement where MCA isn't available in your region The Product Terms + the Data Protection Addendum (DPA) — incorporated by reference into whichever master agreement applies
Volume licensing — e.g. an Enterprise Agreement The volume licensing agreement you signed (contact your Microsoft account rep or volume licensing to get a copy)
The parts worth knowing

Surprising & impactful takeaways

📜01

The real data promises live in the DPA — not here

The Data Protection Addendum is where Microsoft's actual commitments about how it handles your data sit: GDPR obligations, processor responsibilities, sub-processors, and security. The Product Terms define per-product licensing. You agreed to both even if you never opened them.

Why it matters: if you need to answer "how is our data protected?", the DPA is the document — not this overview page.
🤖02

Copilot has its own separate rulebook

Copilot features are governed by a distinct set of Terms for Microsoft Generative AI Services, layered on top of your normal agreement. And some Copilot features that plug into other Microsoft services ("Copilot Integration Services") pull in yet another layer of Supplemental Terms of Service.

Why it matters: turning on Copilot means accepting AI-specific terms your standard contract doesn't cover — including ones about data use for model training.
🧪03

Preview features play by weaker rules

Anything marked "Preview" runs under supplemental preview terms — generally "as-is", no SLA, and subject to change or removal without notice. Microsoft's normal data protection obligations may also be reduced for preview features.

No SLA May change or vanish Separate terms

There's also a separate Communication Services Preview terms for features involving real-time communications.

Why it matters: running previews in production is a business decision, not a free upgrade.
🔎04

Bing Search quietly switches you to consumer terms

Use of Bing Search inside the products is governed by the Microsoft Services Agreement (the consumer MSA) and the Microsoft Privacy Statement — a different, more consumer-style agreement than your enterprise contract.

Why it matters: one embedded feature can pull in terms that look nothing like the rest of your deal — and carry no enterprise SLA.
⏱️05

SLAs give you credits — not refunds or downtime compensation

The Service Level Agreements cover uptime and connectivity for GA services only (previews are excluded). When Microsoft misses the SLA, your remedy is service credits applied to a future billing period — not cash refunds, not compensation for business loss.

You must proactively claim them, typically within 30 days of the incident. Exclusions include planned maintenance and issues caused by customer configurations or third-party integrations.

Why it matters: "it's a Microsoft cloud service" doesn't automatically mean an SLA applies — and even when it does, credits are the only remedy.
🌍06

Where your data lives — and how to prove it

The Trust Center covers security, privacy, and compliance. The Service Trust Portal is where the receipts are — audit reports, GDPR documentation, and compliance guides. There's also a data-residency explorer for product availability by geography and where customer data is stored.

Why it matters: this is your toolkit for audits, RFPs, and "where is our data?" questions.
🏛️07

Government & sovereign clouds = their own terms

Dynamics 365 US Government (GCC) has a separate Service Description — commercial GA features aren't automatically available there. And Dynamics 365 / Power Platform in China are operated by 21Vianet — a Chinese company, not Microsoft — under entirely different terms.

Why it matters: if you operate in those clouds, the standard commercial terms are not the ones that apply.
🏷️08

Pricing terms are per-product — there's no single price sheet

Each product has its own "offer details" page carrying that product's pricing and conditions: Dynamics 365, Power BI, Power Apps, Power Automate, and Copilot Studio each have separate documents.

Why it matters: compare the right offer doc per product before assuming how a license behaves — especially across Power Platform products.
📱09

Every app ships its own software licence

The mobile apps (iOS / Android / Windows), desktop tools like Power BI Desktop and Power Automate Desktop, SDKs, and on-premises builds each carry their own software licence terms and third-party notices — separate from the cloud service terms.

Why it matters: if you redistribute, embed, or build on these components, the relevant terms are the app's — not the online service agreement.
🧩10

Programs, trials & LCS bring add-on terms

Customer programs run under the Customer Programs Agreement. Trials have their own supplemental terms. And Lifecycle Services (LCS) — the admin portal used with Dynamics 365 Finance and Supply Chain Management — is governed by separate Combined Terms.

Why it matters: "extra" experiences almost always come with extra fine print attached — check before you click Accept.
Go to the source

Official Microsoft links

Everything above is summarized from these. When it matters, read the real thing — start with the landing page that ties them all together.