Azure Active Directory B2B collaboration FAQs

These frequently asked questions (FAQs) about Azure Active Directory (Azure AD) business-to-business (B2B) collaboration are periodically updated to include new topics.


Can we customize our sign-in page so it's more intuitive for our B2B collaboration guest users?

Absolutely, see our blog post about this feature. For more information about how to customize your organization's sign-in page, see Add company branding to sign in and Access Panel pages.

Can B2B collaboration users access SharePoint Online and OneDrive?

Yes. However, the ability to search for existing guest users in SharePoint Online by using the people picker is Off by default. To turn on the option to search for existing guest users, set ShowPeoplePickerSuggestionsForGuestUsers to On. You can turn this setting on either at the tenant level or at the site collection level. You can change this setting by using the Set-SPOTenant and Set-SPOSite cmdlets. With these cmdlets, members can search all existing guest users in the directory. Changes in the tenant scope don't affect SharePoint Online sites that have already been provisioned.

Can B2B collaboration users access Power BI content?

Yes, you can distribute Power BI content to external guest users using B2B collaboration. To share Power BI content across Microsoft clouds, you can use Microsoft cloud settings to establish mutual B2B collaboration between your cloud and an external cloud.

Is the CSV upload feature still supported?

Yes. For more information about using the .csv file upload feature, see this PowerShell sample.

How can I customize my invitation emails?

You can customize almost everything about the inviter process by using the B2B invitation APIs.

Can guest users reset their multifactor authentication method?

Yes. Guest users can reset their multifactor authentication method the same way that regular users do.

Which organization is responsible for multifactor authentication licenses?

The inviting organization performs multifactor authentication. The inviting organization must make sure that the organization has enough licenses for their B2B users who are using multifactor authentication.

What if a partner organization already has multifactor authentication set up? Can we trust their multifactor authentication?

Cross-tenant access settings let you trust multifactor authentication and device claims (compliant claims and hybrid Azure AD joined claims) from other Azure AD organizations.

How many organizations can I add in cross-tenant access settings?

Cross-tenant access settings are a policy in the directory that stores your settings for how you collaborate with other organizations. This policy file has a 25kb size limit and once it is maxed out, no additional organizations or changes can be made that would further increase the file size. Due to how we store the content in this policy, there is no defined limit of organizations you can add in cross-tenant access settings. If you need to apply settings to a large number of organizations, we recommend implementing those settings as your default settings. Follow the steps to calculate the current size of your policy and determine whether you are close to hitting the 25kb file size limit.

How can I use delayed invitations?

An organization might want to add B2B collaboration users, provision them to applications as needed, and then send invitations. You can use the B2B collaboration invitation API to customize the onboarding workflow.

Can I make guest users visible in the Exchange Global Address List?

Yes. By default, guest objects aren't visible in your organization's global address list, but you can use Azure Active Directory PowerShell to make them visible. For details, see "Add guests to the global address list" in the Microsoft 365 per-group guest access article.

Can I make a guest user a limited administrator?

Absolutely. For more information, see Adding guest users to a role.

Does Azure AD B2B collaboration allow B2B users to access the Azure portal?

Unless a user is assigned the role of limited administrator, B2B collaboration users won't require access to the Azure portal. However, B2B collaboration users who are assigned the role of limited administrator can access the portal. Also, if a guest user who isn't assigned one of these admin roles accesses the portal, the user might be able to access certain parts of the experience. The guest user role has some permissions in the directory.

Can I block access to the Azure portal for guest users?

Yes, you can create a Conditional Access policy that blocks all guest and external users from accessing the Azure portal. When you configure this policy, be careful to avoid accidentally blocking access to members and admins.

  1. Sign in to your Azure portal as a security administrator or a Conditional Access administrator.
  2. In the Azure portal, select Azure Active Directory.
  3. Under Manage, select Security.
  4. Under Protect, select Conditional Access. Select New policy.
  5. On the New page, in the Name textbox, enter a name for the policy (for example "Block guests from accessing the portal").
  6. Under Assignments, select Users and groups.
  7. On the Include tab, choose Select users and groups, and then select All guest and external users (Preview).
  8. Select Done.
  9. On the New page, in the Assignments section, select Cloud apps or actions.
  10. On the Cloud apps or actions page, choose Select apps, and then choose Select.
  11. On the Select page, choose Microsoft Azure Management, and then choose Select.
  12. On the Cloud apps or actions page, select Done.

Does Azure AD B2B collaboration support multifactor authentication and consumer email accounts?

Yes. Multifactor authentication and consumer email accounts are both supported for Azure AD B2B collaboration.

Do you support password reset for Azure AD B2B collaboration users?

If your Azure AD tenant is the home directory for a user, you can reset the user's password from the Azure portal. But you can't directly reset a password for a guest user who signs in with an account that's managed by another Azure AD directory or external identity provider. Only the guest user or an administrator in the user’s home directory can reset the password. Here are some examples of how password reset works for guest users:

  • Guest users in an Azure AD tenant that are marked "Guest" (UserType==Guest) can't register for SSPR through These type of guest user can only perform SSPR through

  • Guest users who sign in with a Microsoft account (for example can reset their own passwords using Microsoft account self-service password reset (SSPR). See How to reset your Microsoft account password.

  • Guest users who sign in with a Google account or another external identity provider can reset their own passwords using their identity provider's SSPR method. For example, a guest user with the Google account can reset their password by following the instructions in Change or reset your password.

  • If the identity tenant is a just-in-time (JIT) or "viral" tenant (meaning it's a separate, unmanaged Azure tenant), only the guest user can reset their password. Sometimes an organization will take over management of viral tenants that are created when employees use their work email addresses to sign up for services. After the organization takes over a viral tenant, only an administrator in that organization can reset the user's password or enable SSPR. If necessary, as the inviting organization, you can remove the guest user account from your directory and resend an invitation.

  • If the guest user's home directory is your Azure AD tenant, you can reset the user's password. For example, you might have created a user or synced a user from your on-premises Active Directory and set their UserType to Guest. Because this user is homed in your directory, you can reset their password from the Azure portal.

Does Microsoft Dynamics 365 provide online support for Azure AD B2B collaboration?

Yes, Dynamics 365 (online) supports Azure AD B2B collaboration. For more information, see the Dynamics 365 article Invite users with Azure AD B2B collaboration.

What is the lifetime of an initial password for a newly created B2B collaboration user?

Azure AD has a fixed set of character, password strength, and account lockout requirements that apply equally to all Azure AD cloud user accounts. Cloud user accounts are accounts that aren't federated with another identity provider, such as

  • Microsoft account
  • Facebook
  • Active Directory Federation Services
  • Another cloud tenant (for B2B collaboration)

For federated accounts, password policy depends on the policy that is applied in the on-premises tenancy and the user's Microsoft account settings.

An organization might want to have different experiences in their applications for tenant users and guest users. Is there standard guidance for this? Is the presence of the identity provider claim the correct model to use?

A guest user can use any identity provider to authenticate. For more information, see Properties of a B2B collaboration user. Use the UserType property to determine user experience. The UserType claim isn't currently included in the token. Applications should use the Microsoft Graph API to query the directory for the user, and to get the UserType.

Where can I find a B2B collaboration community to share solutions and to submit ideas?

We're constantly listening to your feedback, to improve B2B collaboration. Please share your user scenarios, best practices, and what you like about Azure AD B2B collaboration. Join the discussion in the Microsoft Tech Community.

We also invite you to submit your ideas and vote for future features at B2B Collaboration Ideas.

Can we send an invitation that is automatically redeemed, so that the user is just “ready to go”? Or does the user always have to click through to the redemption URL?

You can invite other users in the partner organization by using the UI, PowerShell scripts, or APIs. You can then send the guest user a direct link to a shared app. In most cases, there's no longer a need to open the email invitation and click a redemption URL. See Azure Active Directory B2B collaboration invitation redemption.

How does B2B collaboration work when the invited partner is using federation to add their own on-premises authentication?

If the partner has an Azure AD tenant that is federated to the on-premises authentication infrastructure, on-premises single sign-on (SSO) is automatically achieved. If the partner doesn't have an Azure AD tenant, an Azure AD account is created for new users.

I thought Azure AD B2B didn't accept and email addresses, and that B2C was used for those kinds of accounts?

We are removing the differences between B2B and business-to-consumer (B2C) collaboration in terms of which identities are supported. The identity used isn't a good reason to choose between using B2B or using B2C. For information about choosing your collaboration option, see Compare B2B collaboration and B2C in Azure Active Directory.

Can an Azure AD B2C local account be invited to an Azure AD tenant for B2B collaboration?

No. An Azure AD B2C local account can only be used to sign in to the Azure AD B2C tenant. The account can't be used to sign into an Azure AD tenant. Inviting an Azure AD B2C local account to an Azure AD tenant for B2B collaboration isn't supported.

What applications and services support Azure B2B guest users?

All Azure AD-integrated applications can support Azure B2B guest users, but they must use an endpoint set up as a tenant to authenticate guest users. You might also need to customize the claims in the SAML token that is issued when a guest user authenticates to the app.

Can we force multifactor authentication for B2B guest users if our partners don't have multifactor authentication?

Yes. For more information, see Conditional Access for B2B collaboration users.

In SharePoint, you can define an "allow" or "deny" list for external users. Can we do this in Azure?

Yes. Azure AD B2B collaboration supports allowlists and blocklists.

What licenses do we need to use Azure AD B2B?

For information about what licenses your organization needs to use Azure AD B2B, see External Identities pricing.

What happens if I invite a user whose email and UPN don’t match?

It depends. By default, Azure AD only allows UPN for login ID. When UPN and email are the same, Azure AD B2B invitations and subsequent sign-ins work as expected. However, issues can arise when a user’s email and UPN don’t match, and the email is used instead of the UPN to sign in. When a user is invited with a non-UPN email, they will be able to redeem the invitation if they redeem using the email invitation link, but redemptions via a direct link will fail. However, even if the user successfully redeems the invitation, subsequent sign-in attempts using the non-UPN email will fail unless the identity provider (either Azure AD or a federated identity provider) is configured to allow email as an alternative login ID. This issue can be mitigated by:

  1. Enabling email as an alternate login ID in the invited/home Azure AD tenant
  2. Enabling the federated identity provider to support email as login ID (if Azure AD is federated to another identity provider) or
  3. Instructing the user to redeem/sign-in using their UPN.

To avoid this issue entirely, administrators should ensure users’ UPN and email are the same value.

Screenshot shows the flow for guest redemption.

Screenshot shows the flow for subsequent sign-ins.


Invitations and redemptions being sent across Microsoft clouds must use UPN. Email is not supported at this time. For example, if a user from a US Government tenant is invited to a Commercial tenant, the user must be invited using their UPN.

Instant-on: What can cause replication latency?

In the B2B collaboration flows, we add users to the directory and dynamically update them during invitation redemption, app assignment, and so on. The updates and writes ordinarily happen in one directory instance and must be replicated across all instances. Replication is completed once all instances are updated. Sometimes when the object is written or updated in one instance and the call to retrieve this object is to another instance, replication latencies can occur. If that happens, refresh or retry to help. If you are writing an app using our API, then retries with some back-off is a good, defensive practice to alleviate this issue.