Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

2.1.2. Joining and Registering Devices

💡 First Principle: Joining and registering are things users do; the tenant's device settings decide whether they're allowed to and on what terms. So when a join "doesn't work" or works too freely, look first at the policy that governs the action — who may join, who may register, how many devices a person may have, and who ends up as local administrator — before suspecting the device.

The governing settings live in the Microsoft Entra admin center at Entra ID > Devices > All devices > Device settings. The Cloud Device Administrator role can read and change them; Intune Administrator and Windows 365 Administrator can only read them.

SettingDefaultWhat to know
Users may join devices to Microsoft Entra IDAllOptions All, Selected, None. Applies to Entra join on Windows 10+, macOS and Linux. Doesn't apply to hybrid join, Entra joined Azure VMs or Autopilot self-deploying mode, which run without a user
Users may register their devices with Microsoft Entra ID—Needed for personal Windows, iOS, Android and macOS registration. When Intune or Basic Mobility and Security is configured, it shows All and None is unavailable
Require multifactor authentication to register or join devicesNoMicrosoft recommends the Conditional Access Register or join devices user action instead
Maximum number of devices (per user)50Counts joined plus registered devices; maximum 100 or Unlimited. Doesn't apply to hybrid joined devices
Registering user is added as local administrator on the device during Microsoft Entra join—Controls local Administrators membership only; grants no directory role
Manage Additional local administrators on Microsoft Entra joined devices—Assigns the Microsoft Entra Joined Device Local Administrator role, which applies tenant-wide and requires Entra ID P1 or P2

MFA at join time. The device-settings MFA toggle and Conditional Access can collide. Microsoft recommends a Conditional Access policy that targets the Register or join devices user action (Target resources > User actions) with a grant of Require authentication strength. When you use that policy, the device-settings toggle must be set to No, or the Conditional Access policy isn't properly enforced. Neither control applies to hybrid joined devices, Entra joined Azure VMs or Autopilot self-deploying devices.

How users actually join or register. On Windows, a user joins during the out-of-box experience (OOBE) or later from Settings > Accounts > Access work or school > Connect. IT can also join at scale with a bulk provisioning package or Windows Autopilot (Phase 3). The three paths differ in ways the exam likes:

  • Self-service (OOBE or Settings) needs the user, and the primary user becomes a local administrator by default.
  • Windows Autopilot needs user interaction and OEM support, and whether the user becomes a local admin is configurable in the profile.
  • Bulk enrollment needs no user interaction, runs only in OOBE, and doesn't make the user a local admin.

Local administrators on joined devices. At join time, three identities are added to the device's local Administrators group: the Microsoft Entra Joined Device Local Administrator role, the Global Administrator role and the joining user. This happens only during the join. Because the Joined Device Local Administrator role applies to all Entra joined devices and can't be scoped to a subset, it's a blunt instrument; for targeted control you use the Intune local group membership policy in 2.3.5. Role changes are also slow: a user gains or loses local admin rights only after a new Primary Refresh Token is issued (up to 4 hours) and they sign out and back in — locking and unlocking isn't enough. To stop ordinary users becoming local admins, change the device registration setting, use an Autopilot profile that makes the user a standard user, or use bulk enrollment.

Managing device objects. Disabling a device (Intune Administrator or Cloud Device Administrator) revokes its Primary Refresh Token and refresh tokens and blocks Windows Hello for Business. Deleting a device is nonrecoverable and removes its stored BitLocker keys, and Autopilot devices can't be deleted from Entra ID before they're deleted from Intune — wipe or retire an Intune-managed device first.

⚠️ Exam Trap: If a Conditional Access policy that requires MFA for the Register or join devices user action "isn't working", check the device-settings toggle Require multifactor authentication to register or join devices. It must be No when the Conditional Access user action is in use — turning it on to "double up" breaks enforcement rather than strengthening it.

Reflection Question: A help desk technician is unexpectedly a local administrator on every Entra joined laptop in the company, while a new hire is a local administrator only on her own laptop. Which two mechanisms produced those results, and why can't the first one be limited to a single department?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned