Registering Android Device in Microsoft Entra ID
Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem. After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen. You have a Microsoft Entra tenant named contoso.com. You purchase an Android device named Device1. You need to register Device1 in contoso.com. Solution: You use Microsoft Entra Connect. Does this meet the goal?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The common trap is confusing identity synchronization tools with device management and registration mechanisms.
This question tests the correct method for registering an Android device with Microsoft Entra ID. The solution using Microsoft Entra Connect is incorrect because it is designed for on-premises directory synchronization, not device registration.
Candidates often select 'Yes' assuming that any Entra-related tool can handle device setup, failing to distinguish between user/object sync and device join/register workflows.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Microsoft Entra Connect (formerly Azure AD Connect) is strictly used to synchronize identities (users, groups, contacts) from on-premises Active Directory to Microsoft Entra ID. It does not perform device registration or joining. To register a personal Android device (Intune Company Portal style) or join it, you use methods like the Settings app, Microsoft Authenticator app, or Intune enrollment profiles. Therefore, using Entra Connect to register Device1 does not meet the goal.Why the Other Options Are Wrong
Option A ('Yes') is incorrect because Entra Connect has no functionality for handling client devices directly. It operates on server-side identity objects, not endpoint clients.Community Comment Notes
Community consensus correctly identifies that Entra Connect is for syncing on-prem resources. One commenter noted that alternatives include the Settings app, Microsoft Authenticator, or third-party products, which aligns with standard registration methods.Official Reference
Exam Strategy
Always distinguish between 'syncing identities' (Entra Connect) and 'registering/joining devices' (Intune/Autopilot/Settings). For MD-102, know that Entra Connect is for hybrid identity infrastructure, not endpoint management.
Frequently Asked Questions
Why is Microsoft Entra Connect wrong for device registration?
Entra Connect syncs users/groups from on-prem AD to cloud, it does not manage or register endpoint devices.
How do I actually register an Android device in Entra ID?
Use the Microsoft Authenticator app, Settings app, or enroll via Intune Company Portal depending on the scenario.
Related Analysis
Practice All MD-102 Questions
Access 92 questions with complete answers and detailed explanations.
View Full MD-102 Practice Test →