Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix AADSTS50058

AADSTS50058 and AADSTS16000: silent sign-in failed with no usable session

11 min read Updated October 5, 2026 Microsoft 365 & Entra ID

Fix it now

An application asked for a token quietly, without showing anyone a sign-in page, and there was no usable session to draw on. Most of the time that is not a fault at all: it is the first half of a normal pattern where the application tries silently, is told to ask properly, and then prompts. It is a real problem only when the prompt never appears or the browser loops.

  1. Reproduce it in a private browsing window. If the sign-in completes there, the fault is in the cookie state of the ordinary profile, not in your tenant.
  2. In the normal window, sign out of every Microsoft session from the account menu, close all browser windows, and reopen.
  3. Clear cookies for the Microsoft sign-in domains and for the application’s own domain, then try again.
  4. Check that the browser is not blocking third-party cookies for those sign-in domains. Strict tracking protection breaks the hidden frame silent authentication relies on.
  5. If two or more accounts are signed into the same browser, sign out of all but the one you need, or give each identity its own browser profile.
  6. Look at the record in Entra ID then Monitoring & health then Sign-in logs. If the interrupt is followed within seconds by a successful interactive sign-in, nothing is broken and no action is needed.

Microsoft notes that AADSTS50058 may be returned to the application when the request specified prompt=none. If your logs are full of them and users are signing in normally, that is the mechanism working, not a fault to chase.

If users can sign in and the interrupts are followed by successes, you are done. If the browser loops or the prompt never appears, the next section explains why.

Why it happens

When an application already believes it knows who you are, it does not put a sign-in page in front of you. It asks the token service for a token on the quiet, relying on either a session cookie held in the browser or a cached grant held by the application. If that cookie is missing, unreadable or ambiguous, the service has no basis on which to decide who is asking. Rather than guessing, it returns an interrupt, and the application is expected to fall back to an interactive request. That interrupt is AADSTS50058, published as session information not being sufficient for single sign-on.

AADSTS16000 is the ambiguity case rather than the absence case. Microsoft’s sign-in error lookup describes it as either multiple user identities being available for the current request, or the selected account not being supported for the scenario. In practice that means several valid sessions exist in that browser and nothing in the request said which to use, so account selection has to be shown. AADSTS16001 follows when the user picks a session tile the select logic rejects, and it is recoverable: the user is offered an updated list of tiles or another account.

AADSTS50059 and AADSTS50128 are the tenant-identification cases. Both mean no tenant-identifying information was found in the request or implied by any provided credentials, which happens when a request reaches a generic endpoint carrying neither a domain hint nor a credential the service can work back from. That is a request-construction problem, and it is usually a hand-built link or an application pointed at the wrong authority rather than anything in the directory.

More than one Microsoft account is signed into the same browser

You have this one if AADSTS16000 or AADSTS16001 in the log, and the problem disappears in a private window.

  1. Sign out of all accounts and sign back in with only the one required.
  2. Give each identity its own browser profile if people genuinely need both at once.
  3. If you own the application, supply a login hint or a domain hint on the authorisation request so the correct session is chosen without asking.
  4. Where a stale account tile keeps reappearing, remove it from the account picker rather than clicking past it.

Cookies for the sign-in domain are blocked, cleared or not persisted

You have this one if AADSTS50058 on every launch, including after a full restart, on a browser set to clear data on exit or to block third-party cookies.

  1. Allow cookies for the Microsoft sign-in domains and for the application’s own domain.
  2. Turn off any policy that clears browsing data on exit for managed devices that need single sign-on.
  3. Check browser policies pushed from Group Policy or your device management platform; centrally applied cookie restrictions are easy to miss on the endpoint.
  4. Avoid launching the application inside an embedded web view that does not share the system browser’s cookie store.

The request carries no tenant or domain information

You have this one if AADSTS50059 or AADSTS50128, usually from a custom application or a link somebody constructed by hand.

  1. Point the application at a tenant-specific authority instead of a generic one, or supply a domain hint.
  2. Confirm the domain suffix being used is one of the verified domains on the tenant, not a similar-looking one.
  3. Check for a typo in the domain suffix in a bookmarked or emailed sign-in link.

The application loops on the silent call instead of falling back

You have this one if The same interrupt repeats every few seconds for one application while everything else is fine.

  1. In the application code, treat the interrupt as a signal to make an interactive request, not as an error to retry.
  2. Move any application still using a retired authentication library onto the current Microsoft authentication library.
  3. Confirm the reply address configured in the app registration matches the address the browser is actually returned to, including scheme and path.

A loop that survives a private browsing window is almost always application logic rather than tenant configuration. That single test saves a great deal of arguing.

A session policy is ending the session sooner than the application expects

You have this one if The interrupt appears at a predictable interval that matches a sign-in frequency or persistent browser session setting.

  1. Check the Conditional Access session controls applying to that application or user group.
  2. Sign-in frequency specifies how long a user can stay signed in before being prompted again; persistent browser session decides whether they stay signed in after closing the browser.
  3. Decide whether the interval is what you intended, and explain the expected prompt cadence to users rather than treating each prompt as an incident.

Full reference

Reading the pattern before changing anything

Pattern Most likely explanation
Interrupt immediately followed by a successful sign-in Normal fallback to an interactive prompt. No action needed
The browser bounces between application and sign-in page The session cookie is not being written back, or the reply address does not match
Only happens with two accounts in one browser No account hint was supplied, so no session could be selected
Only on shared or kiosk machines Profiles are reset between sessions and discard the cookie
Only on one network A proxy is intercepting or stripping cookies on the sign-in domain
At a regular interval matching a policy A Conditional Access session control doing exactly what it was configured to do

Why the log volume is not the measure

Modern Microsoft clients attempt silent token acquisition constantly, and every unsuccessful attempt is recorded. A healthy tenant therefore produces a steady stream of these interrupts, and counting them tells you nothing about whether anything is wrong. What matters is whether each interrupt is followed by a successful sign-in and whether real users are reporting that they cannot get in. If the answer to the first is yes and the second is no, the correct action is to stop looking.

The private window test

  1. Open a private or incognito window with no extensions carried over.
  2. Navigate directly to the application rather than through a bookmark or a link in mail.
  3. Sign in with the single account that should have access.
  4. If it works, the problem is cookie state or account ambiguity in the ordinary profile.
  5. If it fails identically, the problem is the application, the app registration or a policy, and no amount of cookie clearing will touch it.

Hints that stop the ambiguity happening

  • A login hint on the authorisation request nominates the account, so the service does not have to ask.
  • A domain hint sends the request to the right identity provider without a home realm discovery step.
  • Both are set by whoever owns the application, which makes this a development conversation rather than a directory one.
  • Neither is a substitute for users understanding that two accounts in one browser profile will produce prompts.
  • For shared devices, expect the interrupt on every launch and design around it rather than trying to suppress it.

When it is a policy rather than a fault

A prompt arriving on a schedule is a session control working. Sign-in frequency sets how long a user can stay signed in before being challenged again, and persistent browser session controls whether the session survives closing the browser. Neither is a defect, and removing the control to stop the prompts trades a deliberate security position for quiet. If the cadence is wrong, change the interval deliberately and tell people what to expect.

Every code this article covers

Code What it points at Source
AADSTS50058 UserInformationNotProvided: session information is not sufficient for single sign-on, which means the user is not signed in. It may be returned to the application when the request specified prompt=none Microsoft Learn
AADSTS16000 Either multiple user identities are available for the current request, or the selected account is not supported for the scenario, so account selection has to be shown Microsoft sign-in error lookup
AADSTS16001 UserAccountSelectionInvalid: the user selected a tile the session select logic rejected. They can recover by choosing from an updated list or another account Microsoft Learn
AADSTS50059 MissingTenantRealmAndNoUserInformationProvided: no tenant-identifying information was found in the request or implied by any provided credentials Microsoft Learn
AADSTS50128 Invalid domain name: no tenant-identifying information was found in the request or implied by any provided credentials Microsoft Learn

Confirm the fix worked

  1. The affected user signs in from the ordinary browser profile without a loop and without needing a private window.
  2. The sign-in logs show the interrupt followed by a successful entry, or no interrupt at all.
  3. Signing out and back in a second time reuses the session silently, which proves the cookie is persisting.
  4. A second user on the same managed device build gets the same result, confirming the browser policy change applied.
  5. Any prompt that remains lines up with a session control you deliberately configured.

Questions people ask about this

Does fixing this cost anything?

No. Everything described here is browser configuration, application behaviour or account hygiene. There is no plan, add-on or licence that makes silent sign-in work better.

My sign-in logs are full of AADSTS50058. Is the tenant broken?

Almost certainly not. Microsoft notes the code may be returned when a request specifies prompt=none, and modern clients make silent requests constantly. Judge it by whether users can sign in, not by how many interrupts appear.

What does AADSTS16000 actually mean?

That either multiple identities are available for the request or the selected account is not supported for the scenario. In practice it is the account picker being required because nothing in the request said which session to use.

Why does it always work in a private window?

A private window starts with no cookies and no cached accounts, so the application goes straight to an interactive sign-in instead of trying and failing to reuse something. That is a strong sign the problem is cookie state rather than policy.

Should I remove the Conditional Access policy to stop the prompts?

No. Prompts caused by a session control are the policy doing its job. If the cadence is wrong, change the interval deliberately rather than removing the control to silence a symptom.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix AADSTS50020 and AADSTS50034: the account does not exist in this tenant License Error 550 5.1.90 and 550 5.7.232: Exchange Online sending limits have been hit Free Fix HTTP 429 and HTTP 503 in SharePoint Online: throttling and list limits License Error Intune 0x8018002b and 0x80180014: MDM scope, UPN suffix and platform settings block enrolment
โ† Back to Knowledge Base