A cloud-based identity and access management service for securing user authentication and resource access
- The “Registering user is added as local administrator on the device during Microsoft Entra join” setting
- This setting affects only Microsoft Entra joined Windows devices, not “registered” (workplace joined) devices.
- When enabled, the user who performs the join is added to the local Administrators group on that specific device via their Microsoft Entra account.
- It does not grant any Microsoft Entra directory role (for example, it does not make the user a Global Administrator or give them tenant‑wide rights). It is purely a local Windows administrator right on the joined device.
The behavior is implemented through the Primary Refresh Token (PRT). Local admin rights are evaluated from the PRT at sign‑in; they are not visible as an Entra ID role assignment.
- How to validate whether a joining user is local admin
On a Microsoft Entra joined Windows device:
- Sign in as the user in question.
- Open an elevated Command Prompt and run:
If the user is a local admin,whoami /groupsBUILTIN\Administratorsappears in the output. - If the user was just granted local admin via join or via the Entra “local admin” role, and it does not show yet, refresh the PRT and sign‑in state:
Wait 1–2 minutes, sign out, and sign back in, then rundsregcmd /refreshprtwhoami /groupsagain.
This is the same mechanism used when a user is added to the Microsoft Entra Joined Device Local Administrator role; the privilege is delivered via a new PRT and becomes effective after up to 4 hours or after a PRT refresh plus re‑sign‑in.
- What the “Device Administrators” / “Microsoft Entra Joined Device Local Administrator” role is
- The “Manage Additional local administrators on all Microsoft Entra joined devices” link manages the Microsoft Entra Joined Device Local Administrator role.
- Users or groups assigned to this role become local administrators on all Microsoft Entra joined devices in the tenant. This role cannot be scoped to a subset of devices.
- This role is separate from the “registering user is local admin” behavior:
- “Registering user is added…” → local admin only on the device they joined.
- “Microsoft Entra Joined Device Local Administrator” role → local admin on every Entra joined device.
- Users in this role are not listed directly in the local Administrators group on the device; their admin rights are evaluated from the PRT at sign‑in.
- Why the user in the test tenant might not appear as local admin
From the documented behavior of PRT and local admin assignment:
- If the user joined the device while already signed in and using a cached PRT, the PRT might not yet contain the claim that grants local admin. In that case, the user will not show as local admin until:
- The PRT is renewed (up to 4 hours automatically), and
- The user signs out and signs back in, or
-
dsregcmd /refreshprtis run followed by sign‑out/sign‑in.
If the RMM snapshot was taken before the PRT refresh and re‑sign‑in, it would not show the user as local admin yet.
- Direct answers to the numbered questions
- The “Registering user is added as local administrator…” option does not make the user a Global Administrator. It only grants local Windows administrator rights on the device that is being Entra joined.
- This local admin status is not visible as an Entra ID role assignment. Validation is done on the device itself using
whoami /groupsafter ensuring the PRT has been refreshed (dsregcmd /refreshprt+ sign‑out/sign‑in) as described above. - The “Device Administrators” role exposed via “Manage Additional local administrators on all Microsoft Entra joined devices” is the Microsoft Entra Joined Device Local Administrator role. It is a separate, tenant‑wide mechanism to make users local admins on all Entra joined devices and is independent from the “registering user is local admin” setting.
References: