Can You Update a Model-Driven App Sign-In Name in Dataverse?
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: Change Elizabeth’s username in the user record for the app. Does the solution meet the goal?
Community Insight
Tests whether Dataverse user records can be used to change a sign-in name; the trap is treating the app's User Name field as editable when identity is mastered in Microsoft Entra ID.
In a model-driven app, changing a user's sign-in name in the Dataverse user record does not meet the goal because the username is synced from Microsoft Entra ID and read-only; the correct fix is in Microsoft 365.
Answering Yes and editing the User Name field in the app's user record; that field is read-only and any local change would be overwritten by Entra ID sync.
Community Discussion (2 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The solution says to change Elisabeth's username in the app's user record. In Dataverse, the user record (systemuser table) is synced from Microsoft Entra ID, and identity fields such as the username/UPN, full name, and primary email are read-only in the app. Because the sign-in name is mastered in Entra ID, editing it in the model-driven app is not supported and would not persist through the next sync. The supported path is to change the sign-in name in Microsoft 365 admin center/Entra ID; because Dataverse links the user record by object ID, the same systemuser record keeps its application history. Therefore the proposed solution does not meet the goal, so B is correct.Why the Other Options Are Wrong
A (Yes) is wrong because it assumes the User Name field in the model-driven app is editable and authoritative; it is not, and the next Entra ID sync would overwrite any local change. Even if a local edit temporarily appeared, it would not change the user's actual sign-in name. The question's goal is to update the sign-in name without losing history, which requires the identity change at the source (Microsoft 365/Entra ID), not in the app's user record.Community Comment Notes
Community member 49c9343 correctly explains that the systemuser record is synced from Microsoft Entra ID and that fields like the username/UPN are "read-only in Dataverse" and would be overwritten by the next sync. Their answer B matches the supported behavior. seoyeon_01 asked for the reasoning behind the answer, which this breakdown provides: the fix belongs in Entra ID, not the app's user record.Official Reference
Exam Strategy
When a scenario asks you to update a sign-in name in Power Platform, check whether the solution edits Dataverse instead of Entra ID; Dataverse identity fields are read-only. The correct administrative action is almost always in Microsoft 365 admin center, which preserves the same user record and history.
Frequently Asked Questions
Why can't I edit the User Name field in a Dataverse user record?
Identity fields such as the username/UPN are synced from Microsoft Entra ID and read-only in Dataverse, so the field cannot be changed in the app.
Will changing the sign-in name in Microsoft 365 preserve the app history?
Yes. Dataverse links the systemuser record by object ID, so updating the UPN in Entra ID keeps the same user record and its app history.