Local account sign-up verification code flow awkward
When signing up for local account, the flow of asking the user to verify (verification code flow) is awkward. The e-mail verification step is listed at the top but other details must be filled before sending the verification code. This is confusing to our customers.
Justin Magaram commented
I worked at Microsoft for 10 years as a program manager and did a lot of UI design. I recently tried adding the self signup B2C code to my web app. In my personal testing I was completely unable to register a new user account because I couldn’t figure out how to get the Create button enabled at the bottom of the form. I was certain your code was broken or that my passwords didn’t match. I overlooked the Verify button at the top of the form. I repeated this process several times and never figured it out. I think the UI here needs to be fixed. Part of the issue is that we fill in forms from top to bottom. After I fill in the verification code I work my way down to the user name and passwords and then expect the Create button to be enabled. My eyes don’t go back up and see the Verify button. I wasn’t even aware that the Send Code button had morphed into a Verify button - not a noticeable transition. I think it would work better if the Verify button didn’t exist and instead the Create button verified the code and displayed an error message if there was a problem with it. Or some smaller fixes would be to move the Verify button to the left of the Create button and label them “1. Verify code” and “2. Create account”. I’m sure there are bigger changes that would make this easier for users to figure out. But I really hope you’ll do something to make this process more intuitive.
There has got to be a better way to do this. Our customers are complaining that there is no guidance to verify the code before entering the password. If we could separate the verify code and enter password steps either into two separate pages or hide the password feature until the verification is complete that would help. This is a very confusing and frustrating part of using Azure. If a user is already a part of Azure with another application, couldn't that be verified before wasting time entering all the information. Customers are resetting passwords for other Azure linked applications because the confusion of this leads them to believe this is a phishing scam.
Lisa Angara commented
Completely agree! This needs to be fixed.
Frank Palmieri commented
The verification flow is very awkward - we just went through a roll out of an ADB2C based web site and this was the number one confusion for users - we ended up having to put a couple of sentences at the top of the customized page to explain to the user what they needed and create a FAQ page that we linked to so that we could explain it in more detail. Also, the email validation needs to check if the email is already in the directory before sending out the verification email - instead the user runs through the whole convoluted process and when they press the "save" button on the profile, they are finally told that the account already exists.