Option C — Suggested Fix slides up from the chat composer
The AI's proposal docks as a persistent banner just above the chat composer — right where the engineer's eyes already are. Apply lives on the banner (warning amber). Resolve stays generic at the bottom of the task lane, so there's no false-resolve risk. The Suggested Fix card is removed from the task lane entirely.
Outlook won't authenticate after tenant migration
ticket #48213 · in progress · 14:22
AI
A few things we know line up with a stale-credential pattern rather than an MFA or network issue. Can you confirm whether the user has other Microsoft 365 services (Teams, SharePoint) working on the same workstation?
14:16
Teams works fine. SharePoint in browser is fine too. It's just Outlook.
14:17
ME
AI
That narrows it to the Outlook profile specifically. Given Credential Manager still has entries pointing at the prior tenant, the cleanest path is to clear those entries and rebuild the local Outlook profile — the client will re-auth against the current tenant from scratch.
14:22
Suggested Fix 94% confidence
Clear cached credentials + rebuild Outlook profile
Remove stale Credential Manager entries referencing the prior tenant, then rebuild the local Outlook profile so the client re-authenticates cleanly against the current tenant.
Matches an existing Script Library template — one-click apply
Ask a follow-up, paste an error, drop a screenshot…
Task lane
What we know · 5 facts
User cannot authenticate to Outlook; repeated 401s from Exchange Online.
promoted 14:02 · from ticket
Credential Manager still references the prior tenant from six months ago.
promoted 14:07 · from chat
MFA prompt appears but fails silently — no authenticator notification.
promoted 14:11 · from chat
Other devices under same account authenticate successfully.
promoted 14:14 · from chat
Teams + SharePoint work on same workstation — isolated to Outlook.
promoted 14:22 · from chat
How it reads. Proposal arrives with a 320ms slide-up from below the composer, docks as a persistent banner until applied, dismissed, or replaced. Apply is amber (not accent-blue) so it visually belongs to the proposal, not the chat send button. Resolve in the task lane stays generic — there's no false-resolve risk because the two actions are spatially and visually separate.
Banner states
What the same region looks like in the other three states — collapsed to save chat space, after the engineer dismisses it, and when a new proposal replaces an existing one.
Collapsed (saves chat space)
…earlier messages…
Clear cached credentials + rebuild Outlook profile 94% ▸ expand
Type a message…
~28px strip. Auto-collapses after 30s of no interaction, or when the engineer clicks the chevron. Title + confidence still visible. Click strip → expands. Apply still reachable via the expanded state.
Dismissed — parked in the task lane
chat unobstructed · banner gone
Type a message…
Dismissed proposals · 1
Clear cached credentials… restore ↺
Recoverable, out of the way. Dismissing the banner parks the proposal as a pill in the task lane. Clicking restore → banner slides back in. Prevents accidental loss.
Replaced — new proposal overrides old
previous: "Rebuild Outlook profile" — didn't resolve, new proposal below
New suggested fix 78%
Reset Autodiscover registry entries for this user
Type a message…
Old proposal cross-fades out, new one slides in. 200ms cross-fade, same slot. A tiny footnote in chat ("previous didn't resolve") preserves the audit trail without re-stacking banners.