# Discourse-azure-oauth2 -- version token support

**URL:** <https://meta.discourse.org/t/discourse-azure-oauth2-version-token-support/106346>\
**Category:** Product Support\
**Created:** [January 12, 2019, 7:16am UTC](https://meta.discourse.org/t/discourse-azure-oauth2-version-token-support/106346 "2019-01-12T07:16:47Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [January 15, 2019, 10:30am UTC](https://meta.discourse.org/t/discourse-azure-oauth2-version-token-support/106346/4 "2019-01-15T10:30:08Z")

</div>

For Azure B2C, I think you will have more success using the generic [Discourse OpenID Connect (OIDC) - #10](https://meta.discourse.org/t/openid-connect-authentication-plugin/103632/10) rather than **azure-oauth2**. The discovery document URL details can be found here: [Web sign in with OpenID Connect - Azure AD B2C | Microsoft Learn](https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-reference-oidc)

> [@](#):
>
> For example, the metadata document for the `b2c_1_sign_in` user flow in `fabrikamb2c.onmicrosoft.com` is located at:
> 
> `https://fabrikamb2c.b2clogin.com/fabrikamb2c.onmicrosoft.com/v2.0/.well-known/openid-configuration?p=b2c_1_sign_in`

---

_[View the full topic](https://meta.discourse.org/t/discourse-azure-oauth2-version-token-support/106346)._