Working of staging server.

%3CLINGO-SUB%20id%3D%22lingo-sub-1848354%22%20slang%3D%22en-US%22%3EWorking%20of%20staging%20server.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1848354%22%20slang%3D%22en-US%22%3E%3CP%3EHello!%3C%2FP%3E%3CP%3EWe%20have%20two%20Azure%20AD%20connect%20servers%20Main%20and%20Staging.%20We%20plan%20to%20use%20staging%20server%20only%20in%20failover%20cases.%20In%20Azure%20AD%20connect%20we%20use%20positive%20filtering%20and%20synchronize%20only%20selected%20accounts%20by%20its%20attributes.%20During%20testing%20i%20noticed%20that%20main%20server%20can%20synchronize%20user%20when%20attribute%20is%20assigned%20and%20delete%20account%20from%20Azure%20when%20this%20attribute%20is%20deleted%20from%20the%20user.%20But!%20When%20if%20i%20assign%20attribute%2C%20synchronize%20user%20and%20change%20server%20from%20main%20to%20staging%20server%20user%20will%20not%20be%20deleted%20automatically%20after%20attributes%20will%20be%20deleted%20from%20the%20account.%20This%20is%20normal%20work%20of%20staging%20server%3F%20I%20think%20its%20because%20of%20different%20databases%2C%20where%20history%20of%20changes%20are%20store.%20How%20we%20can%20avoid%20such%20situations%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1848354%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EStaging%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESynchronize%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Contributor

Hello!

We have two Azure AD connect servers Main and Staging. We plan to use staging server only in failover cases. In Azure AD connect we use positive filtering and synchronize only selected accounts by its attributes. During testing i noticed that main server can synchronize user when attribute is assigned and delete account from Azure when this attribute is deleted from the user. But! When if i assign attribute, synchronize user and change server from main to staging server user will not be deleted automatically after attributes will be deleted from the account. This is normal work of staging server? I think its because of different databases, where history of changes are store. How we can avoid such situations?

0 Replies