Fix it now
AADSTS50058 is not an error. Microsoft publishes it as UserInformationNotProvided: session information is not sufficient for single sign-on, which is expected when nobody is signed in and is what an application gets back when it asks for a token with prompt=none. What is actually refusing you is named by the companion code.
dsregcmd /status
- Get the real reason from the tenant rather than the client. In the Entra admin centre open the sign-in logs, filter to the affected user and the time of the failure, and open the failed entry.
- Read the conditional access tab of that entry. It names each policy and whether it succeeded, failed or did not apply.
- Read the single sign-on state section of the dsregcmd output. A device with no usable token turns every request into an interactive one, which then trips whatever interactive requirements exist.
- If a policy is named, run the conditional access What If tool with that user, application and device state to confirm it is the one biting.
- Resolve the requirement rather than the symptom: complete multifactor registration, or fix the failing compliance rule on the device.
- Only then clear the client: sign out of Office, remove its Credential Manager entries, restart, and sign in once interactively.
Disabling a conditional access policy is not a fix, it is the removal of a control. Keep at least one cloud-only administrator account excluded from every policy so you can never lock yourself out.
If the user signs in once and is not prompted again on the next launch, you are done. The next section explains what each refusal actually means.
Why it happens
Office does not ask for a password on every request. It acquires a token once, caches it, and refreshes it silently afterwards. Silent refresh works when the client can present something the identity service already trusts: a token issued to the device, or an existing browser session. AADSTS50058 is the service reporting that it received a silent request with nothing to work from – Microsoft’s own text says this is common and expected when a user is unauthenticated, and that it can be returned to an application when prompt=none is specified.
So 50058 tells you the silent path failed and nothing more. The code sitting beside it in the sign-in log is the one that matters, and the four you will meet are worth telling apart because they lead to different places.
AADSTS50079 is UserStrongAuthEnrollmentRequired: the user is required to use multifactor authentication and either needs to register security information, or, if federated, needs the multifactor claim from their identity provider. That cannot be satisfied at a desktop prompt. AADSTS53003 and AADSTS530003 both carry the same published text – BlockedByConditionalAccess, access has been blocked by Conditional Access policies, the access policy does not allow token issuance – so seeing one rather than the other tells you nothing extra.
AADSTS50097 is DeviceAuthenticationRequired, which measures the machine rather than the person. AADSTS50158 is the one people misread: an external security challenge was not satisfied and the user was redirected to another page or provider, and Microsoft says explicitly that this code alone does not indicate a failure to sign in – the sign-in logs may show the challenge was passed. If you are chasing 50158 as a fault, check whether the same sign-in eventually succeeded.
The user has never completed multifactor registration
You have this one if The sign-in log shows AADSTS50079, and the user has no second factor set up.
- Have the user register a method from a browser at the security information page.
- If registration itself is blocked by a policy, allow it from a trusted location or issue a temporary access pass so they can complete it once.
- Retry the desktop application after registration completes.
- Confirm the sign-in log now shows the requirement satisfied rather than failed.
A conditional access policy is blocking the client
You have this one if The sign-in log names a policy in the failure state and carries AADSTS53003 or AADSTS530003.
- Open the named policy and read its assignments and grant controls carefully.
- Use the What If tool with the real user, application and device state to confirm the match.
- Bring the device or client into compliance with the control, or correct the policy’s scope if it is catching something it was never meant to.
- Re-test with the same user and application, not with an administrator account that may be excluded.
The device does not meet a management or compliance requirement
You have this one if The log carries AADSTS53000, DeviceNotCompliant, or AADSTS50097, device authentication required.
- Open the device record in your management platform and read which compliance rule is failing.
- Resolve the rule itself: disk encryption, an operating system version, an endpoint protection state.
- Force a device check-in from the company portal so the compliance state updates.
- Retry sign-in only once the device reports as compliant.
The device’s own token is missing or broken
You have this one if The single sign-on state in dsregcmd shows no usable token, every application prompts, and other machines in the same office are fine.
- Sign out of Windows and back in, then check the state again.
- Confirm the device reports as joined or registered as expected for your environment.
- If the registration is not healthy, rebuild it, checking BitLocker recovery escrow first.
- Confirm the clock is accurate and the identity endpoints are reachable, since both break token acquisition on their own.
Full reference
Reading the sign-in log
| What the evidence shows | What it means |
|---|---|
| A named policy in the failure state | That policy’s requirement is not being met |
| No usable device token in dsregcmd | Every request becomes interactive |
| Only one application prompts repeatedly | A policy scoped to that application or client type |
| New starters affected, existing users fine | Multifactor registration was never completed |
| AADSTS50158 followed by a success | Not a failure; the challenge was satisfied elsewhere |
The refusal codes, side by side
| Code | Short name | Published meaning |
|---|---|---|
| AADSTS50058 | UserInformationNotProvided | Session information is not sufficient for single sign-on; expected when a user is unauthenticated |
| AADSTS50079 | UserStrongAuthEnrollmentRequired | The user is required to use multifactor authentication and must register security info |
| AADSTS53003 | BlockedByConditionalAccess | Access has been blocked by Conditional Access policies |
| AADSTS50097 | DeviceAuthenticationRequired | Device authentication is required |
| AADSTS50158 | – | External security challenge not satisfied; alone it does not indicate a failure |
| AADSTS530003 | BlockedByConditionalAccess | The same published text as AADSTS53003 |
The device-compliance code is AADSTS53000, DeviceNotCompliant, and the domain-join one is AADSTS53001, DeviceNotDomainJoined. If the sign-in log shows one of those, the fix is on the device and not in the policy.
Working the What If tool properly
- Open conditional access in the Entra admin centre and choose the What If tool.
- Enter the actual user, not a test account, because policy assignments are frequently group-scoped.
- Enter the actual cloud app the client is requesting a token for.
- Set the device state to match reality, including compliance and join type.
- Run it and read both lists: policies that would apply and policies that would not, with the reason.
- Compare that against the sign-in log entry. Where they disagree, the sign-in log wins and your device-state assumption is wrong.
When the prompt returns after every fix
- Check whether the user has more than one account signed into Office. A stale second identity produces prompts that look like policy failures.
- Check whether the same user is fine on a phone. Policy conditions are evaluated per platform and per client type, so a rule requiring a compliant Windows device says nothing about an approved mobile app.
- Check whether the clock on the machine is accurate, because a token that is issued and immediately considered invalid produces an endless loop.
- Check whether a security agent is intercepting the identity endpoints, which breaks silent refresh and forces an interactive request every time.
- Check whether the account is in a group that was recently added to a policy assignment; the timing of the change is usually the fastest confirmation you will get.
When a licence is the actual fix
Conditional access is a licensed capability, so a real licensing question sits underneath this one even though a licence is not the fix for the loop itself. Without Entra ID P1, the policies you would use to scope, exclude and target correctly are not available to you, and the alternative is security defaults: a fixed set of protections you turn on or off as a whole, with no scoping and no exclusions. For a small organisation that is a sensible answer and we will not pretend otherwise. Where you need per-application, per-location or per-device rules, or a break-glass account excluded from everything, P1 is what buys that, and Microsoft 365 Business Premium is the usual way to get it alongside the rest of the productivity licence. Arco can check what your tenant is licensed for today and tell you whether the policy you actually want is even available on it before you start writing one.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
AADSTS50058 |
UserInformationNotProvided: session information is not sufficient for single sign-on, which is expected when the user is unauthenticated | Microsoft Learn |
AADSTS50079 |
UserStrongAuthEnrollmentRequired: the user must use multifactor authentication and needs to register security information | Microsoft Learn |
AADSTS53003 |
BlockedByConditionalAccess: access has been blocked by Conditional Access policies | Microsoft Learn |
AADSTS50097 |
DeviceAuthenticationRequired: device authentication is required | Microsoft Learn |
AADSTS50158 |
External security challenge not satisfied; Microsoft states this code alone does not indicate a failure to sign in | Microsoft Learn |
AADSTS530003 |
BlockedByConditionalAccess: the same published text as AADSTS53003 | Microsoft Learn |
Confirm the fix worked
- The user signs in once and is not prompted again on the next launch.
- The sign-in log shows a success, with the relevant policy reported as satisfied or not applied.
- The single sign-on state on the machine is healthy.
- A reboot leaves sign-in silent.
- A second user covered by the same policy behaves the same way, so you know you fixed the policy and not one account.
Questions people ask about this
Is AADSTS50058 an error?
Not on its own. Microsoft describes it as common and expected when a user is unauthenticated, and it is what an application receives when it asks for a token with prompt=none. Read the code beside it in the sign-in log; that is the one refusing you.
Why does the same user work fine on a phone?
Because policy conditions are evaluated per platform, per application and per client type. A rule requiring a compliant Windows device says nothing about a phone running an approved app.
Can I just switch the policy off?
You can, and you will have removed a control someone put there deliberately. Scoping it properly takes slightly longer and leaves the protection intact. If you must disable one to restore service, put a date on turning it back on.
What is the difference between AADSTS53003 and AADSTS530003?
Nothing you can act on. Microsoft publishes the same text for both: blocked by Conditional Access, the access policy does not allow token issuance. The device compliance code you may be looking for is AADSTS53000.
How do I avoid locking myself out?
Keep at least one cloud-only administrator account excluded from every conditional access policy, protect it strongly, and test policies with the What If tool before enabling them. Every organisation that has locked itself out skipped one of those three.
