Microsoft Copilot Won't Sign In? Fix the Account-Type Mismatch That Causes Most Errors

Microsoft has built four distinct products and called them all "Copilot," each one paired with a different identity model — and the error messages when you sign in with the wrong one are nearly identical. This is the single biggest source of "Copilot won't let me in" tickets in 2026. Untangling which Copilot you're actually trying to use is the entire fix in most cases.

The four Copilots, and which account each one wants

If you only remember one thing from this guide, remember this table:

• Copilot (free, consumer) at copilot.microsoft.com — wants a personal Microsoft Account (the same one you use for Xbox or Outlook.com).
• Copilot Pro at the same URL after purchase — same identity, just with a paid subscription tied to it.
• Microsoft 365 Copilot (inside Word, Excel, Outlook, Teams) — wants your work or school account, with a Copilot license assigned by your employer.
• Copilot for Microsoft 365 web at m365.cloud.microsoft (formerly office.com) — same work/school account.

Same email address can be tied to both a personal MSA and a work account. When the sign-in page says "we need more info," it usually means it's not sure which one you meant to use. The fastest way to clarify: read the URL bar. If it says login.live.com, it expects a personal account. If it says login.microsoftonline.com, it expects a work account. For background on the two account types, see the deeper explanation here.

Fix 1: Make sure you've actually been assigned a license

The most common "Copilot won't sign in" reality is: there's nothing to sign in to. The user assumes a Copilot license was added when their company "got Copilot." It wasn't. Licenses are assigned per-user, by an admin.

To check, sign in to portal.office.com with your work account, then click your initials top-right → My account → Subscriptions. You should see "Microsoft 365 Copilot" (or "Copilot Pro" for the consumer flavor) listed as an active product. If it's not listed, you haven't been assigned one. Ask IT directly: "Have I been assigned a Microsoft 365 Copilot license? It's a separate add-on, not included in M365 E3 or E5 by default."

Fix 2: Sign out completely, then sign in once

If the license is there but Copilot won't open, an old token from a previous account is usually the cause. Multi-account browsers like Edge are particularly prone to this. The clean restart:

1. Close every Office app, including Teams.
2. In Edge or Chrome, open Settings → Privacy → Clear browsing data → Cookies and other site data, last hour. Don't clear cached images — just cookies.
3. Open microsoft365.com. Sign in with your work account.
4. Once Office shows up, open Word from the desktop. File → Account → check that the right identity is listed.
5. Now try Copilot from the ribbon.

Nine times out of ten, the icon appears within seconds.

Fix 3: Check the Office update channel

Copilot in desktop Office requires a recent build — older Current Channel installs sometimes lack the integration entirely. Verify in any Office app: File → Account → About. The version number should be 2402 or higher in Current Channel, and the build month should be within the last 90 days. If you're on Semi-Annual Enterprise Channel and the build is older than that, ask IT to update — the Copilot features won't show up until the channel catches up.

If the update is pending but stuck, run the Office update manually: File → Account → Update Options → Update Now.

Fix 4: Conditional Access is blocking the Copilot endpoints

Companies with strict Conditional Access policies sometimes accidentally block Copilot's backend endpoints — particularly when policies require a compliant device, an MDM-enrolled phone, or a specific country. The symptom is a sign-in that succeeds in Word, fails in Copilot, with an "AADSTS50158" or "AADSTS530002" error.

The right move:

1. Take a screenshot of the error including the AADSTS code.
2. Send to your IT helpdesk with: "Copilot sign-in blocked by Conditional Access. Word and Outlook work fine on this device. Error code attached."
3. The admin needs to add the Copilot application IDs as exclusions or confirm device compliance. They'll know what to do.

This isn't something you can work around with a different browser. The block is at the identity layer.

Fix 5: Run dsregcmd to check device trust

For work-managed Windows devices, Copilot needs the device to be in a healthy trusted state with Entra ID (formerly Azure AD). When that trust breaks, all M365 services start prompting — Outlook included — but Copilot is the first to refuse.

Open Command Prompt or PowerShell and run:

dsregcmd /status

Look for these lines in the output:

• AzureAdJoined : YES (or DomainJoined on hybrid)
• AzureAdPrt : YES — this is the primary refresh token. If NO, the device's trust is broken.
• AzureAdPrtUpdateTime within the last 14 days.

If AzureAdPrt is NO, sign out of Windows, sign back in, and rerun the check. If it's still NO, you have a deeper trust issue — see the device trust article for the full repair.

Fix 6: Clear the Web Account Manager cache

Windows holds Office sign-in tokens in a cache called Web Account Manager (WAM). When WAM gets confused — usually after a password change or a tenant move — Copilot starts failing while other Office apps still appear to work.

Clear it without losing anything else:

1. Close all Office apps.
2. Open Settings → Accounts → Email & accounts.
3. For each work or school account listed, click → Manage → sign out / remove.
4. Restart Windows.
5. Open Word, sign in fresh. Other Office apps and Copilot pick up the new token automatically.

This is safe — you're not deleting any data, just the cached credentials.

Fix 7: The "still nothing" rebuild

If everything above checks out and Copilot still refuses to load:

1. Open Apps → Installed apps.
2. Find Microsoft 365 Apps for Enterprise (or for business). Click → Modify.
3. Choose Online Repair (not Quick Repair). It takes 15–30 minutes.
4. Restart Windows when prompted.
5. Sign back into Word. Try Copilot.

Online Repair replaces every Office file from Microsoft's servers. It's the surgical fix when token clears and license checks haven't worked.

Quick-reference: which Copilot, which error

• "This account doesn't have access to Copilot" → Fix 1 (license missing) or Fix 5 (device trust).
• Sign-in spins forever, no error → Fix 2 (WAM/cookies).
• Copilot button missing from Word ribbon → Fix 3 (Office channel/build).
• AADSTS error code → Fix 4 (Conditional Access — IT, not you).
• "We need more info" on personal Copilot → wrong account type — sign in at copilot.microsoft.com with a personal MSA, not work.

The dirty secret of Copilot sign-in problems: nine out of ten are not technical. They're identity confusion — between the four Copilot products, between personal and work accounts, between licensed and unlicensed users. Spend the first five minutes verifying which Copilot you're trying to use and which license you actually have, and most of the rest takes care of itself.