1. Verify the current plan wording before rollout
Check the Claude docs page and the two support articles on the same day. Keep any plan-availability mismatch visible in your internal note instead of assuming the public wording is aligned.
Setup guide
Claude Microsoft 365 connector setup guide
Use this guide to stage the connector for a controlled pilot, assign the right owners, complete the one-time consent flow, and avoid the most common account and rollout mistakes.
Last checked
2026-04-11
Prerequisites
Confirm the rollout prerequisites before the first connection attempt.
If these basics are missing, the connector usually fails in ways that look technical even though the real issue is ownership or account type.
A Microsoft 365 work account tied to a Microsoft Entra tenant for every pilot user.
A Microsoft Entra Global Administrator who can complete the one-time consent flow.
A named Claude owner who can answer plan, enablement, and support questions.
A small pilot cohort and at least one real workflow to validate.
An internal note that warns users not to try personal @outlook.com or @hotmail.com accounts.
Responsibilities
Separate the admin setup work from the end-user connection step.
The connector only feels self-serve after the one-time tenant and organization work is done.
| Task | Admin or owner | End user | Why it matters |
|---|---|---|---|
| Confirm plan and organization gating | Check whether your Claude plan requires an organization owner to enable the connector first. | Do not start the connection flow until your admin confirms the connector is available to your plan and tenant. | On Team and Enterprise plans, users cannot connect until an owner enables the connector in Claude. |
| Complete tenant authorization | A Microsoft Entra Global Administrator grants organization-wide consent the first time the tenant is authorized. | Wait for confirmation that tenant consent is complete before retrying a failed connection. | The first connection attempt can fail or stall if the tenant has not been pre-consented. |
| Limit the first rollout group | Decide whether to restrict the enterprise app to a pilot group before broader rollout. | Use the approved business account and make sure you are in the assigned pilot group. | A narrow pilot lowers review risk and makes troubleshooting and rollback simpler. |
| Publish end-user instructions | Publish the supported Microsoft 365 surfaces, escalation path, and personal-account warning. | Use the guide for approved workflows only and report missing access with the exact failing surface. | Most early connector friction is caused by missing context, not by broken software. |
Step-by-Step
Follow this six-step setup flow for the first pilot.
These steps turn the official admin instructions into a rollout sequence that teams can actually execute.
2. Define the first pilot and name the owners
Document the pilot workflow, the user group, the Microsoft 365 surfaces in scope, and the person who owns Claude-side support.
3. Enable the connector in Claude when required
If you are on Team or Enterprise, have an organization owner enable the Microsoft 365 connector in Claude before users attempt to connect.
4. Complete Microsoft Entra admin consent
Have a Microsoft Entra Global Administrator complete the one-time organization consent so later users only need to authenticate.
5. Restrict access to the initial pilot cohort
Use enterprise app assignment or group-based controls if you want the pilot limited to a small set of users or devices.
6. Connect end users and validate the first workflow
Let end users connect with work accounts only, then validate the approved workflow and document how to revoke access if the pilot must stop.
Pilot Checklist
Use a short rollout checklist before you announce the connector internally.
The pilot should have a clear user list, approved surfaces, and a rollback owner before it becomes a broad communication exercise.
List the pilot users and the workflow each one will validate.
Decide whether SharePoint, OneDrive, Outlook, Teams, or only a subset of services are in scope.
Prepare an internal FAQ that explains delegated permissions and read-only access.
Document where audit activity will be checked during the pilot.
Write down the owner for user support, permission changes, and full rollback.
Account Limitation
Personal Microsoft accounts are not supported
Keep this warning in your rollout guide so users do not discover it by trial and error.
Anthropic's support articles say the connector requires a Microsoft 365 account tied to a Microsoft Entra tenant and a Microsoft Business plan. Personal Microsoft accounts such as @outlook.com and @hotmail.com are not supported and will hit an authentication dead end.
Next Steps
After setup planning, move into scope review, troubleshooting, or compliance questions.
Use the next page that matches the blocker you still need to clear.
Review the permission matrix
Use the matrix to decide which Microsoft 365 surfaces belong in the first pilot and what can be revoked later.
Open pageCheck common errors
Use the troubleshooting page if users are already seeing auth failures, missing data, or policy-related blockers.
Open pageOpen the compliance FAQ
Use the FAQ when a reviewer needs short answers on delegated access, audit logs, retention, or revocation.
Open pageFAQ
These setup answers remove the most common rollout ambiguity.
Use them in your internal guide or support script so the first pilot users get consistent answers.
Is the connector available on all Claude plans?+
Anthropic's docs page and support pages were not aligned on April 11, 2026. The docs page said Team and Enterprise only, while the enable guide and security guide both said the connector was available on all Claude plans. Verify current wording before you publish internal guidance.
Can end users connect with personal Outlook or Hotmail accounts?+
No. The support articles say the connector requires a Microsoft 365 work account tied to a Microsoft Entra tenant. Personal Microsoft accounts such as Outlook.com or Hotmail are not supported.
Can users self-serve the connection on day one?+
Not if the tenant has never been authorized. Anthropic documents a two-step reality: a Microsoft Entra Global Administrator must grant consent first, and on Team or Enterprise plans an organization owner must enable the connector in Claude before team members can connect.