Azure Ad B2c PhoneFactor-Verify skip the send screen

Question

I created an azure ad b2c policy with UserJourney that include an PhoneFactor-Verify step.
I have a TechnicalProfile PhoneFactor-Verify: with ManualPhoneNumberEntryAllowed set to false, so user can NOT change registered phone number.

 <TechnicalProfile Id="PhoneFactor-Verify">  
          <DisplayName>PhoneFactor</DisplayName>  
          <Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.PhoneFactorProtocolProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />  
          <Metadata>  
            <Item Key="ContentDefinitionReferenceId">api.phonefactor</Item>  
            <Item Key="ManualPhoneNumberEntryAllowed">false</Item>  
          </Metadata>  
          <CryptographicKeys>  
            <Key Id="issuer_secret" StorageReferenceId="B2C_1A_TokenSigningKeyContainer" />  
          </CryptographicKeys>  
          <InputClaimsTransformations>  
            <InputClaimsTransformation ReferenceId="CreateUserIdForMFA" />  
          </InputClaimsTransformations>  
          <InputClaims>  
            <InputClaim ClaimTypeReferenceId="userIdForMFA" PartnerClaimType="userId" />  
            <InputClaim ClaimTypeReferenceId="strongAuthenticationPhoneNumber" />  
          </InputClaims>  
          <OutputClaims>  
            <OutputClaim ClaimTypeReferenceId="Verified.strongAuthenticationPhoneNumber" PartnerClaimType="Verified.OfficePhone" />  
          </OutputClaims>  
          <UseTechnicalProfileForSessionManagement ReferenceId="SM-MFA" />  
        </TechnicalProfile>  
  

when I run it, I got this screen:

Is there a way to skip this screen and "send code" automatically? and progress to next validation screen?

I assume I can embed a java script snippet to "click" on the "send code" button, but seems it is a hack.
Is there some thing I can do in policy to skip the click of "send code"?

Answer 1

OK, I just saw this setting: setting.autodial which works fine for me!.

so my modifed PhoneFactor-Verify is:
<TechnicalProfile Id="PhoneFactor-Verify">
<DisplayName>PhoneFactor</DisplayName>
<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.PhoneFactorProtocolProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
<Metadata>
<Item Key="ContentDefinitionReferenceId">cd.verify_otp</Item>
<Item Key="ManualPhoneNumberEntryAllowed">false</Item>
<Item Key="setting.authenticationMode">sms</Item>
<Item Key="setting.autodial">true</Item>
</Metadata>
<CryptographicKeys>
<Key Id="issuer_secret" StorageReferenceId="B2C_1A_TokenSigningKeyContainer" />
</CryptographicKeys>
<InputClaimsTransformations>
<InputClaimsTransformation ReferenceId="CreateUserIdForMFA" />
</InputClaimsTransformations>
<InputClaims>
<InputClaim ClaimTypeReferenceId="userIdForMFA" PartnerClaimType="UserId" />
<InputClaim ClaimTypeReferenceId="strongAuthenticationPhoneNumber" />
</InputClaims>
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="Verified.strongAuthenticationPhoneNumber" PartnerClaimType="Verified.OfficePhone" />
<OutputClaim ClaimTypeReferenceId="newPhoneNumberEntered" PartnerClaimType="newPhoneNumberEntered" />
</OutputClaims>
<UseTechnicalProfileForSessionManagement ReferenceId="SM-MFA" />
</TechnicalProfile>