Does updating a mailbox name change a user's sign-in name?
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result these questions will not appear in the review screen. You administer the Microsoft 365 and Microsoft Power Platform environments for Contoso, Ltd. The company has a model-driven app that is used to track customer interactions with employees. The app uses standard table types for customers. A user named Elisabeth Rice signs in to the app by using the following sign in name: [email protected] . After marriage, Elisabeth changes her legal name to Elisabeth Mueller. You need to update the sign in name for the user without losing any application history. Solution: From Dynamics 365 Settings, select Email Configuration. In the active mailbox for the user, update the name. Does the solution meet the goal?
Community Insight
The question tests whether you can distinguish a user's identity (UPN in Microsoft Entra ID) from a mailbox/server-side email configuration record; the trap is assuming the mailbox name drives sign-in.
Changing the name on a user's mailbox record in Dynamics 365 Email Configuration only edits mailbox settings and leaves the sign-in name untouched. The sign-in name is the user principal name (UPN) in Microsoft Entra ID, so the solution does not meet the goal of renaming Elisabeth while preserving her model-driven app history.
Learners pick "Yes" because the name appears in the mailbox record and the app surfaces the mailbox, but a mailbox rename never writes back to the Entra ID user object or the Dataverse user record.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
A sign-in name for a Microsoft 365 user is the user principal name (UPN) stored on the user object in Microsoft Entra ID, not a field on a mailbox configuration record. The proposed solution navigates to Dynamics 365 Settings > Email Configuration and edits the name on the active mailbox, which is server-side email settings data used for synchronization and routing. Nothing in that action writes to the Entra ID user object, so after the change Elisabeth would still sign in with the old address. Because the goal is specifically to change the sign-in name, the solution does not meet the goal, making "No" the correct answer.
Why the Other Options Are Wrong
"Yes" would only be correct if the mailbox record's name controlled authentication, which it does not — mailbox records hold configuration such as server profile, synchronization method, and email addresses used by the email router or server-side sync. The correct path is to update the UPN (and typically the email address) on the user account in the Microsoft 365 admin center or Microsoft Entra ID, which renames the identity while leaving the Dataverse user record and its app history intact. Because the app history lives in Dataverse and is tied to the user record, renaming the identity does not discard the customer-interaction history.
Community Comment Notes
As one voter who chose B explained, "Changing the name on the mailbox record only renames that mailbox configuration," and the sign-in name is her UPN in Microsoft Entra ID, so the goal is not met. That matches the exam doctrine: identity changes happen on the user object, not on mailbox settings. The practical follow-up in the community discussion is that the user record itself stays the same, which is exactly why the application history survives a correct UPN change.
Official Reference
Exam Strategy
When a scenario asks about a sign-in name, display name, or email change, immediately trace where that attribute lives — Entra ID user object versus a component record such as a mailbox. Mailbox, queue, and email-server settings rarely satisfy identity requirements, so check the wording "sign in name" against the UPN before answering.
Frequently Asked Questions
Why doesn't renaming the mailbox change Elisabeth's sign-in name?
The mailbox record only stores email server and synchronization settings. Authentication uses the UPN on the Microsoft Entra ID user object, which the mailbox rename never updates.
Will Elisabeth lose her model-driven app history if her UPN is changed instead?
No. The Dataverse user record linked to the app history stays intact; updating the UPN in Microsoft Entra ID renames the identity without recreating the user.