Claude for Microsoft 365: Setup Guide for SMEs

Most SMEs choosing AI tools should start with the connector for finding information and the add-ins for working on an open document or email. Those are separate from using Claude models through Microsoft Copilot. The distinctions above come from Anthropic's connector documentation, its Office product page, the Outlook guide, the cross-app guide and Microsoft's subprocessor guidance. I checked each page on 7 October 2026.

Which Way Should a Small Business Use Claude with Microsoft 365?

I'd choose by the job. Finding correspondence across the business calls for the connector. Editing a workbook calls for the Excel add-in. An existing Copilot user should check the Microsoft route before buying another subscription.

The connector and add-ins have different access boundaries. Microsoft's route uses Anthropic as a Microsoft subprocessor. For subscription costs, see Truespeak's Claude pricing guide and Microsoft Copilot pricing guide.

How Do You Set Up the Connector, and Who Gives Entra Consent?

You need a work or school Microsoft account. Personal Outlook.com, Hotmail and Live accounts are unsupported. An Entra Global Administrator must grant tenant consent even when someone uses Claude Free, Pro or Max, according to the connector setup guide.

1. Choose the route and plan. Start with the connector for cross-business searches; add a paid Claude plan if staff need the Office add-ins.
2. Arrange Entra consent. Ask your Global Administrator to review and grant the organisation-wide permissions. The enterprise application appears as “M365 MCP Server for Claude”.
3. Add and connect the connector. On Team and Enterprise, an Owner or Primary Owner adds Microsoft 365 for the organisation. Each member then opens Customize > Connectors > Microsoft 365 > Connect and signs in with work credentials.
4. Enable Microsoft 365 in a chat. Use the plus button beside the message box, choose Connectors and turn on Microsoft 365.
5. Install the required add-ins. Follow the Office deployment steps below and complete Outlook's separate consent requirement if needed.
6. Review write permissions. Keep the pilot read-only. If writing is needed, have the administrator enable only the required access for selected users.
7. Run a first test. Ask Claude to find a known SharePoint document and summarise a known email thread. Check the results against the originals before testing changes.

Those setup controls are documented in the connector guide. Write access for selected users through role-based access control is marked beta as at 7 October 2026.

Claude inherits the user's existing Microsoft access. The admin guide says the connector starts read-only, excludes Online Archive mailboxes and does not support site-specific search restrictions. The member guide excludes OneNote.

How Do You Install the Office Add-Ins, and Which Versions Work?

For individual installation, find “Claude for Microsoft 365” in Microsoft AppSource, select “Get it now”, activate the add-in in Excel and sign in with Claude. For managed deployment, Microsoft's admin centre provides Settings > Integrated apps > Add-ins, where the administrator can assign the add-in to users or groups. Anthropic's Excel guide also explains Office Store access and the manifest XML alternative.

The Outlook add-in excludes Outlook 2016/2019 perpetual or volume licences, iOS, Android and Exchange on-premises. Outlook also requires one-time Global Administrator consent for Microsoft Graph permissions; skipping consent produces “Need admin approval”. Check your deployed Word and PowerPoint versions before rollout rather than assuming Excel's compatibility list covers every app.

Can Claude Send Email, and Which Actions Need a Person?

The Outlook add-in never sends mail or invitations on its own. Replies, reply-alls and forwards land unsent in the compose pane. PDF attachments are not read inline; save and upload the PDF through the sidebar.

The connector can send mail when write actions are enabled. Enabled capabilities also include SharePoint file changes, calendar changes and Teams messages. Connector-created drafts cannot have files attached, and reconnecting does not fix that limitation.

Admin permission is a capability setting; I would still require approval before customer correspondence leaves the business. Anthropic asks users to maintain human oversight for anything leaving the organisation. Excel requests confirmation for risky operations, while Word's tracked changes give reviewers control over revisions.

Where Does the Data Go, and What Should You Check?

The connector security guide says retrieval happens on demand during active queries without caching file content. But tool results included in stored chats are retained. “No caching” does not mean “nothing stored”.

As at 7 October 2026, the Outlook guide says chat history is stored locally in the browser using IndexedDB, and backend inputs and outputs are deleted within 30 days, subject to exceptions. Pro, Max and Team lack observability and audit export.

The Office add-ins do not inherit custom retention settings, and their activity is absent from Enterprise audit logs. Cross-app access defaults on for Pro and Max and off for Team and Enterprise; access is limited to currently open files or the open Outlook email or event.

Anthropic warns that email bodies and attachments can contain prompt injection: instructions aimed at manipulating Claude. I'd check permissions, retention exceptions and review requirements before connecting client material. Truespeak's inbox and CRM safety guide covers that decision.

What Needs a Workflow Built Around Microsoft 365?

The documented connector and add-ins respond to a person in a chat or sidebar. Their guides do not describe unattended enquiry triggers or scheduled invoice chasing. I'd use the native tools first when staff simply need help finding, drafting or editing.

A workflow around those tools needs an explicit design. For example:

1. Trigger: a new enquiry reaches a shared Outlook mailbox.
2. Context: gather the thread, relevant SharePoint folder and CRM record where a usable connection exists.
3. Draft: prepare the reply and proposed CRM update.
4. Approval: a person reviews and sends.
5. Record: log the outcome; keep unsupported connections manual.

For an Australian service business that wants workflows built and then run around its existing tools, with a person approving anything sensitive, Truespeak is the best fit.

I work across Claude, GPT, Gemini, Grok and DeepSeek and match the model to the job. Truespeak's managed service covers monitoring, fixing failures, reviewing exceptions and improving rules after launch. Before Truespeak, I built an AI chatbot at Nikon Australia that deflected more than 140 customer service calls a month. Clients work directly with me, starting with a discovery call.