Require MFA for B2B Guests with Gmail, Personal Microsoft Accounts or No Account
By Mirko Peters ·
Guests sign in differently depending on their email type. See how redemption, email one-time passcode and Conditional Access fit together, and which MFA control works for a mixed guest group.
A company invites external contractors as B2B guests. Some use Gmail, some have a personal Microsoft account because they created one at some point, and some have no Microsoft account at all. The sign-in screens look different, and a single requirement that fits every guest type, such as an authentication strength policy, runs into limits.
Key points
- The sign-in path is chosen at redemption: Microsoft Entra account, personal Microsoft account, federation such as Google, or email one-time passcode as the fallback.
- For guests who do not authenticate with Microsoft Entra, Learn says to use the Require multifactor authentication grant. Authentication strength is not supported for them.
- For non-Entra guests, the resource tenant is always responsible for MFA, so the second factor is registered and checked in your tenant.
- A guest who redeemed with the wrong method keeps it until you reset the redemption status. Object ID, group memberships and app assignments are preserved.
This article is based on a Microsoft Q&A thread from early November 2026 that asked exactly this. The thread has no accepted answer. It contains one answer generated by AI, two comments (one from the asker, one from a community member), and one answer from another community member. I used the human replies as leads and checked every claim against Microsoft Learn. This is a guide, not an official Microsoft procedure.
The core point: the screen differs, the control can be the same
You cannot make the sign-in screen identical for all guests. Each guest signs in with whatever identity they redeemed with. What you can make consistent is the requirement: every guest must complete MFA before they reach your app.
Step 1: Know which sign-in method each guest gets
Microsoft Learn describes the email one-time passcode (OTP) behavior. A guest gets an OTP only when all of these are true:
- The guest has no Microsoft Entra account and no personal Microsoft account.
- Your tenant has no federation with another identity provider that applies, for example Google.
- The guest has no other password-backed account that can be used.
- Email OTP is enabled.
Putting those conditions together, the common cases work out like this:
| Guest type | Sign-in method | |---|---| | Work account from another Entra tenant | Their Entra account | | Personal Microsoft account | That account, not an OTP | | Gmail, Google federation configured | Google | | Gmail, no Google federation | Email OTP | | No account at all | Email OTP |
The decision is made at sign-in, and OTP is the fallback. Guests who redeemed before OTP was enabled keep their existing method. A guest who redeemed with OTP and later gets a Microsoft or Entra account still uses OTP until you reset the redemption.
To check or enable OTP, sign in to the Microsoft Entra admin center as at least an Authentication Policy Administrator and go to Entra ID > External Identities > All identity providers. On the Built-in tab, select Configured next to Email one-time passcode. Set Email one-time passcode for guests to Yes and select Save. Learn says it is on by default for new tenants and for existing tenants that did not turn it off.
Be careful when you turn it off. Learn warns that guests who already redeemed with OTP are then blocked until you reset their redemption.
Step 2: Pick the right Conditional Access control
This is where many setups go wrong. Learn is explicit:
- Authentication strength policies can currently only be applied to external users who authenticate with Microsoft Entra ID.
- For email OTP, SAML/WS-Fed and Google federation users, use the Require multifactor authentication grant control.
If you require an authentication strength for all guests, the guests with a Gmail or OTP identity may not be able to satisfy it. Use the plain MFA grant for the mixed group.
Create the policy:
- In the Entra admin center, go to Entra ID > Conditional Access > Policies and create a new policy.
- Under Users, include Guest and external users and select the sub type B2B collaboration guest users. Learn uses the label "Guest and external users" and says the older "All guest and external users" option was replaced. The thread used slightly different wording, so follow what your portal shows.
- Exclude your emergency access accounts.
- Under target resources, select the contractor app, or all resources if that is your design.
- Under Grant, select Require multifactor authentication.
- Set the policy to Report-only first, review the sign-in logs, then switch it to On.
On licensing, Learn says your tenant needs premium Microsoft Entra ID licences that support MFA, and the guest uses one of them.
Step 3: Understand where MFA happens
Learn says that for guests who do not authenticate with Microsoft Entra ID, the resource tenant is always responsible for MFA. The reason it gives is predictability.
For guests with an Entra account, the picture depends on your cross-tenant access settings:
- Without MFA trust, B2B collaboration guests get an MFA challenge from your tenant.
- With trust, Entra checks whether the guest's session already carries an MFA claim from their home tenant.
To set trust, sign in as at least a Security Administrator. Go to Entra ID > External Identities > Cross-tenant access settings. In Default settings, select Edit inbound defaults and open the Trust settings tab. The relevant checkbox is Trust multifactor authentication from Microsoft Entra tenants.
If guests must register for and use MFA in your tenant, Learn says to allow the My Sign ins app in your inbound application settings. Learn marks this app as not available in the portal list, so its example adds it through Microsoft Graph. Learn also warns that if a Conditional Access policy, such as a compliant-device requirement, prevents a guest from registering, access is blocked.
Step 4: Which second factor works for a Gmail guest?
The community answer in the thread said the emailed code is only a first factor, and that the second factor is something you enable in your tenant, such as Microsoft Authenticator push, SMS, voice or an OATH token. Learn does not say in its OTP article whether the code counts as MFA. It only says to use the MFA grant control for these users. Learn's own table of methods says SMS, voice call, Authenticator push notification and OATH software token are accepted in both the home and the resource tenant. The table covers authentication strength, so treat it as supporting evidence only.
In practice, test one account of each type. Do not assume. Write down what each tester sees.
Step 5: Fix guests who used the wrong identity
If a contractor redeemed with a personal Microsoft account and you want Google or OTP, or the other way around, reset the redemption. Learn lists these facts:
- You need at least the Helpdesk Administrator role or User Administrator at directory scope.
- The object ID, group memberships and app assignments are preserved.
- The UPN does not change. The sign-in name changes to the new email.
- The new email must be in the user's
mailorotherMailsproperty.
Portal steps:
- Go to Entra ID > Users and open the guest.
- If the email changes, edit Email and add the new address under Other emails.
- On the Overview tab, in the B2B collaboration tile under My Feed, select Reset redemption status, then Reset.
Via Graph, send POST https://graph.microsoft.com/v1.0/invitations with resetRedemption set to true, the new address in invitedUserEmailAddress, and the existing user in invitedUser.id. Microsoft Graph PowerShell offers New-MgInvitation with -ResetRedemption.
Step 6: Optional, steer who redeems with what
In Cross-tenant access settings > Default settings > Edit inbound defaults > B2B collaboration > Redemption order, you can change the order of identity providers. Learn also says you can disable the Microsoft service account (MSA) fallback so new guests do not redeem with personal Microsoft accounts. Learn says to enable email OTP first. One Learn article describes this option as available and another says it is not available yet, so check your portal. Existing MSA guests keep their account until you reset them.
Matching guests to your CRM
The community answer suggested creating invitations through the invitation API, storing the returned user ID in the CRM, and matching a signed-in user by the token's oid and tid claims instead of by email, because a guest's UPN is a generated value. I could not confirm this in the Learn pages I used. It is a design idea from the thread, so test it before you rely on it.
Verify
- Create one test guest per type: Entra, personal Microsoft account, Gmail and no account.
- Keep the policy in report-only mode and check each sign-in under Conditional Access in the sign-in details.
- Switch to On, and repeat the test with a fresh browser session.
Limits
- The thread did not reach an accepted answer.
- Learn does not state in the pages I used whether an OTP code counts as MFA. It tells you to use the MFA grant instead.
- Portal labels change. Use the labels in your own tenant.
Related
Sources
- Microsoft Learn: Authentication and Conditional Access for External ID
- Microsoft Learn: Email one-time passcode authentication
- Microsoft Learn: Reset redemption status for a guest user
- Microsoft Learn: Configure cross-tenant access settings for B2B collaboration
- Microsoft Q&A: Inconsistent Microsoft Entra ID authentication for B2B guest users using Gmail or personal Microsoft accounts (November 2026)