# Identity Provider Incidents in Hexnode UEM | Directory Sync & Security

**Architecture Snapshot:** The **Identity Providers** subtab monitors the reliability of directory integrations. It flags synchronization failures and structural changes (deletions) between Hexnode UEM and connected services like Active Directory, Okta, and Google Workspace, ensuring uninterrupted user provisioning and access management.

Directory Integration and Auth Reliability Logic
------------------------------------------------

Identity Provider incidents serve as an early-warning system for authentication disruptions. By tracking the health of directory syncs, Hexnode ensures that the UEM console’s view of users, groups, and OUs remains consistent with the source of truth.

How to access Identity Provider Incidents?
------------------------------------------

To access the Identity Provider incidents:

1. Login to the Hexnode console.
2. Navigate to the **Incidents** tab.
3. Access the **Identity Providers** sub-tab.

Identity Provider Incident Sources Matrix
-----------------------------------------

SourceTechnical Scope and Security Impact**Failed Syncs**Categorized as **High severity**. Monitors synchronization failures for **Active Directory, Okta, Google Workspace,** and general domains. Failure prevents updated user data and group memberships from reflecting in Hexnode.**Recently Deleted**Audits the deletion of directory objects including **users, groups, organizational units (OUs), and domains**. Helps administrators maintain visibility over critical structural changes that could affect policy assignments and access.Strategic Value of IdP Monitoring
---------------------------------

- **Directory Consistency:** Ensures user and group data in Hexnode matches the external Identity Provider.
- **Access Governance:** Rapidly identifies structural changes (deletions) that impact resource availability.
- **Authentication Reliability:** Proactively identifies sync blockers before users encounter sign-in failures.

**Operational Use Case:** If a synchronization fails with **Active Directory**, Hexnode logs a *Failed Sync* incident. The administrator can address the connection issue before automated user provisioning or group-based policy deployments are disrupted.