Setup Guide
Start here if you need to understand who does what before anyone clicks Connect.
- Prerequisites and owner mapping
- Tenant consent sequence
- Pilot rollout checklist
Admin playbook
Claude x Microsoft 365 Admin Playbook
Use this site to plan setup, review permission scope, troubleshoot rollout blockers, and answer compliance questions before you expand the Claude Microsoft 365 connector to real users.
Start Here
Choose the task that matches the job you need to finish.
The playbook is organized around admin tasks, not around product marketing.
Permission Matrix
Use this page to review what SharePoint, OneDrive, Outlook, and Teams access actually means for a pilot.
- Delegated scope mapping
- Audit and revocation references
- Surface-by-surface review questions
Common Errors
Use the error library when users are already stuck and you need to identify the likely owner and the next fix.
- Authentication blockers
- Policy and assignment failures
- Plan wording confusion
Compliance FAQ
Use the compliance FAQ when a security reviewer or approver needs short, direct answers before the pilot moves forward.
- Delegated access basics
- Logging and retention notes
- Revocation and pilot FAQ
Who This Is For
This playbook is written for the people who have to make the rollout work.
If you are searching for connector setup help, permission scope, or review answers, these are the roles this site is written for.
Microsoft 365 admins
You need the one-time setup sequence, tenant prerequisites, and the first rollout checklist.
Security and compliance reviewers
You need to understand delegated scopes, audit visibility, and how to disable or narrow the connector.
AI program owners
You need to publish clear internal guidance so users do not get stuck in avoidable setup loops.
Pilot and rollout managers
You need a narrow pilot with named owners, clear scope, and a rollback path before expansion.
Before You Start
Check these rollout prerequisites before anyone tries to connect.
Most early connector friction is caused by missing owner decisions, account mismatch, or pilot scope gaps.
Confirm that pilot users sign in with Microsoft 365 work accounts tied to a Microsoft Entra tenant.
Decide who owns Claude configuration, who owns Microsoft Entra consent, and who signs off on the pilot.
Choose which Microsoft 365 surfaces are in scope for the first rollout: SharePoint, OneDrive, Outlook, Teams, or a narrower subset.
Prepare a small pilot group before broad communication so app assignment, conditional access, and rollback are easy to manage.
Official Sources
Use the official references and keep the current availability caveat visible.
The links below are the main references behind this playbook. The caveat panel captures the current mismatch you should re-check before publishing internal guidance.
Claude docs
Documentation page that currently says the Microsoft 365 connector is available for Team and Enterprise plan users only.
Enable and use guide
Support article with admin setup steps, permission categories, troubleshooting notes, and all-plan wording dated April 11, 2026.
Microsoft 365 connector security guide
Security article covering delegated permissions, read-only scope, revocation options, and the all-plan wording dated April 11, 2026.
Microsoft Graph delegated access
Microsoft explanation of delegated permissions, where the app acts on behalf of the signed-in user and cannot exceed user access.
Microsoft Purview audit search
Microsoft guidance for audit log search roles, retention, and typical audit record availability.