> 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/integrations/inbound-integrations/azure-alerts/service-health.md).

# Azure Service Health

## In ilert: Create an Azure Alerts alert source <a href="#in-ilert" id="in-ilert"></a>

1. Go to **Alert sources** --> **Alert sources** and click on **Create new alert source**

   <figure><img src="/files/rmL9OoRxcWnDwcJZQm4Y" alt=""><figcaption></figcaption></figure>
2. Search for **Azure Alerts** in the search field, click on the Azure Alerts tile and click on **Next**.

   <figure><img src="/files/1WoRRYB5U40PbeMJ7Hit" alt=""><figcaption></figcaption></figure>
3. Give your alert source a name, optionally assign teams and click **Next**.
4. Select an **escalation policy** by creating a new one or assigning an existing one.

   <figure><img src="/files/y4Bakf2apGhBN56U8ZPR" alt=""><figcaption></figcaption></figure>
5. Select you [Alert grouping](/alerting/configure-alerting/alert-sources.md#alert-grouping) preference and click **Continue setup**. You may click **Do not group alerts** for now and change it later.<br>

   <figure><img src="/files/nTlB0ZCIW1SP3dj6P9nO" alt=""><figcaption></figcaption></figure>
6. The next page show additional settings such as customer alert templates or notification prioritiy. Click on **Finish setup** for now.
7. On the final page, an API key and / or webhook URL will be generated that you will need later in this guide.

   <figure><img src="/files/iFF3BpyuIYMi49K1j7uk" alt=""><figcaption></figcaption></figure>

## In Azure: Create an alert <a href="#in-splunk" id="in-splunk"></a>

1. Go to [**Azure Portal**](https://portal.azure.com) and then to **Service Health.**

![](/files/-MUsBhxh5LijPm-SjZQB)

2. On the next page click on **Add service health alert** button\*\*.\*\*

![](/files/-MUsC3sDeipKTqyxQ7GZ)

3. On the next page change the **Condition** for the alerts and click on the **Add action groups.**

![](/files/-MUsCbbBMJQsbvIoP7Wy)

4. On the modal window click on the **Create action group** button.

![](/files/-MUrytYBsLA9xOyEXXhf)

5. On the next page name the group e.g. **iLert** and click on the **Actions** tab.

![](/files/-MUrzHdFQ71ZG-e1Lytu)

6. **\*\*On the** Actions **tab**, **click on the** Action type **and choose** Webhook.\*\*

![](/files/-MUs-9HcqMGv7V2dBj3L)

7. **On the modal window** in the **URI** section and **\*\*paste the** Webhook URL **that you generated in ilert and click on** OK\*\*. Name the action e.g.\*\* ilert **and click on the** Review + create\*\* button.

![](/files/-MUs-MTqwKn3OxuQdT7f)

8. On the next page click on the **Create** button.

![](/files/-MUs1Lp75Hu3_u5tvC4N)

9. On the next page scroll down to the **Alert rule details** section, name the alert rule and click on the **Create alert rule** button.

![](/files/-MUs1ak-gbcS9hBJUmvc)

10. Finished! Your Azure Service Health alerts will now create alerts in ilert.

## FAQ <a href="#faq" id="faq"></a>

**Will alerts in ilert be resolved automatically?**

Yes, as soon as an alert has been resolved in Azure Alerts, the associated alert in ilert will be resolved automatically.

**Can I connect Azure Alerts with multiple alert sources from ilert?**

Yes, simply create more alert rules in Azure Alerts


---

# 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/integrations/inbound-integrations/azure-alerts/service-health.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.
