Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1069481%22%20slang%3D%22en-US%22%3EAzure%20AD%20B2C%20phone%20sign-in%20experience%20is%20now%20in%20public%20preview!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1069481%22%20slang%3D%22en-US%22%3E%3CP%3EHowdy%20folks%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%E2%80%99m%20thrilled%20to%20announce%20that%20Azure%20AD%20B2C%20now%20supports%20phone-based%20sign-in%20and%20sign-up%20for%20apps%20using%20B2C%20custom%20policy!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20an%20increasing%20number%20of%20users%20signing%20in%20to%20apps%20on%20their%20mobile%20phones%20and%20security%20risks%20with%20password%2C%20many%20organizations%20and%20developers%20are%20looking%20for%20ways%20to%20make%20sign-in%20and%20sign-up%20for%20their%20customer%20facing%20apps%20more%20convenient%20and%20secure.%20This%20feature%20also%20takes%20us%20a%20step%20closer%20to%20our%20vision%20of%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fsecurity%2Ftechnology%2Fidentity-access-management%2Fpasswordless%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Epasswordless%20authentication%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20this%20public%20preview%2C%20Azure%20AD%20B2C%20now%20supports%20phone%20sign-in%20and%20sign-up%20using%20a%20phone%20number%20and%20one-time%20password%20(OTP).%20This%20means%20that%20app%20developers%20can%20add%20a%20user%20flow%20to%20their%20app%20that%20allows%20users%20sign-up%20and%20sign-in%20by%20simply%20entering%20their%20phone%20number%2C%20which%20is%20verified%20by%20entering%20the%20OTP%20received%20via%20SMS%20(Figure%201).%20As%20with%20other%20B2C%20experiences%2C%20this%20user%20flow%20can%20be%20fully%20customized%20by%20the%20developer.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20974px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F162085i5B2389DEF0D1D4B8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Azure%20AD%20B2C%20phone%20sign-in%20experience%203.1.png%22%20title%3D%22Azure%20AD%20B2C%20phone%20sign-in%20experience%203.1.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%201.%20User%20flow%20with%20phone%20sign-in%20and%20sign-up%20using%20OTP.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EThe%20experience%20also%20includes%20support%20for%26nbsp%3Bseamless%20account%20protection%20and%20recovery%20for%20times%20when%20a%20user%20loses%20access%20to%20their%20phone%20or%20changes%20their%20phone%20number.%20During%20sign%20up%2C%20users%20are%20required%20to%20provide%20a%20recovery%20email%2C%20which%20is%20then%20verified%20using%20an%20OTP%20(Figure%202).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20465px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F162087i3E7EB2E3E90B6465%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Azure%20AD%20B2C%20phone%20sign-in%20experience%202.png%22%20title%3D%22Azure%20AD%20B2C%20phone%20sign-in%20experience%202.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%202.%20The%20screen%20asking%20the%20user%20for%20recovery%20email.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EWhen%20users%20change%20their%20phone%20number%20or%20don%E2%80%99t%20have%20access%20to%20their%20phone%2C%20they%20can%20use%20this%20recovery%20email%20to%20sign%20in.%20Updating%20from%20an%20old%20phone%20number%20to%20a%20new%20phone%20number%20requires%20verification%20via%20OTP%20sent%20to%20the%20email%20address%20(Figure%203).%20This%20mitigates%20the%20risk%20of%20accidental%20account%20takeover%20in%20the%20event%20of%20a%20phone%20number%20changing%20hands%20from%20one%20person%20to%20another.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F162201i15239E82C5583D6A%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Figure%203.PNG%22%20title%3D%22Figure%203.PNG%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%203.%20The%20process%20of%20changing%20phone%20number%20is%20accomplished%20in%20three%20steps%3A%20First%2C%20user%20enters%20their%20old%20phone%20number.%20Second%2C%20user%20signs%20in%20with%20the%20OTP%20sent%20to%20the%20recovery%20email%20they%20provided%20during%20sign%20up.%20Third%20and%20finally%2C%20after%20user%20successfully%20verifies%20their%20recovery%20email%20and%20signs%20in%2C%20they%20then%20verify%20their%20new%20phone%20number.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EIn%20addition%2C%26nbsp%3Bphone%20based%20sign-in%20and%20sign-up%20can%20be%20used%20in%20conjunction%20with%20other%20authentication%20methods%20like%20email%20based%26nbsp%3Busername%20and%20password%26nbsp%3B(Figure%204)%2C%20or%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory-b2c%2Ftutorial-add-identity-providers%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Esocial%20identity%20providers%3C%2FA%3E%20already%20supported%20by%20Azure%20AD%20B2C.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20451px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F162092i58B810B4B884C3C4%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Azure%20AD%20B2C%20phone%20sign-in%20experience%204.png%22%20title%3D%22Azure%20AD%20B2C%20phone%20sign-in%20experience%204.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%204.%20The%20combined%20page%20that%20contains%20both%20sign%20in%20and%20sign%20up%20for%20phone%20and%20email.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EI%E2%80%99m%20excited%20to%20bring%20phone%20sign-in%20and%20sign-up%20to%20Azure%20AD%20B2C%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FB2CPhoneAuthCustomPolicy%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eso%20jump%20right%20in%20to%20the%20documentation%3C%2FA%3E%20to%20try%20it%20out!%20And%20as%20always%2C%20we%20would%20love%20to%20hear%20any%20thoughts%20or%20feedback%20in%20the%20comments%20below%20or%20through%20this%20%3CA%20href%3D%22https%3A%2F%2Fmicrosoft.qualtrics.com%2Fjfe%2Fform%2FSV_86C0d46O8Tw6Ghv%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eshort%20survey%3C%2FA%3E.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%20regards%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlex%20Simons%20(%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2FAlex_A_Simons%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%40Alex_A_Simons%3C%2FA%3E)%3C%2FP%3E%0A%3CP%3ECorporate%20VP%20of%20Program%20Management%3C%2FP%3E%0A%3CP%3EMicrosoft%20Identity%20Division%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1069481%22%20slang%3D%22en-US%22%3E%3CP%3EEnable%20users%20to%20sign-in%20and%20sign-up%20with%20their%20phone%20number%20in%20Azure%20AD%20B2C.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20298px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F162083i9AB3A10C7D4CBC4F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Azure%20AD%20B2C%20phone%20sign-in%20experience%20teaser.png%22%20title%3D%22Azure%20AD%20B2C%20phone%20sign-in%20experience%20teaser.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1069481%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Active%20Directory%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1077808%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20B2C%20phone%20sign-in%20experience%20is%20now%20in%20public%20preview!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1077808%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20job%20Linda%3C%2FP%3E%3C%2FLINGO-BODY%3E

Howdy folks,

 

I’m thrilled to announce that Azure AD B2C now supports phone-based sign-in and sign-up for apps using B2C custom policy!

 

With an increasing number of users signing in to apps on their mobile phones and security risks with password, many organizations and developers are looking for ways to make sign-in and sign-up for their customer facing apps more convenient and secure. This feature also takes us a step closer to our vision of passwordless authentication.

 

With this public preview, Azure AD B2C now supports phone sign-in and sign-up using a phone number and one-time password (OTP). This means that app developers can add a user flow to their app that allows users sign-up and sign-in by simply entering their phone number, which is verified by entering the OTP received via SMS (Figure 1). As with other B2C experiences, this user flow can be fully customized by the developer.

 

Azure AD B2C phone sign-in experience 3.1.pngFigure 1. User flow with phone sign-in and sign-up using OTP.

The experience also includes support for seamless account protection and recovery for times when a user loses access to their phone or changes their phone number. During sign up, users are required to provide a recovery email, which is then verified using an OTP (Figure 2).

 

Azure AD B2C phone sign-in experience 2.pngFigure 2. The screen asking the user for recovery email.

When users change their phone number or don’t have access to their phone, they can use this recovery email to sign in. Updating from an old phone number to a new phone number requires verification via OTP sent to the email address (Figure 3). This mitigates the risk of accidental account takeover in the event of a phone number changing hands from one person to another.

 

Figure 3.PNGFigure 3. The process of changing phone number is accomplished in three steps: First, user enters their old phone number. Second, user signs in with the OTP sent to the recovery email they provided during sign up. Third and finally, after user successfully verifies their recovery email and signs in, they then verify their new phone number.

In addition, phone based sign-in and sign-up can be used in conjunction with other authentication methods like email based username and password (Figure 4), or social identity providers already supported by Azure AD B2C.

 

Azure AD B2C phone sign-in experience 4.pngFigure 4. The combined page that contains both sign in and sign up for phone and email.

I’m excited to bring phone sign-in and sign-up to Azure AD B2C, so jump right in to the documentation to try it out! And as always, we would love to hear any thoughts or feedback in the comments below or through this short survey

 

Best regards,

 

Alex Simons (@Alex_A_Simons)

Corporate VP of Program Management

Microsoft Identity Division

1 Comment
Occasional Visitor

Good job Linda