Does Microsoft Authenticator Register an Android Device in 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 the Microsoft Authenticator app. Does this meet the goal?
Community Votes
55% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests the difference between registering a device in Entra ID and merely performing MFA, while the common trap is assuming the Authenticator app can only do multi-factor authentication and passwordless sign-in.
This MD-102 scenario asks whether using the Microsoft Authenticator app satisfies the requirement to register an Android device named Device1 in the contoso.com Microsoft Entra tenant. It does — Microsoft officially lists the Authenticator app alongside Company Portal as a supported way to create an Entra registered (workplace-joined) device identity on Android.
The most common wrong answer is B ("No"), because test-takers remember the Authenticator app only as an MFA/passwordless tool and forget that signing in with a work or school account inside Authenticator also creates an Entra registered device identity.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Registering (not joining) an Android device in Microsoft Entra ID creates a work or school identity on the device — a workplace join that leaves the device in the user's personal ownership. Microsoft documents three client-side paths to reach that state on Android: the Settings app, the Microsoft Authenticator app, or a third-party MDM/product. In the Authenticator app the user adds a work or school account under app settings, and the sign-in flow provisions the Entra registered device object in contoso.com. Since the question only requires registration of Device1 — not Entra join, not Intune enrollment, and not compliance — the Authenticator-based solution fully meets the stated goal, making "Yes" (A) the correct choice.Why the Other Options Are Wrong
Option B ("No") rests on an outdated assumption that Authenticator is strictly an MFA and passwordless authenticator. While that is its headline function, the same app performs the device registration handshake when a work account is added on Android or iOS. The distractor wording pushes candidates toward Company Portal as the "only" enrollment app, but Company Portal is an alternative method, not an exclusive one — the question asks whether the given solution meets the goal, and it does. Nothing in the scenario requires device join, conditional access compliance, or Intune management, so no additional tooling is needed.Community Comment Notes
GamingFuntime1985 enumerates the three supported registration methods and highlights the Authenticator route with "Microsoft Authenticator app (app settings-Work Or School Account-Device Registration)", matching the official documentation. ExamBud agrees that "Both Company Portal and MS Authenticator answers are correct" and links the Entra device registration concept page that lists "iOS/Android – Company Portal or Microsoft Authenticator app". RJTW070 votes B, arguing that "The Microsoft Authenticator app is used for multi-factor authentication (MFA)", and Ayind3 simply answers "Company Portal"; both reflect the MFA-only misconception. The 55/45 vote split for B shows the community majority is misreading the capability, but Microsoft's own registration documentation supports answer A.Official Reference
Exam Strategy
Always separate the verbs in MD-102 device questions: register (Entra registered / workplace join), join (Entra joined), and enroll (Intune managed) have different supported tools. If the scenario only says "register Device1 in contoso.com," an app listed under the registration methods — Authenticator or Company Portal — is sufficient, so answer "Yes."
Frequently Asked Questions
Does the Microsoft Authenticator app really register a device in Microsoft Entra ID?
Yes. Microsoft's device registration documentation lists the Authenticator app for iOS/Android, so adding a work or school account creates an Entra registered device object.
Why is answering "No, use Company Portal" wrong in this MD-102 scenario?
Company Portal is another valid method, not the only one. The question only asks whether the Authenticator solution meets the registration goal, and it does.
Related Analysis
Practice All MD-102 Questions
Access 92 questions with complete answers and detailed explanations.
View Full MD-102 Practice Test →