Fix it now
Conditional Access asked for a device or a client application it can trust and did not get one. AADSTS53000 is the compliant-device requirement; AADSTS53002 is the approved-application requirement. The password is fine and the device is not broken – the sign-in simply arrived from somewhere the policy does not accept.
dsregcmd /status
- Read the Device State section of the output. AzureAdJoined or WorkplaceJoined tells you how the device is registered, and that is what AADSTS53001 and AADSTS50129 are about.
- In the Microsoft Entra admin center, open the sign-in logs under Entra ID monitoring, find the failure and read the Conditional Access tab to see which policy applied and which grant control it demanded.
- For AADSTS53000, check the device in Intune: it must be enrolled and evaluated as compliant against your policies. A device that has enrolled but not yet reported compliance fails exactly like one that never enrolled.
- For AADSTS53002, have the user open the resource in an approved client application rather than the one they used. Microsoft’s documented answer is to use an app from the approved list.
- For AADSTS50005, check which platform the sign-in came from. That code is documented as a device platform not currently supported through the policy.
- Only then consider changing the policy, and change the assignment rather than the control.
If the device reports compliant and the sign-in succeeds, stop here. If the device will not become compliant, or you have nothing that can evaluate compliance, the next section explains what has to exist for the flag to be written at all.
Why it happens
A compliant-device policy is not a check the device performs on itself. Something has to enrol the device, evaluate it against rules you wrote, and write the result back into Entra ID as an attribute on the device object. Conditional Access then reads that attribute. Microsoft documents AADSTS53000 as the policy requiring a compliant device and the device not being compliant, with the resolution that the user must enrol their device with an approved MDM provider like Intune. If nothing in your tenant writes that flag, the requirement can never be met by anything the user does.
Registration and compliance are separate ideas, and the codes keep them separate. AADSTS53001 is documented as the policy requiring a domain joined device where the device is not domain joined. AADSTS50129 is documented as workplace join being required to register the device. Neither of those is about compliance rules; they are about how the device is known to the directory in the first place. dsregcmd /status answers that question in one screen.
AADSTS53002 and AADSTS50005 move the question off the device entirely. Microsoft documents 53002 as the app used not being an approved app for Conditional Access, with the user needing to use one from the approved list, and 50005 as the user trying to sign in from a device platform not currently supported through Conditional Access policy. A user who is compliant on a supported platform can still be refused for opening the wrong client.
The device is not enrolled in anything that can report compliance
You have this one if AADSTS53000 for every user on a class of device, and the device does not appear in your management console at all.
- Enrol the device with an approved MDM provider – Microsoft names Intune – so that a compliance result exists to read.
- Confirm the device object in Entra ID shows a compliance state after enrolment, not just a registration.
- Retry the sign-in once the state has been written; it is not instantaneous.
The device is enrolled but evaluated as non-compliant
You have this one if The device is in the console, and the compliance report names a rule it is failing – encryption, patch level, a required setting.
- Read the failing rule in the compliance report rather than guessing at the policy.
- Remediate the device, or correct a compliance rule that is stricter than you intended.
- Do not remove the compliance grant from the Conditional Access policy to clear the error; that turns a device problem into a tenant-wide exposure.
The device is registered the wrong way for the policy
You have this one if AADSTS53001 or AADSTS50129, and dsregcmd /status shows a join state that does not match what the policy demands.
- Compare what the policy requires – Entra joined, hybrid joined, or registered – against the Device State section of the output.
- For AADSTS50129, complete workplace join so the device is registered with the directory.
- For hybrid join, confirm the on-premises registration is actually completing rather than assuming it is.
The client application is not on the approved list
You have this one if AADSTS53002 from one application while a browser on the same device works normally.
- Have the user open the resource in an application from the approved list.
- If a business-critical application genuinely cannot be approved, change the target resource or the assignment rather than removing the control.
The platform is not supported by the policy
You have this one if AADSTS50005, affecting one operating system or one kind of device.
- Confirm which platforms the policy’s device platform condition includes.
- Add the platform deliberately, with the same controls, rather than widening the policy to all platforms.
Full reference
Reading the device state output
| Line in dsregcmd /status | What it answers |
|---|---|
| AzureAdJoined | Whether the device is joined to Entra ID |
| DomainJoined | Whether the device is joined to on-premises Active Directory; both true is a hybrid join |
| WorkplaceJoined | Whether a work or school account has registered the device |
| DeviceId and TenantId | Which directory object this device corresponds to, so you can find it in the portal |
| Primary refresh token state | Whether the device holds a usable token; a missing one produces repeated prompts across every app |
What has to be true before the flag exists
- The device is enrolled with a management service that Entra ID trusts to report compliance.
- Compliance policies exist and are assigned to the users or devices in question.
- The device has checked in and been evaluated at least once since those policies were assigned.
- The result has been written back to the device object in the directory.
- The Conditional Access policy reads that attribute as its grant control.
Every one of those steps is a place it can stall, and only the last one produces AADSTS53000. That is why a device can be enrolled, correct and still refused – the compliance evaluation has simply not happened yet, or has happened and failed on a rule nobody has read.
SharePoint and OneDrive from unmanaged devices
SharePoint and OneDrive have their own layer on top of this, and it is worth knowing because the message differs. Blocking or limiting access on unmanaged devices relies on Conditional Access policies, and where access is blocked the documented message is: Access Denied. Due to organization policy, you can’t access this resource from this untrusted device. Where access is limited instead of blocked, the user gets browser-only access with no download, print or sync, and no access through apps including the Office desktop applications.
What not to do
- Do not remove the compliance grant to clear one user’s error. It removes the control for everyone the policy covers.
- Do not exclude a user permanently to work around a device that failed one rule. Exclude by group, with a review date, or fix the device.
- Do not assume a device is compliant because it is managed. Enrolment and compliance are separate states and the sign-in reads the second one.
- Do not switch a hybrid-joined estate to registered-only to make a policy pass. The policy is asking for the stronger state deliberately.
When a licence is the actual fix
Configuration alone cannot fix this one. A compliance requirement needs two things working together: a management service that can enrol the device and evaluate your rules, and Conditional Access to read the result and act on it. Microsoft documents Conditional Access as requiring Microsoft Entra ID P1 for the users in scope, and names Intune as the kind of approved MDM provider that writes the compliance flag; it also states that Microsoft 365 Business Premium customers can use Conditional Access features. If the tenant has no management service at all, nothing ever writes the flag and AADSTS53000 persists whatever you change on the device. Check what your subscription already includes before buying anything – the entitlement is frequently already inside a suite you hold. Arco can work through what you own and supply the missing seats where the gap is genuine.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
AADSTS53000 |
The Conditional Access policy requires a compliant device and the device is not compliant; the user must enrol the device with an approved MDM provider such as Intune | Microsoft Learn |
AADSTS53001 |
The policy requires a domain joined device and the device is not domain joined | Microsoft Learn |
AADSTS53002 |
The application used is not an approved app for Conditional Access; the user needs to use one from the approved list | Microsoft Learn |
AADSTS50005 |
The user tried to sign in from a device platform not currently supported through Conditional Access policy | Microsoft Learn |
AADSTS50129 |
Workplace join is required to register the device | Microsoft Learn |
Confirm the fix worked
dsregcmd /statuson the device shows the join state the policy requires.- The device object in Entra ID shows a compliance state, and it is compliant.
- A fresh sign-in record shows the policy evaluating to success rather than failure.
- The user reaches the resource from the client application they actually need to use, not only from a browser.
Questions people ask about this
Why does the same user work on one laptop and not another?
Because the policy is evaluating the device, not the person. One laptop is enrolled and reporting compliant and the other is not. The sign-in record names which device was used.
Is enrolment the same as compliance?
No, and the distinction is the whole article. Enrolment makes the device manageable. Compliance is the result of evaluating it against your rules, and it is the compliance result that Conditional Access reads.
Can I let one device through without weakening the policy?
Exclude by group membership, with a review date, and put that one device’s user in the group. Do not remove the grant control, which applies to everyone the policy covers.
The user is on a personal phone and refuses to enrol it. What are the options?
Approved-client and app-protection controls exist precisely for that case: the device stays unmanaged and the data stays inside applications you trust. That is a different control from compliance, and it is the one to reach for rather than an exclusion.
Why do SharePoint and OneDrive give a different message?
Because the unmanaged-device restriction there is enforced through Conditional Access but surfaced by SharePoint, with its own documented text about an untrusted device, and it can limit access to browser-only rather than blocking it outright.
