from line 1
11# Microsoft 365 connector
22
3> Connect SharePoint, OneDrive, Outlook, and Teams to Claude
3> Connect SharePoint, OneDrive, Outlook, and Teams to Claude so it can search, analyze, and act on your Microsoft 365 information
44
5The Microsoft 365 connector enables Claude to search, analyze, and act on information across SharePoint, OneDrive, Outlook, and Teams.
5The Microsoft 365 connector lets Claude search, analyze, and act on information across SharePoint, OneDrive, Outlook, and Teams, using the access your own Microsoft 365 account already has. It's available on every Claude plan: Free, Pro, Max, Team, and Enterprise. It requires a work or school Microsoft account, and a Microsoft Entra Global Administrator must grant tenant consent for your Microsoft organization.
66
7By the end of this page you have the connector set up for your organization and your own account connected, and you have asked Claude a first question that draws on Microsoft 365.
8
79<Note>
8 Available on all Claude plans: Free, Pro, Max, Team, and Enterprise. On Team and Enterprise plans, an organization Owner must enable the connector before members can connect.
10 * If your organization runs Claude Desktop on third-party inference, see [Connect to Microsoft 365](/docs/third-party/claude-desktop/connectors-m365) instead
11 * If you're in a US government deployment, see [Set up the Microsoft 365 connector](/docs/government/connectors/microsoft-365) in the government section
912</Note>
1013
11## Capabilities
14## Review what Claude can do
1215
13With this connector, Claude can:
16All access is delegated: Claude acts on your behalf and can read or change only what your Microsoft 365 account can already read or change. The table lists what Claude can do in each service; the write column applies only when your administrators have turned on [write actions](#write-actions).
1417
15* **Search and analyze documents** across SharePoint sites and OneDrive libraries
16* **Access email threads** and analyze Outlook communications
17* **Review meeting information** from Teams Calendar
18* **Pull insights** from Teams Chat discussions
19* **Send and manage email**, including drafts, labels, mail filters, and automatic replies
20* **Manage calendar events** and find meeting times
21* **Create and update files** in SharePoint
22* **Send Teams messages** in chats and channels
18| Service | Read and search | Write |
19| --------------------------- | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
20| **SharePoint and OneDrive** | Search and analyze documents across SharePoint sites and OneDrive libraries | Create and update files in SharePoint |
21| **Outlook** | Search email threads and archived email | Send mail and manage drafts, labels, mail filters, and automatic replies; create, update, and delete calendar events and find meeting times |
22| **Teams Calendar** | Review meeting information, summaries, and attendance | None |
23| **Teams Chat** | Read channel and chat discussions | Send chat and channel messages |
2324
24## Setup requirements
25## Set up the connector
2526
26On Free, Pro, and Max plans, no organization-level setup is needed. Connect from **Customize > Connectors** in claude.ai. A Microsoft Entra Global Administrator still needs to grant tenant consent for your Microsoft organization.
27What you do first depends on your Claude plan:
2728
29* **Free, Pro, and Max**: there's no organization-level step in Claude. Skip to [Connect your account](#connect-your-account). A Microsoft Entra Global Administrator still needs to grant tenant consent for your Microsoft organization
30* **Team and Enterprise**: a Claude Owner or Primary Owner [adds the connector for the organization](#add-the-connector-for-your-organization) first, and then each member connects their account
31
2832### Prerequisites
2933
30* A work or school Microsoft account on a Microsoft Entra tenant (personal accounts such as outlook.com, hotmail.com, or live.com aren't supported)
31* Claude user with Owner or Primary Owner role (Team and Enterprise plans)
32* Global Administrator access to Microsoft Entra tenant
33* Active Microsoft 365 accounts for all users (Team and Enterprise plans)
34Check these before you start:
3435
35### Phase 1: Administrator setup
36* A work or school Microsoft account on a Microsoft Entra tenant. Personal accounts such as outlook.com, hotmail.com, or live.com aren't supported
37* Global Administrator access to the Microsoft Entra tenant
38* On Team and Enterprise plans: the Owner or Primary Owner role in Claude, and active Microsoft 365 accounts for all users
3639
37**Automatic Setup (Recommended):**
40### Add the connector for your organization
3841
391. Navigate to **Organization settings > Connectors**
402. Select **Add**, then **All available**
413. Find Microsoft 365 and select "Add to your team"
424. Connect individually and grant organization-wide permissions
435. (Optional) Restrict user access or revoke specific permission scopes
42On Team and Enterprise plans, an Owner or Primary Owner adds the connector once for everyone. The steps below are the automatic setup, which is the recommended path.
4443
45### Phase 2: User enablement
44<Steps>
45 <Step title="Open organization connectors">
46 In claude.ai, go to [**Organization settings > Connectors**](https://claude.ai/admin-settings/connectors).
47 </Step>
4648
47Once enabled by administrators, team members:
49 <Step title="Add Microsoft 365">
50 Select **Add**, then **All available**. Find **Microsoft 365** and select **Add to your team**.
51 </Step>
4852
491. Navigate to **Customize > Connectors**
502. Find Microsoft 365 and click "Connect"
513. Authenticate with credentials
53 <Step title="Connect and grant consent">
54 Connect your own account and grant the organization-wide permissions.
55 </Step>
5256
53## Usage
57 <Step title="Adjust access if needed">
58 Restrict which users can use the connector, or revoke specific permission scopes.
59 </Step>
60</Steps>
5461
55Ask Claude questions requiring Microsoft 365 data, or ask Claude to take an action such as sending an email or updating a file. Claude automatically detects and uses the necessary tools.
62For the detailed administrator walkthrough, see [Set up the Microsoft 365 connector](https://support.claude.com/en/articles/12542951-set-up-the-microsoft-365-connector) in the help center. The [Microsoft 365 connector security guide](https://support.claude.com/en/articles/12684923-microsoft-365-connector-security-guide) covers the permission model.
5663
57### Example queries
64### Connect your account
5865
59* "Find the Q4 strategic planning document in SharePoint"
60* "Summarize email conversations about the product launch"
61* "What discussions happened in Teams about the marketing campaign?"
62* "Review meeting notes from last week's leadership sync"
63* "Draft a reply to the latest email about the vendor contract"
64* "Schedule a 30-minute sync with the design team next week"
66Once the connector is available to you, connect your own Microsoft 365 account.
6567
66## What you can access
68<Steps>
69 <Step title="Open your connectors">
70 Go to [**Customize > Connectors**](https://claude.ai/customize/connectors) in claude.ai. **Customize** is the page that holds your connectors, skills, and plugins.
71 </Step>
6772
68| Service | Capabilities |
69| ----------------------- | ---------------------------------------------------------------------------------------------------------- |
70| **SharePoint/OneDrive** | Search and analyze documents; create and update files in SharePoint |
71| **Outlook** | Search email threads and archived emails; send and manage mail; create, update, and delete calendar events |
72| **Teams Calendar** | Review meeting summaries and attendance |
73| **Teams Chat** | Access channel and chat discussions; send chat and channel messages |
73 <Step title="Connect Microsoft 365">
74 Find **Microsoft 365** and select **Connect**.
75 </Step>
7476
77 <Step title="Sign in to Microsoft">
78 Sign in with your work or school Microsoft credentials.
79 </Step>
80</Steps>
81
82When the connection succeeds, the **Connect** button on the Microsoft 365 connector changes to **Disconnect**. For the member walkthrough, see [Connect to Microsoft 365](https://support.claude.com/en/articles/15183774-connect-to-microsoft-365) in the help center.
83
84## Try the connector
85
86In a conversation, select **+** at the lower left of the message box, select **Connectors**, and turn on **Microsoft 365**. Then ask a question that needs Microsoft 365 data, or ask Claude to take an action such as sending an email or updating a file. Claude detects which tools it needs and uses them. For example, ask Claude:
87
88* Find the Q4 strategic planning document in SharePoint
89* Summarize email conversations about the product launch
90* What discussions happened in Teams about the marketing campaign?
91* Draft a reply to the latest email about the vendor contract
92* Schedule a 30-minute sync with the design team next week
93
94Claude's answer draws on the documents, email, and Teams content it found. Requests that change something, such as the last two examples, work only when write actions are turned on for you; otherwise Claude can still read and search.
95
7596## Write actions
7697
77Claude can take actions in Outlook, SharePoint, and Teams. In Outlook, Claude sends mail and manages drafts, organizes mail with labels, filters, and trash, sets automatic replies, and creates, updates, and deletes calendar events. In SharePoint, Claude creates and updates files. In Teams, Claude sends chat and channel messages. Read and search tools work the same whether or not write actions are enabled.
98Claude can take actions in Outlook, SharePoint, and Teams, as listed in the write column of [Review what Claude can do](#review-what-claude-can-do). Read and search tools work the same whether or not write actions are enabled. Claude can't attach files to the drafts it creates.
7899
79Write actions are controlled by your organization's administrators in two places:
100Your organization's administrators control write actions in two places: the connector's permissions in Microsoft Entra, and the Microsoft 365 connector configuration under **Organization settings > Connectors**.
80101
811. **Approve the write permissions.** If your tenant approved the connector before a write permission (mail, calendar, mailbox settings, file writes, or Teams messages) was added, a Microsoft Entra Global Administrator or Application Administrator approves the added permissions once for the tenant. Reconnecting doesn't add them. See [Approve permissions added to the connector](#approve-permissions-added-to-the-connector).
822. **Turn on write actions.** If write actions are off for your organization, administrators turn them on for all users in the Microsoft 365 connector configuration, or enable them for specific users with role-based access control (beta). Administrators also check the restriction on each tool that sends Teams messages. Open the Microsoft 365 connector under **Organization settings > Connectors**, find **Tool permission restrictions**, and set each Teams messaging tool so that users can choose it. A per-tool restriction overrides the **Default restriction** row, so a tool that is blocked for all users stays unavailable until an administrator changes its restriction.
102### Approve the write permissions
83103
84Claude cannot attach files to the drafts it creates.
104If your tenant approved the connector before a write permission (mail, calendar, mailbox settings, file writes, or Teams messages) was added, a Microsoft Entra Global Administrator or Application Administrator approves the added permissions once for the tenant. Reconnecting doesn't add them. See [Approve permissions added to the connector](#approve-permissions-added-to-the-connector).
85105
86For setup steps, see [Connect to Microsoft 365](https://support.claude.com/en/articles/15183774-connect-to-microsoft-365) and [Set up the Microsoft 365 connector](https://support.claude.com/en/articles/12542951-set-up-the-microsoft-365-connector) in the help center. The [Microsoft 365 connector security guide](https://support.claude.com/en/articles/12684923-microsoft-365-connector-security-guide) covers the permission model.
106### Turn on write actions
87107
108If write actions are off for your organization, administrators turn them on for all users in the Microsoft 365 connector configuration, or enable them for specific users with role-based access control (beta). Administrators also check the restriction on each tool that sends Teams messages. A per-tool restriction overrides the **Default restriction** row, so a tool that is blocked for all users stays unavailable until an administrator changes its restriction. To let users choose those tools:
109
110<Steps>
111 <Step title="Open the connector's configuration">
112 Open the Microsoft 365 connector under **Organization settings > Connectors**.
113 </Step>
114
115 <Step title="Find Tool permission restrictions">
116 Find **Tool permission restrictions**.
117 </Step>
118
119 <Step title="Allow each Teams messaging tool">
120 Set each Teams messaging tool so that users can choose it.
121 </Step>
122</Steps>
123
88124## Permissions
89125
90<Note>
91 All permissions are delegated: Claude acts on behalf of users and can only access and change content that you already have permission to access and change in Microsoft 365. Write actions are available when your administrators enable them (see [Write actions](#write-actions)).
92</Note>
126All permissions are delegated: Claude acts on behalf of users and can only access and change content that you already have permission to access and change in Microsoft 365. Write actions are available when your administrators enable them, as described in [Write actions](#write-actions).
93127
94128### Approve permissions added to the connector
95129
96130If your tenant approved the connector before Anthropic added a permission to it, the Claude feature that needs the permission fails with a permission error until a Microsoft Entra administrator approves it. For example, listing your teams fails until your tenant approves `Team.ReadBasic.All`. Disconnecting and reconnecting the connector in claude.ai doesn't add the permission, because Microsoft [doesn't show a consent screen again once the tenant has approved the connector](https://learn.microsoft.com/en-us/entra/identity-platform/scopes-oidc#the-default-scope). The connector's **Permissions** page in the Entra admin center (under **Enterprise applications**, listed as **M365 MCP Server for Claude**) shows only the permissions your tenant has already approved, so a missing permission doesn't appear there.
97131
98A Global Administrator or Application Administrator approves the added permissions for the whole tenant in three steps.
132A Global Administrator or Application Administrator approves the added permissions for the whole tenant by opening the admin consent link and accepting the list it shows.
99133
100134<Steps>
101135 <Step title="Open the admin consent link">
from line 149
115149 </Step>
116150</Steps>
117151
118Selecting **Grant admin consent for \{your organization}** on that **Permissions** page approves the same list.
152Selecting **Grant admin consent for \{your organization}** on the connector's **Permissions** page in the Entra admin center approves the same list as the admin consent link.
119153
120This link is for the connector used from claude.ai. If the Application ID on the enterprise application's **Overview** page differs from the one in the link (for example in a government deployment), use that ID instead. The Claude Desktop local connector and a self-hosted server use their own app registrations.
154The admin consent link is for the connector used from claude.ai. If the Application ID on the enterprise application's **Overview** page differs from the one in the link (for example in a government deployment), use that ID instead. The Claude Desktop local connector and a self-hosted server use their own app registrations.
121155
122156## Troubleshooting
123157
158If something isn't working, start with the case that matches what you see.
159
124160<AccordionGroup>
125161 <Accordion title="Authentication failures">
126 * Verify correct Microsoft 365 credentials
127 * Check active license status
128 * Review organizational third-party app policies
129 * Try a different browser
130 * Clear cookies and cache
162 If sign-in fails, work through these checks:
163
164 * Confirm you're signing in with your work or school Microsoft 365 credentials, not a personal account
165 * Check that your Microsoft 365 license is active
166 * Review your organization's third-party app policies
167 * Try a different browser, or clear cookies and cache and sign in again
131168 </Accordion>
132169
133170 <Accordion title="Documents not found">
134 * Verify direct access to the document in Microsoft 365
135 * Ensure document is in SharePoint/OneDrive (not local)
136 * Recently uploaded documents may need time to index
137 * Use specific SharePoint site names
138 * Search by exact filename
171 If Claude can't find a document you know exists:
172
173 * Confirm you can open the document directly in Microsoft 365
174 * Make sure the document is stored in SharePoint or OneDrive, not only on your computer
175 * Wait and retry for recently uploaded documents, which can take time to index
176 * Name the specific SharePoint site, or search by the exact filename
139177 </Accordion>
140178
141179 <Accordion title="Incomplete search results">
142 * Be more specific about requirements
180 If results are partial or miss what you expected:
181
182 * Be more specific about what you need
143183 * Specify locations and date ranges
144 * Use exact phrases
145 * Break complex queries into simpler questions
184 * Use exact phrases from the content
185 * Break a complex request into simpler questions
146186 </Accordion>
147187</AccordionGroup>
188
189## Next steps
190
191* [Get started with connectors](/docs/connectors/getting-started): set up another connector and use it in conversations
192* [Connectors directory](/docs/connectors/directory): browse verified and community integrations
148193
No line in this hunk matches that.