> 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/org/general/check-device-onboarding-exclusion_scheduled.md).

# Check Device Onboarding Exclusion Scheduled

Keep unenrolled Autopilot devices in a compliance exclusion group

{% 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

Puts Windows Autopilot devices that are not yet enrolled in Intune, plus devices enrolled only recently, into an exclusion group. Once they are past that grace period, they are taken out again. Devices in the group can get a longer compliance grace period after enrollment.

### Location

Organization → General → Check Device Onboarding Exclusion (Scheduled)

**Full Runbook name**

rjgit-org\_general\_check-device-onboarding-exclusion\_scheduled

### Details

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

### Permissions

#### Application permissions

* **Type**: Microsoft Graph
  * Group.ReadWrite.All
    * *Finds or creates the exclusion group and adds/removes device members*
  * Device.Read.All
    * *Resolves Autopilot and Intune azureADDeviceIds to Entra device objects via /devices*
  * DeviceManagementManagedDevices.Read.All
    * *Lists recently enrolled Windows devices via /deviceManagement/managedDevices*
  * DeviceManagementServiceConfig.Read.All
    * *Lists windowsAutopilotDeviceIdentities to match Autopilot devices for the exclusion group*

### Parameters

#### exclusionGroupName

Display name of the group that holds the excluded devices.

| Property            | Value                                                                          |
| ------------------- | ------------------------------------------------------------------------------ |
| Required            | false                                                                          |
| Default Value       | cfg - Intune - Windows - Compliance for unenrolled Autopilot devices (devices) |
| Type                | String                                                                         |
| Portal display name | Exclusion group name                                                           |

#### maxAgeInDays

Devices enrolled within this many days stay in the group; older ones are removed.

| Property            | Value               |
| ------------------- | ------------------- |
| Required            | false               |
| Default Value       | 1                   |
| Type                | Int32               |
| Portal display name | Grace period (days) |

[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/org/general/check-device-onboarding-exclusion_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.