> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/chatops/microsoft-teams.md).

# Microsoft Teams

Install the certified ilert app in Microsoft Teams and connect it to your ilert account, then receive alerts, raise them, and look up who is on call.

The ilert app for Microsoft Teams brings alerts into your channels, lets responders act on them there, and lets anyone in a channel raise an alert or check who is on call.

Installing and connecting the app is a one-time step. It needs an **Admin** or **Account owner** in ilert, and an administrator in Microsoft Teams who can approve the app for your tenant.

## Install and connect the app

{% stepper %}
{% step %}

## Add the app to a team

Open the ilert app in Microsoft Teams: [teams.microsoft.com/l/app/8f3b287d-df09-44e2-93b3-35e0dfa90756](https://teams.microsoft.com/l/app/8f3b287d-df09-44e2-93b3-35e0dfa90756). Add it to a team and pick the channel it should post in.
{% endstep %}

{% step %}

## Open the welcome message

The app posts a welcome message in that channel, ending in a **Connect** button. If you cannot find it, type `@ilert connect` in a channel of that team to bring it back.
{% endstep %}

{% step %}

## Sign in to ilert

Click **Connect**. ilert asks you to sign in if you are not signed in already. The account you use must be an **Admin** or **Account owner**; anyone else is turned away with "To connect Microsoft Teams to this account you need 'ADMIN' or 'ACCOUNT\_OWNER' privileges."
{% endstep %}

{% step %}

## Grant the app access in Microsoft

Microsoft asks for tenant-wide admin consent and lists what the app may do. Approve it. This is the step that needs a Microsoft administrator — an ilert admin without that role cannot finish here.
{% endstep %}

{% step %}

## Check the Connectors page

You end up back in ilert. In the sidebar, go to **Settings** → **Connectors**: under **ChatOps**, the **Microsoft Teams** card reads **Connected**.

ilert posts no confirmation into Teams, and shows no success message of its own — the card is the confirmation.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Start in Teams, not in ilert.** The **Connect** button on the ilert Connectors page only opens the app's page in the Teams store, because ilert does not yet know your Microsoft tenant. Once you are connected, **⋯** → **Re-connect** on that card does work, and repeats the Microsoft consent.
{% endhint %}

## What the app does with its permissions

Microsoft lists the permissions at the moment you consent. What ilert uses them for:

| The app                                    | Used for                                                                                                                                                              |
| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Reads your groups and teams                | The **Team** list when you create an alert action or set up a Teams alert source                                                                                      |
| Reads a team's channels                    | The **Channel** lists, and channel names in links                                                                                                                     |
| Reads users in your directory              | Matching a Teams user to an ilert user by email address                                                                                                               |
| Posts and updates messages                 | Alert cards, thread replies, and command answers                                                                                                                      |
| Creates channels and manages their members | [Incident channels](/incidents-and-status-pages/incidents/incident-channels.md), including inviting the responders                                                    |
| Creates a calendar event                   | The Microsoft Teams meeting behind an incident [conference bridge](/incidents-and-status-pages/incidents/conference-bridges.md), on the calendar of whoever starts it |
| Reads your organization's settings         | Choosing the language of the alert card: German when your tenant's language is German                                                                                 |

## Certification <a href="#certification-overview" id="certification-overview"></a>

The ilert app is certified by Microsoft, which reviews apps for security, privacy, and compliance. See Microsoft's [Microsoft 365 App Compliance Program](https://learn.microsoft.com/en-us/microsoft-365-app-certification/overview) for what that covers.

## Keep the connection working

<details>

<summary>Re-connect</summary>

On the **Microsoft Teams** card, open **⋯** and choose **Re-connect**. Use this when the app stops responding, or after your Microsoft administrator has changed what the app may do.

When a new ilert feature needs permissions your tenant has not granted, the card replaces **Connected** with an **Update** button. It does the same thing.

</details>

{% hint style="danger" %}
**Disconnecting deletes your Teams alert actions.**

**⋯** → **Disconnect** on the Connectors page, and `@ilert disconnect` in a channel, both remove the connection **and every Microsoft Teams alert action that uses it**. Alert actions built on a [Teams webhook](/chatops/microsoft-teams/incoming-webhook.md) survive, because they do not use the connection. The Connectors page does not ask for confirmation. Alert sources keep working; they simply stop publishing to Teams.

`@ilert disconnect` asks first, and only an ilert Admin or Account owner can confirm it.
{% endhint %}

## Commands in a channel

Type these in a channel of a team the app is installed in. The message has to **start** with the mention.

| Command             |                                                                                               |
| ------------------- | --------------------------------------------------------------------------------------------- |
| `@ilert help`       | Lists the commands                                                                            |
| `@ilert connect`    | Brings back the welcome message with the **Connect** button                                   |
| `@ilert alert`      | [Raises an alert](/chatops/microsoft-teams/create-alerts-in-microsoft-teams.md)               |
| `@ilert oncall`     | [Shows who is on call](/chatops/microsoft-teams/look-up-who-is-on-call-in-microsoft-teams.md) |
| `@ilert disconnect` | Disconnects the account, after a confirmation                                                 |

Commands do not work in a personal chat with the app, which answers "Bot commands are not supported in personal chat. Please use a channel or group chat to configure and interact with the ilert bot."

## Select your use case

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Post alerts to a Teams channel</strong></td><td>Publish alerts to a channel and accept, reroute, and resolve them there.</td><td><a href="/chatops/microsoft-teams/chat.md">Post alerts to a Teams channel</a></td></tr><tr><td><strong>Create alerts in Microsoft Teams</strong></td><td>Let people raise an alert with <code>@ilert alert</code>, with or without an ilert account.</td><td><a href="/chatops/microsoft-teams/create-alerts-in-microsoft-teams.md">Create alerts in Microsoft Teams</a></td></tr><tr><td><strong>Look up who is on call</strong></td><td>Answer "who do I page?" in the channel with <code>@ilert oncall</code>.</td><td><a href="/chatops/microsoft-teams/look-up-who-is-on-call-in-microsoft-teams.md">Look up who is on call in Microsoft Teams</a></td></tr><tr><td><strong>Start a conference bridge</strong></td><td>Create a Teams meeting for an incident, so responders can join a live call.</td><td><a href="/incidents-and-status-pages/incidents/conference-bridges.md">Conference bridges</a></td></tr></tbody></table>

## FAQ

**Can I connect more than one Microsoft tenant?**

No. ilert works with one Microsoft Teams connection per account, and uses it for every team and channel.

**Can two ilert accounts use the same Microsoft tenant?**

Don't. Nothing stops the second connection, but the bot's commands then answer whichever ilert account is found first, which is not predictable.

**The app does not see all of my teams**

The **Team** list shows 150 entries at a time and searches by the **beginning** of the name. Type the first word of the team's name. If a team is missing entirely, ask your Microsoft administrator whether the app is approved for it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ilert.com/chatops/microsoft-teams.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.