riskyUser: dismiss
Namespace: microsoft.graph
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.
Note: Using the riskyUsers API requires a Microsoft Entra ID P2 license.
Dismiss the risk of one or more riskyUser objects. This action sets the targeted user's risk level to none. The maximum count of users to dismiss in one call is 60.
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) | IdentityRiskyUser.ReadWrite.All | Not available. |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | IdentityRiskyUser.ReadWrite.All | Not available. |
For delegated scenarios, the signed-in user must be assigned at least the Security Administrator Microsoft Entra role.
HTTP request
POST /riskyUsers/dismiss
Request headers
Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Request body
Specify the userIds to dismiss in the request body.
Response
If successful, this method returns a 204 No Content
response code. It doesn't return anything in the response body.
Examples
Request
The following example shows a request.
POST https://graph.microsoft.com/beta/riskyUsers/dismiss
Content-Type: application/json
{
"userIds": [
"04487ee0-f4f6-4e7f-8999-facc5a30e232",
"13387ee0-f4f6-4e7f-8999-facc5120e345"
]
}
Response
The following example shows the response.
HTTP/1.1 204 No Content
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for