Forum Discussion
Solved
AAD B2B account creation failure - "An unexpected error occurred. Please try again"
Hi,
We're using AAD and B2B account to allow our partners to access our applications.
One of our customers, to which we've sent an AAD B2B invite got the error message "An unexpected error occurred. Please try again.", after entering the verification code that was sent.
From the image below, I presume a new AAD Tenant was created, as described in the B2B scenarios for accounts that don't have an AAD tenant created yet.
What can be the problem, and how can we help our customer to move forward and gain access to our applications?
Any suggestion is welcome.
Thanks!
Hi Chao,
No, it means it "unblocked" the Domain reservation of my customer and now he was able to accept the invite. You will need to check with MS support if your situatio is the same.
MS also suggested:
- to delete the accounts in my tenant for that Domain and resend the invites.
- to always accept the invites in an InPrivate/Incognito browser session.
My conclusion:
If this error occurs again, create a support ticket with MS so that the domain can be "unblocked" and allow the registration process to succeed. This fix is done per Domain and is not a fix that "unblocks" any other scenarios having the same or a similar issue.
I hope this helps others.
Nelson Morais
Had this issue as well, workaround I found is to set the country to "United States" (at the page where you pick a password)
Hi Simon,
Thanks for the info.
That would be a very wired solution, for now I'm working with MS support to see if we can identify and fix the problem. For the moment we're waitting for our customer to provide us some Fiddler traces to help MS diagnose the situation.
I'll post an update here as soon as I have the problem solved.
Thanks!
From what I could tell for the situation I had, it had issues creating the Azure AD just-in-time tenant for the invited user's domain when using Australia as the country (it creates the JIT tenant when the first person for each domain signs up). Once one person was signed up using US as the country it worked fine for the rest of them on that domain (and no longer asked for a country to be set).
I would open a support ticket through the Azure Portal
Hi Dean,
That's what I did :), and still working with MS Support to find out the problem.
Thanks,
Nelson
