The last sync time is displayed with the Entra ID header. You can rely on the auto-sync, or trigger an on-demand sync.
Auto-sync users
When you create an Entra ID mapping, inSync scans your Entra ID and performs the following actions:
Imports any new user added to Entra ID which matches the Entra ID mapping criteria and creates a new user in inSync. Auto-import of users is by default configured while creating the Entra ID mapping.
Updates user details of users managed using Entra ID.
š Note
User imports are processed on a scheduled basis. After being added to Entra ID, users will be imported within 24 hours. If some users are not imported in the current schedule, they will be imported in the next schedule.
Sync users on-demand
From the Users page select User Provisioning from the left pane.
On the Entra ID Deployment page, click the three-dot menu and then click Sync Users.
A Mapping is created, and it will import the pending users. This is because when a new mapping is created, the Delta Token is created again and this allows existing users to sync as per the defined mappings. The Delta Token is used to import new users from Entra ID or the users that have been modified in Entra ID since the last mapping was created. So, the users who have not been changed in Entra ID will not get imported into Druva until a new Delta Token has been created.
We can use Microsoft Graph Explorer: https://developer.microsoft.com/en-us/graph/graph-explorer to run the below API
https://graph.microsoft.com/beta/users/delta/?$filter=id eq '81d64c9e-6ba8-4686-9eda-5c7f1da41f89'Where the above '81d64c9e-6ba8-4686-9eda-5c7f1da41f89' is the object Id of the user in Entra ID.
š Note
inSync supports only those Azure attributes that are supported by Graph API and return in the response.
On-demand, sync will not begin if already another sync is in progress.
If the licenses have expired, the '
Sync Users' option will not be visible, and scheduled user imports will not work.
Syncing users with domain changes
After synchronization with the IDP, the Druva database is updated with the latest user information, including email addresses, User Principal Names (UPNs), and other relevant details sourced from 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.