I created a new Azure AD B2C for an existing subscription to test out a basic hello-world auth scenario. And it fails with a 500 error using the portal's own tools.
-Create a new Azure AD B2C linked to an existing subscription
-Enable Sign In Sign Up User Flow (email/phone, local account)
-Register an app as SPA with https://jwt.ms as a redirect URI
-Run User Flow
Result is a 500 server error.
It will load the SUSI page BUT if I click on "Sign up with Phone signup or Email signup" it throws a 500.
So, this loads ok:
Clicking sign-up redirects here and FAILS (500):
Now, I could ask about what I configured wrong, but even if I did configure something wrong... the 500 error is NOT a response we should be getting from Azure using their own sanctioned built-in user flows for this. That is a Bug for sure - if something is wrong a proper error should be caught and returned.
NO error shows up in Audit Log. There is NO way to diagnose further, and its a SHOW STOPPER. I cannot proceed. So aside from a legit bug regarding the error, has anyone else experienced this, or know of things I should check?