I'm facing a major challenge with Entra and its licensing for an external tenant. Here's the situation: I have a main tenant set up for B2B purposes and created an Entra ID External Tenant for B2C. However, I need features in the external tenant that require an Entra P1 or P2 license. Unfortunately, I'm unable to purchase or assign any licenses within this External ID tenant. It seems impossible to buy licenses here, and since each tenant needs its own licenses, I can't even use licenses from members of both tenants or share subscriptions. I've tried working with Microsoft outsourced support for about two months, spending dozens of hours, but haven't found a solution. They seem to be confused about how Entra operates. If anyone has any insights or solutions, it would be greatly appreciated. At this point, relying on Entra for our security needs feels like a big mistake.
2 Answers
Are you sure you're working with an "External Identities" tenant and not just a standard B2C tenant? They have different setups and requirements, and that could be where the confusion lies.
Just a heads up, B2C tenants actually don't utilize P1/P2 licenses but rather Monthly Active Users (MAU) for their billing. You may want to look into that.
I've seen conflicting information on that. While end users might not need P1/P2 licenses, it sounds like certain functionalities within the tenant do require them. For example, dynamic groups and custom flows need those licenses to fully function.
Yes, I created an Entra External ID tenant, which is designed for B2C purposes. I think that's part of the trouble; there's still some confusion since the AD B2C has been upgraded to Entra External ID. It hasn't been an easy transition.