Copilot signing you out every day — or every time you close it — turns a helpful assistant into a login chore. Each sign-out also breaks continuity: history sync pauses, preferences reset, and you waste time re-authenticating before you can even ask a question. It is rarely a Copilot bug in the dramatic sense; it is usually a session, token, or account issue that can be fixed methodically.

The causes cluster around identity. Tokens expire or corrupt, accounts conflict when several are signed in, security changes invalidate sessions, and policies on managed devices force re-authentication. Network tools like VPNs add another layer by making your session appear to come from changing locations. Identifying which of these applies to you is the whole job, and the fixes below work through them in order of likelihood.

Related battery and NPU issues can also disturb background sessions. If your machine drains in sleep, see our guide to NPU battery saver not working , and if Photos AI features are also flaky, check Photos super resolution not working . For a deeper NPU account check, our guide to Intel AI Playground not detecting the NPU covers overlapping driver ground.

Why this happens

  • Expired or corrupted tokens: Sign-in tokens expire or corrupt, forcing Copilot to ask you to sign in again.
  • Account security changes: Password changes, two-factor changes, or security alerts invalidate existing sessions.
  • Multiple accounts conflicting: Switching between personal and work accounts can evict the session of the other.
  • Corrupted app cache: A damaged cache can fail to store the session token, so every launch looks like a first launch.
  • Policy-forced re-authentication: Work or school policies may require frequent re-sign-in for security.
  • VPN or network changes: Sessions tied to a location or network can invalidate when the network changes drastically.
  • App closed improperly or reset: Force-closing Copilot or a settings reset can discard the stored session.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Sign in cleanly once and test persistence

Before deeper fixes, establish a baseline: sign in properly, close Copilot normally, and reopen it. If the session holds after a clean sign-in, the problem may have been a one-off token expiry rather than a recurring fault.

  1. Sign out of Copilot completely.
  2. Close the app.
  3. Reopen it and sign in with the correct Microsoft account.
  4. Choose to stay signed in if prompted.
  5. Close Copilot normally, not by force-quitting.
  6. Reopen it and check whether you are still signed in.

Fix 2: Check for account security events

If sign-outs started after a security change, the session invalidation is expected behaviour, and the fix is to complete the security change cleanly rather than fight it.

  1. Sign into your Microsoft account on the web.
  2. Check recent security activity and alerts.
  3. If you changed your password recently, that explains the sign-outs.
  4. Complete any pending security verifications.
  5. Sign into Copilot fresh after the security state settles.
  6. Monitor for a day to confirm sign-outs stop.

Fix 3: Stick to one account

Account switching is a major session killer. If you alternate between personal and work accounts in Copilot, each switch can evict the other’s session. Picking one primary account for Copilot stabilises the session dramatically.

  1. Decide which account should own your Copilot use.
  2. Sign out of all other accounts in Copilot.
  3. Sign in with the primary account only.
  4. Avoid switching accounts in Copilot for a few days.
  5. Check whether sign-outs stop.
  6. If you must use two accounts, use the web version for the second one.

Fix 4: Repair the app cache

A corrupted cache that cannot store tokens produces the classic symptom: signed in now, signed out on next launch. Repairing the app clears the bad cache while preserving your settings.

  1. Open Settings, go to Apps, then Installed apps.
  2. Find Copilot and open Advanced options.
  3. Choose Repair.
  4. Relaunch Copilot and sign in.
  5. Close and reopen Copilot to test persistence.
  6. If Repair fails, choose Reset and repeat the sign-in test.

Fix 5: Check VPN and network stability

VPNs that rotate locations, or networks that change frequently, can make Microsoft’s session checks fail and force re-authentication. Testing without the VPN isolates this cause quickly.

  1. Disconnect your VPN temporarily.
  2. Sign into Copilot and test persistence over a day.
  3. If sign-outs stop, the VPN is the cause.
  4. Configure the VPN to use a stable location, or add Microsoft services to its bypass list if supported.
  5. Reconnect the VPN and retest.
  6. If sign-outs return only on certain networks, note which ones to avoid for Copilot.

Fix 6: Check for policy-forced re-authentication

Managed devices may require sign-in every day by policy, and no app fix overrides that. Greyed-out settings and consistent daily sign-outs on a work device point here.

  1. Check whether your PC is work- or school-managed.
  2. Look for sign-in or session policies in your organisation’s documentation.
  3. Ask IT whether frequent Copilot re-authentication is policy-driven.
  4. If it is, accept it as intended security behaviour.
  5. On a personal PC, check for third-party security tools that clear sessions.
  6. Disable session-clearing features in such tools and retest.

Fix 7: Update Copilot and Windows

Session handling bugs are fixed in app and OS updates. If sign-outs began with a particular version, updating past it is often the complete fix.

  1. Open the Microsoft Store and update Copilot.
  2. Open Settings, go to Windows Update, and install pending updates.
  3. Restart after updating.
  4. Sign into Copilot fresh.
  5. Test persistence across several days.
  6. For ongoing account issues, see the official Windows support pages .

Closing

Copilot repeatedly signing you out is a session problem, not a Copilot rejection of your account. Clean sign-in, one account, a repaired cache, and a stable network fix the overwhelming majority of cases. If sign-outs persist only on a managed device, policy is the likely answer — and knowing that saves you from resetting an app that was never broken.

Frequently asked questions

Why does Copilot keep signing me out?
The usual causes are expired or corrupted sign-in tokens, account security changes, multiple accounts conflicting, a corrupted app cache, or a policy that forces re-authentication. Network changes and VPNs can also invalidate sessions unexpectedly.
Is repeated sign-out a security problem?
Usually not — it is most often a token or cache issue, not a breach. However, if sign-outs coincide with password change alerts or unfamiliar devices on your account, check your Microsoft account security page promptly.
Does signing out delete my Copilot history?
No. Signing out does not delete cloud history tied to your account. History reappears when you sign back in with the same account, once sync completes.
Can I stay signed in permanently?
Copilot is designed to stay signed in on a personal device. If it signs out daily despite healthy settings, something is invalidating the session, and the fixes in this guide address those causes.