Configure external collaboration settings
External collaboration settings let you specify what roles in your organization can invite external users for B2B collaboration. These settings also include options for allowing or blocking specific domains, and options for restricting what external guest users can see in your Azure AD directory. The following options are available:
Determine guest user access: Azure AD allows you to restrict what external guest users can see in your Azure AD directory. For example, you can limit guest users' view of group memberships, or allow guests to view only their own profile information.
Specify who can invite guests: By default, all users in your organization, including B2B collaboration guest users, can invite external users to B2B collaboration. If you want to limit the ability to send invitations, you can turn invitations on or off for everyone, or limit invitations to certain roles.
Enable guest self-service sign-up via user flows: For applications you build, you can create user flows that allow a user to sign up for an app and create a new guest account. You can enable the feature in your external collaboration settings, and then add a self-service sign-up user flow to your app.
Allow or block domains: You can use collaboration restrictions to allow or deny invitations to the domains you specify. For details, see Allow or block domains.
For B2B collaboration with other Azure AD organizations, you should also review your cross-tenant access settings to ensure your inbound and outbound B2B collaboration and scope access to specific users, groups, and applications.
Configure settings in the portal
Sign in to the Azure portal using a Global administrator account and open the Azure Active Directory service.
Select External Identities > External collaboration settings.
Under Guest user access, choose the level of access you want guest users to have:
Guest users have the same access as members (most inclusive): This option gives guests the same access to Azure AD resources and directory data as member users.
Guest users have limited access to properties and memberships of directory objects: (Default) This setting blocks guests from certain directory tasks, like enumerating users, groups, or other directory resources. Guests can see membership of all non-hidden groups. Learn more about default guest permissions.
Guest user access is restricted to properties and memberships of their own directory objects (most restrictive): With this setting, guests can access only their own profiles. Guests aren't allowed to see other users' profiles, groups, or group memberships.
Under Guest invite settings, choose the appropriate settings:
- Anyone in the organization can invite guest users including guests and non-admins (most inclusive): To allow guests in the organization to invite other guests including those who aren't members of an organization, select this radio button.
- Member users and users assigned to specific admin roles can invite guest users including guests with member permissions: To allow member users and users who have specific administrator roles to invite guests, select this radio button.
- Only users assigned to specific admin roles can invite guest users: To allow only those users with administrator roles to invite guests, select this radio button. The administrator roles include Global Administrator, User Administrator, and Guest Inviter.
- No one in the organization can invite guest users including admins (most restrictive): To deny everyone in the organization from inviting guests, select this radio button.
Under Enable guest self-service sign up via user flows, select Yes if you want to be able to create user flows that let users sign up for apps. For more information about this setting, see Add a self-service sign-up user flow to an app.
Under External user leave settings, you can control whether external users can remove themselves from your organization. If you set this option to No, external users will need to contact your admin or privacy contact to be removed.
- Yes: Users can leave the organization themselves without approval from your admin or privacy contact.
- No: Users can't leave your organization themselves. They'll see a message guiding them to contact your admin or privacy contact to request removal from your organization.
You can configure External user leave settings only if you have added your privacy information to your Azure AD tenant. Otherwise, this setting will be unavailable.
Under Collaboration restrictions, you can choose whether to allow or deny invitations to the domains you specify and enter specific domain names in the text boxes. For multiple domains, enter each domain on a new line. For more information, see Allow or block invitations to B2B users from specific organizations.
Configure settings with Microsoft Graph
External collaboration settings can be configured by using the Microsoft Graph API:
- For Guest user access restrictions and Guest invite restrictions, use the authorizationPolicy resource type.
- For the Enable guest self-service sign up via user flows setting, use authenticationFlowsPolicy resource type.
- For email one-time passcode settings (now on the All identity providers page in the Azure portal), use the emailAuthenticationMethodConfiguration resource type.
Assign the Guest Inviter role to a user
With the Guest Inviter role, you can give individual users the ability to invite guests without assigning them a global administrator or other admin role. Assign the Guest inviter role to individuals. Then make sure you set Admins and users in the guest inviter role can invite to Yes.
Here's an example that shows how to use PowerShell to add a user to the Guest Inviter role:
Add-MsolRoleMember -RoleObjectId 95e79109-95c0-4d8e-aee3-d01accf2d47b -RoleMemberEmailAddress <RoleMemberEmailAddress>
Sign-in logs for B2B users
When a B2B user signs into a resource tenant to collaborate, a sign-in log is generated in both the home tenant and the resource tenant. These logs include information such as the application being used, email addresses, tenant name, and tenant ID for both the home tenant and the resource tenant.
See the following articles on Azure AD B2B collaboration: