Question 360
A proposed fix must be validated: An employee already uses a cloud-only Microsoft 365 mailbox, and a new on-premises AD account must be linked without creating a second user. How should the team validate that its change solved the stated problem?
Explanation
Correct Answer
The existing cloud user transitions to the intended synced object without a duplicate mailbox identity. The case concerns match an existing cloud account to an ad identity: An employee already uses a cloud-only Microsoft 365 mailbox, and a new on-premises AD account must be linked without creating a second user. Matching source and cloud objects is identity continuity work, not a bulk user recreation step. This answers the acceptance evidence for this change because it addresses the explicit constraint. The action being validated is: perform an approved matching procedure with a unique source identity before initial sync. The check must use the affected users, data, or devices.
Incorrect Answers
Hybrid UPN planning must reconcile on-premises naming with cloud verified domain requirements. The reason this does not settle the present case is the actual condition: Hybrid synchronization supports controlled object matching and requires avoiding duplicate source anchors.
Attribute export failures are often integrity conflicts rather than general network outages. The current corrective requirement is: Perform an approved matching procedure with a unique source identity before initial sync.
PTA is a cloud sign-in method with on-premises validation dependency, unlike PHS-only validation. The appropriate acceptance check is: The existing cloud user transitions to the intended synced object without a duplicate mailbox identity.