> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/automation/runbooks/runbook-references/user/security/revoke-or-restore-access.md).

# Revoke Or Restore Access

Block this user's sign-in and sessions, or restore access

### Description

Blocks this user from signing in and ends the current sessions, for example during an incident. Access tokens that were already issued stay valid until they expire, usually within an hour; apps with continuous access evaluation, such as Exchange Online, SharePoint and Teams, react within minutes. Re-enable user lifts the block again; ended sessions are not restored.

### Users with administrator roles

Entra ID protects users who hold an administrator role from changes by lower-privileged administrators. With the User Administrator role, the RealmJoin managed identity can block or restore sign-in and revoke sessions for users without administrator roles and for users with a few roles such as Helpdesk Administrator, Password Administrator, Groups Administrator or User Administrator.

For users with any other role, for example Power Platform Administrator, Exchange Administrator or Global Administrator, and for members and owners of role-assignable groups, Entra ID requires a Privileged Authentication Administrator or Global Administrator. The run then stops with "Insufficient privileges" and names the roles of the user. Make the change for such a user in the Entra admin center with a Privileged Authentication Administrator or Global Administrator account.

Granting one of these two roles to the RealmJoin managed identity is not recommended, because both can also reset the credentials of Global Administrators. Microsoft lists which role can change which administrator in [Who can perform sensitive actions](https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/privileged-roles-permissions#who-can-perform-sensitive-actions).

#### Roles in the job output

Before anything changes, the job output lists the Entra ID roles assigned directly to the user. This needs the optional permission for the administrator role check; without it the output shows "could not be read" and the run continues.

### Location

User → Security → Revoke Or Restore Access

**Full Runbook name**

rjgit-user\_security\_revoke-or-restore-access

### Details

| Property         | Value                                                                                    |
| ---------------- | ---------------------------------------------------------------------------------------- |
| Version          | 1.1.0                                                                                    |
| Required modules | <p>RealmJoin.RunbookHelper (>= 0.8.10)<br>Microsoft.Graph.Authentication (>= 2.41.2)</p> |
| Schedulable      | no                                                                                       |

### Permissions

#### Application permissions

* **Type**: Microsoft Graph
  * User.ReadWrite.All
    * *Sets accountEnabled and revokes sign-in sessions on the user*
  * RoleManagement.Read.Directory *(optional — feature: Administrator role check)*
    * *Reads the Entra ID roles of the user to show them and to name the role when Entra ID denies the change for an administrator account*

#### RBAC roles

* User Administrator
  * *Required to block or restore sign-in and revoke sessions for users without administrator roles and with a few roles such as Helpdesk Administrator; other administrators need Privileged Authentication Administrator or Global Administrator*

### Parameters

#### UserName

User principal name of the user the runbook acts on. Set by the portal from the selected user.

| Property         | Value                                  |
| ---------------- | -------------------------------------- |
| Required         | true                                   |
| Default Value    |                                        |
| Type             | String                                 |
| Hidden in portal | yes (preset via runbook customization) |

#### Revoke

Revoke access blocks sign-in and ends the sessions. Re-enable user lets the user sign in again.

| Property            | Value   |
| ------------------- | ------- |
| Required            | false   |
| Default Value       | True    |
| Type                | Boolean |
| Portal display name | Action  |

**Portal options**

| Portal option  | Value |
| -------------- | ----- |
| Re-enable user | false |
| Revoke access  | true  |

[Back to Runbook Reference overview](https://docs.realmjoin.com/automation/runbooks/runbook-references.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmjoin.com/automation/runbooks/runbook-references/user/security/revoke-or-restore-access.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
