Your company has a main office in London that contains 100 client computers.
Three years ago, you migrated to Azure Active Directory (Azure AD).
The company's security policy states that all personal devices and corporate-owned devices must be registered or joined to Azure AD.
A remote user named User1 is unable to join a personal device to Azure AD from a home network.
You verify that User1 was able to join devices to Azure AD in the past.
You need to ensure that User1 can join the device to Azure AD.
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D.B
The Maximum number of devices setting enables you to select the maximum number of devices that a user can have in Azure AD. If a user reaches this quota, they will not be able to add additional devices until one or more of the existing devices are removed.
Incorrect Answers:
C: Azure AD Join enables users to join their devices to Active Directory from anywhere as long as they have connectivity with the Internet.
D: The Users may join devices to Azure AD setting enables you to select the users who can join devices to Azure AD. Options are All, Selected and None. The default is All.
https://docs.microsoft.com/en-us/azure/active-directory/devices/device-management-azure-portal http://techgenix.com/pros-and-cons-azure-ad-join/The issue described in this scenario is that a remote user named User1 is unable to join a personal device to Azure AD from a home network. The company's security policy requires all personal and corporate-owned devices to be registered or joined to Azure AD.
Option A: Assign the User administrator role to User1. This option is not the best choice to resolve the issue because the User administrator role gives a user full control over all user accounts in Azure AD. This level of access is unnecessary to join a device to Azure AD, and it can pose a security risk.
Option B: From the Device settings blade, modify the Maximum number of devices per user setting. This option does not address the root cause of the issue. The problem is not related to the number of devices allowed per user, but rather User1's inability to join a personal device to Azure AD from a home network.
Option C: Create a point-to-site VPN from the home network of User1 to Azure. This option is the best solution to address the issue. Creating a point-to-site VPN from the home network of User1 to Azure will allow User1 to join a personal device to Azure AD securely. This will enable the user to comply with the company's security policy, which requires all personal and corporate-owned devices to be registered or joined to Azure AD.
Option D: From the Device settings blade, modify the Users may join devices to Azure AD setting. This option is not the best choice because it does not address the root cause of the issue. The problem is not related to the setting that allows users to join devices to Azure AD, but rather User1's inability to join a personal device to Azure AD from a home network.
In summary, Option C is the best solution to address the issue described in the scenario. By creating a point-to-site VPN from the home network of User1 to Azure, User1 will be able to join a personal device to Azure AD securely and comply with the company's security policy.