> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Microsoft Teams
> Connect Microsoft Teams to Rootly to create incident channels, run workflow actions, and start Teams meetings from incidents.
Rootly's Microsoft Teams integration automates incident communication and collaboration. When an incident starts, Rootly can create a dedicated Teams channel, invite responders, and post real-time updates. You can also create Microsoft Teams meetings directly from incidents for live collaboration.
Automatically create dedicated Teams channels for each incident with responders invited
Post incident status changes, severity updates, and key events to Teams channels
Create Microsoft Teams meetings for live incident collaboration with one click
Control which events trigger Teams notifications using workflow conditions
***
## How It Works
Authorize Rootly to access your Teams workspace via OAuth.
Add the Rootly app to your Teams workspace to enable channel creation and messaging.
Set up workflows to automatically create channels, send messages, or start meetings when incidents occur.
***
## Before You Begin
**Before you start:**
* Rootly account with Admin permissions
* Microsoft Teams account with access to the workspace you want to connect
* Ability to install apps in your Teams workspace (or admin approval from your Microsoft 365 admin)
Rootly recommends connecting with a **service account** rather than a personal account. This ensures the integration stays active if team members leave your organization.
***
## Installation
Setting up the Microsoft Teams integration involves two steps that work together. First, you authorize Rootly via OAuth so it can call the Microsoft Teams API on your behalf. Then, you install the Rootly bot directly inside Teams so it can create channels and post messages. Both steps are required — OAuth alone isn't enough to create channels or send messages.
### Part 1: Connect via OAuth
The OAuth flow grants Rootly permission to interact with your Microsoft Teams workspace through the API. You'll be redirected to Microsoft to sign in and approve the required permissions, then returned to Rootly automatically.
In Rootly, go to **Configuration → Integrations** and search for **Microsoft Teams**.
Click **Setup** on the Microsoft Teams integration to begin the OAuth flow.
You'll be redirected to Microsoft. Select your Microsoft 365 work account — this should be the service account you intend to use for the integration.
Microsoft will show you the permissions Rootly is requesting. Review them and click **Accept** to grant access.
After approving, you'll be redirected back to Rootly. A success message confirms the integration is connected.
Microsoft Teams is now connected to Rootly.
#### Required OAuth Permissions
| Permission | Purpose |
| ------------------------------------------- | ----------------------------------------------------------- |
| `offline_access` | Keeps the Rootly → Teams connection active between sessions |
| `User.Read` | Identifies the account connecting to Rootly |
| `Team.ReadBasic.All` | Lets Rootly see your Teams and channels |
| `ChatMessage.Send` | Rootly can post messages in chats and channels |
| `Channel.Create` | Rootly can create incident channels |
| `Channel.ReadBasic.All` | Read channel names and descriptions |
| `ChannelMessage.Send` | Rootly can send channel messages |
| `ChannelMessage.ReadWrite` | Rootly can update messages it posts |
| `ChannelSettings.ReadWrite.All` | Allows Rootly to manage channel settings |
| `ChannelMember.ReadWrite.All` | Rootly can add and remove users in incident channels |
| `TeamsTab.ReadWriteSelfForChat` | Rootly can install tabs in chats |
| `TeamsTab.ReadWriteSelfForTeam` | Rootly can install tabs in teams |
| `TeamsAppInstallation.ReadWriteSelfForTeam` | Rootly can install itself in teams |
| `TeamsAppInstallation.ReadWriteSelfForChat` | Rootly can install itself in chats |
| `Chat.Create` | Rootly can create group and one-on-one chats |
| `Chat.ReadWrite` | Rootly can read and send messages in chats |
***
### Part 2: Install the Rootly Bot
OAuth gives Rootly API access, but channel creation and messaging also require the Rootly bot to be present inside Microsoft Teams. Without the bot installed, workflows that create channels or send messages will fail. You install it directly from the Teams app store.
In Microsoft Teams, click **Apps** in the left sidebar and search for **Rootly**.
Click **Add** on the Rootly app listing.
Select the team where you want to install Rootly. Rootly recommends starting with the General channel of your primary incident response team.
The Rootly bot is now installed in your team and ready to create channels and send messages.
You'll need to repeat the bot installation for each team where you want Rootly to create incident channels. The service account must be a member of each team.
***
## Verify Installation
Once both parts are complete, confirm everything is working before setting up workflows:
1. **Check Rootly** — The integration status shows **Connected** on the integrations page
2. **Check Teams** — The Rootly app appears in your team's installed apps
3. **Test end-to-end** — Create a test incident in Rootly and verify a Teams channel is created automatically
If channels aren't being created, check your workflow configuration first. The bot must be installed in the specific team referenced in the workflow action.
***
## Microsoft Teams Meeting
The **Microsoft Teams Meeting** integration is a separate OAuth connection that enables creating video meetings directly from Rootly incidents. It uses a different set of permissions than the main Teams integration and must be connected independently — even if you've already set up the main Teams integration.
Once connected, a **Create a Microsoft meeting** button appears in the incident header, letting anyone on the response team spin up a live video call with one click.
### Setup
1. Go to **Configuration → Integrations** and search for **Microsoft Teams Meeting**
2. Click **Setup** and sign in with your Microsoft 365 work account
3. Approve the requested permissions
4. Once connected, the **Create a Microsoft meeting** button will appear on every incident
Rootly recommends connecting with a **service account** so the meeting integration stays active if a user leaves your organization.
### Required OAuth Permissions
| Permission | Purpose |
| -------------------------- | -------------------------------------------------------------------------- |
| `offline_access` | Required for OAuth authentication |
| `User.Read` | Identifies the account connecting to Rootly |
| `OnlineMeetings.ReadWrite` | Allows Rootly to create online meetings on behalf of the connected account |
### Uninstall the Meeting Integration
1. Log into your **Microsoft Teams Meeting** account
2. Click **Manage → Installed Apps** or search for the **Rootly** app
3. Click the **Rootly** app and click **Uninstall**
***
## Workflows
Auto-create Teams channels at incident start using built-in settings
Build workflows with triggers, conditions, and multiple Teams actions
***
### Available Actions
| Action | What It Does |
| ------------------------------------------- | -------------------------------------------------------------- |
| **Create Microsoft Teams Channel** | Creates a new channel for the incident |
| **Create Microsoft Teams Chat** | Creates a group or one-on-one chat |
| **Add Microsoft Teams Tab** | Adds a tab to the incident channel |
| **Archive Microsoft Teams Channel** | Archives the incident channel |
| **Rename Microsoft Teams Channel** | Changes the channel name |
| **Invite Users to Microsoft Teams Channel** | Invites users to a private incident channel |
| **Send Microsoft Teams Message** | Posts a message to a Teams channel |
| **Send Microsoft Teams Attachments** | Sends attachments to a Teams channel |
| **Create Microsoft Teams Meeting** | Starts a video meeting (requires separate Meeting integration) |
***
### Create a Workflow
Go to **Rootly → Workflows → Create Workflow**.
Select the workflow type that matches your use case (for example, Incident, Retrospective, or Pulse).
Triggers define when this workflow runs.
| Trigger | When It Fires |
| ------------------------------- | ----------------------------------- |
| **Incident Created** | New incident opens |
| **Incident Updated** | Severity, status, or fields change |
| **Incident Status Changed** | Incident moves to a specific status |
| **Incident Commander Assigned** | Someone takes ownership |
| **Incident Resolved** | Incident is resolved |
| **Manual Trigger** | Run on demand from the UI |
Conditions filter when the workflow should run after it's been triggered — keeping Teams activity focused on the incidents that matter.
Examples:
* Only for SEV-1 or SEV-2 incidents
* Only for specific teams or services
* Only for production environments
Click **Add Action** and search for **Microsoft Teams** to see all available actions.
***
### Action Reference
Creates a dedicated Teams channel for the incident. Use this as your first action when an incident opens to give responders a central place to coordinate.
The Microsoft Teams workspace where the channel will be created.
The channel name. Supports Liquid syntax (for example, `{{ incident.title }}`).
Channel names are automatically lowercased, parameterized, and truncated to 50 characters.
An optional description for the channel. Supports Liquid syntax.
Controls channel visibility:
* **auto** — Private for private incidents, public for non-private incidents
* **true** — Always private
* **false** — Always public
If the incident already has a Teams channel, this action skips creation to avoid duplicates.
Creates a group or one-on-one chat for the incident. Once created, the chat ID and URL are stored on the incident for use in subsequent actions.
* **group** — Creates a group chat with multiple members and an optional topic
* **oneOnOne** — Creates a one-on-one chat between exactly two members
A topic for the chat. Only used for group chats. Supports Liquid syntax.
A JSON array of members to add. Each member requires an `email` field. Supports Liquid syntax.
```json theme={null}
[
{"email": "alice@company.com"},
{"email": "bob@company.com", "roles": ["guest"]}
]
```
Group chats require at least three members (including the service account). One-on-one chats require exactly two.
Adds a tab to the incident Teams channel. Use this to give responders quick access to dashboards, runbooks, or the Rootly incident page directly within the channel.
The team that contains the channel.
The channel to add the tab to. Use `{{ incident.microsoft_teams_channel_id }}` to target the incident's channel.
The display name shown on the tab. Supports Liquid syntax.
The URL the tab should point to. Supports Liquid syntax.
Optionally select a playbook to add as a dedicated playbook tab. When a playbook is selected, the tab renders only the playbook checklist — it is a distinct tab type and does not include the Rootly incident dashboard. Leave this empty to use the Title and Link fields to add a URL-based tab, such as a link to the incident page or an external runbook.
The Rootly app must be installed in the target team for this action to work.
Archives the incident channel when it's no longer needed. Keeps the workspace clean while preserving conversation history.
The team that contains the channel.
The channel(s) to archive. Use `{{ incident.microsoft_teams_channel_id }}` to target the incident's channel.
**Common trigger:** Incident Status Changed to "Closed"
Renames an existing Teams channel. Use this to reflect status changes — for example, prefixing resolved incidents with `[RESOLVED]`.
The team that contains the channel.
The channel to rename. Use `{{ incident.microsoft_teams_channel_id }}` to target the incident's channel.
The new channel name. Supports Liquid syntax.
```liquid theme={null}
[RESOLVED] {{ incident.title }}
```
**Common trigger:** Incident Resolved
Invites users to a private incident channel by email. Use this to automatically add on-call responders when they're assigned a role.
The team that contains the channel.
The private channel to invite users to. Supports Liquid syntax.
Comma-separated list of email addresses to invite. Supports Liquid syntax.
This action only works with **private** channels. Public channels are accessible to all team members by default.
**Common triggers:** Incident Created, Incident Commander Assigned
Posts a message to a Teams channel using the Rootly bot. Use Liquid variables to include dynamic incident details in the message.
The channel(s) to post to. Supports Liquid syntax.
The message content. Supports Liquid variables.
```liquid theme={null}
🚨 **Incident Update**
**Title:** {{ incident.title }}
**Severity:** {{ incident.severity }}
**Status:** {{ incident.status }}
**Commander:** {{ incident.commander.name | default: "Unassigned" }}
{{ incident.summary }}
```
If the message text is empty, the action will be skipped.
**Common triggers:** Incident Created, Incident Updated, Status Changed
Sends Adaptive Card attachments to one or more Teams channels. Use this to send richly formatted, interactive content such as structured incident summaries.
The channel(s) to send the attachments to. Supports Liquid syntax.
A JSON payload defining the Adaptive Card content. Supports Liquid syntax. Follows the [Microsoft Adaptive Card schema](https://adaptivecards.io/).
Creates a Microsoft Teams video meeting for live incident collaboration. The meeting link is automatically stored on the incident.
This action requires the **Microsoft Teams Meeting** integration to be installed separately.
The meeting title. Supports Liquid syntax (for example, `{{ incident.title }}`).
**Common trigger:** Incident Created (for high-severity incidents)
***
## Liquid Variables
Use the [Liquid Variable Explorer](https://rootly.com/account/help/liquid-explorer) to test variables with real incident data.
### Incident Variables
| Variable | Description |
| -------------------------------- | ------------------------------------ |
| `{{ incident.title }}` | Incident title |
| `{{ incident.summary }}` | Incident summary |
| `{{ incident.severity }}` | Severity level (for example, "SEV1") |
| `{{ incident.status }}` | Current status |
| `{{ incident.started_at }}` | When the incident started |
| `{{ incident.commander.name }}` | Incident commander name |
| `{{ incident.commander.email }}` | Incident commander email |
| `{{ incident.url }}` | Link to the incident in Rootly |
### Microsoft Teams Variables
| Variable | Description |
| -------------------------------------------- | ------------------------------------- |
| `{{ incident.microsoft_teams_channel_id }}` | ID of the incident's Teams channel |
| `{{ incident.microsoft_teams_channel_url }}` | URL to the Teams channel |
| `{{ incident.microsoft_teams_chat_id }}` | ID of the incident's Teams chat |
| `{{ incident.microsoft_teams_meeting_url }}` | URL to the Teams meeting (if created) |
## Troubleshooting
After completing OAuth, Rootly doesn't appear as a connected app in Teams.
**Solutions:**
* Verify you completed OAuth using the same email as your Teams account
* Make sure Rootly was installed in a specific team, not just your personal app space
* Try uninstalling and reinstalling the Rootly app from the Teams store
* Check if your organization restricts third-party app installations — a Microsoft 365 admin may need to approve Rootly
Teams shows an error when trying to add Rootly to a team.
**Solutions:**
* Ensure you have owner or admin permissions in the team
* Ask a Team Owner or Microsoft 365 admin to approve the Rootly app
* Verify that third-party app installations are enabled in your Microsoft 365 admin center
Teams reports that the signed-in email isn't linked to a Rootly account.
**Solutions:**
* Verify the OAuth email matches exactly the email registered in Rootly
* Confirm this email exists as a user in Rootly
* Add the email under **Rootly → Organization Settings → Members** if needed
* Disconnect and reconnect the Microsoft Teams integration
Workflows run successfully but no Teams channels appear.
**Solutions:**
* Verify the Rootly bot is installed in the specific team referenced in the workflow action
* Check workflow run logs for errors: **Workflows → Your Workflow → ... → View Runs**
* Confirm the team name in the workflow action exactly matches the team in Teams
## Uninstall
To remove the main Microsoft Teams integration from Rootly:
1. Go to **Configuration → Integrations** and find **Microsoft Teams**
2. Click **Connected** to reveal the disconnect option
3. Click **Disconnect**
Disconnecting from Rootly does not remove the Rootly bot from Teams. To fully uninstall, open **Microsoft Teams → Apps → Manage your apps**, find **Rootly**, and click **Uninstall**.
***