License editions: To understand the applicable license editions, see Plans & Pricing.
Overview
An administrator can anytime update the name or the email address associated with a user in inSync.
❗ Important
After updating a user's email address, the administrator must also reset the password for that user. If the password is not reset, the user cannot access the inSync Web or reactivate the inSync Client using a different account. For more information, see Reset the password for a user.
Procedure To update the name or email address of a user
On the inSync Management Console menu bar, click Users.
Click on a Name to view that user's details.
Under the Details tab, in the Summary area, click Edit.
On the Edit User window, update the Email address and/or the Name of the user as per your requirement.
Click Save.
If you have updated the email address, ensure you reset the password of the user. See Reset the password for a user for instructions.
Synchronize User with Domain Change
If the user's domain address is changed, after a synchronization with the Identity Provider (IDP), the Druva database is updated with the latest user information. This includes the user's updated email addresses, User Principal Names (UPNs), and other relevant details sourced from the IDP.
For example, if a user's email address changes from "abc@oldcompany.com" to "abc@newcompany.com" due to a change in the user's domain, the Druva database will be updated with the new email address after the synchronization with the IDP.
This synchronization process ensures that incremental backups for Exchange Online users continue to function correctly, even if their domain affiliations change, preventing backup failures due to such changes.
📝 Note
If a domain or username is changed for a user account, but a new account with the same name as the previously changed one is created before synchronization completes, a data mismatch can occur. This results in the new user’s data being backed up in the latest snapshot while the old user’s data remains in previous snapshots, leading to data from both users being present across different snapshots.
This solution targets the Exchange Online Graph client API and does not cover the legacy APIs.