Hi @Errico, Giuliano [COMRES/EUR/BLU] ,
Thanks for reaching out.
Here is sample custom policy to split the verification into two steps for sign up flow.
In the similar way, you can split the verification into sign in flow.
https://github.com/azure-ad-b2c/samples/tree/master/policies/split-email-verification-and-signup
First, define a technical profile to collect the user's email address. This will likely be a self-asserted technical profile where the user inputs their email.
Then,need to define forceChangePasswordNextSignIn
custom attribute as Boolean to check its value true/false and based on that check precondition in orchestration step of user's journey.
<OrchestrationStep Order="3" Type="ClaimsExchange">
<Preconditions>
<Precondition Type="ClaimEquals" ExecuteActionsIf="true"> <Value>extension_forceChangePasswordNextSignIn</Value>
<Value>true</Value>
<Action>SkipThisOrchestrationStep</Action>
</Precondition>
</Preconditions>
<ClaimsExchanges>
For redirecting the user to a password reset flow, you would typically invoke a sub-journey or a different technical profile designed for password reset.
https://github.com/azure-ad-b2c/samples/tree/master/policies/force-password-reset
Hope this will help.
Thanks, Shweta
Please remember to "Accept Answer" if answer helped you.