Microsoft Defender for Endpoint
Endpoint protection

Post Ti Indicator

In brief

The API reference now documents `rbacGroupNames` as `String[]` and `generateAlert` as `Boolean`. The 400 Bad Request description was also clarified.

What Defender admins need to know

Administrators integrating with this API should verify request schema validation, particularly for RBAC group names and alert-generation settings.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

|expirationTime|DateTimeOffset|The expiration time of the indicator. Optional| |severity|Enum|The severity of the indicator. Possible values are: Informational, Low, Medium, and High. Optional| |recommendedActions|String|TI indicator alert recommended actions. Optional| |rbacGroupNames|String|String[]|Comma-separated list of RBAC group names the indicator would be applied to. Optional| |educateUrl|String|Custom notification/support URL. Supported for Block and Warn action types for URL indicators. Optional| |generateAlert|Enum|Boolean|True if alert generation is required, False if this indicator shouldn't generate an alert.|

Response

  • If successful, this method returns 200 - OK response code and the created / updated Indicator entity in the response body.
  • If not successful:successful, this method returnreturns 400 - Bad Request. Bad requestRequest usually indicates an incorrect request body.

Example