This is a note from setting up a loaner Windows 11 Pro PC for a training program. The plan was to join it to Microsoft Entra ID (formerly Azure AD), set it up with an IT work account, and have the trainee use a separate local account.

Following the procedure, I created the local account user01 for the trainee. When the time came to actually use it as the trainee and I typed user01 on the sign-in screen, it would not log in even though the password was correct. I got stuck for a bit here, so I’m sharing the cause and the fix.

The short answer first: instead of user01, type .\user01 in the username field on the sign-in screen, and Windows will recognize it as a local account and let you in.

What Happened

Here is the account setup from provisioning:

The work account setup01@yourtenant.onmicrosoft.com signs in without any trouble. The local account user01, created afterward, fails to log in no matter how I enter the username and password on the sign-in screen. I assumed I had mistyped the password and re-entered it several times, with the same result every time.

The local account was created correctly from Settings → Accounts, and the user exists. Yet it cannot sign in.

Why You Can’t Sign In to the Local Account

The cause is that on an Entra ID-joined PC, the sign-in screen assumes you are signing in with a work account (an Entra ID account).

When you enter just a bare name like user01 in the username field, Windows tries to resolve it against the default sign-in authority it is currently pointed at. On an Entra ID-joined or domain-joined PC, that default authority points to Entra ID (or the domain), not the local machine, so the local user01 is never matched and authentication fails. Even when the username and password are correct, there is a mismatch over which user01 you mean.

This is long-standing, well-documented behavior on Windows, and it boils down to a few points:

• To sign in with a local account, you qualify it with the machine it lives on, as <ComputerName>\username.
• If you don’t know the computer name, prefixing the username with .\ makes Windows recognize it as a local account.
• This works even on a domain-joined or Entra ID-joined PC, letting you sign in to a local account easily.

In other words, signing in to a local account requires you to make which computer’s account explicit.

The Fix: Prefix the Username with ”.\”

The fix is simple. In the username field on the sign-in screen, enter:

.\user01

The leading . (dot) is shorthand for “this local computer.” .\user01 means “the local account user01 on this computer,” so Windows resolves the local user01 directly without consulting Entra ID. Enter the password after that and the local account signs in just fine.

If you know the computer name, you can use it instead of the dot for the same effect:

DESKTOP-AB12CD\user01

But given the hassle of looking up the computer name, .\ is more practical because it works uniformly on any machine. Once signed in, you can confirm the computer name under Settings → System → About.

flowchart TD
    A["Enter username on sign-in screen"] --> B{"Is it prefixed with .\ ?"}
    B -->|"user01 (bare name)"| C["Resolved against the default<br/>authority = Entra ID"]
    C --> D["Local user01 is not matched<br/>and sign-in fails"]
    B -->|".\user01"| E["Resolved against this<br/>local computer's user01"]
    E --> F["Signs in as a<br/>local account"]

A Note When Handing the PC Over

For a loaner PC where the trainee signs in with a local account, it is considerate to tell the trainee up front that they need to type the .\ prefix. Even if a username is shown on the sign-in screen, that path is usually meant for the work account, so someone using a local account has to overwrite the username field with .\user01 themselves.

Once you sign in with the local account, it often appears as a selectable option on the sign-in screen afterward, so you no longer have to think about .\ on subsequent logins. You only need to know it for the very first sign-in.

Summary

The key points:

• The sign-in screen on an Entra ID-joined PC assumes a work account. Enter a bare username and the local account is never matched, so it won’t log in even with the correct password.
• Prefix the username with .\ and enter .\user01, and Windows treats it as “an account on this local computer,” letting the local account sign in.
• The . (dot) is shorthand for “this local computer”; <ComputerName>\user01 does the same thing. .\ is more practical since you don’t have to look up the computer name.
• For loaner PCs where the trainee uses a local account, tell them about the .\ prefix so they don’t get stuck.

When the username and password are correct but sign-in still fails, it’s tempting to suspect a typo. But on an Entra ID-joined PC, the real issue can simply be that you haven’t made which computer’s account explicit. It’s fixed by adding two characters, .\, so it’s worth remembering to avoid getting stuck when provisioning a loaner PC.

That’s all from the Gemba of setting up a loaner Windows PC.

References

• Microsoft Learn: What is a Microsoft Entra joined device?
• Microsoft: Microsoft Entra ID
• Microsoft: Windows 11 Pro