Hi @Henry Petersen ,
Thanks for reaching out and apologies for delay in response.
As per your query, it seems you are confusing B2B with B2C.
Azure AD B2B and B2C are two different services that are built on the same technology but for different purposes.
Azure AD B2B is a feature of Azure AD. It allows organizations to grant access to their applications and services for users from other tenants. From your app perspective nothing changes. It is still same Azure AD app. Azure AD B2B has an API which can be used to create flows for the invitation of users from another directory.
Whereas Azure AD B2C is another service built on the same technology but not the same in functionality as Azure AD. Azure AD B2C target is to build a directory for consumer applications where users can register with e-mail ID or social providers like Google, FB, MSA, known as Federation Gateway. The goal for Azure AD B2C is to allow organizations to manage single directory of customer identities shared among all applications i.e. single sign-on.
For B2C tenant, the recommended option is to select Accounts in any identity provider or organizational directory (for authenticating users with user flows)- This is the most common option for apps that are exposed to your customers. You must select this option to authenticate users with Azure AD B2C user flows.
B2B targets organizations users while B2C targets consumers.
Microsoft has introduced a new solution which merges B2B and B2C - It is called "External Identities". It is a mechanism to allow you, to have external users, self-registration for them and control on their process, within your Azure AD tenants.
Reference : https://learn.microsoft.com/en-us/azure/active-directory/external-identities/external-identities-overview
Hope this will help.
Thanks,
Shweta
Please remember to "Accept Answer" if answer helped you.