Refer to the exhibit. An engineer must configure Cisco ThousandEyes SSO to use Microsoft Entra ID using the configuration shown in the exhibit. Which feature must be set to override to complete the…

Question

Options

• AService Provider Issuer
• BLogout Page URL
• CLogin Page URL
• DIdentity Provider Issuer

• A
  79% (34)
• B
  2% (1)
• C
  7% (3)
• D
  12% (5)

Explanation

When configuring ThousandEyes SSO with Microsoft Entra ID, the Service Provider Issuer field contains an Override toggle that must be enabled so you can manually specify the SP Entity ID (Application ID URI) that matches what is registered in the Entra ID enterprise application - without this override, ThousandEyes uses its default issuer value, which Entra ID will reject because the entity IDs won't match.

Why the distractors are wrong:

• B (Logout Page URL) - This is simply a URL field populated from Entra ID metadata; no override toggle is involved.
• C (Login Page URL) - This is the IdP-provided SAML endpoint you copy from Entra ID; it's a straightforward paste, not an override.
• D (Identity Provider Issuer) - This is the Entra ID entity ID you copy directly from the IdP metadata; ThousandEyes accepts it as-is with no override needed.

Memory tip: Think "SP must speak first" - the Service Provider Issuer is the one ThousandEyes controls, so it's the one that needs an override to align with what you registered in Entra ID. The IdP-side values (C, D) are just copied in; only the SP-side value needs to be customized.

No community discussion yet for this question.