Microsoft Teams
List teams and channels, send channel messages, and read and send chat messages.
A Microsoft Teams connection gives a playbook's functions six operations of Microsoft Graph, from a document Auto ships. You sign in with your work account and allow access, and the connection acts as you: a channel message it sends is from you, and the chats it reads are yours.
Available on Auto Cloud and on self-hosted runtimes.
What a playbook can do with Microsoft Teams
- List the teams you are in and their channels.
- Send a message to a channel.
- List your one-to-one and group chats, read their messages, and send a chat message.
It reads no channel's messages: the Graph permission for that always needs an administrator's consent, so the connection does not ask it. A playbook that must read a channel's history uses the Teams connection to post and a chat for the replies it reads.
The tools, as the connection lists them
Tools that read: me.ListJoinedTeams, teams.ListChannels, me.ListChats and chats.ListMessages.
Tools that act: chats.CreateMessages and teams.channels.CreateMessages.
An example workflow
A daily stand-in for the status round. A schedule trigger runs the workflow at 16:30 on weekdays. A lookup function reads the day's items from a Linear or Jira connection: what closed, what is blocked. A reasoning function writes a four-line summary in the team's voice. An interaction function sends it to the project channel through the Teams connection. For the blocked items, a second interaction function asks the owner in a one-to-one chat whether they need help, and waits, reading the chat's messages for the reply until the next morning; an answer is recorded on the run, and silence ends it as unanswered, which the manager sees in Studio. Nothing is sent that the reasoning function's prompt did not shape, and every message is in the run's history.
How to connect Microsoft Teams
- Sign in with your work account and allow access to your teams, channels and chats. Your tenant's consent policy may require an administrator to allow Auto once, as Microsoft's default policy for new tenants does for chats. The consent screen shows the permissions listed below.
Then:
- Ask your agent to connect Microsoft Teams to Auto, or open Settings, Agents, Connections in Auto Studio and choose Microsoft Teams.
- On the Studio page, check the service and its access, choose which playbooks may use the connection, and approve it.
- Have your agent check one small read through the connection before a function depends on it.
What it needs
- A work or school account in a Microsoft 365 tenant with Teams. A personal Microsoft account does not sign in here.
- If your tenant's policy requires it, an administrator who allows Auto once; Microsoft's default policy for new tenants requires that for
Chat.Read. - Your agent connected to Auto and signed in as you, with permission to change your organization, if your agent adds the connection.
- On a self-hosted runtime, an application registered in Microsoft Entra for the runtime, since Microsoft registers no client itself, as Let people add connections sets out.
Permissions Auto asks for
- Read the names and descriptions of teams in Microsoft Teams.
- Read the names and descriptions of channels in Microsoft Teams.
- Send channel messages in Microsoft Teams.
- Read the one-to-one and group chat messages of the person who connects in Microsoft Teams.
- Send one-to-one and group chat messages in Microsoft Teams.
- Keep access to Microsoft Teams when nobody is signed in.
Good to know
A message the connection sends is from you, so the playbook's words carry your name; keep the prompt that shapes them where the team can read it, in Studio. What a function reads from your chats is kept in the run's history, where people with access to the playbook can read it.