Copilot Web-wrapper app on macOS causing identity conflict, missing history, and repeated credential errors Case Number: 7107631998
Hello, I’m requesting help escalating an identity-related issue involving Copilot on macOS. This is not a Copilot M365 problem — it appears to be an identity token conflict caused by a second Copilot login pathway on macOS.
What happened
A Copilot app icon appeared in my macOS Applications folder. When opened, it launched the browser-based Copilot web experience, not Copilot M365. This indicates it was a browser-installed web-wrapper (PWA-style), not the native macOS Copilot app.
This web-wrapper authenticated using a different Microsoft account identity than my Copilot M365 subscription. As soon as this happened:
- My Copilot M365 history and library remained intact
- My browser-based Copilot history and library disappeared
- The web-wrapper began generating repeated credential pop-ups
- The browser version showed no history
- Copilot M365 continued working normally
- The corrupted identity token caused persistent “The credential is invalid” errors
Error details
- Correlation Id: 94806c66-895c-40d2-b44c-77a9a4f8d725
- Timestamp: 2026-08-22T13:17:36.000Z
- DPTI: 93079af6e703aab7f30524126c44bbb3f91f800ca9398b331453cdf89da0d25c
- Message: The credential is invalid
- Tag: 965ya
- Code: 0
Root cause
The macOS web-wrapper Copilot app authenticated using a different Microsoft account token than Copilot M365. This created a cross-identity conflict between:
- Copilot M365 (correct identity)
- Copilot Web-wrapper (incorrect identity, corrupted token)
This conflict caused repeated authentication attempts and degraded performance.
Steps I’ve already taken
- Removed the web-wrapper Copilot app from macOS Applications
- Cleared browser identity and cache
- Signed back into Copilot using my Microsoft 365 account
- Verified Copilot M365 history and library are intact
- Issue continues
Request
Please escalate this case to the Identity & Token Integrity engineering team. This issue involves:
- Cross-identity token collision
- Corrupted browser/PWA authentication token
- Incorrect identity routing between Copilot Web and Copilot M365
- Repeated credential invalidation loops
This is not a Copilot M365 issue — it is an identity-layer issue affecting Copilot Web on macOS.
Thank you for your help. — ClarenceHello, I’m requesting help escalating an identity-related issue involving Copilot on macOS. This is not a Copilot M365 problem — it appears to be an identity token conflict caused by a second Copilot login pathway on macOS.
What happened
A Copilot app icon appeared in my macOS Applications folder. When opened, it launched the browser-based Copilot web experience, not Copilot M365. This indicates it was a browser-installed web-wrapper (PWA-style), not the native macOS Copilot app.
This web-wrapper authenticated using a different Microsoft account identity than my Copilot M365 subscription. As soon as this happened:
- My Copilot M365 history and library remained intact
- My browser-based Copilot history and library disappeared
- The web-wrapper began generating repeated credential pop-ups
- The browser version showed no history
- Copilot M365 continued working normally
- The corrupted identity token caused persistent “The credential is invalid” errors
Error details
- Correlation Id:
94806c66-895c-40d2-b44c-77a9a4f8d725 - Timestamp:
2026-08-22T13:17:36.000Z - DPTI:
93079af6e703aab7f30524126c44bbb3f91f800ca9398b331453cdf89da0d25c - Message:
The credential is invalid - Tag:
965ya - Code:
0
Root cause
The macOS web-wrapper Copilot app authenticated using a different Microsoft account token than Copilot M365. This created a cross-identity conflict between:
- Copilot M365 (correct identity)
- Copilot Web-wrapper (incorrect identity, corrupted token)
This conflict caused repeated authentication attempts and degraded performance.
Steps I’ve already taken
- Removed the web-wrapper Copilot app from macOS Applications
- Cleared browser identity and cache
- Signed back into Copilot using my Microsoft 365 account
- Verified Copilot M365 history and library are intact
- Issue continues
Request
Please escalate this case to the Identity & Token Integrity engineering team. This issue involves:
- Cross-identity token collision
- Corrupted browser/PWA authentication token
- Incorrect identity routing between Copilot Web and Copilot M365
- Repeated credential invalidation loops
This is not a Copilot M365 issue — it is an identity-layer issue affecting Copilot Web on macOS.
Thank you for your help. — Clarence