Status check

Is Microsoft Copilot down right now?

This page covers consumer Microsoft Copilot (copilot.microsoft.com) — not GitHub Copilot or work Microsoft 365 Copilot. If Copilot still fails while status looks fine, try another browser or confirm you are signed in. We link Microsoft’s public service health.

Official status

Checking…

Fetching the official status feed…

Open status

Loading official feed…

Lite page — status.cloud.microsoft. Consumer Copilot companion only; not GitHub Copilot or M365 admin health.

Quick checks

Is it just you — or is Copilot down?

Confirm you are talking about consumer Copilot — then rule out local issues.

01
Confirm the product
copilot.microsoft.com (consumer) ≠ GitHub Copilot ≠ Microsoft 365 Copilot for work/school. Wrong product = wrong status board.
02
Open Microsoft service health
Use the official link above for public signals. Tenant-level M365 detail often needs an admin center.
03
Another browser / Microsoft account
Account holds, regional limits, and extension conflicts can look like a global Copilot outage.
04
Edge sidebar vs web
Sidebar Copilot and the full web companion can fail on different paths — try both.

Who this hits

When a Copilot outage hurts most

Consumer Copilot downtime interrupts Pages, drafting threads, and image iterations — not your IDE. Signed-in history is the other fragile surface.

Copilot Pages

Pages turn a chat into a persistent editable workspace. Losing the thread mid-edit means losing the plan/outline trail — copy the visible Page content first.

Writing / planning chats

Cover letters, itineraries, and long outlines built through follow-ups. The decision trail is hard to recreate from memory.

Image creation / editing iterations

Text-to-image plus follow-up edits in the same conversation. Save the prompt stack if generation fails.

While you wait

What to do if you had an unfinished chat

Consumer Copilot outages interrupt Pages, writing drafts, planning threads, and image prompts. Save visible text before you reload.

Copy Pages / unfinished drafts

Grab Page content, itineraries, or rewrites still on screen. A response that disappears mid-stream often never lands in history.

Check signed-in vs Guest / Temporary Chat

If history is missing, confirm you are signed in — Guest or Temporary Chat will not show your usual sidebar history.

Not GitHub Copilot / not M365 work

IDE Copilot and Microsoft 365 Copilot for work/school are different products. This page is about copilot.microsoft.com chats.

Back up Copilot chats you want to find again

Pactify syncs consumer Copilot conversations to Notion and indexes chat history for local search (copilot.microsoft.com only — not GitHub Copilot or work M365). When Copilot is down, you can still find chats you already backed up.

While you wait — a simple backup

Back up Copilot chats — search your history later

This page covers consumer Microsoft Copilot (copilot.microsoft.com) — not GitHub Copilot or work M365. Pactify backs up those Copilot conversations to Notion and indexes chat history for search on this device.

Sync chats to Notion

Sync consumer Copilot chats to Notion when a thread matters — a backup in your workspace, not only in a stuck tab.

Search chat history on this device

Full-text search across Copilot chats indexed on this device. Find past answers when Copilot is down — for chats you already opened or synced with Pactify.

Export when you need a copy

One-shot export to Markdown / Word (and Notion) for any open Copilot chat — handy after a long thread you do not want to lose to copy-paste.

Add to Chrome — Free

Free · Backup to Notion · Chat history search · Export

What is at stake

What usually survives vs what is at risk

Finished companion chats usually return; unfinished drafts are fragile.

Usually still there later

Earlier Copilot companion threads (once service returns)
Microsoft account settings
Files you already downloaded from the chat

Easy to lose right now

Half-written drafts still streaming
Prompt iterations not copied out
Sidebar-only context that never synced to history

Status honesty

What Copilot status covers — and what it doesn’t

Consumer Copilot does not get a ChatGPT-style public JSON board. We stay honest.

Consumer only on this page

We deliberately exclude GitHub Copilot and Microsoft 365 work Copilot from this landing page’s promise.

Public health ≠ tenant admin detail

Workplace outages may only be visible inside M365 admin health for your organization.

Public service health link

Pactify links Microsoft’s public service health page so you can confirm widespread issues.

What you might see

Copilot feels down — what people usually mean

This page is about consumer Copilot on the web. Match what you see to a simple next step.

“Something went wrong” / the reply vanishes

Copy any draft still on screen before you reload — disappearing replies often never save to history.

Conversation history not showing

Check that you are signed in. Guest or Temporary Chat will not show your usual past chats, even when Copilot still answers.

Edge sidebar is blank, but the website works

Try the full site at copilot.microsoft.com. The sidebar and the website do not always fail together.

Work Copilot or GitHub Copilot errors

Those are different products. This page only covers consumer Copilot — work tools and coding Copilot have their own status channels.

FAQ

Copilot down — FAQ

Why does Microsoft Copilot go down sometimes?

Microsoft Copilot runs on shared cloud infrastructure. Traffic spikes, model rollouts, and upstream network issues can cause partial or full outages — often on one surface (web chat, API, or a single model) rather than everything everywhere. Short incidents are common and usually not about your account alone.

How long do Microsoft Copilot outages usually last?

Many incidents resolve in under an hour; larger events can last several hours. Prefer the official status page over social rumor for live updates.

Will I lose my Microsoft Copilot chats if it goes down?

A temporary outage usually does not delete your existing conversation history. What you often lose is the unfinished assistant reply — a generation that never committed cleanly. Copy anything useful on screen before you refresh.

How do I prevent losing important Microsoft Copilot conversations?

During an outage: copy key prompts and answers to a note. For ongoing protection: back up chats you care about. Pactify can sync Microsoft Copilot conversations to Notion and index chat history for full-text search on this device — so when the host is down, you can still find chats you already backed up (it does not keep Microsoft Copilot itself running).

Where is the official Microsoft Copilot status page?

Use the official status source linked at the top of this page (https://status.cloud.microsoft/). Pactify summarizes that source when available.

Is this GitHub Copilot?

No. This page is about consumer Microsoft Copilot at copilot.microsoft.com. GitHub Copilot is a different product with separate status channels.

Is this Microsoft 365 Copilot for work?

No. Work/school Copilot health is usually visible in Microsoft 365 admin service health for tenants. We focus on the consumer companion experience.

Will Copilot delete my chat history during an outage?

Temporary outages usually do not wipe history. Copy unfinished drafts and Pages content — those are the fragile part.

Can Pactify recover Copilot chats I never backed up?

No. Pactify can sync consumer Copilot chats to Notion, export open chats, and search history already indexed on this device. It cannot recover chats never captured, and it cannot replace Copilot while it is down.

Also check

Other AI status pages

Outages are often product-specific. If one host is down, another may still be reachable — or you may want the matching status check.

Back up chats. Search history on this device.

When an AI site is down, you usually cannot keep chatting — but you can still find conversations you already saved. Add Pactify free: sync to Notion, export open chats, and full-text search indexed history on this device.