An administrator noticed users are never disabled in the Workspace ONE UEM Console after they are disabled in Active Directory. What can be done to resolve the issue?

Question

Options

• AEnable custom attributes for user status.
• BEnable automatic sync for user status.
• CManually sync attributes.
• DEnable auto merge.

• B
  93% (14)
• D
  7% (1)

Explanation

Enabling automatic sync for user status (B) ensures Workspace ONE UEM continuously monitors and reflects changes made in Active Directory - when a user is disabled in AD, the sync propagates that status change to the UEM console automatically. Without this setting, UEM has no mechanism to pull real-time or scheduled status updates, so disabled accounts in AD remain active in UEM indefinitely.

Why the distractors are wrong:

• A (Custom attributes) - Custom attributes extend what data fields are imported, not whether status changes are reflected; adding attributes won't trigger disability propagation.
• C (Manual sync) - Manually syncing would work as a one-time fix but doesn't resolve the underlying issue of users never being disabled; it's not a sustainable solution.
• D (Auto merge) - Auto merge handles conflicting records between directory and UEM (e.g., duplicate accounts), not the synchronization of account status changes.

Memory tip: Think "status needs a sync" - the word status in the problem maps directly to automatic sync for user status. Whenever UEM isn't reflecting a state that AD already has, the answer involves syncing that state, not merging or adding attributes.

No community discussion yet for this question.