v5 Microsoft Entra docs reference provider that doesn't exist in @auth/core@2.8.0 / 5.0.0-beta.16

[mhg-sov]

What is the improvement or update you wish to see?

Remove the microsoft entra entry from your V5 documentation until you release V5 beta.17 / start using @auth/core@2.9.0

SUPER FRUSTRATING to spend days on this to figure out that the adapter is just.... non-existent in the folder where it should be.

Not only are the docs wrong, but there is a message up (new today?) about this feature being released in next-auth@5.0.0-beta.17

What it SHOULD SAY is "this provider has not been released yet".

There is no estimate on when this will happen. There is no explanation in the docs, on github, or npmjs.org.

Looking on npmjs.org the most recent version of next-auth available is 5.0.0-beta.16 which was released 23 days ago.

On github the most recent tagged release is next-auth@5.0.0-beta.15.

Sooo... it feels "less than accurate" to suggest that beta.17 has been "released". I can't find it anywhere!

I feel like someone is trying to show that the MS entra integration is "published" even though the work has not been completed. I spent half a week troubleshooting this and now I have to go back to my boss and explain that while I thought we could use entra I have NO IDEA when the supposedly "released" code will be available.

Entra provider isn't published yet. Please make your docs factually accurate.

Is there any context that might help us understand?

https://github.com/nextauthjs/next-auth/releases?q=5.0.0&expanded=true

https://www.npmjs.com/package/next-auth?activeTab=versions

Does the docs page already exist? Please link to it.

https://authjs.dev/getting-started/providers/microsoft-entra-id

[ndom91]

Hey sorry about the frustration. It's merged to main, just hasn't been released yet. We noticed the discrepancy and therefore added the message on the docs yesterday.

But as I've mentioned, it's merged in main already and will be in the very next release :pray:

I also clarified the docs to say "To be released..".

The AzureAD provider is definitely released and available though, have you given that a shot? The Entra one is mostly a rename and update of icons, etc.

[mhg-sov]

@ndom91

Thank you for the update, definitely woke up on the wrong side of the bed today.

OSS software is a gift and the folks who are creating it deserve applause... not getting yelled at bc software isnt released soon enough. Sorry for being rude I was just so frustrated after looking through releases and not being able to figure out why what I needed was missing.

Ending on a positive note, I do have a working test repo using 5.0.0-beta.16 to interact with Entra through the Azure AD provider so your suggestion looks correct from my research.