Forum Discussion

Nelson Morais's avatar
Nelson Morais
Copper Contributor
Jul 10, 2017
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 occur...
Azure AD B2B
  • Nelson Morais's avatar
    Nelson Morais
    Jul 21, 2017

    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

Nelson Morais's avatar
Nelson Morais
Copper Contributor
Jul 17, 2017

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!

Simon Watson's avatar
Simon Watson
Copper Contributor
Jul 18, 2017

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).

  • Nelson Morais's avatar
    Nelson Morais
    Copper Contributor
    Jul 18, 2017

    Thank you Simon,

     

    I'll point this thread to MS support to see if our problem is related with the solution you describe.

     

    Thanks!

    • Nelson Morais's avatar
      Nelson Morais
      Copper Contributor
      Jul 20, 2017

      Hi,

       

      I got an answer from Microsoft support.

      Apparently the domain name reservation was present in a worker and this situation was the reason why the problem was occurring.

      MS removed that reservation from the worker and we're now waitting for our customer to try the registration process after new accounts and invites were sent.

      I'll update this post as soon as I got a confirmation that this actually solved the problem.

       

      Nelson Morais

      • vabby547's avatar
        vabby547
        Copper Contributor
        Dec 13, 2021

        Nelson Morais - Do you know how they remove the worker we have the same problem

Resources