The answer is to enable trust for multi-factor authentication from the partner tenant under inbound trust settings. This configuration is correct because cross-tenant trust MFA for B2B allows Azure AD to accept the partner tenant’s MFA claims, eliminating redundant MFA prompts for users who already authenticated in their home directory. On the AZ-500 exam, this scenario tests your understanding of cross-tenant access settings as a security control for B2B collaboration, often appearing as a distractor against options like conditional access policies or external identities settings. A common trap is confusing inbound trust (trusting the partner’s MFA) with outbound trust (having your MFA trusted by the partner); remember that you configure inbound trust for the partner tenant to honor their MFA claims. A useful memory tip is “inbound trust, inbound MFA”—you trust the MFA coming into your tenant from the partner, so your users don’t re-authenticate.
AZ-500 Manage identity and access Practice Question
This AZ-500 practice question tests your understanding of manage identity and access. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company has a partner organization in another Azure AD tenant. They want to allow users from the partner tenant to access their Azure resources through Azure AD B2B collaboration. They also want the partner's Multi-Factor Authentication (MFA) claims to be trusted when partner users access their resources, so that they do not need to perform MFA again. Which configuration in cross-tenant access settings should they enable?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Trust multi-factor authentication from the partner tenant (inbound trust).
Option A is correct because cross-tenant access settings in Azure AD allow you to configure inbound trust for MFA from an external Azure AD tenant. When enabled, Azure AD B2B collaboration will accept the partner tenant's MFA claims, so partner users who have already satisfied MFA in their home tenant will not be prompted again when accessing your resources. This is configured under 'Cross-tenant access settings' > 'Inbound trust settings' for the specific partner tenant.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Trust multi-factor authentication from the partner tenant (inbound trust).
Why this is correct
This setting accepts MFA claims from the partner tenant, avoiding redundant MFA prompts.
Related concept
Read the scenario before looking for a memorised answer.
✗
Trust device compliance from the partner tenant.
Why it's wrong here
Device compliance trust is for device-based conditional access, not MFA claims.
✗
Enable a Conditional Access policy that grants access to the partner tenant.
Why it's wrong here
Conditional Access policies apply to users in your tenant, not directly to external MFA trust.
✗
Configure identity synchronization with the partner tenant.
Why it's wrong here
Identity synchronization is used for B2B direct connect, not for trusting MFA claims.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse Conditional Access policies with cross-tenant trust settings, thinking they can use a Conditional Access policy to 'trust' external MFA, when in fact the trust must be explicitly configured in the cross-tenant access settings for inbound MFA claims.
Detailed technical explanation
How to think about this question
Under the hood, when inbound MFA trust is enabled, Azure AD evaluates the 'MFA' claim in the partner user's token (issued by the partner's Azure AD) and treats it as if the user performed MFA in the resource tenant. This is based on the SAML/WS-Fed assertion of authentication strength, and the resource tenant's Conditional Access policies will see the user as having satisfied MFA. In a real-world scenario, if the partner tenant uses a third-party MFA provider, the trust setting still works as long as the partner tenant marks the user as MFA-strong authenticated in the token.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-500 question in full detail.
Manage identity and access — This question tests Manage identity and access — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Trust multi-factor authentication from the partner tenant (inbound trust). — Option A is correct because cross-tenant access settings in Azure AD allow you to configure inbound trust for MFA from an external Azure AD tenant. When enabled, Azure AD B2B collaboration will accept the partner tenant's MFA claims, so partner users who have already satisfied MFA in their home tenant will not be prompted again when accessing your resources. This is configured under 'Cross-tenant access settings' > 'Inbound trust settings' for the specific partner tenant.
What should I do if I get this AZ-500 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-500 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-500 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.