Contents
| Type | AI inside the office suite |
|---|---|
| Headquarters | Redmond, Washington |
| Pricing | Published |
| Website | microsoft.com |
Copilot's security argument is continuity: prompts and responses fall under the same contract that already covers a company's email and files in Microsoft 3651.
Best for: Companies already on Microsoft 365 that want AI over their own mail, files and meetings under the contract, permissions and retention rules they already have.
Not the right fit for: Companies whose SharePoint and Teams permissions are loose: Copilot shows each user whatever that user can already open.
What Microsoft commits to
Microsoft covers Copilot and Copilot Chat under its Products and Services Data Protection Addendum, acting as data processor. It says data is encrypted at rest and in transit and isolated between tenants, that Copilot respects the company's identity model and permissions, inherits sensitivity labels, applies retention policies and supports audit, and that prompts, responses and data accessed through Microsoft Graph are not used to train foundation models1. Prompts and responses are logged under the company's retention policies and available for eDiscovery2.
The condition: permissions
Copilot only surfaces organisational data to which a user has at least view permission, and Microsoft tells customers to use the permission models in Microsoft 365 services such as SharePoint to make sure the right people have the right access3. In practice, a company with loosely shared folders should tidy them before switching Copilot on.
Location
For EU users, traffic stays within the EU Data Boundary, and Copilot is covered by Microsoft's data residency commitments; customers outside the EU may have queries processed in the US, the EU or other regions3. Claude models from Anthropic used inside Copilot are currently excluded from the EU Data Boundary1.
Strengths and limits
Strengths
- Covered by the Microsoft Products and Services Data Protection Addendum, with Microsoft acting as data processor.
- Respects existing permissions, sensitivity labels and retention policies, and supports audit and eDiscovery through Microsoft Purview.
- EU traffic stays within the EU Data Boundary, and Copilot is covered by Microsoft’s data residency commitments.
- Published prices, and Copilot Chat at no additional cost on eligible plans.
Limits
- It surfaces whatever a user can already open, so oversharing in SharePoint and Teams becomes visible through Copilot. Microsoft tells customers to use its permission models to prevent it.
- Claude models from Anthropic are currently excluded from the EU Data Boundary when used inside Copilot.
- Agents and web search follow their own terms: Microsoft says to check each agent’s privacy statement, and web queries go to Bing under separate terms.
Choose another option if: Your company runs on Google Workspace (Gemini), or you want AI that acts across systems beyond Microsoft 365 with approvals you define (OpenLazarus).
Pricing
Published: Copilot Business add-on $18 per user a month on yearly billing (first-year promotion, listed at $21) or $25.20 monthly; Business Standard with Copilot $23.50 and Business Premium with Copilot $32 per user a month on yearly billing. Microsoft notes an annual commitment and first-year promotional pricing.
What to ask Microsoft or a partner
- Which of our sites and teams are shared with everyone, and what will Copilot surface from them?
- Which retention policy applies to Copilot interactions, and who can search them?
- Which agents are allowed in our tenant, and under whose terms?
- Which models are enabled, and are any excluded from our data boundary?
For Copilot beside the other options, see the comparison table.
Sources
- Enterprise data protection in Microsoft Copilot and Microsoft Copilot Chat. Microsoft Learn, 29 May 2026. Accessed 19 Nov 2026.
- Microsoft 365 Copilot plans and pricing. Microsoft. Accessed 19 Nov 2026.
- Data, privacy, and security for Microsoft Copilot. Microsoft Learn, 9 Jul 2026. Accessed 19 Nov 2026.
