# Inquiries configure domain for non federated

**URL:** <https://community.auth0.com/t/inquiries-configure-domain-for-non-federated/136690>\
**Category:** Get Help\
**Tags:** other, community-topic\
**Created:** [June 20, 2024, 2:59am UTC](https://community.auth0.com/t/inquiries-configure-domain-for-non-federated/136690 "2024-06-20T02:59:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![marcelina.barycka](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/marcelina.barycka/32/56162_2.png) [@marcelina.barycka](https://community.auth0.com/u/marcelina.barycka)\
**Post date:** [June 20, 2024, 11:38am UTC](https://community.auth0.com/t/inquiries-configure-domain-for-non-federated/136690/2 "2024-06-20T11:38:31Z")

</div>

Hi tehre @rizki.rachman ,

Thank you for reaching out.

You should be able to keep the AzureAD B2B connection as a button in the New Universal Login widget. For the rest of SAML connections you can utilize [Home REALM discovery](https://auth0.com/docs/authenticate/login/auth0-universal-login/identifier-first#define-home-realm-discovery-identity-providers) while for the non-federated users - use a regular database connection. 🙂

For these settings, I suggest using the [Identifier first](https://auth0.com/docs/authenticate/login/auth0-universal-login/identifier-first#configure-identifier-first) login experience so that a user is first presented with a screen to enter their email.

You can also read more in this post: [Multiple Connections per Organization - #4 by marcelina.barycka](https://community.auth0.com/t/multiple-connections-per-organization/98549/4).

Does this answer your question?

---

_[View the full topic](https://community.auth0.com/t/inquiries-configure-domain-for-non-federated/136690)._