Native Authentication
In brief
Browser-based apps require a tenant-verified custom domain, while non-browser clients using native HTTP transports do not.
What Entra admins need to know
Configure a tenant-verified custom domain for API V2 browser-based applications to support their authentication journeys.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
ms.service: identity-platform
ms.subservice: external
ms.topic: overview
ms.date: 11/13/17/2026
ms.custom: msecd-doc-authoring-1030
ai-usage: ai-assisted
#customer intent: As an application developer, I want to understand Embedded native authentication so that I can choose and implement an application-managed authentication experience.
SPAs with Embedded native authentication and BYO UX websites need a proxy or edge cross-origin resource sharing (CORS) policy for cross-origin browser API calls. Android and iOS apps using native HTTP transports don't need CORS or a CORS proxy. See Native authentication CORS concepts.
All serviceThe Native Authentication API calls in the current native authentication integration useV2 requires a tenant-verified custom domain for browser-based apps, such as SPAs, to help protect against cross-site request forgery (CSRF). Non-browser clients, such as Android and iOS apps using native HTTP transports, don't require a custom domain. An embedded browser or webview isn't a native HTTP transport. BYO UX websites still require a tenant-verified custom domain. Configure the tenant GUID. Configure thatservice authority before starting a journey; see Configure the API authority.
@@ -5,7 +5,7 @@ manager: dougeby ms.service: identity-platform ms.subservice: external ms.topic: overview-ms.date: 11/13/2026+ms.date: 11/17/2026 ms.custom: msecd-doc-authoring-1030 ai-usage: ai-assisted #customer intent: As an application developer, I want to understand Embedded native authentication so that I can choose and implement an application-managed authentication experience.@@ -74,7 +74,7 @@ Use the configuration guide and API references for a direct integration, or use SPAs with Embedded native authentication and BYO UX websites need a proxy or edge cross-origin resource sharing (CORS) policy for cross-origin browser API calls. Android and iOS apps using native HTTP transports don't need CORS or a CORS proxy. See [Native authentication CORS concepts](concept-native-authentication-cors.md). -All service API calls in the current native authentication integration use a tenant-verified custom domain and the tenant GUID. Configure that authority before starting a journey; see [Configure the API authority](how-to-native-authentication-configure-app.md#configure-the-api-authority).+The Native Authentication API V2 requires a tenant-verified custom domain for browser-based apps, such as SPAs, to help protect against cross-site request forgery (CSRF). Non-browser clients, such as Android and iOS apps using native HTTP transports, don't require a custom domain. An embedded browser or webview isn't a native HTTP transport. BYO UX websites still require a tenant-verified custom domain. Configure the service authority before starting a journey; see [Configure the API authority](how-to-native-authentication-configure-app.md#configure-the-api-authority). <a name="security-considerations-for-native-authentication"></a> 