[Feature request] Compatibility of B2C implementation with Microsoft Entra External ID

[btall]

Hello,

I am wondering about the current and future compatibility of the Azure Auth FastAPI library with Microsoft Entra External ID.

Until now, the integration of external identities on the Microsoft side has essentially been via Azure AD B2C. However, Microsoft has announced that Azure AD B2C will no longer be available to new customers from 1 May 2025, with a recommended gradual migration to Microsoft Entra External ID.

This raises questions about the future of B2C-based integrations.

Specifically:

• Is the library's current B2C implementation compatible with External ID scenarios (especially for integrating external identities via Entra)?
• If not, is this compatibility planned in your short- or medium-term roadmap?
• Are there any recommendations or best practices for integrating External ID (outside the traditional B2C model) with your library?

Thank you in advance for your insights and, if applicable, for any indication of a roadmap or monitoring of this development.

Thanks 😉

[JonasKs]

Hi!

Thanks for letting me know – it's hard to keep up with Azure, they like breaking things.

To answer specifically:

• I don't know.
• no, not in short term. I'm on vacation, and I don't know what the potential change would be.
• I'm not sure what external ID entails. Hard to answer yet.

The original implementation was done by @Bulga-xD , im not sure if he's still around or want to contribute to this.

Anyway, we can keep this issue to track any progress.

As always, the best way to get progress is to contribute with findings, resources or PRs.

[btall]

Hi!

Understood.

We'll keep monitoring the evolution of Entra External ID and its compatibility surface. If we opt for it and identify relevant integration patterns or gaps, we may contribute back findings or PRs when feasible.

Thanks for maintaining the project. 👍🏾

[chrismoseley]

Any news on this? It's now no longer possible to set up Azure AD B2C so users have to try with Microsoft Entra External ID. Following the docs almost results in a working solution (you can sign in) but the actual endpoints fail when called from Swagger for example.