Azure Sync failing with DeltaLink error
This document explains why Azure synchronisation can fail with a DeltaLink age error, and how to restore successful synchronisation.
Overview
Activate Azure synchronisation relies on DeltaLink tokens to track incremental changes. If these tokens become stale, Azure sync will fail and report that a DeltaLink older than 30 days is not supported.
Cause
DeltaLink tokens are expected to remain current between synchronisation runs. If Azure sync has not completed successfully for an extended period, or tokens have become invalid, Activate is unable to continue with a delta-based sync.
Resolution
Force a full Azure synchronisation by removing the stored DeltaLink parameters.
Navigate to:
//Resources/ActiveDirectory/External Directories/Azure
Delete the following parameters:
- UserSync_Token
- RoleSync_Token
- GroupSync_Token
Removing these parameters causes Activate to perform a full synchronisation the next time Azure sync is run.
Recommended Follow-up
After deleting the tokens:
- Run the Azure sync manually to confirm it completes successfully
- Monitor the sync results to ensure users, roles, and groups are refreshed as expected
Manual synchronisation interactively refreshes the membership of the Azure Users role and validates that delta tracking has been re-established.
Operational Notes
- Ensure Azure sync runs regularly to prevent DeltaLink expiry
- Investigate and resolve recurring sync failures promptly to avoid repeated full synchronisations
- Full sync operations may take longer than delta syncs, depending on tenant size