> 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/devices/delete-stale-devices_scheduled.md).
# Delete Stale Devices Scheduled
Delete Intune devices that have been inactive for too long
{% 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
Finds Intune devices that have not checked in for a given number of days, filtered by platform and optionally by the group membership of their primary user. By default it only lists what it would delete; deletion has to be switched on explicitly. The report can be sent by email or provided as a download link.
### Common use cases
This runbook deletes managed devices from Intune based on inactivity, so use it with care.
* Regular cleanup of stale device records in Intune
* Simulation runs (report-only mode) before enabling the actual deletion
* Scheduled lifecycle management with an audit trail via the email report
### User scope filtering
The runbook supports optional user scope filtering to include or exclude devices based on the group membership of their primary user. This acts as an additional safety net when deletion is enabled.
### Setup regarding email sending
Sending an email report is optional and only happens when a recipient (`EmailTo`) is provided. The sender address is taken from the `RJReport.EmailSender` tenant setting.
This runbook sends emails using the Microsoft Graph API. To send emails via Graph API, you need to configure an existing email address in the runbook customization.
See the [RealmJoin Report Settings documentation](https://docs.realmjoin.com/automation/runbooks/runbook-report-settings) for details on all available settings.
#### Email branding
The report email honors the optional `RJReport.Branding.*` tenant settings:
* **Header and footer image** – public HTTPS URLs, PNG/JPEG/GIF, max. 200 KB each
* **Footer link** – target of the footer image
* **Accent and text color** – 6-digit hex values, e.g. `#0052cc`
When these settings are not configured, the default RealmJoin graphics and colors are used. An image that cannot be downloaded or validated, or an invalid color value, never prevents the report email – the corresponding default is used instead.
Setup instructions and image requirements: [Email branding](https://docs.realmjoin.com/automation/runbooks/runbook-report-settings#email-branding-optional).
### Location
Organization → Devices → Delete Stale Devices (Scheduled)
**Full Runbook name**
rjgit-org\_devices\_delete-stale-devices\_scheduled
### Details
| Property | Value |
| ---------------- | ------------------------------------------------------------------------------------------------------------------ |
| Version | 2.2.0 |
| Required modules | RealmJoin.RunbookHelper (>= 0.8.10)
Microsoft.Graph.Authentication (>= 2.41.2)
Az.Accounts (>= 5.5.2)
|
| Schedulable | yes |
### Permissions
#### Application permissions
* **Type**: Microsoft Graph
* DeviceManagementManagedDevices.ReadWrite.All
* *Lists stale Intune devices and deletes them via DELETE /deviceManagement/managedDevices/{id}*
* Directory.Read.All
* *Reads include/exclude group members, primary user details and the tenant name*
* Mail.Send *(optional — feature: Email report)*
* *Sends the report email via Send-RjReportEmail when EmailTo is configured*
### Parameters
#### Days
Devices with no check-in for at least this many days count as stale.
| Property | Value |
| ------------------- | --------------------- |
| Required | false |
| Default Value | 30 |
| Type | Int32 |
| Portal display name | Days without activity |
#### Windows
Includes Windows devices.
| Property | Value |
| ------------------- | ------------------------ |
| Required | false |
| Default Value | True |
| Type | Boolean |
| Portal display name | Include Windows devices? |
#### MacOS
Includes macOS devices.
| Property | Value |
| ------------------- | ---------------------- |
| Required | false |
| Default Value | True |
| Type | Boolean |
| Portal display name | Include macOS devices? |
#### iOS
Includes iOS and iPadOS devices.
| Property | Value |
| ------------------- | -------------------- |
| Required | false |
| Default Value | True |
| Type | Boolean |
| Portal display name | Include iOS devices? |
#### Android
Includes Android devices.
| Property | Value |
| ------------------- | ------------------------ |
| Required | false |
| Default Value | True |
| Type | Boolean |
| Portal display name | Include Android devices? |
#### DeleteDevices
Delete removes the stale devices from Intune. Report only lists them and changes nothing.
| Property | Value |
| ------------------- | ------------- |
| Required | false |
| Default Value | False |
| Type | Boolean |
| Portal display name | Deletion mode |
**Portal options**
| Portal option | Value |
| ----------------------------------------------------- | ----- |
| Report only - show what would be deleted (simulation) | false |
| Delete stale devices from Intune | true |
#### EmailFrom
Sender address of the report email. Taken from the tenant setting RJReport.EmailSender.
| Property | Value |
| ---------------- | -------------------------------------- |
| Required | false |
| Default Value | |
| Type | String |
| Hidden in portal | yes (preset via runbook customization) |
#### BrandingHeaderImageUrl
Header image of the report email (HTTPS URL, PNG/JPEG/GIF, max 200 KB). Taken from the tenant setting RJReport.Branding.HeaderImageUrl; the default RealmJoin header is used when empty.
| Property | Value |
| ---------------- | -------------------------------------- |
| Required | false |
| Default Value | |
| Type | String |
| Hidden in portal | yes (preset via runbook customization) |
#### BrandingFooterImageUrl
Footer image of the report email (HTTPS URL, PNG/JPEG/GIF, max 200 KB). Taken from the tenant setting RJReport.Branding.FooterImageUrl; the default RealmJoin footer is used when empty.
| Property | Value |
| ---------------- | -------------------------------------- |
| Required | false |
| Default Value | |
| Type | String |
| Hidden in portal | yes (preset via runbook customization) |
#### BrandingFooterLink
Link behind the footer image of the report email. Taken from the tenant setting RJReport.Branding.FooterLink; realmjoin.com is used when empty.
| Property | Value |
| ---------------- | -------------------------------------- |
| Required | false |
| Default Value | |
| Type | String |
| Hidden in portal | yes (preset via runbook customization) |
#### BrandingAccentColor
Accent color of the report email as a 6-digit hex value. Taken from the tenant setting RJReport.Branding.AccentColor; the RealmJoin default is used when empty or invalid.
| Property | Value |
| ---------------- | -------------------------------------- |
| Required | false |
| Default Value | |
| Type | String |
| Hidden in portal | yes (preset via runbook customization) |
#### BrandingTextColor
Text color of the report email as a 6-digit hex value. Taken from the tenant setting RJReport.Branding.TextColor; the RealmJoin default is used when empty or invalid.
| Property | Value |
| ---------------- | -------------------------------------- |
| Required | false |
| Default Value | |
| Type | String |
| Hidden in portal | yes (preset via runbook customization) |
#### ReportFileFormat
Deliver the report as CSV, as an Excel workbook, or both.
| Property | Value |
| ------------------- | ------------------ |
| Required | false |
| Default Value | CSV & XLSX |
| Type | String |
| Portal display name | Report file format |
**Portal options**
| Portal option | Value |
| ------------- | ---------- |
| CSV & XLSX | CSV & XLSX |
| CSV only | CSV only |
| XLSX only | XLSX only |
#### CreateDownloadLink
Also upload the report and return a download link that expires after a few days.
| Property | Value |
| ------------------- | ----------------------- |
| Required | false |
| Default Value | False |
| Type | Boolean |
| Portal display name | Create a download link? |
**Portal options**
| Portal option | Value |
| ---------------------------------------------- | ----- |
| Yes - upload report and return a download link | true |
| No - do not create a download link | false |
#### ContainerName
Storage container the report files are uploaded to. Set per runbook.
| Property | Value |
| ---------------- | -------------------------------------- |
| Required | false |
| Default Value | delete-stale-devices |
| Type | String |
| Hidden in portal | yes (preset via runbook customization) |
#### ResourceGroupName
Resource group of the storage account for report uploads. Taken from the tenant setting RJReport.StorageAccount.ResourceGroup.
| Property | Value |
| ---------------- | -------------------------------------- |
| Required | false |
| Default Value | |
| Type | String |
| Hidden in portal | yes (preset via runbook customization) |
#### StorageAccountName
Storage account for report uploads. Taken from the tenant setting RJReport.StorageAccount.StorageAccountName.
| Property | Value |
| ---------------- | -------------------------------------- |
| Required | false |
| Default Value | |
| Type | String |
| Hidden in portal | yes (preset via runbook customization) |
#### LinkExpiryDays
Number of days a download link stays valid. Taken from the tenant setting RJReport.StorageAccount.LinkExpiryDays.
| Property | Value |
| ---------------- | -------------------------------------- |
| Required | false |
| Default Value | 6 |
| Type | Int32 |
| Hidden in portal | yes (preset via runbook customization) |
#### UseUserScope
Whether devices are filtered by the group membership of their primary user. Set by the "Filter by primary user group?" choice.
| Property | Value |
| ---------------- | -------------------------------------- |
| Required | false |
| Default Value | False |
| Type | Boolean |
| Hidden in portal | yes (preset via runbook customization) |
#### IncludeUserGroup
Only devices whose primary user is in this group.
| Property | Value |
| ------------------- | -------------------------------------- |
| Required | false |
| Default Value | |
| Type | String |
| Portal display name | Include users from group |
| Hidden in portal | yes (preset via runbook customization) |
#### ExcludeUserGroup
Skips devices whose primary user is in this group.
| Property | Value |
| ------------------- | -------------------------------------- |
| Required | false |
| Default Value | |
| Type | String |
| Portal display name | Exclude users from group |
| Hidden in portal | yes (preset via runbook customization) |
#### EmailTo
Send the report to these addresses. Separate several with commas; each recipient gets a separate email.
| Property | Value |
| ------------------- | --------------------------- |
| Required | false |
| Default Value | |
| Type | String |
| Portal display name | Recipient email address(es) |
[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/devices/delete-stale-devices_scheduled.md?ask=&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.