Azure B2B sign up and sign in flow - errors when creating new user

Diccon Towns 101 Reputation points
2021-10-12T15:13:22.53+00:00

We use an AD tenant to allow partners access to our application. We have enabled self service to allow users to register themselves.

The application is a React Application, using the MSAL packages: @azure/msal-browser and @azure/msal-react.

When the user (with an existing Microsoft account that doesn't already exist in our tenant) clicks to sign in, they are redirected to the login.microsoftonline.com login page where they authenticate.

They then get the message "This account does not exist in this organisation. Enter a different account or create a new one". They click 'Create a new one', then 'Sign up with email'

They provide their email address and password, then accept the permissions for the application, after which they provide personal details (City, Region, Display name, Given name and Surname).

They then get the message: "Help us to protect your account Microsoft has enabled Security Defaults to keep your account secure . . .". Click Next and they are redirected to the broken page below (https://account.activedirectory.windowsazure.com/securityinfo?isOobe=False&brkr=&brkrVer=2.16.1&clientSku=msal.js.browser):

139941-screenshot-2021-10-12-at-160520.png

Page content:

)]}',
{"CID":"e158000e-4d57-4fa2-84f4-6eeed7d02d32","Date":"2021-10-12T13:54:41.9631039Z","Exception":null}

At this point, the user can be seen in our Active Directory. If the user refreshes the page and resubmits their form data, the MFA Authenticator process is invoked and the sign up can be completed successfully.

Any thoughts on what may be causing this? Users with accounts already registered with our tenant can login without issue. It appears to be a bug specifically around creating new accounts and MFA.

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
23,149 questions
{count} votes

Accepted answer
  1. Diccon Towns 101 Reputation points
    2021-10-13T17:08:25.563+00:00

    This was fixed by Microsoft Support after I raised a ticket (had to buy a Support package to do do so, obviously).

    I'm not sure what the resolution was, although the Support agent said he had 'run some diagnostics on our tenant' so am unable to provide much info for posterity, sadly.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. James Hamil 26,981 Reputation points Microsoft Employee
    2021-10-13T22:22:57.94+00:00

    Hi @Diccon Towns , do you have the ticket number? I can look into it and post the solution here. I'm glad you got your issue resolved!

    Best,
    James


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.