Quick Answer
The scheduled synchronization time is based on the local timezone of the administrator configuring it.
Behind the scenes, Pinnacle converts that local time to UTC before storing it in the database. This ensures the scheduler has a single, consistent time standard regardless of where it is running.
For example, if an administrator in the US Central Time Zone schedules the synchronization for 11:00 PM, Pinnacle converts and stores this as 04:00 UTC. When the scheduler runs, it uses the UTC value, which corresponds to 11:00 PM Central Time.
Similarly, if an administrator in Singapore (UTC+8) configures the synchronization for 8:00 AM, the system stores this as 00:00 UTC, and the synchronization will run at 8:00 AM Singapore time.
What This Article Helps With
Entra ID synchronization settings within the Admin Portal. Admins can specify the exact time the synchronization should take place. This article helps you understand how our system interprets the time setting vs the time zone your system is in.
Helpful Tips
- Tip: If administrators in different regions configure the schedule, remember that each administrator sees and enters the time in their own local timezone. The system stores the schedule internally in UTC.
- Tip: If your organization has administrators in multiple time zones, agree on who will configure the synchronization schedule to ensure everyone has the same expectation of when it will run.
Common Questions
Q. Why is the time stored differently in the database?
The scheduler stores all times in UTC to provide a consistent scheduling mechanism across different regions and servers. This is expected behaviour.
Q. Will my synchronization still run at the time I selected?
Yes. Although the time is stored in UTC, the synchronization runs at the equivalent time for the timezone in which it was configured.
Q. I'm in Singapore (UTC+8). If I schedule the sync for 8:00 AM, when is it stored?
It is stored as 00:00 UTC and will run at 8:00 AM Singapore time.
Q. What happens during daylight saving time (DST)?
The scheduler uses the timezone from the administrator configuring the schedule and converts it to UTC. When daylight saving begins or ends, the stored UTC time may change so that the synchronization continues to run at the configured local time.
Q. Can I enter a UTC time instead of my local time?
No. Always enter the time you want the synchronization to run in your local timezone. Pinnacle performs the UTC conversion automatically.
Q. Can administrators in different countries see different times?
Yes. Administrators will see and configure the schedule in their own local timezone, while Pinnacle stores the schedule internally in UTC.
Q. Why does Pinnacle use UTC?
Using UTC avoids ambiguity between time zones and daylight saving changes, ensuring the scheduler uses a consistent internal time regardless of where the application or database is hosted.
Will this affect existing users?
The configured synchronization time determines when Pinnacle automatically imports changes from Microsoft Entra ID, such as new users, updated user information, group membership changes, or account status updates.
End users are not affected by the timezone conversion itself. They will simply see directory changes reflected in Pinnacle after the next scheduled synchronization has completed.
The only practical impact is timing:
If the sync is scheduled for 8:00 AM, changes made at 7:50 AM will typically appear shortly after 8:00 AM.
- Changes made at 8:10 AM won't be reflected until the following scheduled synchronization (unless a manual sync is performed).
Still Need Help