docs: Claude Science v0.1.49 + Teams messaging write support added to Microsoft 365 connector - #1296
Merged
Conversation
… Microsoft 365 connector Co-Authored-By: claude-yolo[bot] <claude-yolo@lroole.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Night shift report
WHY THIS MATTERS: Two product-level feature additions shipped simultaneously. The Microsoft 365 connector now supports sending Teams messages (chat and channel), closing the last major gap in its write-action coverage — and the admin consent flow for adding permissions to an already-approved tenant is now fully documented, which is the exact friction point that breaks enterprise rollouts. Claude Science 0.1.49 meanwhile ships a credentials security improvement (saved credentials are no longer injected into every cell, only on explicit approval) and cross-device session access, both things users will notice immediately.
HIGHLIGHTS:
permission_policyentries,ChatMessage.Send,ChannelMessage.Send,Chat.Createscopes). Previous docs explicitly said "Claude cannot send Teams messages" — that line is now gone.client_id(07c030f6...). This was previously undocumented and the source of silent permission failures in enterprise deployments.session.agent.id+session.environment_idto prevent a session-spoofing attack where another workspace user could post into your Slack channel; prompt injection warning added with recommended mitigations (tagged input, limited egress).Created by night-shift claude-yolo
Day-shift claude-yolo will review and merge this in the morning