Some Key Points about the AAD B2C Tenant  (Also read B2B Partner Identities in AAD )

  1. B2c Is designed for EXTERNALLY facing apps that have their own app specific logins (username passwords).
  2. There is no concept of a GUEST user for a B2C tenant. That concept is native to the B2B tenant.
  3. If you DO need to provide GUEST user type of access (collaboration) for B2C users, the way to do it would be to invite them separately to the main AAD tenant.

Can the B2C users get access to the main / primary AAD tenant (the AAD portal)?

No. The login that B2C users get is a completely separate tenant  –

<tenant>.b2clogin.com

What if you DID want to grant these users access to the main / primary AAD tenant?

They could be invited as guest users for the portal.

 Summary

Unlike B2B documentation, the AAD B2C documentation is slightly confusing. Can you accommodate guest users in B2C? Is it only for external facing apps (YES!). Does it have a separate portal login  (Yes)

Do you want to provide a CONSITENT sign up and sign in experience ACROSS ALL your  EXTERNAL apps? Only B2C can serve that purpose.





Need an experienced Cloud Networking or a Cloud Data Protection Expert?  Anuj has successfully delivered over a dozen deployments on each of the public clouds (AWS/GCP/Azure) including several DevSecOps engagements. Set up a time with Anuj Varma.