AAD B2C creates a new tenant. I don't get it-CodePudding

I want to deploy an application on Azure. I want users to be able to authenticate in my app without a Microsoft account. This guided me to use the AAD-B2C service. I followed the tutorial shown here: https://docs.microsoft.com/en-us/azure/active-directory-b2c/tutorial-create-tenant expecting that this will create a new AAD-B2C Directory in my existing Directory and tenant. I had in my mind something like the following tree:

Subscription: Pay-As-You-Go

Directory: Default

Resource Group: Default-EU

Tenants: Default, Application

User Pools: Default(Internal Users), Application(External Users)

I'm not sure I understand how this works and I'm very confused. Is it possible to use external sign-ins from users that don't have a Microsoft account without creating 2 tenants and 2 directories under my subscription?

CodePudding user response：

Azure AD B2C is different from Azure AD. So, when you create Azure AD B2C, it creates another tenant

You need to create Azure AD B2C Tenant in the same subscription in which your application is deployed

Create an App Registration in your Azure AD B2C Tenant

Go to your web application and select Authentication. You can add your app registration details in the identity provider

Reference: Azure App Service Authentication (Ez Auth) with Azure AD B2C - DEV Community

CodePudding user response：

When you create a B2C tenant, there are two completely different entities that get created - B2C Tenant Resource and B2C Tenant/Directory itself.

The B2C Tenant Resource gets created in the subscription linked to your standard Azure AD tenant (Default Directory e.g., contosocorp.onmicrosoft.com) you used to create the B2C tenant from. This resource is primarily used to change your Azure AD B2C tenant's pricing tier.

A separate tenant for your B2C directory gets created (e.g. contosob2c.onmicrosoft.com). This is an independent tenant/directory than your Default Directory and is not stored in the default tenant.

The way subscription is linked to standard Azure AD tenant is different than the B2C tenant. A subscription in B2C is required for Support, Billing, Custom Policies, and using the Identity Experience Framework. You cannot create resources for Static Web App or Function App, or Cosmos DB in the B2C tenant and you will have to use your Default Directory for this purpose.