AZ-400 Develop a security and compliance plan Practice Question
You need to ensure that only authorized users can access the Azure DevOps organization. Which identity provider should you configure for single sign-on (SSO)?
⚠ Common exam trap
It's easy for candidates to confuse personal Microsoft accounts (MSA) or external identity providers like Google Workspace as valid SSO options, but Azure DevOps SSO exclusively requires a Microsoft Entra ID tenant for organizational access control.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Microsoft Entra ID
Microsoft Entra ID (formerly Azure AD) is the required identity provider for configuring single sign-on (SSO) for Azure DevOps organizations. Azure DevOps relies on Entra ID to authenticate users and enforce conditional access policies, ensuring only authorized identities from your tenant can sign in. This integration also supports SAML-based SSO and OAuth 2.0 flows, making it the native and only supported IdP for Azure DevOps SSO.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Microsoft Entra ID
Why this is correct
Microsoft Entra ID (formerly Azure AD) is the native identity provider for Azure DevOps, enabling enterprise-grade SSO, conditional access, and multi-factor authentication. It is the only supported option for centrally managing user permissions and access control across an Azure DevOps organization, making it the correct choice.
- ✗
Google Workspace
Why it's wrong here
Google Workspace is not a supported identity provider for Azure DevOps; Azure DevOps only accepts Microsoft Entra ID, personal Microsoft Accounts, and external users invited via Entra B2B collaboration. Google identities cannot be used for authentication, so this option is incorrect.
- ✗
Microsoft account (MSA)
Why it's wrong here
Microsoft accounts (MSA) are intended for personal use and do not support enterprise SSO or centralized access control in Azure DevOps. While individual users can sign in with an MSA, it lacks the directory-based management, conditional access, and group-based permission features provided by Microsoft Entra ID, making it unsuitable for this scenario.
- ✗
GitHub ID
Why it's wrong here
GitHub ID is not supported as an identity provider for Azure DevOps; it is used for GitHub authentication only. Azure DevOps requires Microsoft Entra ID or Microsoft accounts for authentication, so GitHub IDs cannot ensure authorized user access, making this option incorrect.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Azure DevOps
Azure DevOps is a Microsoft service that provides development tools for planning, building, testing, and deploying software applications using automated pipelines and collaboration features.
Key term
DevOps
DevOps is a set of practices that combines software development (Dev) and IT operations (Ops) to shorten the development lifecycle and deliver high-quality software continuously.
About these practice questions
Courseiva writes every AZ-400 question from scratch — 823 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.