> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/automations/subworkflows/rewst-task-365-on-prem-disable-user-account.md).

# \[REWST - TASK] 365/On-Prem: Disable User Account

This workflow provides a standardized method to disable user accounts across both Microsoft 365 and on-premises Active Directory environments, serving as a critical building block in comprehensive offboarding automation chains and security incident response protocols. MSPs will find this particularly valuable during client employee departures, security breaches requiring immediate account lockdown, or compliance scenarios demanding rapid access revocation - all without requiring technicians to remember the specific steps for each environment type. Technically, the workflow validates inputs, checks applicable identity environments (Microsoft 365/on-premises), then executes the appropriate disabling action using Microsoft Graph API for cloud accounts and PowerShell via RMM for on-premises accounts, with built-in error handling for operational reliability. This automation significantly reduces the risk of missed steps during offboarding while cutting the average technician time from 15-20 minutes down to mere seconds per user deactivation.

This workflow contains 10 tasks.

### Inputs

* **idp\_config** - string
  * One of: on\_prem, hybrid\_no\_sync, azure\_ad, on\_prem\_only
* **on\_prem\_id** - string
  * On-prem ID of user to be disabled
* **aad\_user\_id** - string
  * Entra ID of user to be disabled

### Outputs

* **automation\_log**: Standardized Rewst automation log
* **success**: Boolean; States if workflow was successful.

### Key tasks

* **check\_aad**: Validation/verification
* **failure\_catch**: Core integration: noop
* **disable\_aad\_user**: Microsoft Graph integration: Graph API Request
* **disable\_on\_prem**: Workflows integration: \[REWST - TASK] Run Powershell via RMM
* **check\_on\_prem**: Validation/verification

### Jinja examples

#### Example 1

```jinja
{{ CTX.aad_user_id|d != \"\" and CTX.idp_config|d in [\"hybrid_no_sync\", \"azure_ad\"] }}
```


---

# 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.rewst.help/documentation/automations/subworkflows/rewst-task-365-on-prem-disable-user-account.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.