Skip to main content
Let your agents read your Teams channels and chats, post and reply to messages, start chats and look up colleagues on your behalf.

Connection

  • Authentication: OAuth 2.0 — you authorize Atako via Microsoft Teams’s consent screen; no key to copy.
  • Scopes requested:
    • offline_access
    • User.Read
    • User.ReadBasic.All
    • Team.ReadBasic.All
    • Channel.ReadBasic.All
    • ChannelMessage.Read.All
    • ChannelMessage.Send
    • TeamMember.Read.All
    • Chat.Read
    • Chat.Create
    • ChatMessage.Send
Nothing to paste: click Connect and sign in with your Microsoft 365 work or school account (personal Microsoft accounts are not supported by Teams APIs). Prerequisite on the Atako side — Teams reuses the Microsoft Entra app of the Outlook connector: an administrator sets INTEGRATION_OAUTH_MICROSOFT_TEAMS_CLIENT_ID / _CLIENT_SECRET to the same values as INTEGRATION_OAUTH_OUTLOOK_CLIENT_ID / _CLIENT_SECRET, and adds the delegated permissions in Entra → App registrations → Atako → API permissions → Microsoft Graph → Delegated: User.Read, User.ReadBasic.All, Team.ReadBasic.All, Channel.ReadBasic.All, ChannelMessage.Read.All, ChannelMessage.Send, TeamMember.Read.All, Chat.Read, Chat.Create, ChatMessage.Send, offline_access. ChannelMessage.Read.All and TeamMember.Read.All require an administrator of your Microsoft 365 tenant to grant consent.See Microsoft Teams’s documentation.

Read actions (12)

Write actions (4)

Permissions

Every action above must be explicitly granted to an agent before it can be used. See Permissions for the grant model and Security for how credentials are protected.