Back to All Scenarios
PASSEDcloud / azure_ad_connect_sync_loop
Azure AD Connect Sync Loop
Azure AD Connect enters a synchronization loop where the delta sync cycle never completes, continuously restarting. Password hash synchronization stops working, and on-premises changes are not reflecting in Azure AD.
Pattern
AZURE_CLOUD
Severity
CRITICAL
Confidence
85%
Remediation
Remote Hands
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | AZURE_CLOUD | AZURE_CLOUD | |
| Severity Assessment | CRITICAL | CRITICAL | |
| Incident Correlation | Yes | 5 linked | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Remote Hands — Corax contacts on-site support via call, email, or API |
Scenario Conditions
Azure AD Connect 2.1.x. Delta sync cycle never completing. Sync scheduler restarting every 3 minutes. Password hash sync broken. On-premises user changes not syncing to Azure AD. Conditional access policies affected by stale data.
Injected Error Messages (1)
Azure AD Connect sync loop detected — delta sync cycle failing and restarting every 3 minutes, azure ad synchronization not completing, password hash sync broken for 6 hours, on-premises user attribute changes not reflecting in Azure AD, azure ad conditional access policies operating on stale data, event ID 6100: sync cycle stopped unexpectedly
Neural Engine Root Cause Analysis
Azure AD Connect is experiencing a sync loop where delta synchronization cycles are failing and automatically restarting every 3 minutes (Event ID 6100). This indicates either corrupted sync metadata, conflicting object changes, connectivity issues to Azure AD, or service account permission problems. The 6-hour duration suggests this is not a transient network issue but likely a persistent configuration or data corruption problem that requires service intervention.
Remediation Plan
1. Check Azure AD Connect service status and restart ADSync service if needed 2. Review Application Event Logs for detailed sync errors and conflicting objects 3. Run 'Start-ADSyncSyncCycle -PolicyType Full' to force full sync and clear delta issues 4. Verify Azure AD service account permissions and connectivity 5. Check for corrupted metaverse objects using Synchronization Service Manager 6. If corruption detected, consider exporting sync rules, clearing sync database, and re-initializing sync
Tested: 2026-03-30Monitors: 1 | Incidents: 1Test ID: cmnck10y5063zobqeu98f7plr