# Ensure that 'Require Multi-Factor Authentication to register or join devices with Azure AD' is set to 'Yes'

- Source: https://support.icompaas.com/support/solutions/articles/62000219698-ensure-that-require-multi-factor-authentication-to-register-or-join-devices-with-azure-ad-is-set-to
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Azure CIS Benchmark Level 1 & Level 2](https://support.icompaas.com/support/solutions/62000112163) › [1. Identity and Access Management](https://support.icompaas.com/support/solutions/folders/62000167544)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Description:

Requiring multifactor authentication (MFA) to register or join devices with Microsoft Entra ensures that only verified and trusted users can add new devices to the organization’s directory. This security control helps prevent unauthorized device enrollment by adding an additional layer of identity verification beyond the user’s password. By enforcing MFA during device registration, organizations reduce the risk of compromised accounts being used to introduce unauthorized or potentially harmful devices into the environment.

  

Rationale:

Requiring MFA prevents unauthorized users from registering or joining devices by ensuring only verified identities can complete the process. This added security layer reduces the risk of compromised accounts introducing untrusted devices and strengthens overall access control within the organization.

  

Impact:

Security is increased because only users who complete MFA can add devices. It prevents unknown or unverified devices from joining the organization.

  

Default Value:

By default, this setting is not always turned on. Administrators must manually set it to Yes if they want to require MFA for device registration or joining.

  

Pre-requisites:

-   You must sign in with a Global Administrator or Privileged Role Administrator account.
    

  

Test Plan:

1.  Go to the Azure portal at [https://portal.azure.com](https://portal.azure.com/).
    
2.  In the portal, search for  Microsoft Entra ID.
    
3.  In the left-side menu, under Manage, select Devices.
    
4.   Under Manage, Select Device settings.
    
5.  Locate the setting “Require Multifactor Authentication to register or join devices with Microsoft Entra.”
    
6.  Verify that the setting is set to Yes.
    

![](https://support.icompaas.com/assets/kb/d53612d3ad82b95b.png)

7.  If it is No, follow the implementation plan.
    

  

Implementation Plan:

1.  Go to the Azure portal at [https://portal.azure.com](https://portal.azure.com/).
    
2.  In the portal, search for  Microsoft Entra ID.
    
3.  In the left-side menu, under Manage, select Devices.
    

                                              ![](https://support.icompaas.com/assets/kb/037a54bfb1b09674.png)

4.   Under Manage, Select Device settings.
    
5.  Find the option "Require Multifactor Authentication to register or join devices with Microsoft Entra."
    
6.  Set this option to Yes.
    

![](https://support.icompaas.com/assets/kb/3d5149009e4f38d6.png)

6.  Click Save to apply the change.  
      
    

Backout Plan:

1.  Go to the Azure portal at [https://portal.azure.com](https://portal.azure.com/).
    
2.  In the portal, search for  Microsoft Entra ID.
    
3.  In the left-side menu, under Manage, select Devices.
    
4.   Under Manage, Select Device settings.
    
5.  Locate the setting “Require Multifactor Authentication to register or join devices with Microsoft Entra.”
    
6.  Change the option back to No.
    
7.  Click Save to apply the change.
    

  

Reference:

-   [https://learn.microsoft.com/en-us/entra/identity/devices/device-management-azure-portal](https://learn.microsoft.com/en-us/entra/identity/devices/device-management-azure-portal)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
