[DOCS] M365 3P local connector reference is missing Teams write scopes documented as supported in the changelog
Documentation Type
Missing documentation (feature not documented)
Documentation Location
https://claude.com/docs/third-party/claude-desktop/connectors-m365#grant-write-scopes
Section/Topic
Grant write scopes
Current Documentation
The Cowork changelog states that Microsoft Teams write operations are supported as of
v1.24012.0 and later:
https://claude.com/docs/cowork/changelog#v1-24012-0
However, the M365 connector configuration reference does not list any Teams write scopes in
its "Grant write scopes" section:
https://claude.com/docs/third-party/claude-desktop/connectors-m365#grant-write-scopes
The two pages disagree, so there is no documented way to actually enable the Teams write
operations the changelog says are available. Users who read the changelog and then go to the
configuration reference to grant the required permissions hit a dead end.
What's Wrong or Missing?
The two pages contradict each other. The changelog advertises Teams write support, but the configuration reference documents no Teams write scopes at all. There is therefore no documented path to enabling the feature the changelog says exists.
Suggested Improvement
Add a Teams row to the "Grant write scopes" table on the M365 connector page covering the Graph permissions required for Teams write operations, and state which operations each scope unlocks. eg:
Microsoft Teams
ChatMessage.Send — send messages in 1:1, group, and meeting chats the signed-in user is a member of.
ChannelMessage.Send — post messages to Teams channels.
Teams write operations require Claude Desktop v1.24012.0 or later. If these scopes are not granted, Teams tools remain read-only (teams_list_chats, chat_message_search) and write tools such as teams_send_chat_message will not appear.
The exact scope names should be confirmed against the connector's actual manifest before publishing.
Additionally, cross-link the changelog entry to the "Grant write scopes" section so users landing on the changelog know where to go next. If Teams write support was in fact rolled back or is gated behind something other than scopes, the changelog entry should be amended instead so the two pages agree.
Impact
High - Prevents users from using a feature
Additional Context
_No response_