-
Suggestion
-
Resolution: Fixed
-
19
-
Update :
The Custom Sync Interval for Azure AD Sync allows admins to configure how frequently automated user, group, and domain syncs run between Azure AD and Atlassian. Instead of the fixed 4-hour interval, admins can now select from 1, 2, 4, or 24 hours. This addresses customer friction by offering greater flexibility based on organizational needs.
-----------------------------------------------------------------------------------------------------------------
Problem Definition
The default sync interval of 4hrs is not configurable, and for some customers it is not frequent enough, or is too frequent
Suggested Solution
Allow customers to define a specific sync interval for Azure AD sync configuration, or introduce an API which could be used to trigger on-demand sync.
Why this is important
Admins have specific requirements in regards to provisioning/de-provisioning of their users
Workaround
After making a change in Azure AD, immediately navigate to your Atlassian organization Azure AD sync configuration page, and click "Sync now" to trigger a sync on demand.
- is related to
-
- Gathering Interest
[ACCESS-1426] Custom Azure AD sync interval
The Custom Sync Interval for Azure AD Sync allows admins to configure how frequently automated user, group, and domain syncs run between Azure AD and Atlassian. Instead of the fixed 4-hour interval, admins can now select from 1, 2, 4, or 24 hours. This addresses customer friction by offering greater flexibility based on organizational needs.
Yes, 4hrs is too infrequent. Configurable sync interval should have been there in the first place.
The Custom Sync Interval for Azure AD Sync allows admins to configure how frequently automated user, group, and domain syncs run between Azure AD and Atlassian. Instead of the fixed 4-hour interval, admins can now select from 1, 2, 4, or 24 hours. This addresses customer friction by offering greater flexibility based on organizational needs.