> 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/look-up-who-is-on-call-in-microsoft-teams.md).

# Look up who is on call in Microsoft Teams

Answer "who do I page?" inside Microsoft Teams with @ilert oncall, for an alert source or an escalation policy.

{% 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).
{% endhint %}

`@ilert oncall` answers who is on call, in the channel you type it in. The app posts a **See who is on-call** card; **Continue** opens the dialog.

There are two ways to set it up:

|                | Who can look up                            | What you configure                                            |
| -------------- | ------------------------------------------ | ------------------------------------------------------------- |
| **Restricted** | Teams users who also have an ilert account | Nothing beyond connecting the app                             |
| **Open**       | Anyone in the team                         | A Microsoft Teams alert source with the on-call option ticked |

## Option 1: Restrict to Teams users with an ilert account

Anyone whose ilert username or email address matches their Teams email address can type `@ilert oncall` in a channel of a team the app is installed in.

The dialog offers **Search an alert source** and **Search an escalation policy**, each with its own **Search** button, over what that person may read in ilert. In a channel that belongs to a Teams alert source, the dialog opens with that source's on-call people already listed, and the search boxes underneath.

## Option 2: Let anyone in the team look up who is on call

Useful in a team's own channel: colleagues ask who to page without knowing the name of an escalation policy, and without an ilert account.

{% stepper %}
{% step %}

## Create or open a Microsoft Teams alert source

Follow [Create alerts in Microsoft Teams](/chatops/microsoft-teams/create-alerts-in-microsoft-teams.md#option-2-let-anyone-in-the-team-raise-an-alert) to create one, or open the **Microsoft Teams settings** tab of an existing Teams alert source. One alert source covers both commands.
{% endstep %}

{% step %}

## Choose the team, the channels, and the escalation policies

Under **Team** and **Channels**, add the channels where the lookup should work. Under **Escalation policies**, choose the policies it should report on, at most 10. With none chosen, the alert source's own escalation policy is used.
{% endstep %}

{% step %}

## Turn the lookup on

Under **@ilert oncall command configuration**, tick **Let Microsoft Teams users without an ilert account see who is on-call using the @ilert oncall command**.

This also ticks **Include the primary phone number of the user who is on-call in on-call posts**. Untick it if the phone numbers of your on-call people should not be shown to everyone in the channel.
{% endstep %}

{% step %}

## Save

Click **Continue setup** on a new alert source, or **Save** on one that is already set up.
{% endstep %}
{% endstepper %}

Anyone in those channels can now run `@ilert oncall` and get the list, without a search.

## What the answer shows

* One block per escalation policy, with the people on call.
* **Only the first escalation level** of each policy. Later levels, and the delays between them, are not shown — the answer is "who gets paged first", not the whole policy.
* A user rule shows that user as always on call; a schedule shows the current shift and when it ends; a team rule lists its members.
* Phone numbers, where you allowed them.
* A footer names the time zone the times are given in.

## FAQ

### Someone gets "You don't have permission to view current on-call."

They have no ilert account, and the channel's Teams alert source does not allow the open lookup. Tick **Let Microsoft Teams users without an ilert account see who is on-call using the @ilert oncall command** in that alert source's **Microsoft Teams settings**.

### The dialog says the channel is not configured

That is the answer for someone **with** an ilert account in a channel that belongs to no Teams alert source. They can still search any alert source or escalation policy they may read. Add the channel to a Teams alert source to get the list without searching.

### "Your Microsoft Teams bot has no permission. Please reauthorize the bot."

The connection needs renewing, or the person searched for something they may not read in ilert. Open **Settings** → **Connectors** and use **Update** on the **Microsoft Teams** card if it is offered, or **⋯** → **Re-connect**.

### Can I hide phone numbers?

Yes. Untick **Include the primary phone number of the user who is on-call in on-call posts**. People who do have an ilert account still see the numbers.


---

# 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/look-up-who-is-on-call-in-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.