Entra External ID Guest User invitation unstable

For the two issues (no invitation email and “Invitation redemption failed”), use the following checks and remediation steps.

1. Invitation email not received

• Ask the invitee (or their mail admin) to allow the sender address used by Entra B2B invitations:
  • Commercial cloud: Invites@microsoft.com
  • Azure operated by 21Vianet: ******@oe.21vianet.com
  • Microsoft Entra Government: ******@azuread.us
• Have the invitee check spam/junk and any mail security filters for blocked/quarantined messages from that address.
• If delivery is unreliable and a custom message is important, consider suppressing the built‑in invitation email and sending your own mail with the redemption link via your organization’s email system. This avoids cases where privacy rules prevent custom text from being included in the Microsoft‑sent invite.

2. “Invitation redemption failed” when user clicks the link Work through these common causes:

• Home tenant blocks creation of “EmailVerified” users
  • If the invitee’s organization uses Microsoft Entra ID but the specific user account does not exist there, their admin may have disabled creation of EmailVerified users.
  • Ask the invitee to contact their admin to verify whether external/EmailVerified users are allowed. If not, the admin must update the authorization policy to allow EmailVerified users (see the Update-MgPolicyAuthorizationPolicy guidance in the linked article in the context).
• External user doesn’t exist in a federated domain
  • If the invitee’s organization uses federation and the user isn’t synchronized into their Entra tenant, redemption fails.
  • Their admin must synchronize the user’s account to Entra ID before the invitation can be redeemed.
• ProxyAddress collision with an existing user
  • Entra checks for collisions in proxyAddresses across the invitee’s home tenant and your tenant.
  • If the email/proxyAddress already exists on a local user or another guest, the invite can fail or behave unexpectedly.
  • For external users, Entra will add the email to the existing B2B user’s proxyAddresses. For local users, direct the person to sign in with the existing account instead of inviting them again.
• Guest object / contact conflicts in your directory
  • If the invited email matches an existing Contact object, the guest’s proxyAddresses or mail may not be populated.
  • The redemption process has been updated to search both proxyAddresses and the invited email, so this should no longer block just‑in‑time redemption or email OTP. If issues persist, use Microsoft Graph PowerShell to search for conflicting contacts:
    1. Connect-MgGraph as at least Directory Reader.
    2. Run Get-MgContact -All | ? {$_.Mail -match '******@domain.com'} to find duplicates and clean them up if needed.

3. Additional troubleshooting steps

• Confirm the guest user was actually created in your tenant after the first invite:
  • In Entra admin center → Microsoft Entra ID → Users, search for the guest’s UPN (for example, user_contoso.com#EXT#@yourtenant.onmicrosoft.com).
• If the guest object is in a bad state (for example, created with the wrong email or accepted with the wrong account), remove and re‑invite:
  1. Use Microsoft Graph PowerShell:
     • Connect-MgGraph -Scopes "User.ReadWrite.All","Directory.ReadWrite.All"
     • Locate the guest: Get-MgUser -Filter "UserPrincipalName eq 'jondoe_contoso.com#EXT#@yourdomain.onmicrosoft.com'" -Property Id,UserPrincipalName,UserType
     • Remove it: Remove-MgUser -UserId <user-id> -Confirm:$false
     • (Optional) Permanently delete from recycle bin if needed.
  2. Ask the user to clear browser cache (including cookies and site data) or use an InPrivate/Incognito window when accepting the new invite to avoid cached credentials.

4. How to proceed with the current failure

• Capture the RequestId/CorrelationId/Timestamp from the error page (as in the screenshot) and provide them to Microsoft support if the above checks do not resolve the issue. These identifiers allow support to trace the exact backend error.

These steps focus on mail delivery, home‑tenant policies, identity synchronization, and directory conflicts, which are the main documented causes of unstable or failing B2B invitation redemption.

References:

• Troubleshoot common issues with Microsoft Entra B2B collaboration
• Error when a guest user accepts a SharePoint Online invitation by using another account
• Add and manage B2B collaboration users in the Microsoft Entra admin center
• Multitenant user management scenarios