Cross-tenant access settings for B2B collaboration apply only to Microsoft Entra ID tenants, not to Google or Microsoft accounts

Answer Correct answer: A — Cross-tenant access settings for B2B collaboration support only Microsoft Entra ID tenants as identity providers.

You have a Microsoft Entra tenant named contoso.com. You plan to collaborate with a partner organization that has a Microsoft Entra tenant named fabrikam.com. Fabrikam.com uses the following identity providers: • Google Cloud Platform (GCP) • Microsoft accounts • Microsoft Entra ID You need to configure the Cross-tenant access settings for B2B collaboration. Which identity providers support cross-tenant access?

  1. Microsoft Entra ID only Correct Answer
  2. GCP and Microsoft Entra ID only
  3. Microsoft accounts and Microsoft Entra ID only
  4. GCP, Microsoft accounts, and Microsoft Entra ID

Community Votes

A
59%
D
41%

59% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The distinction is between B2B collaboration (which can invite Google/Microsoft-account users) and cross-tenant access settings (which only govern Entra ID tenant-to-tenant trust). The question explicitly says 'cross-tenant access settings', so only Entra ID qualifies.

Cross-tenant access settings configure trust and access policies between Microsoft Entra ID organizations. They support only Microsoft Entra ID tenants as identity providers; Google Cloud (Google federation) and personal Microsoft accounts are not Entra tenants and cannot use cross-tenant access settings.

People pick D because Fabrikam uses GCP, Microsoft accounts, and Entra ID for B2B, but cross-tenant access settings are a tenant-to-tenant construct; Google and Microsoft accounts are not tenants and are excluded.

Community Discussion (14 comments)

Pamban 👍 5 Selected: D
I would go for D Link: https://learn.microsoft.com/en-us/entra/external-id/identity-providers
Hot_156 👍 2 Selected: A
The three of them can be granted access through B2B !!!!BUT!!!! not for cross-tenant access settings!
roky008 👍 1 Selected: A
Cross-tenant access settings for B2B collaboration in Microsoft Entra ID allow secure and managed collaboration between different Microsoft Entra tenants. However, only Microsoft Entra ID supports cross-tenant access settings. Other identity providers, such as Google Cloud Platform (GCP) and Microsoft accounts (personal accounts like Outlook.com or Hotmail.com), do not support cross-tenant access settings in Microsoft Entra ID.
ITFranz 👍 2 Selected: A
To support the Answer: fabrikam.com uses multiple identity providers (GCP, Microsoft accounts, and Microsoft Entra ID), only their Microsoft Entra ID identities will be able to leverage the cross-tenant access settings for B2B collaboration with your contoso.com tenant. Google Cloud Platform (GCP) and Microsoft accounts are not directly supported for cross-tenant access in this context. For cross-tenant access settings in B2B collaboration between your Microsoft Entra tenant (contoso.com) and the partner organization's tenant (fabrikam.com), only Microsoft Entra ID is supported as the identity provider. Cross-tenant access settings are specifically designed for collaboration between Microsoft Entra organizations. They allow you to configure inbound and outbound access policies, trust multifactor authentication (MFA), and device claims from other Microsoft Entra tenants. Answer = A
62Juan 👍 1 Selected: D
B2B collaboration lets you invite external partners to access your Microsoft, SaaS, or custom-developed apps. B2B collaboration is especially useful when the external partner doesn't use Microsoft Entra ID or it's not practical or possible to set up B2B direct connect. B2B collaboration allows external users to sign in using their preferred identity, including their Microsoft Entra account, consumer Microsoft account, or a social identity you enable such as Google. With B2B collaboration, you can let external users sign in to your Microsoft applications, SaaS apps, custom-developed apps, and so on. https://learn.microsoft.com/en-us/entra/external-id/b2b-direct-connect-overview
JBAnalyst 👍 1 Selected: D
For external Id : Ms entra id, a Microsoft email account , one time passcode via email of your choice , google, facebook , SAML, and I think apple too Not sure about apple though, read that somewhere
obaemf 👍 2 Selected: A
https://learn.microsoft.com/en-us/entra/external-id/cross-tenant-access-settings-b2b-collaboration
obaemf 👍 2
Answer: A Cross-tenant access settings is for B2B collaboration between Microsoft Entra organisations. https://learn.microsoft.com/en-us/entra/external-id/cross-tenant-access-settings-b2b-collaboration
nExoR 👍 1
"You need to configure the Cross-tenant access settings for B2B collaboration." - although Microsoft Account can share files with other providers, you can't set up any global settings/policies. each share must be separately configured during creation. thus C makes most sense - these are 'corporate solutions' giving ability to be configured (settings set).
pentium75 👍 1 Selected: A
"Cross-TENANT access" is about other [Entra] tenants. Of course you can establish trusts with Google Cloud etc., but you cannot grant access to the Google Cloud users already trusted by the other tenant.
ruscomike 👍 2 Selected: A
another not clear question: if the question is "You need to configure the Cross-tenant "access settings*" I will go for A, only Entra ID tenant supports cross-tenant access settings (like trust settings). If the question is "You need to configure the Cross-tenant access" I will go for D: I can create B2B configuration for all the listed providers
ruscomike 👍 1
another not clear question: if the question is "You need to configure the Cross-tenant "access settings*" I will go for A, only Entra ID tenant supports cross-tenant access settings (like trust settings). If the question is "You need to configure the Cross-tenant access" I will go for D: I can create B2B configuration for all the listed providers
JaridB 👍 1
D. GCP (Google Cloud Platform, referred to as Google federation), Microsoft accounts, and Microsoft Entra ID. - The identity providers that support cross-tenant access settings for B2B collaboration in Microsoft Entra include Microsoft Entra ID, Microsoft accounts, and Google federation. This means you can configure cross-tenant access to allow guest users to authenticate using their Microsoft Entra accounts, personal Microsoft accounts, or their Google accounts.
Apptech 👍 1
I go with C) GCP accounts are associated with Google Cloud services. they are not directly used for Microsoft Entra cross-tenant collaboration. Within a single tenant it is possible to invite a GCP user but it is not possible to be used for cross tenant scenarios

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Cross-tenant access settings manage how users in one Microsoft Entra ID organization collaborate with users in another Entra ID organization. They operate at the tenant level, so the only supported identity provider in this scenario is Microsoft Entra ID. (Option A)

Why the Other Options Are Wrong

  • Option B (GCP and Entra ID) incorrectly includes Google Cloud Platform; Google federation is not an Entra tenant and cannot be governed by cross-tenant access settings.
  • Option C (Microsoft accounts and Entra ID) incorrectly includes personal Microsoft accounts, which are not tenants.
  • Option D (all three) conflates B2B collaboration invitations (which can include Google/Microsoft accounts) with cross-tenant access settings (tenant-to-tenant only).

Community Comment Notes

Commenters clarified: 'Cross-TENANT access is about other [Entra] tenants. You cannot grant access to the Google Cloud users already trusted by the other tenant.' The official cross-tenant access documentation confirms only Entra ID is supported.

Official Reference

Related Analysis

← Back to AZ-500 Study Guide