What Is Slack Error AADSTS75011 and How Do I Fix It?

A Microsoft Entra/Azure AD sign-in mismatch — here’s what it means and how to fix it

---

Seeing AADSTS75011 when trying to sign into Slack through your work account is a specific Microsoft Entra ID (formerly Azure Active Directory) error rather than something originating from Slack itself.

This error means the authentication method your organization’s identity system tried to use doesn’t match what was actually requested or expected during sign-in. Here’s exactly what’s happening and how to resolve it.

---

What AADSTS75011 Actually Means

AADSTS error codes come from Microsoft Entra ID, the identity and access management system many organizations use to control sign-ins to work-connected apps like Slack through Single Sign-On (SSO). The specific code 75011 relates to a mismatch in the authentication method — Microsoft’s identity platform expected a particular way of verifying you (such as a specific multi-factor method, or a particular conditional access policy outcome) and what actually happened during the sign-in attempt didn’t line up with that expectation.

Slack itself is just the application requesting sign-in — it passes you over to your organization’s Microsoft identity system to handle authentication, and this error comes back from that handoff rather than from anything Slack’s own servers are doing.

---

This Is an IT Admin-Side Issue, Not a Slack Bug

The most important thing to understand upfront — this error is almost always rooted in how your organization’s Microsoft Entra ID and conditional access policies are configured, not in anything wrong with your Slack account, your password, or Slack’s service itself.

This means the fix usually isn’t something you can fully resolve on your own as an end user — your IT administrator typically needs to adjust a policy on their end. Still, there are checks worth doing first, since a few common situations can be resolved without IT involvement.

---

Try Signing In Again

Authentication handoffs between Slack and Microsoft Entra occasionally fail transiently due to a brief timing issue or a session token that expired mid-process.

Close the sign-in window, return to Slack, and attempt to sign in again from scratch. If this was a one-time hiccup rather than a policy misconfiguration, a second attempt sometimes succeeds without any other changes.

---

Clear Browser Cache and Cookies

Stale authentication cookies or cached sign-in data from Microsoft’s login pages can cause the wrong authentication context to be sent, triggering this mismatch error even when the underlying policy would otherwise allow you in.

Clear cookies and cached data specifically for login.microsoftonline.com and slack.com, or clear your browser’s cache entirely via Ctrl + Shift + Delete (or Cmd + Shift + Delete on Mac), setting the time range to All Time. Restart the browser and try signing in again.

---

Try an Incognito or Private Window

Testing in a private browsing window rules out extensions, cached sessions, and cookies all at once, and quickly tells you whether the issue is browser-state-related.

Open an incognito or private window (Ctrl + Shift + N in Chrome/Edge, or Cmd + Shift + N on Mac), navigate to Slack, and attempt to sign in there. If it succeeds, your regular browser session had stale data causing the conflict — the cache clear above resolves it going forward.

---

Try the Slack Desktop App Instead of a Browser (or Vice Versa)

Switching between the desktop app and a browser sometimes avoids the specific authentication path that’s triggering the mismatch, since the two can occasionally handle the SSO handoff slightly differently depending on how your organization’s Entra ID app registration is configured.

If you were trying to sign in through a browser, try the Slack desktop app instead, or vice versa, and see whether the alternate path succeeds.

---

Check Whether You’re Using the Correct Sign-In Method

If your organization requires a specific method — such as signing in only through a company-managed device, a specific VPN connection, or a particular multi-factor authentication app — attempting to sign in outside of that expected context is a common trigger for this exact error.

Confirm you’re on your normal work device and network if your organization restricts sign-ins that way, and confirm you’re using the multi-factor method your IT department has set up for you (an authenticator app, a hardware key, etc.) rather than an old or unsupported method.

---

Try a Different Network

Conditional access policies in Microsoft Entra ID frequently restrict sign-ins based on network location — for example, requiring a corporate VPN or blocking sign-ins from networks Microsoft hasn’t been told to trust.

If you’re on a home network, public Wi-Fi, or a personal hotspot, try connecting through your organization’s VPN if one is available, then attempt to sign in again. If a network-based conditional access policy is the cause, this often resolves it immediately.

---

Check for an Expired or Misconfigured Multi-Factor Authentication Method

If your MFA method itself has expired, been deregistered, or was recently changed (a new phone, a reset authenticator app, an expired hardware key), Entra ID can fail to match the expected authentication strength during sign-in, producing this exact mismatch error.

Try authenticating with a backup MFA method if you have one configured. If your primary method seems to be the problem, this is something to flag to your IT department, since re-registering or resetting an MFA method on a managed account typically isn’t something end users can fully self-serve.

---

Report It to Your IT Administrator With the Full Error Details

Since the root cause lives in your organization’s Entra ID configuration, this is the step that resolves the issue in most cases that survive the basic checks above.

When you contact your IT helpdesk or administrator, provide:

The exact error code (AADSTS75011) and the full error message if more detail was shown beyond just the code. The approximate time the error occurred. What app you were signing into (Slack) and what method you were using (browser vs. desktop app, which network, which device).

This lets your IT team look directly at Entra ID sign-in logs for your account at that specific time, which show exactly which conditional access policy or authentication method requirement caused the failure — information that isn’t visible to you as the end user but is the fastest path to a real fix on their end.

---

What IT Administrators Typically Check

If you’re the administrator receiving this report, AADSTS75011 specifically points toward a few common configuration areas worth checking in the Microsoft Entra admin center:

Conditional Access policies — review policies applied to the affected user and the Slack enterprise application, checking for authentication strength requirements that may not align with what’s actually configured for that user’s MFA methods.

Authentication method policies — confirm the user’s registered MFA methods match what conditional access policies expect, particularly after any recent changes to authentication method policies at the tenant level.

Slack’s Entra ID app registration/SSO configuration — confirm the SAML or OIDC configuration between Slack and Entra ID hasn’t drifted out of sync, particularly after any recent changes to either Slack’s SSO settings or the Entra ID enterprise application.

Sign-in logs — the Entra admin center → Monitoring → Sign-in logs, filtered to the affected user and timeframe, show the specific policy or requirement that triggered the failure in much more detail than the end-user-facing error provides.

---

A Quick Checklist

Work through these in order:

• Try signing in again — rule out a transient failure
• Clear browser cache and cookies for login.microsoftonline.com and slack.com
• Try an incognito/private window
• Switch between the desktop app and browser sign-in methods
• Confirm you’re using the expected device, network, and MFA method
• Try connecting through your organization’s VPN if applicable
• Try a backup MFA method if your primary one may be expired or misconfigured
• Report the exact error code and timing to your IT administrator if the above doesn’t resolve it

---

The Bottom Line

AADSTS75011 is a Microsoft Entra ID authentication mismatch error passed through during Slack’s SSO sign-in process — not a fault in Slack itself. A handful of end-user checks (clearing cache, trying a different network or sign-in method, confirming MFA is working correctly) resolve some cases, but the underlying cause typically lives in your organization’s conditional access policy configuration.

If the basic checks don’t work, the fastest real fix is reporting the exact error code and timing to your IT administrator, since they have direct access to Entra ID’s sign-in logs showing precisely which policy or requirement caused the mismatch — detail that isn’t available to you as the person signing in.

Slack is just the messenger here — the actual conversation about whether you’re allowed in is happening between your browser and your organization’s Microsoft identity system, and that’s where this one gets fixed.