Azure Active Directory insights

Okta Verify Enrollment QR Code Validity Window

Deactivated Active Directory users can still enroll in Okta Verify if their enrollment QR code was generated before deactivation, creating a security gap until QR code timeout.

Custom extensibility logic (Actions, Hooks, Rules, Custom DB connections) experiences throttling when concurrent in-flight requests exceed tenant limits, causing authentication delays and failures.

Azure AD authentication requests may fail when Auth0 rate limits are exceeded, particularly during peak load or batch operations. This causes authentication failures and service degradation.

802.1X Authentication Failures Breaking Client Access

Clients fail to connect when RADIUS authentication fails due to incorrect credentials, unreachable RADIUS servers, certificate validation issues, or Active Directory problems. Manifests as 'auth failure' errors in dashboard 802.1X tests.

Directory synchronization fails when Azure AD Connect cannot reach domain controllers or experiences connectivity loss. This prevents identity synchronization between on-premises AD and Azure AD.

Directory synchronization fails when credentials used by Azure AD Connect expire or lose required permissions, preventing object and attribute synchronization.

Directory synchronization stops when the SQL Server database used by Azure AD Connect runs out of space, potentially causing permanent database corruption and sync failures.