FIX Jun 16, 2026 12 min read

Microsoft Copilot Login Not Working — Fix Sign-In Failures Fast

TL;DR Clear browser cookies for copilot.microsoft.com and login.microsoftonline.com — stale auth tokens cause most login loops. Try an InPrivate/Incognito window first to isolate extension and cache issues from account problems.…

by Bugi 12 min

TL;DR

Clear browser cookies for copilot.microsoft.com and login.microsoftonline.com — stale auth tokens cause most login loops.
Try an InPrivate/Incognito window first to isolate extension and cache issues from account problems.
Enterprise (Entra ID) users: check with your IT admin — Conditional Access policies and license assignment silently block Copilot access.

Quick fixes to try first

Open Copilot in a private/incognito window to rule out a bad browser session.
Disable extensions, VPN, or strict privacy tools temporarily, then retry the same action.
Check the official status page or app notice before assuming your account is broken.
Try the web app and mobile/desktop app separately to isolate the failing surface.

Overview

Microsoft Copilot login failures hit personal Microsoft accounts, enterprise Entra ID (formerly Azure AD) accounts, and GitHub-linked developer accounts differently. The symptom looks the same — you click “Sign in” and nothing happens, or you land in a redirect loop — but the root cause varies by account type and platform.

This guide separates browser-side fixes from account-level problems so you stop guessing. Work through the quick fixes first. If those fail, the numbered steps below isolate whether the issue is your browser, your account configuration, or a service-side problem.

Quick fixes

Open copilot.microsoft.com in an InPrivate or Incognito window. If login works there, the problem is cached data or a browser extension.
Clear cookies specifically for login.microsoftonline.com and copilot.microsoft.com. A full cache clear is unnecessary.
Try a different browser entirely — Edge and Chrome handle Microsoft auth differently.
Check Microsoft’s service health dashboard for active incidents affecting Copilot or Entra ID.
If you use a work or school account, confirm your organization’s Microsoft 365 plan includes Copilot access.

Symptoms

Browser (copilot.microsoft.com): The sign-in button redirects to login.microsoftonline.com, then bounces back to the Copilot page without authenticating. Some users see a blank white page after entering credentials. Others get stuck in an infinite redirect loop where the URL keeps cycling between Microsoft login and Copilot.

Microsoft Edge sidebar: Copilot loads but shows “Sign in to get started” even though you’re already signed into Edge with a Microsoft account. Clicking sign-in does nothing or briefly flashes a login prompt that disappears.

Mobile app (iOS/Android): The app opens to a login screen, accepts credentials, then returns to the same login screen. On some devices, the app crashes immediately after authentication.

Enterprise/work accounts: Users see “You don’t have access to this” or “Ask your admin for access” after successful authentication. The login itself succeeds, but Copilot features are unavailable.

Why This Happens

Microsoft Copilot authentication flows through multiple services — Entra ID (identity), Microsoft Account (consumer), and the Copilot service itself. A failure at any point in this chain produces the same visible result: login doesn’t work.

Stale authentication tokens. Microsoft’s OAuth tokens are cached aggressively by browsers. When a token expires but the cached version persists, the browser sends an invalid token, gets rejected, and retries with the same cached token — creating a loop.

Browser extension interference. Ad blockers, privacy extensions, and VPN browser extensions frequently block requests to login.microsoftonline.com or strip authentication headers. uBlock Origin and Privacy Badger are common culprits because they block third-party cookies that Microsoft’s auth flow requires.

Multiple Microsoft accounts. If you’re signed into both a personal Microsoft account and a work/school account in the same browser profile, the auth system may pick the wrong account silently. This is especially common in Edge, which ties its browser-level sign-in to Copilot access.

Conditional Access policies (enterprise). Organizations using Entra ID often configure Conditional Access rules that restrict Copilot to managed devices, specific IP ranges, or users with particular licenses. These policies block access after authentication succeeds, producing confusing “no access” messages.

DNS or network filtering. Corporate networks and DNS-level ad blockers (Pi-hole, NextDNS) may block Microsoft telemetry domains that the auth flow depends on, even if they allow login.microsoftonline.com itself.

## Verify Account Status and Service Availability

Before troubleshooting your browser, confirm the basics.

**Check service status.** Visit Microsoft’s cloud service health page. Look for incidents affecting “Microsoft Copilot” or “Microsoft Entra.” If there’s a known outage, no local fix will help — wait for resolution.

**Confirm your account works elsewhere.** Sign in to office.com or `outlook.com` with the same credentials. If that fails too, the problem is your Microsoft account, not Copilot specifically. Reset your password at `account.live.com` (personal) or contact your IT admin (work/school).

**Check your subscription.** Not all Microsoft 365 plans include Copilot access. Enterprise users need a Copilot license explicitly assigned by an admin. Personal users should verify their account at `account.microsoft.com` under “Subscriptions.”

Note

If you can sign into other Microsoft services but not Copilot, the issue is almost certainly browser-side (Step 02) or permission-side (Step 03), not account-side.

## Fix Browser and App Session Issues

Most Copilot login failures are browser problems. Work through these in order.

### InPrivate/Incognito test

Open an InPrivate (Edge) or Incognito (Chrome) window and navigate to `copilot.microsoft.com`. Try signing in. If this works, your regular browser session has corrupted cache, conflicting cookies, or an interfering extension. Proceed to the cookie clear below.

### Clear targeted cookies

Don’t clear all cookies — that signs you out of everything. Target only Microsoft auth cookies:

**Chrome:**

chrome://settings/cookies/detail?site=login.microsoftonline.com

Delete all entries. Repeat for `copilot.microsoft.com`.

**Edge:**

edge://settings/cookies/detail?site=login.microsoftonline.com

Same process. Also check `edge://settings/cookies/detail?site=copilot.microsoft.com`.

**Firefox:** Open Settings → Privacy & Security → Cookies and Site Data → Manage Data. Search for `microsoftonline` and `copilot.microsoft`, remove those entries.

**Safari:** Preferences → Privacy → Manage Website Data. Search and remove entries for `microsoftonline.com` and `microsoft.com`.

### Disable extensions temporarily

Disable all browser extensions, then try logging in again. If login succeeds, re-enable extensions one at a time to find the culprit. Common offenders:

– **uBlock Origin** — blocks third-party cookie domains Microsoft auth needs
– **Privacy Badger** — flags `login.microsoftonline.com` as a tracker
– **VPN extensions** — route auth requests through servers Microsoft blocks
– **Grammarly** — injects scripts that occasionally break OAuth popups

Tip

If uBlock Origin is the problem, add @@||login.microsoftonline.com^ to your custom filter list instead of disabling the entire extension.

### Multiple account conflicts (Edge-specific)

Edge ties its browser sign-in to Copilot. If you’re signed into Edge with account A but trying to use Copilot with account B:

1. Open `edge://settings/profiles`
2. Sign out of your current Edge profile
3. Sign back in with the account you want for Copilot
4. Or create a separate Edge profile for the other account

## Resolve Permission and License Problems

This step applies primarily to work/school (Entra ID) accounts. If you use a personal Microsoft account and Step 02 didn’t fix the issue, skip to Step 04.

### Check Copilot license assignment

Your organization’s IT admin assigns Copilot licenses through the Microsoft 365 admin center. You can check your own license status:

1. Go to `myaccount.microsoft.com`
2. Click “Subscriptions”
3. Look for “Microsoft Copilot” or “Microsoft 365 Copilot” in your assigned licenses

If Copilot isn’t listed, you need your admin to assign the license. No amount of browser troubleshooting will fix a missing license.

### Conditional Access blocks

Organizations often restrict Copilot to:

– **Managed devices only** — your personal laptop may be blocked even with valid credentials
– **Specific network ranges** — working from home or a VPN may trigger a block
– **Compliant devices** — devices must meet Intune compliance policies (disk encryption, OS version, etc.)

You’ll typically see “You don’t have access” or “Your sign-in was successful but your admin requires your device to be managed” messages. Contact your IT admin — these policies can only be changed at the organizational level.

### Tenant-level Copilot availability

Some organizations disable Copilot at the tenant level through Microsoft 365 admin settings. If your admin hasn’t enabled Copilot for your tenant, individual users can’t access it regardless of license status.

Warning

Don’t try to bypass Conditional Access by using a personal account on a work device. Your organization may have policies that flag this, and it won’t give you access to work-context Copilot features anyway.

## Run Platform-Specific Checks

### Windows desktop

If Copilot is integrated into Windows but won’t sign in:

1. Open Settings → Accounts → Your info. Verify you’re signed into Windows with the correct Microsoft account.
2. Open PowerShell and run `dsregcmd /status`. Under “User State,” confirm `AzureAdJoined` shows `YES` if you need enterprise Copilot.
3. Try `wsreset.exe` to clear Microsoft Store cache — this affects Copilot components that rely on Store authentication.

### macOS

Microsoft Copilot on macOS uses the system keychain for credential storage:

1. Open Keychain Access → search for “microsoft”
2. Delete entries related to `login.microsoftonline.com` or `copilot`
3. Restart the Copilot app and sign in again

### iOS

1. Settings → Apps → Copilot (or Microsoft Copilot) → Clear cache if available
2. Delete and reinstall the app — iOS doesn’t always clear auth tokens on cache clear
3. Settings → Safari → Clear History and Website Data if you’re using Copilot in Safari

### Android

1. Settings → Apps → Microsoft Copilot → Storage → Clear Cache, then Clear Data
2. If using Microsoft Authenticator, open it and verify your account is listed and synced
3. Check that your device’s date and time are set to automatic — OAuth token validation fails with clock skew

### Network-level blocks

If you’re on a corporate or school network:

nslookup copilot.microsoft.com
nslookup login.microsoftonline.com

Both should resolve to Microsoft IP addresses. If either fails or returns a local/block IP, your network is filtering these domains. Switch to a mobile hotspot to confirm, then contact your network administrator.

If It Still Fails

If none of the above steps resolved the issue:

Capture the exact error. Open browser DevTools (F12) → Network tab → reproduce the login failure. Look for HTTP 403 or 401 responses in the network log. Screenshot the error page including the URL bar.
Try a completely different device and network. Use your phone on cellular data (not WiFi). This eliminates browser, device, and network variables simultaneously. If it works there, the problem is definitively on your original device or network.
Check Microsoft’s community forums. Search Microsoft Answers for your specific error message. Login issues often affect many users simultaneously, and workarounds appear in community threads before official fixes.
Contact support. Personal accounts: use support.microsoft.com. Work/school accounts: contact your IT admin first — they have access to Entra ID sign-in logs that show exactly why authentication failed.

Danger

Do not follow advice to edit Windows registry entries or modify Group Policy settings from unverified sources. Incorrect changes to these can break system-wide authentication beyond just Copilot.

Takeaway

Most Copilot login failures are stale cookies or extension interference — an InPrivate window test isolates this in seconds. Enterprise users should check license assignment before any browser troubleshooting.

Isolate the failing surface

Repeat the same microsoft copilot login not working check in another browser, private window, or app so you know whether the issue is local or account-wide.

Remove local blockers

Temporarily disable extensions, VPN, custom DNS, or network filters, then refresh the session and try again.

Escalate only after the basics fail

If the issue follows your account across devices, collect the exact error text and contact the vendor support channel with that evidence.

FAQ

Why does Microsoft Copilot keep asking me to sign in?

Repeated sign-in prompts usually mean your browser is not storing the authentication cookie. Check that third-party cookies are allowed for login.microsoftonline.com, disable ad blockers temporarily, and clear existing cookies for Microsoft domains. In Edge specifically, confirm your browser profile sign-in matches the account you want for Copilot.

Does Microsoft Copilot require a paid subscription to sign in?

Microsoft Copilot offers a free tier with basic access using any personal Microsoft account. However, enterprise Copilot features within Microsoft 365 apps require a paid Copilot license assigned by your organization’s admin. If you can sign in but see limited features, you may be on the free tier.

Why does Copilot login work in Incognito but not in my regular browser?

This confirms the issue is cached data or a browser extension in your regular session. Clear cookies for login.microsoftonline.com and copilot.microsoft.com, then disable extensions one at a time to find the culprit. Privacy-focused extensions and ad blockers are the most common offenders.

Can a VPN cause Copilot login failures?

Yes. VPNs can trigger Microsoft’s location-based security checks, especially for enterprise accounts with Conditional Access policies that restrict sign-in to specific regions or IP ranges. Try disconnecting the VPN and signing in on your regular network. If that works, you may need to add the VPN’s IP range to your organization’s allowed locations.

Why do I see ‘You don’t have access’ after successfully entering my credentials?

This typically means authentication succeeded but authorization failed. For enterprise accounts, your admin may not have assigned a Copilot license, your device may not meet compliance requirements, or Copilot may be disabled at the tenant level. Check with your IT admin — they can see the exact denial reason in Entra ID sign-in logs.

How do I fix Copilot login on my phone?

On iOS, delete and reinstall the Copilot app — clearing cache alone may not remove stored auth tokens. On Android, go to Settings, Apps, Microsoft Copilot, Storage, then tap both Clear Cache and Clear Data. Also verify your device clock is set to automatic, as OAuth authentication fails with incorrect time settings.

Is there a way to check if Microsoft Copilot is down?

Check the Microsoft service health dashboard at status.cloud.microsoft.com for reported incidents. You can also check downdetector.com for user-reported outages as a secondary signal. If the service status shows healthy but login still fails, the issue is likely specific to your account, browser, or network.