Fix it now
These are two different refusals. AADSTS530035 is documented as security defaults blocking the request, because it used legacy authentication or was judged unsafe. AADSTS53004 is the registration block: the user has to complete multifactor registration before reaching the content, and that registration is what is being refused.
- Work out which one you have. If the tenant has no Conditional Access policies and security defaults are on, AADSTS530035 is almost certainly them.
- Check the client and protocol on the failed sign-in record. Security defaults block legacy authentication protocols outright, and that is the most common cause of AADSTS530035 – the answer is to move the client onto modern authentication, not to switch the protections off.
- Read the current setting at Entra ID, Overview, Properties, Manage security defaults so you know what is actually enabled before changing anything.
- For AADSTS53004, do not try to register the user’s way past it. Deal with the risk on the account first: verify the person out of band, reset the password through your normal process, and confirm the account is clean.
- For AADSTS53010, the block is on where registration may happen. Have the user register from a location or device the organisation permits.
- For AADSTS50125, the interrupt is a password reset or password registration entry, so complete that flow rather than treating it as a failure.
Turning security defaults off to clear AADSTS530035 removes multifactor authentication from every account in the tenant, including administrators. Do not do it without a Conditional Access policy ready to replace them.
If the sign-in completes, or the user finishes registration cleanly, stop here. If you cannot see why the account is flagged, the next section explains what you can and cannot see without Identity Protection.
Why it happens
Security defaults are a single tenant-wide set of protections with no scoping and no exclusions. Microsoft documents what they enforce: every user must register for multifactor authentication, administrators in the listed roles must complete it, users must complete it when Microsoft’s own evaluation decides it is necessary, legacy authentication protocols are blocked, privileged activity in the Azure portal, the Microsoft Entra admin center, Azure PowerShell and Azure CLI is protected, and from 1 July 2026 device code flow is blocked for new tenants. AADSTS530035 is documented as access being blocked by security defaults, because the request used legacy authentication or was deemed unsafe by those policies.
That is a different thing from the registration blocks, and conflating them is what sends people down the wrong path. AADSTS53004 carries the internal name ProofUpBlockedDueToRisk, and Microsoft’s published description says the user needs to complete the multifactor registration process before accessing the content. The awkward part is that the registration itself is what is being refused, so telling the user to register harder achieves nothing.
The two neighbouring codes are narrower again. AADSTS53010 is documented as multifactor authentication methods not being configurable because the organisation requires this information to be set from specific locations or devices – a deliberate control on where security info may be registered. AADSTS50125 is documented as the sign-in being interrupted because of a password reset or password registration entry, which is a normal interrupt rather than a block at all.
A legacy authentication client is being refused
You have this one if AADSTS530035 for an older mail client, a multifunction device or a line-of-business integration, while browsers work.
- Read the client application and protocol on the failed sign-in record to confirm what was used.
- Move the client onto modern authentication. Security defaults block legacy protocols by design and there is no exclusion to grant.
- Where a device genuinely cannot, that is the case for moving to Conditional Access, where a narrow scoped exception is possible.
Do not disable security defaults to make one scanner work. The blocked protocol is the one attackers use for password spray.
Security defaults are on and you did not know
You have this one if Sign-ins are refused or challenged in ways that match no policy you wrote, and the Conditional Access area is empty or unavailable.
- Read Entra ID, Overview, Properties, Manage security defaults.
- Remember they are enabled automatically on tenants created on or after 22 October 2019, with a 24-hour grace period, and can be turned on for existing tenants that have no Conditional Access policies, no premium licences and no active legacy clients.
- Decide deliberately between keeping them and replacing them with Conditional Access – you cannot run both.
The account is flagged as risky and cannot register
You have this one if AADSTS53004, on one account, with everything else in the tenant working normally.
- Verify the person’s identity out of band, through a channel that does not depend on the account.
- Reset the password through your normal process and confirm nothing else on the account has changed – forwarding rules, registered methods, application consents.
- Have them register a method once the account is clean.
Without Identity Protection you can act on the account but you cannot see which detection flagged it, which means you are treating a symptom you cannot read.
Registration is restricted to particular locations or devices
You have this one if AADSTS53010, and the user is remote or on an unmanaged device.
- Have the user register from a location or device the organisation permits.
- If the restriction is unintended, review the registration control rather than removing the requirement.
- For a genuinely remote new starter, a Temporary Access Pass issued by an administrator is the usual route in.
The interrupt is a password reset, not a block
You have this one if AADSTS50125, and the user is bounced into a password or registration flow rather than refused.
- Let the user complete the flow; it is working as documented.
- If it repeats every sign-in, check whether registration is completing and being recorded.
Full reference
Telling the four codes apart
| Code | Documented meaning | First move |
|---|---|---|
| AADSTS530035 | Blocked by security defaults – legacy auth, or deemed unsafe | Read the protocol on the sign-in record |
| AADSTS53004 | The user must complete multifactor registration before accessing the content | Deal with the account, not the registration |
| AADSTS53010 | Methods cannot be configured because the organisation requires this to be set from specific locations or devices | Move the registration, not the policy |
| AADSTS50125 | Sign-in interrupted by a password reset or password registration entry | Complete the flow |
Security defaults or Conditional Access, not both
Microsoft states that organisations implementing Conditional Access policies to replace security defaults must disable security defaults, and recommends enabling equivalent Microsoft-managed policies immediately when they do. That is the decision behind most AADSTS530035 tickets: you either accept a single tenant-wide switch with no exceptions, or you move to policies you can scope, which is a licensed capability. There is no configuration that gives you exceptions inside security defaults.
What is excluded from security defaults
- The directory synchronisation account used by Entra Connect and cloud sync, which holds the Directory Synchronization Accounts role, is documented as excluded.
- Nothing else is. There is no user exclusion, no group exclusion, no per-application targeting and no trusted location.
- The 14-day grace period for registering multifactor authentication was removed on 29 July 2024 for new and existing tenants.
- Administrators are in scope exactly as users are, which is worth confirming before you change anything.
Working a risk block without Identity Protection
- Verify the user out of band. Never through a channel that the compromised account could control.
- Reset the password through your normal process rather than letting the user self-serve while the account is flagged.
- Audit the account for the things an attacker leaves behind: mailbox forwarding rules, new registered methods, consented applications, delegate permissions.
- Have the user register a fresh method from a device you trust.
- Watch the account afterwards, because you have no detection detail to tell you whether the underlying cause was addressed.
That sequence is the honest answer for a tenant without Identity Protection: it is sound incident hygiene, and it works, but you are acting on a flag you cannot read. Whether that matters depends on how often it happens and on what the accounts can reach.
When a licence is the actual fix
Identity Protection is what turns a risk block from a mystery into something you can act on, and Microsoft documents risk-based Conditional Access as requiring Microsoft Entra ID P2, which includes Identity Protection. With it you can see which detection flagged the account, review the evidence, dismiss the risk or confirm the account as compromised, and write policies that remediate automatically. Without it the account is blocked, you cannot see why, and your only reliable remediation is the manual sequence above. P2 can be assigned to the subset of users who need it, though risk policies apply only to users who hold the licence, which is the detail that catches people out when they licence half the finance team. Check what your tenant already holds first. Arco can confirm that and supply P2 seats where the gap actually matters.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
AADSTS530035 |
Access has been blocked by security defaults, because the request used legacy authentication or was deemed unsafe by security defaults policies | Microsoft Learn |
AADSTS53004 |
The user needs to complete the multifactor authentication registration process before accessing this content | Microsoft Learn |
AADSTS53010 |
Multifactor authentication methods cannot be configured because the organisation requires this information to be set from specific locations or devices | Microsoft Learn |
AADSTS50125 |
The sign-in was interrupted because of a password reset or password registration entry | Microsoft Learn |
Confirm the fix worked
- The user completes a full sign-in and the record shows the second factor satisfied.
- The client that was failing with AADSTS530035 is now using modern authentication, confirmed on the sign-in record rather than assumed.
- For a risk block, the password has been reset, the account has been audited for forwarding rules and consented applications, and a fresh method is registered.
- The setting at Entra ID, Overview, Properties, Manage security defaults is what you intend it to be, and you know which mechanism the tenant is running.
Questions people ask about this
Can I exclude one account from security defaults?
No. The only documented exclusion is the directory synchronisation account used by Entra Connect and cloud sync. Everything else in the tenant is in scope, with no user or group exclusions available.
Should I just turn security defaults off?
Only with a replacement ready. Microsoft’s own guidance is that organisations replacing security defaults with Conditional Access must disable them and should enable equivalent policies immediately. Turning them off on their own removes multifactor authentication from every account you have.
Why can the user not register their way out of AADSTS53004?
Because the registration is what is being refused. The account has to be dealt with first, and only then does registration succeed.
Does a password reset clear the risk?
It is the usual remediation, but without Identity Protection you cannot see which detection fired, so you cannot confirm you addressed the cause rather than the symptom. Audit the account as well as resetting it.
Is AADSTS50125 a security problem?
No. It is documented as a sign-in interrupted by a password reset or password registration entry. Let the flow complete.
