Microsoft 365 connector changedconnectors/microsoft/365
Nearest release: v2.1.288, published 11 hours after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 2 Oct 2026 06:33 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+70added
Lines−80removed
From line
6
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits6to this page, all time
The whole hunk
from line 6, old and new numbered
/
from line 6
66
77By 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.
88
9<Note>
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
12</Note>
9> [!NOTE]
10>
11> * If your organization runs Claude Desktop on third-party inference, see [Connect to Microsoft 365](/docs/third-party/claude-desktop/connectors-m365) instead
12> * If you're in a US government deployment, see [Set up the Microsoft 365 connector](/docs/government/connectors/microsoft-365) in the government section
1313
1414## Review what Claude can do
1515
from line 41
4141
4242On 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.
4343
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>
44**1. Open organization connectors**
4845
49 <Step title="Add Microsoft 365">
50 Select **Add**, then **All available**. Find **Microsoft 365** and select **Add to your team**.
51 </Step>
46In claude.ai, go to [**Organization settings > Connectors**](https://claude.ai/admin-settings/connectors).
5247
53 <Step title="Connect and grant consent">
54 Connect your own account and grant the organization-wide permissions.
55 </Step>
48**2. Add Microsoft 365**
5649
57 <Step title="Adjust access if needed">
58 Restrict which users can use the connector, or revoke specific permission scopes.
59 </Step>
60</Steps>
50Select **Add**, then **All available**. Find **Microsoft 365** and select **Add to your team**.
6151
52**3. Connect and grant consent**
53
54Connect your own account and grant the organization-wide permissions.
55
56**4. Adjust access if needed**
57
58Restrict which users can use the connector, or revoke specific permission scopes.
59
6260For 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.
6361
6462### Connect your account
from line 63
6563
6664Once the connector is available to you, connect your own Microsoft 365 account.
6765
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>
66**1. Open your connectors**
7267
73 <Step title="Connect Microsoft 365">
74 Find **Microsoft 365** and select **Connect**.
75 </Step>
68Go to [**Customize > Connectors**](https://claude.ai/customize/connectors) in claude.ai. **Customize** is the page that holds your connectors, skills, and plugins.
7669
77 <Step title="Sign in to Microsoft">
78 Sign in with your work or school Microsoft credentials.
79 </Step>
80</Steps>
70**2. Connect Microsoft 365**
8171
72Find **Microsoft 365** and select **Connect**.
73
74**3. Sign in to Microsoft**
75
76Sign in with your work or school Microsoft credentials.
77
8278When 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.
8379
8480## Try the connector
from line 103
107103
108104If 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:
109105
110<Steps>
111 <Step title="Open the connector's configuration">
112 Open the Microsoft 365 connector under **Organization settings > Connectors**.
113 </Step>
106**1. Open the connector's configuration**
114107
115 <Step title="Find Tool permission restrictions">
116 Find **Tool permission restrictions**.
117 </Step>
108Open the Microsoft 365 connector under **Organization settings > Connectors**.
118109
119 <Step title="Allow each Teams messaging tool">
120 Set each Teams messaging tool so that users can choose it.
121 </Step>
122</Steps>
110**2. Find Tool permission restrictions**
123111
112Find **Tool permission restrictions**.
113
114**3. Allow each Teams messaging tool**
115
116Set each Teams messaging tool so that users can choose it.
117
124118## Permissions
125119
126120All 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).
from line 125
131125
132126A 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.
133127
134<Steps>
135 <Step title="Open the admin consent link">
136 Replace `YOUR_TENANT_ID` with the Directory (tenant) ID shown in **Entra admin center > Overview**, then open the link. The `client_id` value is the connector's Application ID, shown on the **M365 MCP Server for Claude** enterprise application's **Overview** page.
128**1. Open the admin consent link**
137129
138 ```text theme={null}
139 https://login.microsoftonline.com/YOUR_TENANT_ID/adminconsent?client_id=07c030f6-5743-41b7-ba00-0a6e85f37c17
140 ```
141 </Step>
130Replace `YOUR_TENANT_ID` with the Directory (tenant) ID shown in **Entra admin center > Overview**, then open the link. The `client_id` value is the connector's Application ID, shown on the **M365 MCP Server for Claude** enterprise application's **Overview** page.
142131
143 <Step title="Review the permissions and accept">
144 The consent screen lists every permission the connector requests, including any added since your tenant first approved it and the permissions that write actions need. The Teams tools use `Team.ReadBasic.All` to list teams, `People.Read` to look up people, and `ChatMessage.Send`, `ChannelMessage.Send`, and `Chat.Create` to send messages. Select **Accept**.
145 </Step>
132```text theme={null}
133https://login.microsoftonline.com/YOUR_TENANT_ID/adminconsent?client_id=07c030f6-5743-41b7-ba00-0a6e85f37c17
134```
146135
147 <Step title="Confirm the approval">
148 Check the address bar of the page Microsoft sends you to. The approval succeeded when the address contains `admin_consent=True`, and the approved permissions then appear on the connector's **Permissions** page.
149 </Step>
150</Steps>
136**2. Review the permissions and accept**
151137
138The consent screen lists every permission the connector requests, including any added since your tenant first approved it and the permissions that write actions need. The Teams tools use `Team.ReadBasic.All` to list teams, `People.Read` to look up people, and `ChatMessage.Send`, `ChannelMessage.Send`, and `Chat.Create` to send messages. Select **Accept**.
139
140**3. Confirm the approval**
141
142Check the address bar of the page Microsoft sends you to. The approval succeeded when the address contains `admin_consent=True`, and the approved permissions then appear on the connector's **Permissions** page.
143
152144Selecting **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.
153145
154146The 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.
from line 149
157149
158150If something isn't working, start with the case that matches what you see.
159151
160<AccordionGroup>
161 <Accordion title="Authentication failures">
162 If sign-in fails, work through these checks:
152> **Authentication failures**
153>
154> If sign-in fails, work through these checks:
155>
156> * Confirm you're signing in with your work or school Microsoft 365 credentials, not a personal account
157> * Check that your Microsoft 365 license is active
158> * Review your organization's third-party app policies
159> * Try a different browser, or clear cookies and cache and sign in again
163160
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
168 </Accordion>
161> **Documents not found**
162>
163> If Claude can't find a document you know exists:
164>
165> * Confirm you can open the document directly in Microsoft 365
166> * Make sure the document is stored in SharePoint or OneDrive, not only on your computer
167> * Wait and retry for recently uploaded documents, which can take time to index
168> * Name the specific SharePoint site, or search by the exact filename
169169
170 <Accordion title="Documents not found">
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
177 </Accordion>
178
179 <Accordion title="Incomplete search results">
180 If results are partial or miss what you expected:
181
182 * Be more specific about what you need
183 * Specify locations and date ranges
184 * Use exact phrases from the content
185 * Break a complex request into simpler questions
186 </Accordion>
187</AccordionGroup>
170> **Incomplete search results**
171>
172> If results are partial or miss what you expected:
173>
174> * Be more specific about what you need
175> * Specify locations and date ranges
176> * Use exact phrases from the content
177> * Break a complex request into simpler questions
188178
189179## Next steps
190180
No line in this hunk matches that.