> 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/add-device-via-corporate-identifier.md).

# Add Device Via Corporate Identifier

Register a device in Intune by its corporate identifier

### Description

Adds a device to Intune's list of corporate identifiers, such as a serial number or IMEI, so it counts as corporate-owned when it enrolls. An existing entry for the same identifier can be overwritten, and a description can be stored with it.

### Location

Organization → Devices → Add Device Via Corporate Identifier

**Full Runbook name**

rjgit-org\_devices\_add-device-via-corporate-identifier

### Details

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

### Permissions

#### Application permissions

* **Type**: Microsoft Graph
  * DeviceManagementServiceConfig.ReadWrite.All
    * *Imports the serial or IMEI as Intune corporate identifier via importDeviceIdentityList*

### Parameters

#### CorpIdentifierType

Serial number for most devices, IMEI for cellular devices.

| Property            | Value           |
| ------------------- | --------------- |
| Required            | true            |
| Default Value       | serialNumber    |
| Type                | String          |
| Portal display name | Identifier type |

**Portal options**

| Portal option | Value        |
| ------------- | ------------ |
| Serial Number | serialNumber |
| IMEI          | imei         |

#### CorpIdentifier

Value of the chosen identifier, exactly as printed on or reported by the device.

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

#### DeviceDescripton

Free text stored with the identifier, for example the device model or its owner.

| Property            | Value       |
| ------------------- | ----------- |
| Required            | false       |
| Default Value       |             |
| Type                | String      |
| Portal display name | Description |

#### OverwriteExistingEntry

Replaces an entry that already exists for the same identifier.

| Property            | Value                        |
| ------------------- | ---------------------------- |
| Required            | false                        |
| Default Value       | True                         |
| Type                | Boolean                      |
| Portal display name | Overwrite an existing entry? |

[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/add-device-via-corporate-identifier.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.