# Azure AD multitenant configuration not working

**URL:** <https://community.auth0.com/t/azure-ad-multitenant-configuration-not-working/11154>\
**Category:** Get Help\
**Created:** [April 25, 2018, 10:52pm UTC](https://community.auth0.com/t/azure-ad-multitenant-configuration-not-working/11154 "2018-04-25T22:52:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sr.lucas](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sr.lucas/32/13158_2.png) [@sr.lucas](https://community.auth0.com/u/sr.lucas)\
**Post date:** [April 25, 2018, 10:52pm UTC](https://community.auth0.com/t/azure-ad-multitenant-configuration-not-working/11154/1 "2018-04-25T22:52:13Z")

</div>

Hi all,  
We are a SaaS and we are trying to add support to different Azure Active Directories.

So I’m trying to set up a multi-tenant Azure AD authentication that will point to the common [https://login.windows.net/common](https://login.windows.net/common) .

When I enable the toggle that does so, and save. Nothing happens.

I did not set the app uri because 1) I’m not sure where to get it from, 2) it appears to be optional.

Any ideas?

---

<div class="post-metadata">

**Author:** ![sr.lucas](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sr.lucas/32/13158_2.png) [@sr.lucas](https://community.auth0.com/u/sr.lucas)\
**Post date:** [April 25, 2018, 11:11pm UTC](https://community.auth0.com/t/azure-ad-multitenant-configuration-not-working/11154/2 "2018-04-25T23:11:55Z")

</div>

This is the URL the current configuration goes to: https://login.microsoftonline.com/lukewoocar.onmicrosoft.com/login

and of course, since the user does not belong to my own AD, but to a different one, the following error is thrown:  
User account ‘test.woocar@zarcam.com.ar’ from identity provider ‘[https://sts.windows.net/71034d81-e1c6-4ec2-9425-313a89c5e393/](https://sts.windows.net/71034d81-e1c6-4ec2-9425-313a89c5e393/)’ does not exist in tenant ‘Woocar AD’ and cannot access the application ‘a453aa36-0abd-42bb-9a52-54e505e499c9’ in that tenant. The account needs to be added as an external user in the tenant first. Sign out an

---

<div class="post-metadata">

**Author:** ![jcuribe](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@jcuribe](https://community.auth0.com/u/jcuribe)\
**Post date:** [January 16, 2019, 8:56pm UTC](https://community.auth0.com/t/azure-ad-multitenant-configuration-not-working/11154/3 "2019-01-16T20:56:14Z")

</div>

Hi, did you ever solve this issue. I am having the same issue.

---

<div class="post-metadata">

**Author:** ![jonah.mcintire.admin](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jonah.mcintire.admin/32/14803_2.png) [@jonah.mcintire.admin](https://community.auth0.com/u/jonah.mcintire.admin)\
**Post date:** [July 19, 2019, 10:23am UTC](https://community.auth0.com/t/azure-ad-multitenant-configuration-not-working/11154/4 "2019-07-19T10:23:35Z")

</div>

I’m also hitting this issue, and agree that the documentation is dated.

---

<div class="post-metadata">

**Author:** ![swathy.jayaseelan](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/swathy.jayaseelan/32/13131_2.png) [@swathy.jayaseelan](https://community.auth0.com/u/swathy.jayaseelan)\
**Post date:** [August 4, 2019, 5:39pm UTC](https://community.auth0.com/t/azure-ad-multitenant-configuration-not-working/11154/5 "2019-08-04T17:39:03Z")

</div>

@jonah.mcintire.admin Were you able to solve this issue? I am stuck because of this.

---

<div class="post-metadata">

**Author:** ![a7labs](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@a7labs](https://community.auth0.com/u/a7labs)\
**Post date:** [February 23, 2023, 6:08pm UTC](https://community.auth0.com/t/azure-ad-multitenant-configuration-not-working/11154/6 "2023-02-23T18:08:29Z")

</div>

Was able to resolve this on my end, If you’re using an enterprise connection, you need to make sure click the “Use Common Endpoint”, this will allow Microsoft to handle the Home Realm discovery

 ![image](https://global.discourse-cdn.com/auth0/original/3X/0/a/0ae3b65ef421eac491e3417f797060be6314351a.png)
