> 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/activity-logs.md).

# Azure Activity Logs

Create alerts in ilert based on Azure Activity Logs queries.

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

1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Azure Alerts**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.

   <figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-8a281bf3931f5a1a531951ce97984d50989dd875%2Falert-source-escalation-step.png?alt=media" alt="The escalation step of the ilert alert source wizard, headed Who should be notified about alerts, with an escalation policy selected and a preview of its escalation rules below."><figcaption><p>Pick an existing escalation policy, or generate a basic one without leaving the wizard.</p></figcaption></figure>
5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.

## 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 **Activity log.**

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MUs20k1NsCA1RozKcNe%2F-MUs2dG5YTuORORLCaSr%2FHome_-_Microsoft_Azure.png?alt=media\&token=e3131fb1-5135-4284-a6cf-5acd721463f1)

2. Find and click on the activity log for which you'd like to create an alert.

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MUs20k1NsCA1RozKcNe%2F-MUs3jzKHgJLGceBkTYr%2FActivity_log_-_Microsoft_Azure.png?alt=media\&token=26c931f9-4ce9-4ece-b9e7-546ae2bee1ea)

3. On the modal window click on the **New alert rule** button\*\*.\*\*

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MUs3qQxLS9PdC5G3O0P%2F-MUs4EcYhUKrJhitYzNN%2FDelete_action_group_-_Microsoft_Azure.png?alt=media\&token=e28d02a7-87ef-40cc-aefc-5082cf3c7f93)

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

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MUrt7CW11sZPGpnMQgW%2F-MUrz5DM-OOOEqFWQ5p6%2FCreate_alert_rule_-_Microsoft_Azure.png?alt=media\&token=2ccb24b1-45ca-455a-863c-2def192db2b0)

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

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MUrt7CW11sZPGpnMQgW%2F-MUrytYBsLA9xOyEXXhf%2FSelect_an_action_group_to_attach_to_this_alert_rule_-_Microsoft_Azure.png?alt=media\&token=52b6faa9-2d81-4674-9748-1348137b40d1)

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

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MUrt7CW11sZPGpnMQgW%2F-MUrzHdFQ71ZG-e1Lytu%2FCreate_action_group_-_Microsoft_Azure.png?alt=media\&token=902e5c5e-cd99-4ec5-8e5e-c70b2bafcd50)

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

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MUs-3NneMCV63HhUv4P%2F-MUs-9HcqMGv7V2dBj3L%2FCreate_action_group_-_Microsoft_Azure.png?alt=media\&token=93c53cbe-bb6f-417b-9565-45a724d58042)

8. **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.

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MUs-3NneMCV63HhUv4P%2F-MUs-MTqwKn3OxuQdT7f%2FWebhook_-_Microsoft_Azure.png?alt=media\&token=513a3a5c-5f48-4b04-ab38-09d6d760d03d)

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

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MUs0ngk7rtVR9vECR9c%2F-MUs1Lp75Hu3_u5tvC4N%2FCreate_action_group_-_Microsoft_Azure.png?alt=media\&token=2454f6b0-2daf-4c67-a2fc-730252fd311f)

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

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MUs1NhnzuQ6D-otAXCU%2F-MUs1ak-gbcS9hBJUmvc%2FCreate_alert_rule_-_Microsoft_Azure1.png?alt=media\&token=91e809dc-b347-4db2-9dd8-d64495f1fd07)

11. Finished! Your Azure Activity Logs alerts will now create alerts in ilert.

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

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

No, unfortunately Azure Sentinel alert do not fire resolve events.

**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/activity-logs.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.
