Need some way to deal with: "AADB2B_0001 : We cannot create a self-service Azure AD account for you because the directory is federated"
Not all B2B invites can be redeemed successfully. Failures happen for reasons that are out of the inviters control (leading to an inability to fix the problem) and are not predictable (leading to poor user experience).
I suspect this problem happens most frequently when a partner organization bungles taking ownership of their tenant. MSFT needs to make it much harder for people to render their production tenant in such a disfunctional state.
Same issue with another 365 domain user, but not with Google account holders.
It would seem Microsoft is less compatible with itself then other vendors.
same issue here, guest company does not have any cloud email system.
Jeff Earley commented
Starting to run into this as well...come on Microsoft
Martin Garza commented
I had an issue with a Gmail account but the technician speculated it was because it was already associated with Teams channel (likely true). I tried another Gmail account without any association and it worked fine. Next step might be deleting the first Gmail account I tried from the previous organization.
Nick Lai commented
We've run into this issue, too. The interesting thing is not all the users from same organization having this issue.
Would appreciate an update.
Martin Garza commented
I've run into this issue as well and would appreciate an update.
Aliaksei Ziamnovich commented
Given I am an administrator of Azure AD tenant (non-federated), when I add a guest user from another Azure AD tenant (federated), I have to guess the exact spelling of email address to create a working invitation link. If there is a difference in case, the invited user cannot redeem the invitation.
I've raised an issue https://github.com/MicrosoftDocs/azure-docs/issues/52544 but it bounced here.
Mike Farrow commented
Any movement on this? Our organization has run into this issue as well.
Jesse Lambert commented
We have a very large client base and utilize Azure B2B for our client portals. We are seeing this more and more, and I echo what Jeremy has said. It's a very bad user experience, and very difficult to explain to the average user. I've been very impressed with B2B, but this is a big gap.