MENU
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: Elisabeth.Rice@contoso.com. 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: Ask the Microsoft 365 administrator to sign in to the admin portal and change the user name.
Does the solution meet the goal?
The Microsoft 365 administrator should change the user's sign-in name in the Microsoft 365 or Microsoft Entra administration plane. Dataverse user records are synchronized from the tenant identity, so the authoritative user principal name must be updated at its source. The existing identity object remains the same, preserving its directory object identifier and the corresponding Dataverse system-user relationship. Consequently, record ownership, activity history, audit associations, and security-role assignments are not replaced simply because the sign-in name changes. Administrators should allow synchronization to complete and then verify the updated username and mailbox information in the Power Platform environment. Creating a new user would risk separating the historical record from the new identity and would require reassignment work. The scenario asks for a name change without losing application history, which is precisely why the existing directory account must be modified instead of replacing the Dataverse user. This aligns with the Study Guide's security and identity collaboration expectations and its ''configure security'' objective for Dataverse-backed applications. The proposed Microsoft 365 administrator action therefore meets the goal.
Study Guide reference/topic: ''Build data models --- Configure security.'' AB-410 Study Guide | Microsoft Learn technical reference
Currently there are no comments in this discussion, be the first to comment!