To use the authentication method "Device Compliance (with Workspace ONE UEM)", where in Workspace ONE Access must it be enabled first to establish the communication with Workspace ONE UEM?

Question

Options

• AConnector Authentication Methods
• BIdentity Providers
• CConnectors
• DHub Configuration
• EUEM Integration
• FDirectories

• B
  3% (1)
• C
  10% (3)
• E
  83% (25)
• F
  3% (1)

Explanation

UEM Integration (E) is the correct answer because the "Device Compliance (with Workspace ONE UEM)" authentication method requires you to first configure the UEM Integration settings in Workspace ONE Access - this is where you provide the UEM tenant URL and API credentials to establish the trust and communication channel between the two products.

Why the distractors are wrong:

• A (Connector Authentication Methods) - this is where you enable or configure authentication methods after the integration is already set up, not where UEM connectivity is established.
• B (Identity Providers) - Identity Providers define how users authenticate (SAML, etc.), not how device compliance data is sourced from UEM.
• C (Connectors) - Connectors handle directory sync and on-prem authentication flows; they are not the integration point for UEM.
• D (Hub Configuration) - Hub Configuration relates to the Intelligent Hub app experience and notification settings, not UEM API connectivity.
• F (Directories) - Directories is for configuring LDAP/AD user sources, unrelated to UEM compliance checks.

Memory tip: Think of it as "you must integrate before you can authenticate" - UEM Integration is the handshake that has to happen first, and it lives under its own dedicated section precisely because it's a prerequisite for everything UEM-related in Workspace ONE Access.

No community discussion yet for this question.