> 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/chat.md).
# Post alerts to a Teams channel
Publish ilert alerts into a Microsoft Teams channel and accept, reroute, and resolve them there, without opening ilert.
{% hint style="info" %}
**Install and connect the ilert app first**
An **Admin** or **Account owner** connects the app once, as described in the [Microsoft Teams integration guide](/chatops/microsoft-teams.md). Creating the alert action below needs no admin role.
{% endhint %}
Alerts reach Microsoft Teams through an **alert action**: a rule that publishes the alerts of one or more alert sources to one channel. Create one alert action per channel.
## Create a Microsoft Teams alert action
{% stepper %}
{% step %}
## Start a new alert action
In the sidebar, go to **Alerting** → **Alert actions** and click **Create new alert action**.
You can also start from the alert source: open it, go to its **Alert actions** tab, and click **Create new alert action** there. The source is filled in for you.
{% endstep %}
{% step %}
## Choose Teams
Select the **Teams** tile and leave **Use webhook** unticked — [the webhook variant](/chatops/microsoft-teams/incoming-webhook.md) posts messages without the buttons. Click **Next**.
{% endstep %}
{% step %}
## Choose the alert sources and the events to publish
Select the alert sources whose alerts should reach the channel, and leave **Trigger mode** on **Automatic**.
Under **Trigger events**, only **Alert created** is ticked. Add at least **Alert accepted** and **Alert resolved** — see [which events to pick](#choose-which-events-reach-teams). Click **Next**.
{% endstep %}
{% step %}
## Skip the conditions
**Conditional execution** narrows an alert action to alerts that meet conditions you set. Click **Next** to publish every alert of the chosen sources.
{% endstep %}
{% step %}
## Name it and choose the channel
Give the alert action a name. **Teams action** is already set to **Chat**; pick the **Team** and the **Channel**, then click **Save**.
Only channels of the chosen team appear in the list.
{% endstep %}
{% step %}
## Save again, then test
**Save** opens the alert action's edit page; click **Save** there to reach its detail page. Click **Test** in the top right, and a test alert appears in the channel.
The app also posts "Channel is now connected to an alert source!" into the channel when the alert action is created.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
For a live call on a major incident, attach an incident [conference bridge](/incidents-and-status-pages/incidents/conference-bridges.md). A call belongs to an incident, not to a single alert.
{% endhint %}
## What the message looks like
The card carries a status dot and the alert's summary as a link into ilert, the alert details, and the fields you need while triaging: **Escalation policy**, **Priority**, **Labels**, **Responders**, **Links**, **Affected services**, and the images attached to the alert. Long details are collapsed behind **Show more**, and long lists behind **Show 2 more responders** and the like.
The card is written in German when your Microsoft tenant's language is German, and in English otherwise. Responders are listed by name; the card mentions nobody, so it does not notify people outside the channel.
### The buttons
| Button | What it does |
| ---------------------------- | ---------------------------------------------------------------------- |
| **Accept** | Takes ownership of the alert, which stops the escalation |
| **Reroute** | Assigns the alert to a different escalation policy, chosen in a dialog |
| **Resolve** | Closes the alert |
| **Escalate** | Moves the alert to a chosen level of its escalation policy |
| **Add responder** | Adds a user, or the person currently on call in a schedule |
| **Merge into another alert** | Merges this alert into another open alert |
| **Add comment** | Writes a comment on the alert |
| **Raise priority** | Raises a low-priority alert to high |
| *alert action name* | Runs a manual alert action of that alert source |
Resolved alerts keep only **Merge into another alert** and **Add comment**. An alert that was merged into another shows a link to the main alert instead.
**Accept** and **Resolve** work for everyone in the channel, including people without an ilert account; the thread then reads "*Alert accepted by* **Name**". Every other button needs an ilert user whose email address matches the Teams account, and tells anyone else: "User *name* doesn't exist in ilert. Please contact your ilert/Teams administrator."
## Choose which events reach Teams
The **Trigger events** you tick decide when the card is **updated in place**, and which short notes are posted as replies in its thread — "*Name* accepted the alert", "Alert assigned to *Name*", "Alert priority raised", "Alert reached end of escalation policy and is still pending", and so on. An event you leave unticked leaves the card alone — including when the change was made from Teams itself.
{% hint style="warning" %}
With only **Alert created** ticked, the card is not updated as the alert moves on. Somebody presses **Accept** in Teams, the alert is accepted in ilert, and the card still reads `[PENDING]`. Tick at least **Alert accepted** and **Alert resolved**.
{% endhint %}
**Alert comment added** behaves differently from the rest: a comment is posted as a new reply in the thread rather than folded into the card.
Some things reach Teams whatever you tick. Three event types skip the filter entirely: the alert is merged into another alert, another alert is merged into it, and a log is attached to it. Pressing **Accept** or **Resolve** in the channel also posts a short reply in the thread naming who pressed it, whether or not the matching event is ticked — but the card itself is only updated if that event is ticked.
To change the events later, open the alert action and click **Edit**.
## Comments from Teams
Replying in the card's thread writes the reply to the alert as a comment, where it appears under the alert's **Comments** tab. Click **Reply in thread** on the alert message and post your reply.
Inside channels with Threads layout
Inside channels with Posts layout
For that to work, the person replying needs an ilert user whose username or email address matches their Teams email address. Replies from anyone else are dropped without a message. Images in a reply are kept as links, and the text of that reply is dropped.
The reply appears under the alert's Comments tab.
Comments written in ilert reach the thread only if **Alert comment added** is one of the alert action's trigger events.
## FAQ
### Can I publish alerts from several alert sources to one channel?
Yes. One alert action can carry up to 49 alert sources. Each alert action keeps its own card for an alert, so two alert actions posting to two channels means two cards.
### The channel I want is not in the list
The **Team** list shows every group in your directory, 150 at a time, and searches by the **beginning** of the name — type the first word. Pick the team first; the channel list is loaded for that team.
If a channel is missing, it is a private channel the app has not been added to. Add the ilert app in that channel, or pick a standard channel.
### How do I uninstall the ilert app from Microsoft Teams?
In Teams, open the team, click **More options** → **Manage team** → **Apps**, find **ilert**, and click **Uninstall**. That leaves the ilert-side connection in place; use **Disconnect** on the ilert Connectors page as well, remembering that it [deletes the Teams alert actions](/chatops/microsoft-teams.md#keep-the-connection-working).
### Nothing arrives in the channel. Where do I look?
Open the alert action and read **Alert action logs** at the bottom of its detail page: recent deliveries are listed with their status, and failures carry Microsoft's error message. A failure is also written to the alert's timeline.
---
# 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/chat.md?ask=&goal=
```
`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.
