> 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/group/devices/unenroll-updatable-assets_scheduled.md).

# Unenroll Updatable Assets Scheduled

Unenroll this group's devices from Windows Update for Business

{% hint style="info" %}
This is a scheduled runbook. It is designed to run on a recurring schedule rather than being triggered for a single object. See [Scheduling](/automation/runbooks/scheduling.md) for details on how to configure runbook schedules.
{% endhint %}

### Description

Removes every device in this group from Windows Update for Business, either for one update category or by deleting the updatable asset registration entirely. Optionally the devices owned by the group's user members are included. Use it to offboard devices from Windows Update for Business reporting or to reset their enrollment.

### Location

Group → Devices → Unenroll Updatable Assets (Scheduled)

**Full Runbook name**

rjgit-group\_devices\_unenroll-updatable-assets\_scheduled

### Details

| Property         | Value                               |
| ---------------- | ----------------------------------- |
| Version          | 1.1.1                               |
| Required modules | RealmJoin.RunbookHelper (>= 0.8.10) |
| Schedulable      | yes                                 |

### Permissions

#### Application permissions

* **Type**: Microsoft Graph
  * Group.Read.All
    * *Reads the group's transitive device and user members to find devices to unenroll*
  * WindowsUpdates.ReadWrite.All
    * *Unenrolls each device via updatableAssets DELETE or unenrollAssets*
  * User.Read.All *(optional — feature: User-owned devices)*
    * *Reads each user member's owned devices via /users/{id}/ownedDevices when IncludeUserOwnedDevices is enabled*

### Parameters

#### GroupId

Object ID of the group the runbook acts on. Set by the portal from the selected group.

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

#### UpdateCategory

Update category (driver, feature or quality) to unenroll the devices from. Choose all to delete the updatable asset registration entirely.

| Property            | Value           |
| ------------------- | --------------- |
| Required            | true            |
| Default Value       | all             |
| Type                | String          |
| Portal display name | Update category |

#### IncludeUserOwnedDevices

Also unenrolls every device owned by the users in this group, nested groups included.

| Property            | Value                                  |
| ------------------- | -------------------------------------- |
| Required            | false                                  |
| Default Value       | False                                  |
| Type                | Boolean                                |
| Portal display name | Include devices owned by user members? |

[Back to Runbook Reference overview](/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/group/devices/unenroll-updatable-assets_scheduled.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.