Policies for allowing guest access and B2B external user access
Article
This article discusses adjusting the recommended Zero Trust identity and device access policies to allow access for guests and external users that have a Microsoft Entra Business-to-Business (B2B) account. This guidance builds on the common identity and device access policies.
These recommendations are designed to apply to the starting point tier of protection. But you can also adjust the recommendations based on your specific needs for enterprise and specialized security protection.
Providing a path for B2B accounts to authenticate with your Microsoft Entra organization doesn't give these accounts access to your entire environment. B2B users and their accounts have access to services and resources (for example, files) designated by Conditional Access policy.
Updating the common policies to allow and protect guests and external user access
This diagram shows which policies to add or update among the common identity and device access policies, for B2B guest and external user access:
The following table lists the policies you need to create and update. The common policies link to the associated configuration instructions in Common identity and device access policies.
Modify this policy to exclude guests and external users.
To exclude guests and external users from Conditional Access policies, go to Assignments > Users > Exclude > Select users and groups: Select Guest or external users, and then select all of the available user types:
B2B collaboration guest users
B2B collaboration member users
B2B direct connect users
Local guest users
Service provider users
Other external users
More information
Guests and external user access with Microsoft Teams
Microsoft Teams defines the following users:
Guest access uses a Microsoft Entra B2B account that can be added as a member of a team and have access to the communications and resources of the team.
External access is for an external user that doesn't have a B2B account. External user access includes invitations, calls, chats, and meetings, but doesn't include team membership and access to the resources of the team.
This policy requires guests to register for MFA in your organization, regardless of whether they're registered for MFA in their home organization. Guests and external users in your organization are required to use MFA for every request to access resources.
Excluding guests and external users from risk-based MFA
While organizations can enforce risk-based policies for B2B users using Microsoft Entra ID Protection, there are limitations in a resource directory because their identity exists in their home directory. Due to these limitations, we recommend that you exclude guests from risk-based MFA policies and require these users to always use MFA.
Excluding guests and external users from device management
Only one organization can manage a device. If you don't exclude guests and external users from policies that require device compliance, these policies block these users.
Work with external users in Teams and the access controls from different places, including Microsoft Entra ID, Microsoft 365, Teams, and SharePoint admin centers.