Hi RT,
Thank you for posting your query on Microsoft Q&A.
I hope this information is helpful. Please feel free to reach out if you have any further questions.
Based on your query, I understand you would like to configure sign up and sign in for social accounts.
I see there is a might be a mis configuration on the user journey of combined sign up and sign in. Could you please add the following steps in your user journey:
<OrchestrationStep Order="1" Type="ClaimsProviderSelection" ContentDefinitionReferenceId="api.idpselections.signup">
<ClaimsProviderSelections>
<ClaimsProviderSelection TargetClaimsExchangeId="SignUpWithLogonEmailExchange" />
</ClaimsProviderSelections>
</OrchestrationStep>
Identity provider selection for sign-up - Lists identity providers that users can choose from during sign-up. The options are usually enterprise identity providers, social identity providers such as Facebook and Google+, or local accounts.
Now in the orchestration steps, you can precondition as below as well:
<OrchestrationStep Order="2" Type="ClaimsExchange">
<Preconditions>
<Precondition Type="ClaimsExist" ExecuteActionsIf="true">
<Value>objectId</Value>
<Action>SkipThisOrchestrationStep</Action>
</Precondition>
</Preconditions>
<ClaimsExchanges>
<ClaimsExchange Id="FacebookExchange" TechnicalProfileReferenceId="Facebook-OAUTH" />
<ClaimsExchange Id="SignUpWithLogonEmailExchange" TechnicalProfileReferenceId="LocalAccountSignUpWithLogonEmail" />
</ClaimsExchanges>
</OrchestrationStep>
I would request you to configure your ClaimsExchange
using the following document: Set up a sign-up and sign-in flow with a social account by using Azure Active Directory B2C custom policy
Please make sure to have a look at the complete document and make sure to have green tick on steps configured from the document.
If the answer is helpful, please click "Accept Answer" and kindly "upvote it". If you have extra questions about this answer, please click "Comment".