> 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/es/automatizacion/runbooks/runbook-references/device/general/set-primary-user.md).

# Establecer usuario principal

Establece un nuevo usuario principal en este dispositivo

### Descripción

Asigna al usuario elegido como el nuevo usuario principal de este dispositivo en Intune y reemplaza al actual. El resultado muestra la asignación anterior y la nueva.

### Ubicación

Dispositivo → General → Establecer usuario principal

**Nombre completo del runbook**

rjgit-device\_general\_set-primary-user

### Detalles

| Propiedad          | Valor                                                                                    |
| ------------------ | ---------------------------------------------------------------------------------------- |
| Versión            | 1.0.2                                                                                    |
| Módulos requeridos | <p>RealmJoin.RunbookHelper (>= 0.8.10)<br>Microsoft.Graph.Authentication (>= 2.41.2)</p> |
| Programable        | no                                                                                       |

### Permisos

#### Permisos de aplicación

* **Tipo**: Microsoft Graph
  * DeviceManagementManagedDevices.ReadWrite.All
    * *Resuelve el dispositivo de Intune y reemplaza su usuario principal mediante managedDevices('{id}')/users/$ref*
  * User.Read.All
    * *Resuelve el UPN y el nombre para mostrar del nuevo usuario principal antes de la asignación*

### Parámetros

#### DeviceId

ID de dispositivo de Entra ID del dispositivo sobre el que actúa el runbook. Lo establece el portal a partir del dispositivo seleccionado.

| Propiedad            | Valor                                                       |
| -------------------- | ----------------------------------------------------------- |
| Requerido            | verdadero                                                   |
| Valor predeterminado |                                                             |
| Tipo                 | Cadena                                                      |
| Oculto en el portal  | sí (preconfigurado mediante la personalización del runbook) |

#### NewPrimaryUserId

Usuario a asignar. El usuario principal actual se reemplaza; ambos se muestran en el resultado.

| Propiedad            | Valor     |
| -------------------- | --------- |
| Requerido            | verdadero |
| Valor predeterminado |           |
| Tipo                 | Cadena    |

[Volver a la vista general de referencia del runbook](/es/automatizacion/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/es/automatizacion/runbooks/runbook-references/device/general/set-primary-user.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.