# Getting "That Microsoft account doesn't exist" for Microsoft logins?

**URL:** <https://community.auth0.com/t/getting-that-microsoft-account-doesnt-exist-for-microsoft-logins/161889>\
**Category:** Get Help\
**Tags:** login-experience, new-universal-login-experience\
**Created:** [December 12, 2024, 3:14pm UTC](https://community.auth0.com/t/getting-that-microsoft-account-doesnt-exist-for-microsoft-logins/161889 "2024-12-12T15:14:58Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![kkrp1](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@kkrp1](https://community.auth0.com/u/kkrp1)\
**Post date:** [December 12, 2024, 3:14pm UTC](https://community.auth0.com/t/getting-that-microsoft-account-doesnt-exist-for-microsoft-logins/161889/1 "2024-12-12T15:14:58Z")

</div>

I’ve set up social login with Microsoft and it works fine when I test with personal MS accounts e.g. [something@outlook.com](mailto:something@outlook.com). But we’re finding that multiple of our clients who use MS for their organisation email are getting the below error (see image).

I have verified that the Azure app I set up to connect to Auth0 supports _all_ types of MS account, not just personal ones.

 ![image](https://global.discourse-cdn.com/auth0/original/3X/2/6/26858675ace8a0d5a42812ee8a5d599d376050c6.png)

Any thoughts here?

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [December 12, 2024, 7:08pm UTC](https://community.auth0.com/t/getting-that-microsoft-account-doesnt-exist-for-microsoft-logins/161889/3 "2024-12-12T19:08:36Z")

</div>

Hi @kkrp1,

Microsoft Social logins are generally used to log in with their personal MS accounts. If you require your end-users to log in with their MS account for their organization, you have to [Connect Your App to Microsoft Azure Active Directory](https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/azure-active-directory/v2).

Let me know if you have any follow-up questions.

Thanks,  
Rueben

---

<div class="post-metadata">

**Author:** ![kkrp1](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@kkrp1](https://community.auth0.com/u/kkrp1)\
**Post date:** [December 13, 2024, 4:20pm UTC](https://community.auth0.com/t/getting-that-microsoft-account-doesnt-exist-for-microsoft-logins/161889/4 "2024-12-13T16:20:56Z")

</div>

Hi @rueben.tiow

Thanks for the reply. But I’ve already done most of the steps in the linked article. That is, I have the app, I’ve set up the redirect URLs, the permissions, etc. And the below screenshot suggests that organisational accounts should work. See below:

 ![image](https://global.discourse-cdn.com/auth0/original/3X/8/b/8baf9afb955260cf96abf087753d1c3ab764fe2c.png)

The one part of the article I can’t do is the part about Auth0 Enterprise. I’m a free user. So does this ultimately mean I can’t support organisational MS login, in the same way I **can** with organisational Google login (working fine)?

Continued thanks.

---

<div class="post-metadata">

**Author:** ![kkrp1](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@kkrp1](https://community.auth0.com/u/kkrp1)\
**Post date:** [December 16, 2024, 1:15pm UTC](https://community.auth0.com/t/getting-that-microsoft-account-doesnt-exist-for-microsoft-logins/161889/5 "2024-12-16T13:15:49Z")

</div>

@rueben.tiow Apologies but any further thoughts here based on the above?

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [December 16, 2024, 6:36pm UTC](https://community.auth0.com/t/getting-that-microsoft-account-doesnt-exist-for-microsoft-logins/161889/6 "2024-12-16T18:36:20Z")

</div>

Hi @kkrp1,

Thanks for your replies.

> [@kkrp1](#):
>
> The one part of the article I can’t do is the part about Auth0 Enterprise. I’m a free user.

That’s correct! I have just checked your tenant and confirmed that you are on the free subscription plan, which does not allow you to use Enterprise Connections. This feature is only available to Enterprise subscription plans.

Secondly, when I check your connection settings, it looks like you have Google and Microsoft social connections configured with your own developer keys. Neither of them is an Enterprise connection.

One thing we could do is to set your tenant on the trial period again so you can test these features out. However, if enterprise connections are a requirement, you will need to upgrade your tenant to an Enterprise subscription plan.

Let me know if this is something you would like me to do.

Thanks,  
Rueben

---

<div class="post-metadata">

**Author:** ![kkrp1](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@kkrp1](https://community.auth0.com/u/kkrp1)\
**Post date:** [December 17, 2024, 9:24pm UTC](https://community.auth0.com/t/getting-that-microsoft-account-doesnt-exist-for-microsoft-logins/161889/7 "2024-12-17T21:24:07Z")

</div>

Hi @rueben.tiow

Thanks for your helpful reply. Could I just row back a bit to clarify something for my understanding: all I’m trying to do is support login via Google and Microsort. It works with Google, but with Microsoft it works only with personal accounts. Are you saying that, to support Microsoft work/organisation accounts, I need Enterprise?

Or am I on the wrong lines…

Continued thanks,

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [December 18, 2024, 8:22pm UTC](https://community.auth0.com/t/getting-that-microsoft-account-doesnt-exist-for-microsoft-logins/161889/8 "2024-12-18T20:22:45Z")

</div>

Hi @kkrp1,

Thanks for the follow-up.

Yes, that is correct. You will need Enterprise to support Microsoft’s work/organization accounts. The Microsoft Social connection is only meant for personal accounts.

Thanks,  
Rueben

---

<div class="post-metadata">

**Author:** ![kkrp1](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@kkrp1](https://community.auth0.com/u/kkrp1)\
**Post date:** [December 19, 2024, 7:53pm UTC](https://community.auth0.com/t/getting-that-microsoft-account-doesnt-exist-for-microsoft-logins/161889/9 "2024-12-19T19:53:39Z")

</div>

Thanks @rueben.tiow for the clarification. Just out of interest, that’s not the case for Google, right? I have Google logins working fine, even with work/organisational Google accounts, not just personal.

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [December 19, 2024, 11:06pm UTC](https://community.auth0.com/t/getting-that-microsoft-account-doesnt-exist-for-microsoft-logins/161889/10 "2024-12-19T23:06:02Z")

</div>

Hi @kkrp1,

Of course, you’re welcome.

For Google, there is the [Google Workspace](https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/google-apps) Enterprise connection and [Google Social](https://marketplace.auth0.com/integrations/google-social-connection) connection.

The difference is that Google Social is a Social IdP, whereas Google Workspace is an Enterprise IdP.

Here are some key takeaways:  
**Social IdP (Google Social Connection):**

- Anyone who has an account in the IdP can login.
  - For example, I can create a new Google account and log in to your application.

- You receive some pre-defined user profile attributes from the IdP.
- Mainly used for B2C applications.

**Enterprise IdP (Google Workspace SSO):**

- Only the members of your IdP can log in.
  - Since I have a normal/social Google account, I cannot log in to your application because I’m not a member of your Google Workspace.

- You can define what user profile attributes you send from the IdP to the Auth0 tenant. For example, attributes that you use for access control purposes: role, name of the team the user belongs, etc.
- Mainly used for B2B applications.

I hope the clarification helps!

Thanks,  
Rueben

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [January 2, 2025, 11:06pm UTC](https://community.auth0.com/t/getting-that-microsoft-account-doesnt-exist-for-microsoft-logins/161889/12 "2025-01-02T23:06:36Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
