Microsoft Entra External ID reaches GA, Azure AD B2C goes into freeze
Microsoft Entra External ID went generally available in September 2024 as the successor to Azure AD B2C. New B2C licenses stopped 1 May 2025. P2 retired 15 March 2026. Remaining P1 tenants stay supported until at least May 2030, frozen. New work belongs on External ID.
What happened
Microsoft Entra External ID reached general availability in September 2024 as the consolidated CIAM offering that replaces Azure AD B2C. The timeline as of 19 August 2026:
- September 2024, Entra External ID GA.
- 1 May 2025, Azure AD B2C end-of-sale to new customers.
- 15 March 2026, Azure AD B2C Premium P2 (Identity Protection) retired. Existing P1 tenants did not shut down.
- At least May 2030, Remaining B2C P1 tenants stay supported in maintenance mode.
New work belongs on External ID. P1 is not an emergency cutover.
Why it matters
Azure AD B2C had a difficult reputation among CIAM practitioners. The policy XML model was legendary for its complexity, the developer experience trailed the modern tier by years, and pricing was opaque. Entra External ID modernizes the policy model, the admin experience, and the SDK surface. For Microsoft-shop teams, it is an honest improvement over what came before.
For non-Microsoft customers, External ID is still a Microsoft-first product. The integration value is real for organizations on Microsoft 365 and Azure. Outside that ecosystem, the developer-first tier (Auth0, Stytch / Twilio, Clerk) usually wins on velocity.
Correction (19 August 2026)
An earlier version of this entry stated that existing B2C tenants retired on 15 March 2026. Microsoft's FAQ is narrower: that date retired P2 / Identity Protection. P1 remains supported until at least May 2030. See the B2C P2 retirement entry for the full correction.
Deepak's take
Microsoft's identity strategy in 2024-2026 has been consolidation: Azure AD became Entra ID, Azure AD B2C is becoming Entra External ID, B2B Collaboration is being absorbed into the broader Entra family. The branding rationalization is overdue. The Azure AD vs Azure AD B2C confusion was a real friction point for buyers.
The substantive improvement is the policy model. B2C's XML-driven custom-policy framework was punishing for non-trivial flows. External ID's primitives are more approachable. For buyers who chose B2C and regretted it, External ID is the version of the product Microsoft should have shipped years earlier. Even with the improvements, External ID still trails the developer-first tier on velocity for non-Microsoft-native architectures. The FedRAMP High compliance posture is genuinely differentiated.
What to do
If you are on Azure AD B2C:
- Confirm P2 / Identity Protection is already gone or never in scope.
- Inventory custom policies. They do not port.
- Treat External ID as the default successor if you stay on Microsoft. Do not treat March 2026 as a P1 shutdown.
If you are evaluating CIAM in 2026 from a Microsoft-aligned organization:
- Entra External ID is on the shortlist alongside Auth0 and, for B2B-only, WorkOS.
- If FedRAMP High or Microsoft 365 / Azure-native integration is a hard requirement, External ID likely wins. Otherwise evaluate broadly.
Related: Entra External ID profile, Microsoft Entra alternatives.