> 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 Integration

Install the certified ilert bot in Microsoft Teams to receive and act on alerts, raise them, and look up who is on-call.

Install the ilert bot in your Microsoft Teams tenant, then configure each capability you need. The bot is certified by Microsoft; the scopes it requests are listed under [Scope definitions](#scope-definitions).

## 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>Receive and respond to alerts in Microsoft Teams</strong></td><td>Post alerts into a channel and act on them there, via the chat app or an incoming webhook.</td><td><a href="/chatops/microsoft-teams/chat.md">Microsoft Teams Chat Integration</a></td></tr><tr><td><strong>Create alerts in Microsoft Teams</strong></td><td>Use Microsoft Teams as an alert source and let Teams users raise alerts.</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>Check who is on-call for an alert source or escalation policy from any channel.</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>Use the Teams connector to create a 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>

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

Our bot has undergone a rigorous certification process by Microsoft, ensuring it meets the high standards for security, privacy, and compliance set forth by Microsoft. This attestation confirms that our app adheres to best practices in software development and data handling.

For a deeper understanding of what certification means and why it matters, please refer to the [Microsoft Certification Documentation](https://learn.microsoft.com/en-us/microsoft-365-app-certification/overview) for third-party apps and services.

## Scope definitions <a href="#scope-definitions" id="scope-definitions"></a>

Below is a list and description of each scope used by our bot:

### 1. `Calendars.ReadWrite` <a href="#id-1-calendarsreadwrite" id="id-1-calendarsreadwrite"></a>

* **Description:** Allows the bot to create, read, update, and delete events in user calendars.
* **Use Case:** Lets ilert create the Microsoft Teams meeting behind an incident [conference bridge](/incidents-and-status-pages/incidents/conference-bridges.md). The meeting is created on the calendar of the person who starts the bridge.

### 2. `Channel.Create` <a href="#id-2-channelcreate" id="id-2-channelcreate"></a>

* **Description:** Enables the bot to create new channels.
* **Use Case:** Create an [incident channel](/incidents-and-status-pages/incidents/incident-channels.md) when an incident is declared, or from the incident view.

### 3. `Channel.ReadBasic.All` <a href="#id-3-channelreadbasicall" id="id-3-channelreadbasicall"></a>

* **Description:** Grants the ability to read basic properties of channels, including names and descriptions.
* **Use Case:** This scope is commonly used to allow the bot to provide a summary of available channels or guide users to the right channel.

### 4. `ChannelMember.Read.All` <a href="#id-4-channelmemberreadall" id="id-4-channelmemberreadall"></a>

* **Description:** Allows reading the list of members in each channel.
* **Use Case:** Necessary for bot that actions based on channel membership e.g. alert acknowledgment.

### 5. `ChannelMember.ReadWrite.All` <a href="#id-5-channelmemberreadwriteall" id="id-5-channelmemberreadwriteall"></a>

* **Description:** Allows the bot to add or remove members from channels.
* **Use Case:** Necessary for the bot to add the responders working an incident to its incident channel.

### 6. `Chat.Create` <a href="#id-6-chatcreate" id="id-6-chatcreate"></a>

* **Description:** Permits the bot to create one-on-one or group chats.
* **Use Case:** Enable bots to initiate conversations based on alert actions.

### 7. `Directory.Read.All` <a href="#id-7-directoryreadall" id="id-7-directoryreadall"></a>

* **Description:** Allows reading data in your organization's directory, such as users, groups, and apps.
* **Use Case:** Required for the bot to get basic information about a user who is active in ilert and Microsoft Teams, and then combine those activities together.

### 8. `Group.ReadWrite.All` <a href="#id-8-groupreadwriteall" id="id-8-groupreadwriteall"></a>

* **Description:** Enables the bot to read and modify groups, including creating new groups or updating group settings.
* **Use Case:** Enables the bot to show information about groups in ilert management UI

### 9. `Team.ReadBasic.All` <a href="#id-10-teamreadbasicall" id="id-10-teamreadbasicall"></a>

* **Description:** Provides access to read basic properties of teams, such as team name and description.
* **Use Case:** Enables the bot to show information about teams in ilert management UI

### 10. `User.Read.All` <a href="#id-11-userreadall" id="id-11-userreadall"></a>

* **Description:** Allows reading basic profiles of all users in your organization.
* **Use Case:** Required for the bot to get basic information about a user who is active in ilert and Microsoft Teams, and then combine those activities together.

The use of these scopes ensures that our bot can interact effectively with Microsoft Teams and its users, providing functionalities that enhance productivity and collaboration within the platform. The scopes are managed carefully to balance functionality with security and privacy concerns.


---

# 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.
