Can You Update a Model-Driven App Sign-In Name in Dataverse?
Short answer
B Changing the username in the app's Dataverse user record fails; the sign-in name is read-only and synced from Microsoft Entra ID, so change it in Microsoft 365.
Question
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?
Key Takeaways
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.
Common mistake: 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.
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
This link opens the official vendor documentation in a new tab.
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?
Will changing the sign-in name in Microsoft 365 preserve the app history?
Discussion 2 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 2
-
49c9343 👍 1 Answered BIn a model-driven app, the User record (the systemuser table) is synced from Microsoft Entra ID. Identity fields such as the username or UPN, the full name and the primary email are read-only in Dataverse because they’re managed at the source. Even if you could edit the username in the app, the next sync from Entra ID would overwrite it. Changing it in Dataverse also wouldn’t change how Elisabeth signs in, because sign-in is handled by Entra ID, not by the app. So this solution doesn’t update her sign-in name.
-
seoyeon_01 👍 1Would someone be able to explain the reasoning behind this answer?
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.