Updating User Sign-In Name Without Losing History in Power Platform

AB-410 By islever Editorial Last updated

Implement business and process logic

Short answer

A Yes, updating the User Principal Name in the Microsoft 365 admin portal preserves the immutable Microsoft Entra Object ID, ensuring all application history remains linked to the user.

Question

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: Ask the Microsoft 365 administrator to sign in to the admin portal and change the user name.
Does the solution meet the goal?
  1. Yes Correct Answer
  2. No

Key Takeaways

Power Platform uses the immutable Microsoft Entra Object ID (GUID) for record ownership, not the mutable User Principal Name (UPN).

Learn why changing a user's UPN in Microsoft 365 does not affect Power Platform history due to immutable Object IDs. The correct answer is Yes (A).

Common mistake: Choosing 'No' by assuming that changing the username breaks historical data links. In reality, only the display/login string changes, while the internal Object ID reference remains intact.

Expert Analysis

The core of this question lies in understanding how Microsoft Dataverse and Power Platform identify users versus how Microsoft 365 manages identity.

Identity Stability via Object ID Power Platform applications (Model-Driven Apps) do not primarily track users by their User Principal Name (UPN). Instead, they link data records to the user's unique Microsoft Entra ID object identifier (a GUID). This identifier is immutable; it never changes, even if the user's UPN or display name is modified.

Impact of UPN Changes When a Microsoft 365 administrator updates a user's sign-in name (UPN) in the admin portal, the underlying Entra ID object remains the same. Consequently:

  1. The user retains access to all existing apps and solutions.
  2. All historical records (created, modified, owned) remain associated with that specific user because the foreign key references the stable Object ID, not the mutable UPN string.
  3. There is no loss of application history or data integrity.

Evaluating the Solution The proposed solution is to "Ask the Microsoft 365 administrator to sign in to the admin portal and change the user name." Since changing the UPN does not alter the Object ID, this action successfully updates the login identity while preserving all historical context. Therefore, the solution meets the goal.

Why 'No' is Incorrect Selecting 'No' implies that changing the UPN would break links to historical data or require complex migration steps. This is incorrect for standard Microsoft 365/Entra ID setups where the Object ID serves as the primary key for resource ownership.

Official Reference

https://learn.microsoft.com/en-us/power-platform/admin/manage-users-permissions

This link opens the official vendor documentation in a new tab.

Exam Strategy

Always distinguish between mutable attributes (like UPN or Display Name) and immutable identifiers (like Object IDs or GUIDs). When a question asks about preserving relationships or history after an identity change, look for mechanisms that rely on stable keys rather than human-readable names.

Frequently Asked Questions

What happens to Dataverse records if I change my email address?

Records remain linked to you because Dataverse uses your immutable Entra Object ID (GUID) for ownership, not your email address.

Can I rename myself directly in Power Apps without M365 Admin?

You can change your display name in Outlook or Teams, but to change your sign-in name (UPN), you must use the Microsoft 365 admin center.

More AB-410 FAQ →

Discussion 3 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 3

  1. aed747e 👍 2 Answered B
    Updating the User Principal Name in Microsoft 365 admin center updates the user's login identity while preserving their underlying Microsoft Entra Object ID. This preserves all historical record ownership and data within Dataverse automatically.
  2. seoyeon_01 👍 2
    I'm confused—why is this answer correct?
  3. FabiolaRT 👍 1 Answered A
    Answer: A. the Microsoft 365 admin portal updates the sign-in name while all related application history/records intac

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

How to Configure Manager and Position Hierarchy in Power Apps?

S-grade

Configure Business Process Flow Branching and Automation

S-grade

Preventing Table Display Name Changes During Promotion

S-grade

Configuring Visual Insights in Model-Driven Apps

S-grade

← Back to AB-410 Study Guide