Use Microsoft accounts (MSA) for B2B collaboration
Applies to: Workforce tenants
External tenants (learn more)
Your B2B guest users can use their own personal Microsoft accounts for B2B collaboration without further configuration. Guest users can redeem your B2B collaboration invitations or complete your sign-up user flows using their personal Microsoft account.
Microsoft accounts are set up by a user to get access to consumer-oriented Microsoft products and cloud services, such as Outlook, OneDrive, Xbox LIVE, or Microsoft 365. The account is created and stored in the Microsoft consumer identity account system, run by Microsoft.
Guest sign-in using Microsoft accounts
Microsoft account is available by default in the list of External Identities > All identity providers. No further configuration is needed to allow guest users to sign in with their Microsoft account, using either the invitation flow, or a self-service sign-up user flow.
Microsoft account in the invitation flow
When you invite a guest user to B2B collaboration, you can specify their Microsoft account as the email address they'll use to sign in.
Microsoft account in self-service sign-up user flows
Microsoft account is an identity provider option for your self-service sign-up user flows. Users can sign up for your applications using their own Microsoft accounts. First, you'll need to enable self-service sign-up for your tenant. Then you can set up a user flow for the application, and select Microsoft account as one of the sign-in options.
Verifying the application's publisher domain
As of November 2020, new application registrations show up as unverified in the user consent prompt, unless the application's publisher domain is verified, and the company’s identity has been verified with the Microsoft Partner Network and associated with the application. For Microsoft Entra External ID user flows, the publisher’s domain appears only when using a Microsoft account or another Microsoft Entra tenant as the identity provider. To meet these new requirements, follow the steps below:
- Verify your company identity using your Microsoft Partner Network (MPN) account. This process verifies information about your company and your company’s primary contact.
- Complete the publisher verification process to associate your MPN account with your app registration using one of the following options:
- If the app registration for the Microsoft account identity provider is in a Microsoft Entra tenant, verify your app in the App Registration portal.
- If your app registration for the Microsoft account identity provider is in an Azure AD B2C tenant, mark your app as publisher verified using Microsoft Graph APIs (for example, using Graph Explorer).
Next steps
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for