Question 890
A cloud account is unexpectedly duplicated after changing its on-premises UPN. What should the Microsoft 365 administrator implement to address this situation?
Explanation
Correct Answer
The matching Microsoft 365 administration decision is check sourceAnchor and matching attributes rather than assuming UPN alone defines identity. The underlying principle is Persistent matching identifiers are distinct from mutable sign-in names. Check: only the intended cloud object is associated with the local source.
Incorrect Answers
This other action addresses a different situation: a cloud-only user exists before corresponding local AD identity begins synchronizing. Its technical purpose is Matching avoids creating a duplicate cloud object with separate licenses and mailbox. The current task instead requires only the intended cloud object is associated with the local source.
Although relevant to a large OU filtering change would remove hundreds of already-synchronized users., it does not establish the requested outcome. Accidental scope removals can deprovision cloud identities. Here the measurable requirement is only the intended cloud object is associated with the local source.
This would focus on an on-premises user is deleted unexpectedly and the sync engine schedules deletion in Entra ID. rather than the present constraint. Sync exports can propagate unintended mass deletions. The required success state remains only the intended cloud object is associated with the local source.