Note: This question is part of a series of questions that present the same scenario.

Changing the username directly in the app’s Dataverse user record does not meet the goal. The application user entry is synchronized from Microsoft Entra ID and is not the authoritative place to change a person’s sign-in identity. A direct modification may be blocked, overwritten by synchronization, or leave the tenant sign-in name unchanged. The correct operation is to update the existing user account in Microsoft 365 or Microsoft Entra administration so the same directory object is retained and its new user principal name flows into the Power Platform environment. Retaining the object identity is what protects ownership and application history. The spelling difference in the proposed “Elizabeth” record also creates an additional risk of modifying the wrong identity. After the tenant update, administrators should verify synchronization and mailbox approval without creating a replacement user. The AB-410 profile expects collaboration with identity administrators for “roles, identity, and authentication,” and the data-model objective includes “configure security.” Because the proposed app-record edit bypasses the identity source, the answer is No.

Study Guide reference/topic: “Build data models — Configure security.” AB-410 Study Guide | Microsoft Learn technical reference