Issue Summary

We have identified a scenario where automated backup and restore processes can lead to the creation of duplicate user accounts. This occurs when a user's email address is updated, but a subsequent automated restore uses a backup file created before that change took place.

Steps to Reproduce

1. Enable Automation: Set up automatic backup and restore within the organization.

1. Update User Email: Change a user's email address (e.g., from test@abc.com to test@xyz.com) either manually or via an Identity Provider (IdP).

1. Backup Timing: Ensure a backup was captured while the user was still using the old email address.

1. Perform Restore: Run the restore process after the email update has been completed.

1. Result: The old email account is recreated in the organization, resulting in two separate accounts for the same user.

Note: This behavior is specifically observed when the domain claim settings for both the old and new email domains are set to Automatic within the organization.

Expected Results

The restore process should recognize the existing user identity and avoid recreating the old account, ensuring that no duplicate accounts are introduced into the Cloud environment after an email update.

Actual Results

The system recreates the user account using the old email address found in the backup file, leading to a duplicate identity for that user within the organization.

Workaround

To avoid the creation of duplicate accounts, you can temporarily opt out of automated restores. This prevents the system from automatically pulling in user data from older backups until the user directory is stabilized.