Query on Azure AD B2C licensing and features



Wondering whether I could get some assistance / feedback from the forum to the queries related to Azure AD B2C licensing and features.


  • B2C linked to P1 subscription level, but Azure AD blade displays "Azure AD Free"

    Azure AD B2C Tenant is linked to subscription with P1 pricing tier.
    However, Azure AD Tenant blade lists AD Tenant License as "Azure AD Free".

    "Azure AD Free" does not have SLA commitment and has 50k object limit.

    Must we also procure few Azure AD P1 license for B2C tenant in additional to the B2C P1 subscription to ensure AD tenant SLA and overcoming 50k object limit ?

  • License for organization employees accessing B2C apps

    According to Azure AD external identities FAQ - the MAU pricing for P1 subscription is applicable only for external users. All organization employees need a P1 license.

    Is this clause also applicable to B2C tenant or is it relevant only for B2B tenant ?

    Suppose that few organization employees like technical support admins also need to access Apps in B2C tenant - this can be facilitated by creating OIDC identity provider in B2C tenant to federate to organization Azure AD B2B tenant for authentication of employees.
    Do these organization users users need additional P1 license for B2C tenant ?
    Are the organization users also counted towards the MAU P1 subscription just like external users in case of B2C scenario ?

  • AD Group feature capability for B2C tenant

    According to supported AD features "Consumer accounts can not be member of any group."

    Currently we are able to add B2C consumer accounts as member or owner of Azure AD security groups.

    For instance: One could use group membership with custom sign-in / sign-up policy - user shall be added to "App Group" when user is signed up by App, and only "App Group" members shall be able to signin to App.

    Is this the case of documentation not up to date ? Or is the intended group usage one of unsupported features in B2C tenant.


1 Reply



I have exactly the same problem, did you manage to fix this?

Really hard to find how to exactly troubleshoot this problem.

I already unlinked and linked the B2C instance in the main tenant, which did not work.


I think it has something to do with the licencing of the user who creates the B2C instance. Since this user becomes a member (owner) of that AD instance you will need a single licence for that user.  In our situation, all other users become guests which fall under the 50.000 MAU free tier.