The timing needs the same care. Anthropic's financial-services announcement of May 5, 2026, said Claude worked across Excel, PowerPoint and Word, with Outlook listed as "coming soon." The current product page shows Outlook in beta. So the Office trio has been available for months, Outlook has moved from announced to beta, and the cross-app workflow is the main selling point.
What each add-in does, according to Anthropic
All of the following are Anthropic's descriptions, not independent benchmark results:
- Excel: Answers questions about cells, changes assumptions without breaking formulas, and builds models from scratch. Anthropic's example builds a model from a Word brief by pulling numbers from the document and writing formulas across several tabs.
- PowerPoint: Builds slides in your existing template, edits whatever you have selected, and creates native charts and diagrams. The May announcement also said decks can update when the underlying numbers change.
- Word: Edits with tracked changes, replies to comment threads, and revises content to match company styles.
- Outlook (beta): Triages your inbox, drafts replies, and finds meeting times across calendars.
For Outlook, Anthropic states that Claude cannot send an email without your approval. Drafts and calendar invites open in Outlook's normal compose window and wait for you to click Send. If you're worried about an AI agent emailing your biggest client on its own, that's the guarantee to check before you enable it.
Section summary: The add-ins are a GA trio plus an Outlook beta, each working on the open document, with a human approving the final output.
The cross-app mode
The add-ins share context. Anthropic says one conversation can move from Outlook to Word to Excel to PowerPoint. Its example workflow goes like this:
- Triage email and pick out a request.
- Open the related brief in Word.
- Build the model in Excel.
- Create the PowerPoint deck.
- Draft the review meeting invite in Outlook.
Anthropic also says you can drop a PDF or Word document into any sidebar and refer to it from the other apps. Workflows can be saved as "Skills" that the whole team can use in all four apps.
The source report joked that your boss now has a technical excuse to ask for the sales figures in Excel, the summary in Word and the deck in PowerPoint before lunch. The joke works because cross-app context is exactly what removes the copy-paste work that used to make that request unreasonable.
The caveat: nothing here independently tests how reliably context carries over between apps, or whether every workflow works in every configuration. Treat the demos as vendor claims until you've run your own pilot.
Requirements: read the fine print
Microsoft's Office Store listing for "Claude for Microsoft 365" covers Excel, Word and PowerPoint. It names Office 2016 or later on Windows and Mac, plus the web versions of all three apps. Outlook isn't on that listing; Anthropic offers it as a separate beta install.
Anthropic's own documentation is stricter than the store listing. According to Anthropic's support article, Excel on Windows needs a Microsoft 365 subscription, build 16.0.13127.20296 or later. A third-party guide from AgentsCamp says it does not run on Excel 2016 or 2019 perpetual and volume licenses, on Excel for iPad, on Excel for Android, or on older Microsoft 365 builds, because the add-in requires SharedRuntime support. That claim comes from a third party, not Anthropic or Microsoft. Still, if your organization runs perpetual-license Office 2019, test before you promise anything to users.
You don't need a Copilot seat. One setup guide notes that Claude for Excel authenticates against your paid Claude plan. You need a Microsoft 365 subscription with a work or school account to host the add-in, but you do not need the separate Microsoft 365 Copilot per-seat license. Treat the work-or-school account requirement as that guide's claim; Anthropic's own requirement is the paid Claude plan.
Section summary: Use Anthropic's build requirement, not the store's "2016 or later" line, when you check compatibility.
Admin deployment
The source report said administrators control deployment through the usual admin panels. Anthropic's documentation confirms that, at least for Excel: organization admins can deploy Claude for Excel through the Microsoft 365 Admin Center. The documented steps:
- In the Microsoft 365 Admin Center, go to Settings, Org Settings, User owned apps and services, and turn on "Let users access the Office Store".
- Search for "Claude for Microsoft 365" in Microsoft AppSource. Several setup guides, including AgentsCamp's, say you then assign it to the whole organization or to specific groups from Integrated apps.
- Deploy. After deployment, users can activate the Claude add-in from Tools, Add-ins on Mac or Home, Add-ins on Windows, sign in, and start working.
If your tenant blocks the Office Store, there's another route: download the Excel manifest XML file, then follow Deploy with a custom manifest for the upload steps.
The PIM problem. Anthropic documents a known issue. If your organization uses Microsoft Entra Privileged Identity Management (PIM) for admin roles, the Integrated apps page does not recognize roles activated through PIM, so deployment fails. The workaround is to deploy from an admin account with the required role assigned as permanently active rather than PIM-eligible. Expect your security team to object to a permanently active admin role. A short, documented exception is probably the cleanest fix.
Using your own cloud instead of Claude accounts
Organizations don't have to give everyone a Claude account. Anthropic's product page lists Microsoft Foundry, Amazon Bedrock and Gemini Enterprise Agent Platform as connection options. Its support documentation says that if your organization routes AI traffic through Amazon Bedrock, Google Cloud Vertex AI, Azure AI Foundry, or an LLM gateway, your admin can deploy the add-in without individual Claude accounts.
That route has its own prerequisites. Anthropic's third-party-platform guide lists Microsoft 365 with Entra ID for admin consent and token issuance, and the upload path goes through Settings, Integrated apps, Upload custom apps. It also notes that the Claude organization admin who edits served settings can be a different person from the Microsoft 365 admin who deployed the manifest. Agree in advance who owns which part of the setup, or the two admins will spend the rollout blaming each other.
What Anthropic hasn't documented
The source report also said admins set policies for "how the data it handles is processed." That goes further than the evidence. Anthropic says the add-ins work "within your existing compliance framework," and its documentation covers who gets the add-in and which backend it uses. It doesn't spell out per-tenant data-processing policies the way the source report suggests. Some third-party guides claim more, such as activity feeding into Microsoft 365 audit logs, but I couldn't confirm that against Anthropic or Microsoft documentation. Ask your Anthropic representative for written confirmation before relying on it.
Does Copilot still matter?
This is part of a larger shift. Microsoft already offers Claude models inside Copilot. One guide notes that in a company, an admin may first have to allow Anthropic as a model provider in the Microsoft 365 Admin Center. So organizations now have two ways to use Claude in Office:
| Claude add-ins | Claude via Copilot | |
|---|---|---|
| License | Paid Claude plan (or cloud provider) | Microsoft 365 Copilot / eligible plans |
| Delivery | AppSource add-in, sidebar | Built into the Office ribbon |
| Cross-app context | Anthropic's shared-context mode | Microsoft's Copilot integration |
| Admin path | Integrated apps / custom manifest | Model-provider setting in admin center |
Neither is clearly better. If you already pay for Copilot, the add-ins could duplicate it. If you're mostly a Claude shop with Office installed, the add-ins avoid a second per-seat license.
Bottom line
The Claude add-ins are real, deployable through standard Microsoft 365 admin tooling, and generally available for Excel, Word and PowerPoint. Outlook is still a beta that drafts but never sends on its own. My advice:
- Start with a pilot group rather than an org-wide push.
- Check Office builds against Anthropic's Microsoft 365 requirement, not the store's "2016 or later" line.
- Plan around PIM before deployment day.
- Get data-handling commitments in writing.
Your manager may well ask for the report in three apps by lunch. You'll still be the one who signs off on it.
References
- Claude arrives in Microsoft 365 with add-ins for Excel, Word, PowerPoint and Outlook Foro3D · 2026-11-16T22:29:49+00:00
- Claude for Microsoft 365 | Claude by Anthropic claude.com
- Use Claude for M365 with third-party platforms - Claude.ai Documentation support.claude.com