> 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/device/general/rename-device.md).

# Rename Device

Rename this device in Intune and Autopilot

### Description

Gives this device a new name in Intune and in its Windows Autopilot record. Before anything is changed, the name is checked against the Windows computer name rules. It may have up to 15 letters, digits and hyphens, must start and end with a letter or digit, and cannot be digits only.

### Location

Device → General → Rename Device

**Full Runbook name**

rjgit-device\_general\_rename-device

### Details

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

### Permissions

#### Application permissions

* **Type**: Microsoft Graph
  * Device.Read.All
    * *Resolves the Entra device object via /devices before renaming*
  * DeviceManagementManagedDevices.Read.All
    * *Finds the Intune device by azureADDeviceId to get its Intune object id*
  * DeviceManagementServiceConfig.ReadWrite.All
    * *Reads the Autopilot identity and renames it via updateDeviceProperties*
  * DeviceManagementManagedDevices.PrivilegedOperations.All
    * *Triggers the privileged setDeviceName action on the Intune device*

### Parameters

#### DeviceId

Entra ID device ID of the device the runbook acts on. Set by the portal from the selected device.

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

#### NewDeviceName

Up to 15 letters, digits and hyphens, starting and ending with a letter or digit, not digits only.

| Property            | Value           |
| ------------------- | --------------- |
| Required            | true            |
| Default Value       |                 |
| Type                | String          |
| Portal display name | New device name |

[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/device/general/rename-device.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.