Edit

Update case management case

Namespace: microsoft.graph.security.caseManagement

Important

APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.

Update the properties of a microsoft.graph.security.caseManagement.case object.

This API is available in the following national cloud deployments.

Global service US Government L4 US Government L5 (DOD) China operated by 21Vianet

Permissions

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.

Permission type Least privileged permissions Higher privileged permissions
Delegated (work or school account) CaseManagement.ReadWrite.All Not available.
Delegated (personal Microsoft account) Not supported. Not supported.
Application CaseManagement.ReadWrite.All Not available.

Important

For delegated access using work or school accounts, the signed-in user must be assigned a supported Microsoft Entra role or a custom role that grants the permissions required for this operation. This API supports the following built-in roles:

  • Global Reader
  • Security Reader
  • Security Operator
  • Security Administrator

HTTP request

PATCH /security/caseManagement/cases/{caseId}

Request headers

Name Description
Authorization Bearer {token}. Required. Learn more about authentication and authorization.
Content-Type application/json. Required.

Request body

In the request body, supply only the values for properties to update. Existing properties that aren't included in the request body maintain their previous values or are recalculated based on changes to other property values.

The following table specifies the properties that can be updated.

Supply a JSON representation of the resource. For polymorphic resources, include @odata.type to identify the concrete case type. The properties that can be updated depend on the case type.

To update customFields, call List customFields at /security/caseManagement/caseTypeConfigurations/{caseTypeConfigurationId}/customFields, where {caseTypeConfigurationId} matches the case type. Use each definition's displayName, not its id, as the dynamic property name. The name must match exactly one definition. Each dynamic value must be an object that includes the mapped concrete @odata.type and the corresponding value, values, or valueDateTime property from the custom field value mapping; bare values aren't supported.

For genericCase objects, all properties can be updated except id, createdBy, createdDateTime, lastModifiedBy, and lastModifiedDateTime, which are inherited from caseManagementEntity. The API ignores these properties if you include them in the request body.

The following properties can be updated for all case types.

Property Type Description
displayName String The display name of the case.
status String The tenant-defined lifecycle status of the case. Use a displayName value returned in the status tree by List statuses from /security/caseManagement/caseTypeConfigurations/genericCase/statuses or /security/caseManagement/caseTypeConfigurations/incidentCase/statuses, depending on the case type.

For genericCase objects, you can also update the following properties.

Property Type Description
assignedTo String The user assigned to the generic case.
closingNotes String Notes recorded when the generic case is closed.
customFields microsoft.graph.security.caseManagement.customFieldValues Tenant-defined custom field values keyed by the exact displayName of each custom field definition.
description String The description of the generic case.
dueDateTime DateTimeOffset The target completion date and time for the generic case.
priority String The priority assigned to the generic case. Possible values are: veryLow, low, medium, high, and critical.

For incidentCase objects, the following properties are synchronized with the underlying incident. A PATCH request that includes any of these properties returns 202 Accepted with no response body. The changes might take a few minutes to synchronize and appear on the case.

Property Type Description
assignedTo String The user assigned to the incident case.
classification microsoft.graph.security.caseManagement.incidentClassification The classification assigned to the incident.
determination microsoft.graph.security.caseManagement.incidentDetermination The determination assigned to the incident.
displayName String The display name of the incident case.
severity microsoft.graph.security.caseManagement.incidentSeverity The severity assigned to the incident.
status String The tenant-defined lifecycle status of the incident case. Use a displayName value returned in the status tree by List statuses from /security/caseManagement/caseTypeConfigurations/incidentCase/statuses.

The following incident case properties aren't synchronized with the underlying incident. A PATCH request that updates only these properties returns 200 OK with the updated incidentCase object in the response body.

Property Type Description
customFields microsoft.graph.security.caseManagement.customFieldValues Tenant-defined custom field values keyed by the exact displayName of each custom field definition.
dueDateTime DateTimeOffset The target completion date and time for the incident case.

If a PATCH request includes properties from both groups, the method returns 202 Accepted with no response body.

Response

If successful, this method returns one of the following response codes:

Examples

Example 1: Update a generic case

Request

The following example shows a request.

PATCH https://graph.microsoft.com/beta/security/caseManagement/cases/{caseId}
Content-Type: application/json

{
  "@odata.type": "#microsoft.graph.security.caseManagement.genericCase",
  "displayName": "Case MS-001",
  "status": "Open",
  "description": "Investigating potential credential compromise.",
  "assignedTo": "john.doe@contoso.com",
  "priority": "high",
  "dueDateTime": "2026-06-29T17:54:43Z",
  "closingNotes": "Follow up with the account owner.",
  "customFields": {
    "Customer impact": {
      "@odata.type": "#microsoft.graph.security.caseManagement.customFieldStringValue",
      "value": "Multiple executive mailboxes affected"
    }
  }
}

Response

The following example shows the response.

HTTP/1.1 200 OK
Content-Type: application/json

{
  "@odata.type": "#microsoft.graph.security.caseManagement.genericCase",
  "id": "987757fb-6ef4-1061-17e7-9de0d088e1dd",
  "createdDateTime": "2026-05-20T11:12:28Z",
  "createdBy": "user@contoso.com",
  "lastModifiedDateTime": "2026-05-20T11:18:45Z",
  "lastModifiedBy": "user@contoso.com",
  "displayName": "Case MS-001",
  "status": "Open",
  "description": "Investigating potential credential compromise.",
  "assignedTo": "john.doe@contoso.com",
  "priority": "high",
  "dueDateTime": "2026-06-29T17:54:43Z",
  "closingNotes": "Follow up with the account owner.",
  "customFields": {
    "Customer impact": {
      "@odata.type": "#microsoft.graph.security.caseManagement.customFieldStringValue",
      "value": "Multiple executive mailboxes affected"
    }
  }
}

Example 2: Update synchronized incident case properties

Request

The following example updates properties that are synchronized with the underlying incident.

PATCH https://graph.microsoft.com/beta/security/caseManagement/cases/{caseId}
Content-Type: application/json

{
  "@odata.type": "#microsoft.graph.security.caseManagement.incidentCase",
  "displayName": "Incident Case MS-002",
  "status": "InProgress",
  "classification": "truePositive",
  "determination": "phishing",
  "severity": "high"
}

Response

The following example shows the response.

HTTP/1.1 202 Accepted