Anthropic Takes on Microsoft: The Battle for Your Workplace AI

Anthropic now ships Claude as add-ins inside Microsoft Excel, PowerPoint, and Word, generally available on every paid Claude plan, with Outlook in public beta. That puts Anthropic's model inside the same Office apps where Microsoft sells its own Copilot, and the two products take opposite positions on who should own your AI setup. If you are choosing workplace AI, the practical question is no longer "which model is smartest" but "which architecture fits how your business actually works."

This post lays out what each side actually offers today, what each one costs, where each one falls short, and how to decide.

What Anthropic is actually shipping

Two things are easy to confuse, so it is worth separating them.

The Office add-ins. Claude for Excel, PowerPoint, and Word are distributed through Microsoft AppSource and run as a sidebar inside each Office app, authenticating against your paid Claude plan. They went generally available in May 2026 after a staged rollout: Excel in beta in October 2025, PowerPoint as a research preview in February 2026, Word in April 2026. Claude for Outlook is in public beta. The four add-ins share one conversation thread, so a financial model built in Excel can become a PowerPoint deck and then a Word memo without re-explaining the inputs at each step. You can read the rollout timeline in this setup guide for the Claude Office add-ins.

The open-source plugins. Separate from the add-ins, Anthropic open-sourced a set of Cowork plugins on GitHub that turn Claude into a role-specific agent: legal, finance, sales, product management, and more. A plugin is a portable folder of skills, commands, and connector configuration that you own. It runs in Claude Cowork, in Claude Code, and in anything built on the Claude Agent SDK. Anthropic's enterprise plugins announcement also covers private plugin marketplaces, so an admin can distribute vetted plugins across a company, and new connectors for Google Workspace, Docusign, FactSet, MSCI, and others.

The strategic point is portability. The plugins and the agent logic live with you, not inside Microsoft's licensing. Anthropic's finance push shows the intent: five Anthropic-built finance plugins (financial analysis, investment banking, equity research, private equity, wealth management) plus partner plugins from LSEG and S&P Global, all in a public repository you can fork, per Anthropic's finance plugins post.

What changed about Microsoft Copilot

Two claims you will still see repeated are now wrong.

First, Copilot is no longer OpenAI-only. Since late 2025, Microsoft hosts Claude inside its own surfaces: the Researcher agent in Microsoft 365 Copilot, Copilot Studio for custom agents, and Excel Agent Mode. Microsoft is model-agnostic where it suits them, because the product they are selling is the Microsoft 365 integration layer, not the model.

Second, Copilot is no longer a single $30 add-on. Current Microsoft 365 Copilot pricing spans several tiers:

• Microsoft 365 Copilot Business add-on: $21 per user per month (annual), with promotions as low as $18 for existing Business plan customers
• Business Standard with Copilot: $23.50 per user per month, annual
• Business Premium with Copilot: $32 per user per month, annual, with advanced security and Purview data governance
• Enterprise add-on: around $30 per user per month on top of a qualifying Microsoft 365 plan
• Copilot Chat: included at no extra cost with eligible Microsoft 365 subscriptions, with metered pricing for agents

Claude's side of the ledger: the Office add-ins work on any paid Claude plan. Pro is $20 per month, Max is $100 or $200 per month depending on usage tier, Team is $30 per user per month billed annually with a five-seat minimum, and Enterprise is custom. Critically, you do not need a Microsoft 365 Copilot license to run Claude inside Office. You need a Microsoft 365 work or school subscription to host the add-in, plus your Claude plan.

A worked cost example: 50-person team

Take a 50-person operations team already on Microsoft 365 Business Standard.

• All-in Microsoft: Business Standard with Copilot bundled at $23.50 per user per month comes to about $14,100 per year for the whole team, and that includes the Office apps themselves.
• Claude alongside existing M365: keep the existing Business Standard licenses (which the team already pays for) and add Claude Team at $30 per user per month, annual. That is $18,000 per year on top of existing Microsoft spend.
• Mixed deployment: Copilot Chat (free with the existing subscription) for general use, Claude Team seats only for the 10 power users who build models and decks. That is $3,600 per year.

The mixed deployment is how most cost-conscious rollouts actually start, and neither vendor's marketing page will suggest it to you.

Where Copilot genuinely wins

Be honest about the trade-offs before betting on portability.

• Depth of integration. Copilot reads Microsoft Graph: your emails, calendar, Teams chats, and SharePoint documents, with your existing permission model enforced. Claude's add-ins see the file you have open and what you share with them. For "summarize everything that happened on this account last week," Copilot is structurally better placed.
• Deployment friction. An admin enables Copilot from the Microsoft 365 admin center and it appears for everyone. Claude's add-ins install from AppSource, but on managed tenants users cannot self-install, and getting plugins, connectors, and a private marketplace configured is real implementation work.
• Governance and support. Microsoft bundles Purview, enterprise SLAs, and compliance certifications into the E5 world. Anthropic offers SSO, audit logging, and OpenTelemetry export on Enterprise, but add-in actions are not yet included in enterprise audit logs, which matters in regulated environments.

For a 30-person company with no developers, all-in on Microsoft 365, Copilot is the sensible default. Portability you never use is not worth setup cost.

Where Claude's approach wins

• Multi-vendor environments. Most businesses run a mix: Microsoft for documents, Slack or Google Workspace for communication, Salesforce or a vertical tool for the system of record. Claude's connectors span those systems, and the plugins work across them. Copilot is best exactly as long as your work stays inside Microsoft.
• Custom agents per role. The open-source plugins can be forked and rebuilt. A law firm can take the legal plugin and bend it to its own playbook; a fund can do the same with the equity research plugin. We do this kind of customization as part of our Claude implementation work, and the same plugin architecture underpins our Claude for financial services and Claude for legal offerings. Copilot Studio allows custom agents too, but within Microsoft's framework and pricing.
• Model flexibility. The plugin and agent layer is not welded to one model vendor. Claude add-ins can also route through Amazon Bedrock, Google Cloud Vertex AI, or Microsoft Foundry, which lets enterprises keep Claude inside their existing cloud and compliance perimeter. If you are running autonomous AI agents in production, the ability to change models without rebuilding integrations is worth real money.

Limitations you should know before rolling out Claude in Office

The Claude add-ins have real gaps today, documented in this add-in overview:

• No macros, VBA, or data tables in either add-in. Heavy Excel shops hit this first.
• Chat history is not saved between sessions. Context resets when you reopen the app.
• Audit gaps. Add-in actions do not appear in enterprise audit logs yet.
• Prompt injection risk. Malicious instructions can be embedded in external files and templates, so users should only open trusted documents with the add-in active.
• Mac and Windows desktop only. No iOS or Android add-ins announced.

These are exactly the kinds of issues that surface in agent monitoring and observability work: if you cannot log what the agent did, you cannot govern it.

How to decide: a short checklist

1. Where does your work live? 90% inside Microsoft 365 favors Copilot. Spread across Microsoft, Google, Slack, and vertical SaaS favors Claude.
2. Who are your power users? If a handful of analysts produce most of the models and decks, seat them on Claude and leave everyone else on Copilot Chat.
3. Do you need role-specific agents? If yes, look at the open plugin repos before building anything from scratch.
4. What does governance require? If audit logging of every AI action is mandatory, Copilot's Purview integration is ahead today.
5. What is your switching cost tolerance? If a future move away from Microsoft is plausible, portable plugins reduce it. If not, deep integration is a benefit, not a risk.

For a broader framework on putting agents into day-to-day business workflows, our autonomous agents implementation guide covers the rollout sequence.

Frequently asked questions

Do I need a Microsoft 365 Copilot license to use Claude in Excel?

No. Claude for Excel is an AppSource add-in published by Anthropic that authenticates against your paid Claude plan. You need a Microsoft 365 work or school subscription to host the add-in, but not the separate Copilot per-seat license.

Which Claude plans include the Office add-ins?

All paid plans: Pro ($20 per month), Max ($100 or $200 per month), Team ($30 per user per month, annual), and Enterprise. Free accounts are excluded. Outlook is in public beta on the same plans.

Can Claude replace Microsoft Copilot entirely?

Not for most organizations. Copilot's access to Microsoft Graph (email, calendar, Teams, SharePoint) has no Claude equivalent, and Copilot Chat is already included with eligible Microsoft 365 subscriptions. Claude is stronger as a specialist layer for document-heavy analytical work and cross-platform agents.

Are Anthropic's plugins really free to use and modify?

Yes. The knowledge-work plugins are open source on GitHub and are plain file systems you can fork, customize, and redistribute inside your company through a private marketplace. You still need a paid Claude plan to run them.

What is the biggest risk of the Claude add-ins for enterprises?

Governance. Add-in actions are not yet captured in enterprise audit logs, chat history is not retained between sessions, and prompt injection through untrusted documents is a real attack surface. Plan logging and document-handling policies before broad rollout.

Where to go from here

The honest answer for most companies is not picking a winner but deciding which layer each vendor owns: Microsoft for the integrated default, Claude for the portable specialist work. If you want help designing that split, our Claude implementation service covers add-in rollout, plugin customization, and connector setup.

Related reading

• Anthropic's Sonnet 4.6: AI Agents Just Got Scary Good at Using Your Computer
• Claude Goes Free and Ad-Free While ChatGPT Rolls Out Ads: What the AI Monetization Battle Means
• Claude Finance Agents: What the Ten Templates Do and Cost