Registering or joining a device should require a second sign-in factor
This check looks at whether users must complete multifactor authentication before they register or join a device with Microsoft Entra. The safe setting is that MFA is required for those actions, either through the device setting or a Conditional Access policy.
Why it matters
A registered or joined device can become a trusted part of sign-in, and it may carry a primary refresh token that gives single sign-on to company apps. If a password alone is enough to add a device, someone who steals a password can enrol their own device and gain a longer-lived foothold. Asking for a second factor at that moment closes that route.
Microsoft documents the setting and a recommendation in Manage devices in Microsoft Entra ID: it recommends enforcing MFA with the Register or join devices user action in Conditional Access, and says the toggle must be set to No if you use such a policy. See also Require MFA for device registration.
How to check it yourself
In the Microsoft Entra admin center go to Entra ID > Devices > Device settings and read Require multifactor authentication to register or join devices with Microsoft Entra. Also open Conditional Access > Policies and look for a policy targeting the user action Register or join devices that requires MFA.
Read-only PowerShell with Microsoft Graph (needs the Policy.Read.All permission):
Connect-MgGraph -Scopes "Policy.Read.All"
(Get-MgPolicyDeviceRegistrationPolicy).MultiFactorAuthConfigurationA value of required means the toggle is on. If it is notRequired, confirm that a Conditional Access policy covers the same action.
How to fix it
Preferred route: create a Conditional Access policy that targets all users, selects the user action Register or join devices and grants access only with MFA, then keep the device setting at No as Microsoft instructs. Alternative if you do not use Conditional Access: set the device setting to Yes in Device settings. First make sure users already have an MFA method registered.
To turn the setting on with Graph (this changes your tenant, so run it yourself; ConfigCobra never changes your environment; it needs Policy.ReadWrite.DeviceConfiguration):
Update-MgPolicyDeviceRegistrationPolicy -BodyParameter @{ multiFactorAuthConfiguration = "required" }What changes when you fix it
Users who register a personal device or join a Windows device to Microsoft Entra will be prompted for MFA during that step. Users with no MFA method will be stuck, so have them register one first. Per Microsoft, the setting does not apply to hybrid joined devices, Entra joined virtual machines in Azure or Windows Autopilot self-deploying mode, and it may not work with third-party identity providers. Help desk staff enrolling devices for others should expect the extra prompt too.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Microsoft Azure Foundations v6.0.0 | 5.1.2 | Level 1 |
Check this on your Microsoft Azure
ConfigCobra runs this check with every other control of the CIS Microsoft Azure Benchmarks, read-only.