emailThreatSubmission: review
Namespace: microsoft.graph.security
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.
Review a threat submission. Only emailThreatSubmission objects submitted by end users support the review action.
Review actions for urlThreatSubmission and fileThreatSubmission objects are not supported for end user.
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) | ThreatSubmission.ReadWrite.All | Not available. |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | ThreatSubmission.ReadWrite.All | Not available. |
HTTP request
POST /security/threatSubmission/emailThreats/{emailThreatsId}/review
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 a JSON representation of the parameters.
The following table shows the parameters that can be used with this action.
Parameter | Type | Description |
---|---|---|
category | String | The email is being reported as notSpam, junk, phishing, malware. Case insensitive. |
Response
If successful, this action returns a 204 No Content
response code.
Examples
Request
The following example shows a request.
POST https://graph.microsoft.com/beta/security/threatSubmission/emailThreats/49c5ef5b-1f65-444a-e6b9-08d772ea2059/review
Content-type: application/json
{
"category": "phishing"
}
Response
The following example shows the response.
HTTP/1.1 204 No Content