I looked into this a while ago for a customer who needed approval and expiration workflows for their B2C users, and we confirmed with Microsoft that access packages and the full Entitlement Management feature set aren’t available in an Azure AD B2C tenant.
B2C is structured differently from a standard EntraID directory, and the identity governance features you see in Entra ID, like access packages, catalogs, and life-cycle workflows—aren’t part of the B2C feature set. Microsoft’s own documentation lists which Entra features work in B2C, and entitlement management isn’t included there.
For scenarios where you need request-and-approval or time-bound access for B2C identities, the approach we used was to build those flows outside B2C.
Most teams handle it with custom policies, user flows, or an external workflow engine like Logic Apps or Functions and then write back to B2C once the request is approved.
It takes more development work, but that’s the supported pattern today because B2C doesn’t include the identity governance layer you get in standard Entra ID tenants.