How to Add Claude to PowerPoint: Install Steps, Version Requirements, and Why the Add-In Does Not Appear

Claude for PowerPoint is installed from Microsoft AppSource, not from Claude, and it needs two things you cannot see from inside PowerPoint: a Claude plan of Pro or above, and a Microsoft 365 build at or past 16.0.13127.20296 on Windows or 16.46 on Mac. Anthropic publishes both numbers, plus an explicit list of versions where the add-in never runs at all. Almost every "Claude is not showing in PowerPoint" report is one of those two gates rather than a bug.

The install itself takes under a minute. What takes the afternoon is working out why it did not appear for the one colleague on an older laptop, or why the admin deployment silently failed for the whole finance team. Both have documented causes, so this walks through the setup first and then the checks in the order that actually resolves them.

How to add Claude to PowerPoint

Three steps, exactly as Anthropic documents them:

1. Open the Claude for Microsoft 365 listing on Microsoft AppSource.
2. Select Get it now to install.
3. Open PowerPoint, activate the add-in, and sign in with your Claude account.

After that, Claude appears as a sidebar. On Windows you activate it from Home, Add-ins. On Mac it is Tools, Add-ins. The add-in is free to install and does not carry its own subscription: usage draws from the allowance on the Claude plan you already pay for.

One thing worth knowing before you start. The listing is called Claude for Microsoft 365 rather than Claude for PowerPoint, because the same install covers PowerPoint, Excel, Word and Outlook. If you searched AppSource for "Claude for PowerPoint" and found nothing, that is why.

Which PowerPoint versions does Claude support?

This is the check most people skip and most people need. Anthropic publishes both a supported list and an unsupported list, with exact numbers.

The perpetual license row is the one that ends conversations. A business running PowerPoint 2019 under a volume license has no upgrade path to the add-in short of moving the organization to Microsoft 365 subscriptions, which is a procurement decision rather than an IT ticket.

How to add Claude to PowerPoint on Mac

Same AppSource install, different activation path and a different version floor. You need PowerPoint 16.46 or later, and you activate the add-in from Tools, Add-ins rather than the Home ribbon. If your Mac build predates 16.46, PowerPoint on the web is the workaround while you wait for an update to be approved, and it behaves identically.

Why is Claude not showing in PowerPoint?

Four causes, in the order worth checking:

1. Your Claude plan. The add-in is documented as generally available to Pro, Max, Team and Enterprise plans. A Free account will not activate it. This is separate from file creation in a normal Claude conversation, which Anthropic documents as available on every plan including Free.
2. Your PowerPoint build. Below the published floor, the add-in either never appears or appears and refuses to load. Test in PowerPoint on the web: if Claude works there and not on your desktop, the build is the problem.
3. An unsupported version. PowerPoint 2016, 2019, iPad and Android are never going to work. Confirm which one you are actually on before troubleshooting further.
4. Office Store access is switched off. Anthropic warns that organizations which have disabled "Let users access the Office Store" may find admin-deployed add-ins do not appear for users at all. The fix is on the admin side, covered below.

How do admins deploy Claude for PowerPoint across an organization?

Through the Microsoft 365 Admin Center. Turn on Office Store access under Settings, Org Settings, User owned apps and services, then go to Settings, Integrated apps, Add-ins, search AppSource for Claude for Microsoft 365, and assign it to the organization or to specific users and groups. Anthropic notes that a full organization rollout can take up to 24 hours.

Two failure modes are worth knowing in advance, because both look like the deployment simply did not happen.

The first is Microsoft Entra Privileged Identity Management. Anthropic documents that the Integrated apps page does not recognize roles activated through PIM, so deployment fails outright. This is a known Microsoft issue with tracking ID 11126536. The workaround is to deploy from an admin account whose role is permanently active rather than PIM-eligible.

The second is the Office Store being disabled as policy, which many regulated organizations do deliberately. In that case admin-deployed add-ins can fail to reach users. The documented route around it is to download the custom manifest XML file, then in Integrated apps choose Upload custom apps, Office Add-in, and upload the manifest, assigning it to the organization, a group, or just yourself for testing.

If your organization routes AI traffic through Amazon Bedrock, Google Cloud Vertex AI, Azure AI Foundry or an LLM gateway, the add-in can be deployed without individual Claude accounts, with the available models coming from that platform and your admin's configuration rather than from Claude.ai settings.

Does Claude work with PowerPoint and Excel at the same time?

Yes, and this is genuinely useful. Claude for PowerPoint shares context with Claude for Excel, Word and Outlook, so one conversation can span an open deck, a workbook and an inbox. A single install covers all four apps.

One catch that causes confusion: persistent instructions do not travel. Anthropic states that instructions you set in PowerPoint apply only to PowerPoint and are separate from the ones you set in Excel or Word. If you wrote your brand rules once and expected them everywhere, you need to write them in each app.

The model list is also narrower than you may expect. Claude for Microsoft 365 offers what Anthropic calls a curated subset of models, the ones that work best for Office tasks, so the dropdown in the add-in can be shorter than the one on Claude.ai. Your organization's model access settings apply on top of that.

What Claude for PowerPoint will not do

The output quality is not the weak point. The add-in reads your slide master, layouts, fonts and color scheme, and it produces editable native PowerPoint charts rather than pictures, which is more than most AI deck tools manage. The constraints sit elsewhere.

Anthropic states plainly that it is not recommended for final client deliverables without human review, for presentations containing highly sensitive or regulated data without proper controls, or for replacing your judgment on design and narrative flow.

There is a compliance gap that procurement teams should see before a pilot, not after. Anthropic documents that Claude for PowerPoint does not inherit custom data retention settings an organization may have set, and that activity is not included in Enterprise audit logs or the Compliance API. Chat history is stored locally in the browser using IndexedDB, is not stored on Anthropic's servers, and is not synced across devices, so it also cannot be centrally reviewed. For a bank or a healthcare provider, that combination is usually the blocker rather than anything about slide quality.

There is also an explicit prompt injection warning. Anthropic advises using the add-in only with trusted files, and states that testing identified scenarios where it can be manipulated into extracting sensitive information, modifying critical data or performing destructive actions if allowed to act without verification. Downloaded templates, vendor files and collaborative documents are the named risks. Any team wiring assistants into tools that can read and change real files eventually wants a layer that inspects untrusted input before the model ever acts on it, and an Office add-in that edits your documents is exactly the shape of thing that argument was written about. In the meantime, the add-in asks you to confirm risky operations. Read those confirmations rather than clicking through them.

When converting the document is the shorter route

The add-in is built around a deck you already have open. You describe what you want, it generates against your template, you refine. That is the right tool when the content is in your head or in the prompt.

It is the wrong shape when the content already exists as a document. A 40-page quarterly report, a research PDF, a workbook of results: those already contain the structure and the numbers, and re-describing them to an assistant throws that away. Converting the file directly keeps headings as headings and tables as tables, and lets you cut the outline before any slide is generated. That path is covered on Claude to PowerPoint, which also lays out what each of the two Claude routes can and cannot read.

The equivalent question for other assistants has the same answer: ChatGPT to PowerPoint, Copilot to PowerPoint for the Microsoft licensing gate, and Gamma to PowerPoint where the export exists but arrives partly flattened. If your source is a spreadsheet, Excel to PowerPoint rebuilds its tables as native chart objects with your figures still behind them. If it is a written report, report to presentation splits the headline onto the slide and the paragraph into speaker notes.

The short version

Install Claude for Microsoft 365 from AppSource, sign in, and check two numbers if it does not appear: your Claude plan must be Pro or above, and your PowerPoint must be at 16.0.13127.20296 on Windows or 16.46 on Mac. If you are on a 2016 or 2019 perpetual license, an iPad or an Android tablet, no amount of troubleshooting will help, because those are on the documented unsupported list. And if your compliance team needs audit logs, ask that question at the start of the pilot rather than the end.