{"id":2478,"date":"2026-04-01T12:37:15","date_gmt":"2026-04-01T19:37:15","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/identity\/?p=2478"},"modified":"2026-04-01T12:37:15","modified_gmt":"2026-04-01T19:37:15","slug":"native-auth-social-idps-web-view-ga","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/identity\/native-auth-social-idps-web-view-ga\/","title":{"rendered":"General Availability: Social Identity Providers for Native Authentication via Browser\u2011Delegated Flows (web-view) in Microsoft Entra External ID"},"content":{"rendered":"<p>We\u2019re excited to announce the General Availability of Social Identity Provider (IdP) support for Native Authentication in Microsoft Entra External ID. This release enables developers to integrate popular social sign\u2011in options such as Google, Facebook, and Apple \u2014 into native and single\u2011page applications that use Native Authentication. Importantly, social identity providers are supported through a browser\u2011delegated (web\u2011view) authentication flow. This approach ensures compatibility with social providers while maintaining the security posture expected of enterprise\u2011grade identity systems.<\/p>\n<p><div  class=\"d-flex justify-content-center\"><a class=\"cta_button_link btn-primary mb-24\" href=\"https:\/\/learn.microsoft.com\/en-us\/entra\/identity-platform\/concept-native-authentication?toc=%2Fentra%2Fexternal-id%2Ftoc.json&amp;bc=%2Fentra%2Fexternal-id%2Fbreadcrumb%2Ftoc.json\" target=\"_blank\">Get Started with Native Authentication<\/a><\/div><\/p>\n<h2>Clarifying native vs. browser\u2011delegated social authentication<\/h2>\n<p>Native Authentication in Entra External ID supports integrating Social Identity Providers while maintaining application\u2011centric user experiences.<\/p>\n<p>Social sign\u2011in is currently supported:<\/p>\n<table>\n<thead>\n<tr>\n<th>Authentication stage<\/th>\n<th>What\u2019s supported<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Native app UX<\/td>\n<td>App\u2011owned native sign\u2011in or sign\u2011up screen<\/td>\n<\/tr>\n<tr>\n<td>Social IdP authentication (GA)<\/td>\n<td>Google, Facebook, Apple \u2014 via browser\u2011delegated (web\u2011view) flow<\/td>\n<\/tr>\n<tr>\n<td>Post\u2011social authentication (GA)<\/td>\n<td>Entra External ID authentication steps (for example, MFA via Conditional Access) \u2014 via browser\u2011delegated (web\u2011view) flow<\/td>\n<\/tr>\n<tr>\n<td>Fully native post\u2011social UX (future)<\/td>\n<td>Planned \u2014 Entra External ID authentication steps (for example, MFA) performed via native API\u2011driven experience instead of browser\u2011delegated flow<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>After a user selects a Social Identity Provider, authentication continues in a browser\u2011delegated (web\u2011view) experience to comply with provider OAuth requirements. Subsequent authentication steps such as MFA when Conditional Access is enabled \u2014 are also completed within this delegated flow. This model enables Social IdP support in Native Authentication today. A future release will introduce native UX for post\u2011social authentication steps, replacing the current browser\u2011delegated experience where applicable.<\/p>\n<h2>Why Social Identity Providers matter for native apps<\/h2>\n<p>Consumer and external\u2011facing applications increasingly need to offer familiar sign\u2011in options such as Google, Facebook, or Apple without compromising security or standards compliance.<\/p>\n<ul>\n<li>When social sign\u2011in is required \u2014 for example, to streamline onboarding, improve conversion, or support bring\u2011your\u2011own\u2011identity scenarios.<\/li>\n<li>While preserving app\u2011centric experiences \u2014 the initial sign\u2011in or sign\u2011up screens remain native within the application.<\/li>\n<li>Without handling user credentials in application code \u2014 authentication with social providers is performed using a browser\u2011delegated (web\u2011view) flow that aligns with OAuth requirements.<\/li>\n<\/ul>\n<p>Native Authentication enables developers to integrate Social Identity Providers into native experiences while maintaining security boundaries enforced by the provider and Entra External ID. Subsequent authentication steps such as MFA when Conditional Access is enabled \u2014 continue within the same browser\u2011delegated flow.<\/p>\n<h2>What\u2019s now generally available<\/h2>\n<p>With this GA release, developers can now:<\/p>\n<ul>\n<li>Enable Social Identity Providers (such as Google and Facebook) in native sign\u2011in and sign\u2011up experiences.<\/li>\n<li>Allow users to authenticate with supported social providers using a browser\u2011delegated (web\u2011view) flow within the application.<\/li>\n<li>Leverage standards\u2011compliant OAuth redirect flows required by social identity providers.<\/li>\n<li>Rely on Entra External ID to issue ID and access tokens after successful social authentication\u2014without handling user credentials in application code.<\/li>\n<li>\n<p>Present a native sign\u2011in or sign\u2011up screen within the app, after which authentication continues in a browser\u2011delegated (web\u2011view) experience for:<\/p>\n<ul>\n<li>The selected social identity provider (for example, Google, Facebook, or Apple), and<\/li>\n<li>Any subsequent Entra External ID authentication steps (such as MFA when Conditional Access is enabled).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Native Authentication continues to issue tokens only after the selected social provider has successfully completed authentication through the browser\u2011delegated flow.<\/p>\n<h2>Ready to get started?<\/h2>\n<p>To begin using Social Identity Providers with Native Authentication, configure the provider in your Entra External ID tenant and integrate using the Native Authentication SDKs. Social sign\u2011in is supported through a browser\u2011delegated (web\u2011view) authentication flow.<\/p>\n<p><div  class=\"d-flex justify-content-center\"><a class=\"cta_button_link btn-primary mb-24\" href=\"https:\/\/learn.microsoft.com\/en-us\/entra\/identity-platform\/tutorial-native-authentication-android-identity-provider-sign-in-sign-up?toc=\/entra\/external-id\/toc.json&amp;bc=\/entra\/external-id\/breadcrumb\/toc.json\" target=\"_blank\">Tutorial: Add email one-time passcode MFA to your Android app<\/a><\/div><\/p>\n<p><div  class=\"d-flex justify-content-center\"><a class=\"cta_button_link btn-primary mb-24\" href=\"https:\/\/learn.microsoft.com\/en-us\/entra\/identity-platform\/tutorial-native-authentication-android-email-strong-authentication-method?toc=%2Fentra%2Fexternal-id%2Ftoc.json&amp;bc=%2Fentra%2Fexternal-id%2Fbreadcrumb%2Ftoc.json\" target=\"_blank\">Tutorial: Add federated identity provider sign-in and sign-up web flow to your Android app<\/a><\/div><\/p>\n<p><div  class=\"d-flex justify-content-center\"><a class=\"cta_button_link btn-primary mb-24\" href=\"https:\/\/learn.microsoft.com\/en-us\/entra\/identity-platform\/tutorial-native-authentication-single-page-app-react-social-sign-in\" target=\"_blank\">Tutorial: Support federated identity providers in a React single-page app by using native authentication JavaScript SDK<\/a><\/div><\/p>\n<p><div  class=\"d-flex justify-content-center\"><a class=\"cta_button_link btn-primary mb-24\" href=\"https:\/\/learn.microsoft.com\/en-us\/entra\/identity-platform\/tutorial-native-authentication-single-page-app-angular-social-sign-in\" target=\"_blank\">Tutorial: Support federated identity providers in an Angular single-page app by using native authentication JavaScript SDK<\/a><\/div><\/p>\n<h2>Stay connected and informed<\/h2>\n<p>To learn more or test out features in the Microsoft Entra suite of products, visit our\u202f<a href=\"https:\/\/developer.microsoft.com\/en-us\/identity\/\">developer center<\/a>. Make sure you subscribe to the\u202f<a href=\"https:\/\/devblogs.microsoft.com\/identity\/\">Identity blog<\/a>\u202ffor more insights and to keep up with the latest on all things Identity. And, follow us on <a href=\"https:\/\/www.youtube.com\/@MicrosoftSecurity\/playlists\">YouTube<\/a> for video overviews, tutorials, and deep dives.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>We\u2019re excited to announce the General Availability of Social Identity Provider (IdP) support for Native Authentication in Microsoft Entra External ID. This release enables developers to integrate popular social sign\u2011in options such as Google, Facebook, and Apple \u2014 into native and single\u2011page applications that use Native Authentication. Importantly, social identity providers are supported through a [&hellip;]<\/p>\n","protected":false},"author":135210,"featured_media":2495,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[33],"tags":[],"class_list":["post-2478","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-product-updates"],"acf":[],"blog_post_summary":"<p>We\u2019re excited to announce the General Availability of Social Identity Provider (IdP) support for Native Authentication in Microsoft Entra External ID. This release enables developers to integrate popular social sign\u2011in options such as Google, Facebook, and Apple \u2014 into native and single\u2011page applications that use Native Authentication. Importantly, social identity providers are supported through a [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/identity\/wp-json\/wp\/v2\/posts\/2478","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/identity\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/identity\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/identity\/wp-json\/wp\/v2\/users\/135210"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/identity\/wp-json\/wp\/v2\/comments?post=2478"}],"version-history":[{"count":1,"href":"https:\/\/devblogs.microsoft.com\/identity\/wp-json\/wp\/v2\/posts\/2478\/revisions"}],"predecessor-version":[{"id":2494,"href":"https:\/\/devblogs.microsoft.com\/identity\/wp-json\/wp\/v2\/posts\/2478\/revisions\/2494"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/identity\/wp-json\/wp\/v2\/media\/2495"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/identity\/wp-json\/wp\/v2\/media?parent=2478"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/identity\/wp-json\/wp\/v2\/categories?post=2478"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/identity\/wp-json\/wp\/v2\/tags?post=2478"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}