Overview
The Microsoft Teams integration unlocks workflow actions that you can use to automate incident communication in Microsoft Teams channels and chats. If you are unfamiliar with how Workflows function, please visit our Workflows documentation first.Channel Actions
Create Microsoft Teams Channel
This action creates a dedicated Microsoft Teams channel for an incident. Responding to each incident in a designated channel helps teams keep communication organized.Team
Select the Microsoft Teams team where the channel will be created.Title
Specify a title for the incident channel. This field supports Liquid variables. Setting the field toincident-{{ incident.created_at | date: '%Y%m%d' }}-{{ incident.title }} will create a channel named incident-20231119-<incident-title>.
Channel names are automatically formatted: lowercased, parameterized, and truncated to 50 characters (Microsoft’s hard limit).
Description
An optional description for the channel. This field supports Liquid variables.Private
Controls whether the channel is created as public or private:- auto - Creates a private channel for private incidents and a public channel for non-private incidents.
- true - Always creates a private channel.
- false - Always creates a public channel.
If the incident already has a Microsoft Teams channel, this action will skip channel creation to avoid duplicates.
Archive Microsoft Teams Channel
This action archives one or more Microsoft Teams channels. Archiving channels after an incident is resolved helps keep the workspace clean while preserving the conversation history.Team
Select the Microsoft Teams team that contains the channel(s) to archive.Channels
Select which Microsoft Teams channel(s) to archive.Rename Microsoft Teams Channel
This action renames an existing Microsoft Teams channel. Use it to update channel names as incident status changes (for example, prefixing resolved incidents withresolved-).
Team
Select the Microsoft Teams team that contains the channel to rename.Channel
Select the channel to rename. This field supports Liquid variables.Title
The new title for the channel. This field supports Liquid variables.Invite to Microsoft Teams Channel
This action invites users to a Microsoft Teams channel by email. This is useful for automatically adding responders to a private incident channel when they are assigned a role.Team
Select the Microsoft Teams team that contains the channel.Channel
Select the channel to invite users to. This field supports Liquid variables.Emails
A comma-separated list of email addresses to invite. This field supports Liquid variables.Add Microsoft Teams Channel Tab
This action adds a custom tab to a Microsoft Teams channel. Tabs provide quick access to dashboards, runbooks, or any web-based resource directly within the incident channel.Team
Select the Microsoft Teams team that contains the channel.Channel
Select the channel to add the tab to. This field supports Liquid variables.Title
The display name shown on the tab. This field supports Liquid variables.Link
The URL the tab should point to. This field supports Liquid variables.Playbook
Optionally, select a playbook to add as a tab instead of specifying a title and link manually.The Rootly app must be installed in the target team for this action to work.
Send Microsoft Teams Channel Message
This action sends a text message to one or more Microsoft Teams channels using the Rootly bot.Channels
Select which Microsoft Teams channel(s) to send the message to. This field supports Liquid variables.Text
The content of the message to send. This field supports Liquid variables.If the message text is empty, the action will be skipped.
Send Microsoft Teams Attachments
This action sends Adaptive Card attachments to one or more Microsoft Teams channels. Adaptive Cards allow you to send richly formatted, interactive content such as structured incident summaries or action buttons.Channels
Select which Microsoft Teams channel(s) to send the attachments to. This field supports Liquid variables.Attachments
A JSON payload defining the Adaptive Card content. This field supports Liquid variables. Attachments follow the Microsoft Adaptive Card schema.Chat Actions
Create Microsoft Teams Chat
This action creates a new Microsoft Teams chat for an incident. It supports both group chats (multiple members with a topic) and one-on-one chats (exactly two members). Once created, the chat ID and URL are stored on the incident for use in subsequent workflow actions.Chat Type
Select the type of chat to create:- group - Creates a group chat that supports multiple members and an optional topic.
- oneOnOne - Creates a one-on-one chat between exactly two members.
Topic
Set a topic for the chat. Only used for group chats. This field supports Liquid variables.Members
A JSON array specifying the members to add to the chat. Each member requires anemail field. An optional roles field defaults to ["owner"]. This field supports Liquid variables.
For group chats, at least three members are required (including the service account). For one-on-one chats, exactly two members are needed.
Send Microsoft Teams Chat Message
This action sends a message to one or more Microsoft Teams chats.Chats
Select or specify which Microsoft Teams chat(s) to send the message to. You can use{{ incident.microsoft_teams_chat_id }} to target the incident’s associated chat.
Text
The content of the message to send. This field supports HTML formatting and Liquid variables.Add Microsoft Teams Chat Tab
This action adds a custom tab to a Microsoft Teams chat. Tabs provide quick access to dashboards, tickets, or any web-based resource directly within the chat.Chat
Specify which chat to add the tab to. You can use{{ incident.microsoft_teams_chat_id }} to target the incident’s associated chat.
Title
The display name shown on the tab. This field supports Liquid variables.Link
The URL the tab should point to. This field supports Liquid variables.The Rootly app must be installed in the target team for this action to work. Rootly will automatically attempt to install the app into the chat before adding the tab.