An Azure service that provides an enterprise-grade analytics engine.
Error code AADSTS700003 means the device object was not found in the tenant directory. It is a device registration issue, not evidence by itself that repeated failed logons caused the error.
In this scenario, the repeated authentication attempts could be a symptom of a stale or broken device-bound sign-in state, but the documented meaning of 700003 is that the sign-in flow is referencing a device object that has been deleted or is no longer valid.
Supported recovery depends on the device join type:
- Microsoft Entra registered device
Go to Settings > Accounts > Access Work or School, disconnect the work or school account, then register the device again. - Microsoft Entra joined device
Open an elevated PowerShell window and run:
Then sign in again.dsregcmd /forcerecovery - Microsoft Entra hybrid joined device
Open an elevated PowerShell window and run:
Then restart the device and sign in again with domain credentials.dsregcmd /leave
If this happened during sign-in to a Microsoft Entra joined VM, also verify:
- the device used to connect is Microsoft Entra joined or hybrid joined to the same tenant as the session host
- PKU2U is enabled on both the local PC and the session host
- per-user MFA is disabled for the user account, because it isn’t supported for Microsoft Entra joined VMs
So, to the client’s question: no, 700003 does not mean “the user logged in multiple times.” The documented cause is a missing/deleted device object. Multiple failed authentications may happen around the same time, but they are not the defined meaning of this error.