question

SathkaalS-1951 avatar image
1 Vote"
SathkaalS-1951 asked HarjaniAshish-7896 commented

Azure AD B2C - Sign up with Phone

Hi,

In Azure AD B2C the Sign up process with Phone is expecting the emailId during the sign up process.
Our use case is that we just need to ask the user only Phone number during the sign up process. Is there a way that we can avoid asking the emailid from the user during Sign up process with Phone?

I tried couple of options like by removing the email check step from the User Journey as shown below:

<OrchestrationStep Order="3" Type="ClaimsExchange">
<Preconditions>
<Precondition Type="ClaimsExist" ExecuteActionsIf="true">
<Value>isLocalAccountSignIn</Value>
<Action>SkipThisOrchestrationStep</Action>
</Precondition>
</Preconditions>
<ClaimsExchanges>
<ClaimsExchange Id="SignUpWithPhone_CollectEmailAddress" TechnicalProfileReferenceId="LocalAccountSignUpWithLogonPhoneNumber_CollectEmailAddress" />
</ClaimsExchanges>
</OrchestrationStep>

But none of the options are work. Appreciate a quick response on this issue.

Thanks,
SathKaal



azure-active-directory
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@amanpreetsingh-msft - I am landing in the same issue as described above. We are already in PROD and don't want to change the templates. The templates that I used to implement the Phone Sign UP/IN experience is present at : https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack/tree/master/scenarios/phone-number-passwordless

Can you please help how can we disable the Email Recovery Step from these flows ? Appreciate your response !


Thanks,
Ashish

0 Votes 0 ·

Hi MSFT B2C Community ,

Any inputs on above question please ?


Thanks,
Ashish

0 Votes 0 ·

1 Answer

amanpreetsingh-msft avatar image
1 Vote"
amanpreetsingh-msft answered SathkaalS-1951 commented

Hi anonymous user

You can use This Sample, as for signup/signin all you need to provide is the Phone Number and no other attributes are needed to be provided.

Steps:

  1. Download the starter pack and use the "SocialAndLocalAccountsWithMfa" template.

  2. Follow the steps mentioned here: Add application IDs to the custom policy and upload the policy files.

  3. Update the base policy tag in the TrustFrameworkLocalization.xml file provided in the sample to point towards your TrustFrameworkExtension file and upload the file.

  4. Upload the phone-signup-signin.xml file in B2C IEF section from the sample after updating the file with your tenant name.


Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi Aman,

Yes, it got worked. Thanks for the help.

Sathkaal

0 Votes 0 ·