Skip to content

Commit ccc9b29

Browse files
committed
Acrolinx fixes
1 parent 0603ab9 commit ccc9b29

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

api-reference/beta/api/user-invalidateallrefreshtokens.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ Namespace: microsoft.graph
1414

1515
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
1616

17-
Invalidates all of the user's refresh tokens issued to applications (as well as session cookies in a user's browser), by resetting the **refreshTokensValidFromDateTime** user property to the current date-time. Typically, this operation is performed (by the user or an administrator) if the user has a lost or stolen device. This operation would prevent access to any of the organization's data accessed through applications on the device without the user first being required to sign in again. In fact, this operation would force the user to sign in again for all applications that they have previously consented to, independent of device.
17+
Invalidates all of the user's refresh tokens issued to applications and session cookies in a user's browser, by resetting the **refreshTokensValidFromDateTime** user property to the current date-time. Typically, this operation is performed (by the user or an administrator) if the user has a lost or stolen device. This operation would prevent access to any of the organization's data accessed through applications on the device without the user first being required to sign in again. In fact, this operation would force the user to sign in again for all applications that they have previously consented to, independent of device.
1818

19-
For developers, if the application attempts to redeem a delegated access token for this user by using an invalidated refresh token, the application will get an error. If this happens, the application will need to acquire a new refresh token by making a request to the authorize endpoint, which will force the user to sign in.
19+
For developers, if the application attempts to redeem a delegated access token for this user by using an invalidated refresh token, the application receives an error. If this happens, the application needs to acquire a new refresh token by making a request to the OAuth 2.0 `/authorize` endpoint, which forces the user to sign in.
2020

2121

2222
[!INCLUDE [national-cloud-support](../../includes/all-clouds.md)]
@@ -29,7 +29,7 @@ Choose the permission or permissions marked as least privileged for this API. Us
2929

3030
> [!IMPORTANT]
3131
>
32-
> In delegated scenarios with work or school accounts, the signed-in user must be assigned a supported [Microsoft Entra role](/entra/identity/role-based-access-control/permissions-reference?toc=%2Fgraph%2Ftoc.json) or a custom role with a supported role permission. The following least privileged roles are supported for this operation:
32+
> In delegated scenarios with work or school accounts, the signed-in user must be assigned a supported [Microsoft Entra role](/entra/identity/role-based-access-control/permissions-reference?toc=%2Fgraph%2Ftoc.json) or a custom role with the `microsoft.directory/users/invalidateAllRefreshTokens` role permission. The following least privileged roles are supported for this operation:
3333
> - Directory Writers
3434
> - Helpdesk Administrator
3535
> - Authentication Administrator

0 commit comments

Comments
 (0)