Announcing the general availability of two key features in Azure AD B2C

Published Aug 15 2019 09:00 AM 13.3K Views

Howdy folks,

 

I’m excited to announce the general availability of two key features in Azure AD B2C. First, is the ability to add custom OpenID Connect (OIDC) identity providers for user flows. Second, is the capability to passthrough the access token from identity providers to your application.

 

Adding custom OIDC identity providers 


Our custom policies currently allow you to use any OIDC identity provider. We extended this capability to the built-in user flows. Just like you can sign in users into Azure AD B2C via Facebook and Google, you can now use any other OIDC identity providers in your user flows. You can even use this to allow users to sign in to Azure AD B2C using their Azure AD work accounts.

 

To set this up, on the Identity Providers blade, click the New OpenID Connect provider button, and enter the OIDC metadata information. For details, read Set up sign-up and sign-in with OpenID Connect using Azure Active Directory B2C.

 

OpenID Connect identity provider configuration in the Azure portal.OpenID Connect identity provider configuration in the Azure portal.

 

Use the access token from identity providers in your application

We made it easier for your application to leverage the power of social identity providers and their APIs. When a user signs in using an identity provider, like Facebook, your application can now get the identity provider's access token passed through as part of the Azure AD B2C token. You’ll be able to use this access token when you call the identity provider’s API, such as the Facebook Graph API. To learn more, read Pass an access token through a user flow to your application in Azure Active Directory B2C.



Identity provider access token in an Azure AD B2C token.Identity provider access token in an Azure AD B2C token.

We always love to hear your feedback and suggestions. Let us know what you think in the comments below or email the team at aadb2cpreview@microsoft.com. 

 

Best regards,

Alex Simons (@Alex_A_Simons)

Corporate VP of Program Management

Microsoft Identity Division

3 Comments
Version history
Last update:
‎Jul 24 2020 01:36 AM
Updated by: