Why Active Directory changes take time to reach Opensense
Overview
Section titled “Overview”Opensense syncs user data from Azure Active Directory (Entra ID) automatically, twice a day. A change you make in your on-premises Active Directory first has to reach Azure AD through your AD Connect tool, and that delay depends on how often AD Connect is set to sync and on the size of your organization. Larger organizations take longer to sync. Without a manual sync, updates typically take 24 to 72 hours to show in the Opensense portal.
- Active Directory
- On-premises directory, on a Windows Server.
- Azure Active Directory
- Cloud-based directory. Microsoft renamed it Entra ID, so where this article says Azure, it also means Entra ID.
Speeding up the sync
Section titled “Speeding up the sync”To see a change in Opensense sooner:
- In your AD Connect tool, force a sync to the cloud, so the change reaches Azure AD.
- In Opensense, run a manual sync.
Running a manual sync in Opensense
Section titled “Running a manual sync in Opensense”- Open the Signatures menu, and select Users & Compliance.
- On the left side of the page, find Sync Tools, and click its blue plus icon
to open it. - Under Office 365 (Azure) Directory Sync, sync all the choices. Sync Groups first, then Users. The choices you see depend on your configuration.
- Wait for the sync to finish before you refresh the page. It can take some time, depending on the number of users.
- Refresh your browser. The new data appears in Users & Compliance.
What’s next
Section titled “What’s next”- Syncing Active Directory attributes to Entra ID (directory extensions): sync attributes that exist only in on-premises Active Directory.
- How often Opensense syncs user data: how often Opensense syncs your directory.