# Using OpenID Connect with User Flows in Azure B2C

**URL:** <https://meta.discourse.org/t/using-openid-connect-with-user-flows-in-azure-b2c/304271>\
**Category:** SSO\
**Tags:** openid-connect\
**Created:** [August 28, 2022, 11:51am UTC](https://meta.discourse.org/t/using-openid-connect-with-user-flows-in-azure-b2c/304271 "2022-08-28T11:51:19Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![TechGeek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techgeek/32/274321_2.png) [@TechGeek](https://meta.discourse.org/u/TechGeek)\
**Post date:** [August 28, 2022, 11:51am UTC](https://meta.discourse.org/t/using-openid-connect-with-user-flows-in-azure-b2c/304271/1 "2022-08-28T11:51:19Z")

</div>

[Discourse OpenID Connect (OIDC)](https://meta.discourse.org/t/discourse-openid-connect/103632)

Does above steps works with User flows in Azure B2C, which are pre-built policy for use cases.

Email address doesn’t get populated in the new user dialog when the authorization is returned. Using a standard user flow to manage the sign-up experience, but the claim is returning something labeled as “emails” and it’s a stringcollection, not a single email.

Setting up openid\_connect\_authorize\_scope to `openid emails` also doesn’t work.

---

_[View the full topic](https://meta.discourse.org/t/using-openid-connect-with-user-flows-in-azure-b2c/304271)._