<![CDATA[Using Separate Applications in a Single Tenant for AD/Entra ID and Client Authentication]]>We’d like to configure FusionAuth so that our Admin portal authenticates against Active Directory/Microsoft Entra ID, while our client-facing site uses FusionAuth for authentication. Does this setup make sense, and should we use separate tenants for this, or can both flows be managed within a single tenant?

]]>https://fusionauth.io/community/forum/topic/3056/using-separate-applications-in-a-single-tenant-for-ad-entra-id-and-client-authenticationRSS for NodeWed, 11 Mar 2026 03:40:10 GMTWed, 10 Sep 2025 01:11:07 GMT60<![CDATA[Reply to Using Separate Applications in a Single Tenant for AD/Entra ID and Client Authentication on Wed, 10 Sep 2025 01:12:52 GMT]]>You can manage both flows within a single tenant. Typically, you’d configure separate applications, one for the Admin portal tied to your AD/Entra ID provider, and another for your client-facing site using FusionAuth. You can then use login hints or managed domains to direct users to the correct Identity Provider (IdP).

Identity Provider Hints
Managed Domains

]]>https://fusionauth.io/community/forum/post/8368https://fusionauth.io/community/forum/post/8368Wed, 10 Sep 2025 01:12:52 GMT