Relate alerts to incidents in Microsoft Sentinel


Azure Sentinel is now called Microsoft Sentinel, and we’ll be updating these pages in the coming weeks. Learn more about recent Microsoft security enhancements.

This article shows you how to relate alerts to your incidents in Microsoft Sentinel. This feature allows you to manually or automatically add alerts to, or remove them from, existing incidents as part of your investigation processes, refining the incident scope as the investigation unfolds.


Incident expansion is currently in PREVIEW. The Azure Preview Supplemental Terms include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.

Expand the scope and power of your incidents

One thing that this feature allows you to do is to include alerts from one data source in incidents generated by another data source. For example, you can add alerts from Microsoft Defender for Cloud, or from various third-party data sources, to incidents imported into Microsoft Sentinel from Microsoft 365 Defender.

This feature is built into the latest version of the Microsoft Sentinel API, which means that it's available to the Logic Apps connector for Microsoft Sentinel. So you can use playbooks to automatically add an alert to an incident if certain conditions are met.

You can also use this automation to create custom correlations, or to define custom criteria for grouping alerts into incidents when they're created.

Add alerts using the investigation graph

The investigation graph is a visual, intuitive tool that presents connections and patterns and enables your analysts to ask the right questions and follow leads. You can use it to add alerts to and remove them from your incidents, broadening or narrowing the scope of your investigation.

  1. From the Microsoft Sentinel navigation menu, select Incidents.

    Screenshot of incidents queue displayed in a grid.

  2. Select an incident to investigate. In the incident details panel, select the Actions button and choose Investigate from the pop-up menu. This will open the investigation graph.

    Screenshot of incidents with alerts in investigation graph.

  3. Hover over any entity to reveal the list of exploration queries to its side. Select Related alerts.

    Screenshot of alert exploration queries in investigation graph.

    The related alerts will appear connected to the entity by dotted lines.

    Screenshot of related alerts appearing in investigation graph.

  4. Hover over one of the related alerts until a menu pops out to its side. Select Add alert to incident (Preview).

    Screenshot of adding an alert to an incident in the investigation graph.

  5. The alert is added to the incident, and for all purposes is part of the incident, along with all its entities and details. You'll see two visual representations of this:

    • The line connecting it to the entity in the investigation graph has changed from dotted to solid, and connections to entities in the added alert have been added to the graph.

      Screenshot showing an alert added to an incident.

    • The alert now appears in this incident's timeline, together with the alerts that were already there.

      Screenshot showing an alert added to an incident's timeline.

Special situations

When adding an alert to an incident, depending on the circumstances, you might be asked to confirm your request or to choose between different options. The following are some examples of these situations, the choices you will be asked to make, and their implications.

  • The alert you want to add already belongs to another incident.

    In this case you'll see a message that the alert is part of another incident or incidents, and asked if you want to proceed. Select OK to add the alert or Cancel to leave things as they were.

    Adding the alert to this incident will not remove it from any other incidents. Alerts can be related to more than one incident. If you want, you can remove the alert manually from the other incident(s) by following the link(s) in the message prompt above.

  • The alert you want to add belongs to another incident, and it's the only alert in the other incident.

    This is different from the case above, since if the alert is alone in the other incident, tracking it in this incident could make the other incident irrelevant. So in this case, you'll see this dialog:

    Screenshot asking whether to keep or close other incident.

    • Keep other incident preserves the other incident as is, while also adding the alert to this one.

    • Close other incident adds the alert to this incident and closes the other incident, adding the closing reason "Undetermined" and the comment "Alert was added to another incident" with the open incident's number.

    • Cancel leaves the status quo. It makes no changes to either the open incident or any other referenced incident.

    Which of these options you choose depends on your particular needs; we don't recommend one choice over the other.


  • Microsoft Sentinel imports both alerts and incidents from Microsoft 365 Defender. For the most part, you can treat these alerts and incidents like regular Microsoft Sentinel alerts and incidents.

    However, you can only add Defender alerts to Defender incidents (or remove them) in the Defender portal, not in the Sentinel portal. If you try doing this in Microsoft Sentinel, you will get an error message. You can pivot to the incident in the Microsoft 365 Defender portal using the link in the Microsoft Sentinel incident. Don't worry, though - any changes you make to the incident in the Microsoft 365 Defender portal are synchronized with the parallel incident in Microsoft Sentinel, so you'll still see the added alerts in the incident in the Sentinel portal.

    You can add Microsoft 365 Defender alerts to non-Defender incidents, and non-Defender alerts to Defender incidents, in the Microsoft Sentinel portal.

  • An incident can contain a maximum of 150 alerts. If you try to add an alert to an incident with 150 alerts in it, you will get an error message.

Add/remove alerts using playbooks

Adding and removing alerts to incidents are also available as Logic Apps actions in the Microsoft Sentinel connector, and therefore in Microsoft Sentinel playbooks. You need to supply the incident ARM ID and the system alert ID as parameters, and you can find them both in the playbook schema for both the alert and incident triggers.

Microsoft Sentinel supplies a sample playbook template in the templates gallery, that shows you how to work with this capability:

Screenshot of playbook template for relating alerts to incidents.

Here's how the Add alert to incident (Preview) action is used in this playbook, as an example for how you can use it elsewhere:

Screenshot of adding an alert to an incident using a playbook action.

Add/remove alerts using the API

You're not limited to the portal to use this feature. It's also accessible through the Microsoft Sentinel API, through the Incident relations operation group. It allows you to get, create, update, and delete relationships between alerts and incidents.

Create a relationship

You add an alert to an incident by creating a relationship between them. Use the following endpoint to add an alert to an existing incident. After this request is made, the alert joins the incident and will be visible in the list of alerts in the incident in the portal.


The request body looks like this:

    "properties": { 
        "relatedResourceId": "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/{workspaceName}/providers/Microsoft.SecurityInsights/entities/{systemAlertId}" 

Delete a relationship

You remove an alert from an incident by deleting the relationship between them. Use the following endpoint to remove an alert from an existing incident. After this request is made, the alert will no longer be connected to or appear in the incident.


List alert relationships

You can also list all the alerts that are related to a particular incident, with this endpoint and request:


Specific error codes

The general API documentation lists expected response codes for the Create, Delete, and List operations mentioned above. Error codes are only mentioned there as a general category. Here are the possible specific error codes and messages listed there under the category of "Other Status Codes":

Code Message
400 Bad Request Failed to create relation. Different relation type with name {relationName} already exists in incident {incidentIdentifier}.
400 Bad Request Failed to create relation. Alert {systemAlertId} already exists in incident {incidentIdentifier}.
400 Bad Request Failed to create relation. Related resource and incident should belong to the same workspace.
400 Bad Request Failed to create relation. Microsoft 365 Defender alerts cannot be added to Microsoft 365 Defender incidents.
400 Bad Request Failed to delete relation. Microsoft 365 Defender alerts cannot be removed from Microsoft 365 Defender incidents.
404 Not found Resource '{systemAlertId}' does not exist.
404 Not found Incident doesn’t exist.
409 Conflict Failed to create relation. Relation with name {relationName} already exists in incident {incidentIdentifier} to different alert {systemAlertId}.

Next steps

In this article, you learned how to add alerts to incidents and remove them using the Microsoft Sentinel portal and API. For more information, see: