Revoke User Sign In Sessions

Invalidates the refresh tokens issued to applications for an Azure Active Directory user, and the session cookies in the user's browser.

After calling revoke sign in sessions, there may be a short delay before the tokens get revoked.

Input

Field Definition Type Required

Field	Definition	Type	Required
User
ID or Username	User ID is the unique identifier for the user. Should be treated as an opaque identifier. Username of the Office 365 user. This is the user's User Principal Name (UPN). A UPN is formed by taking the username and domain and combining them with the `@` separator. For example, `john.doe@somedomain.com`. This could be the user's email address, but not always. This property can't contain accent characters. Only the following characters are allowed A-Z, a-z, 0-9, '.-_!#^~.	Text	TRUE

User

ID or Username

User ID is the unique identifier for the user. Should be treated as an opaque identifier.

Username of the Office 365 user. This is the user's User Principal Name (UPN). A UPN is formed by taking the username and domain and combining them with the @ separator.

For example, john.doe@somedomain.com. This could be the user's email address, but not always.

This property can't contain accent characters. Only the following characters are allowed A-Z, a-z, 0-9, '.-_!#^~.

Text

TRUE

If the string for the UPN input begins with the $character, remove the slash / after /users and enclose the UPN value in parentheses and single quotes. For example, /users('$AdeleVance@contoso.com'). See Known issues with Microsoft Graph.

To search for a B2B user using a UPN input value, encode the hash # character as %23. For example, /users/AdeleVance_adatum.com%23EXT%23@contoso.com.

Output

Field Definition Type

Field	Definition	Type
Response
Are All Sessions Revoked?	`True` if all the refresh tokens issued to applications for a user are revoked. `False` otherwise. There might be a small delay of a few minutes before the tokens get revoked.	True/False
Status Code	Result of the operation. The connector returns an HTTP status code that indicates whether the action taken by the card succeeded or failed. For example: A 201 Created status code indicates success where a new resource was created. A 403 Forbidden error indicates that the HTTP request wasn't processed because the necessary permissions were missing. For a full list of possible status codes, see HTTP status codes.	Number

Response

Are All Sessions Revoked?

True if all the refresh tokens issued to applications for a user are revoked.
False otherwise.

There might be a small delay of a few minutes before the tokens get revoked.

True/False

Status Code

Result of the operation. The connector returns an HTTP status code that indicates whether the action taken by the card succeeded or failed. For example:

A 201 Created status code indicates success where a new resource was created.
A 403 Forbidden error indicates that the HTTP request wasn't processed because the necessary permissions were missing.

For a full list of possible status codes, see HTTP status codes.

Number

Revoke User Sign In Sessions

Input

Output

Related topics