| title | alert: moveAlerts |
|---|---|
| description | Move one or more alerts to an incident. |
| author | HarelDamti |
| ms.localizationpriority | medium |
| ms.subservice | security |
| doc_type | apiPageType |
| ms.date | 02/24/2026 |
Namespace: microsoft.graph.security
[!INCLUDE beta-disclaimer]
Move one or more alert resources to an existing incident.
[!INCLUDE national-cloud-support]
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
[!INCLUDE permissions-table]
[!INCLUDE rbac-security-alerts-incidents-apis-write]
POST /security/alerts_v2/moveAlerts| Name | Description |
|---|---|
| Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
| Content-Type | application/json. Required. |
In the request body, provide a JSON object with the following parameters.
| Parameter | Type | Description |
|---|---|---|
| alertIds | String collection | Required. The IDs of the alerts to move. |
| incidentId | String | Optional. The ID of the target incident. A request with null creates a new incident. |
| alertComment | String | Optional. A comment to add when moving the alerts. |
| newCorrelationReasons | microsoft.graph.security.correlationReason | Optional. The correlation reasons to associate with the move operation. This object is a flags enum that allows multiple values to be specified. |
If successful, this action returns a 200 OK response code and a microsoft.graph.security.mergeResponse object in the response body.
The following example moves two alerts to an existing incident.
POST https://graph.microsoft.com/beta/security/alerts_v2/moveAlerts
Content-Type: application/json
{
"alertIds": [
"da637551227677560813_-961444813",
"da637551227677560813_-961444814"
],
"incidentId": "2972395",
"alertComment": "Moving alerts for investigation consolidation",
"newCorrelationReasons": "sameAsset, temporalProximity"
}[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
The following example shows the response.
HTTP/1.1 200 OK
Content-type: application/json
{
"targetIncidentId": "2972395"
}