Mismatching Core Identity Stores After Recovery!
summary
Recommends choosing the most recent backup and running a gap analysis against Entra ID before reconnecting, with concrete steps: disable synchronization before recovery, query Entra for hybrid objects, recreate placeholder AD objects, populate immutableID (MSDS‑ConsistencyGUID) and test sync. Uses tools like AADInternals and PowerShell, warns that Cloud Sync can hard‑delete groups (example: 12 users + 12 groups + 12 contacts → 36 deletions), and shows that rebuilding Connect Sync from a saved export plus PHS for auth lets users keep working.
AI-written summary · about
chapters (10)
- 0:00Active Directory recovery challenges
- 6:26Wrong AD backup sync issues
- 12:09Mismatched identities AD Entra ID
- 16:26Hybrid identity auth mechanisms
- 21:45Rebuilding Azure AD Connect Sync
- 27:11Connect Sync misconfigurations
- 31:02Gap analysis recreating objects
- 35:40Cloud Sync pitfalls recovery
- 38:49AD recovery recommendations
- 40:18Q&A
related talks
36mWhy You Should Avoid Identity Sync Like Wildfire?
53mThe Importance of Identity-Centric Security in 2024
47mSafeguarding The Security Posture Of Your AD, Pre-Attack And Post-Attack
32mRansomware, Risk, & Recovery: Protecting and Creating Resilience for Hybrid Active Directory
11mBuild identity into your apps within minutes!
50mAttacking and Defending the Microsoft Cloud (Office 365 & Azure AD)
50mHybrid Active Directory Attacks: Anatomy and Defenses
24mChaos to Control: Automating the Identity Life Cycle in the Cloud