Microsoft Teams

Category: Team Messaging
Connect by: Connect with OAuth
Official API docs: https://learn.microsoft.com/en-us/graph/api/resources/teams-api-overview

What the agent can see

Capability	API call	Risk	Needs approval
List messages in a team channel. (docs)	GET /teams/{team-id}/channels/{channel-id}/messages	🟢 low	— no
List messages in a chat. (docs)	GET /chats/{chat-id}/messages	🟢 low	— no

What the agent can do

Capability	API call	Risk	Needs approval
Post a new message to a team channel. (docs)	POST /teams/{team-id}/channels/{channel-id}/messages	🟡 medium	✅ yes
Send a new message to a chat. (docs)	POST /chats/{chat-id}/messages	🟡 medium	✅ yes

Connecting it

• You provide: Microsoft 365 account (OAuth)
• Where to get it: Register an app in the Microsoft Entra admin center (App registrations), add Microsoft Graph DELEGATED permissions, grant admin consent, then connect via OAuth. Posting uses delegated permissions (the agent posts as the signed-in user).
• Permissions/scopes: https://graph.microsoft.com/ChannelMessage.Send, https://graph.microsoft.com/ChatMessage.Send, https://graph.microsoft.com/ChannelMessage.Read.All, https://graph.microsoft.com/Chat.Read, offline_access

Account setup

• Account needed: A Microsoft 365 tenant with Teams.
• App registration: Register an app in Microsoft Entra ID (client id + secret + redirect URI); add delegated Graph permissions ChannelMessage.Send, ChatMessage.Send, ChannelMessage.Read.All, Chat.Read; a tenant admin grants consent.
• Verification required: Higher-privileged/.All permissions require tenant-admin consent. Posting is delegated-only (no headless app-only posting except a migration permission).
• Testing: Use your own M365 dev tenant; note Microsoft's ToS: don't use Teams 'as a log file'.

Limits

Microsoft Graph applies per-app/per-tenant throttling; HTTP 429 with Retry-After on exceed.