Excel's COPILOT Function Is Being Retired — Here's What to Actually Do Before September 14

By Imran Khan (AI Tech Safar)

If you built even one Excel formula using `=COPILOT()` over the past year, you have until September 14, 2026 before it silently stops working — and Microsoft's own migration guidance amounts to a single sentence pointing you toward a chat sidebar that doesn't actually replace what a formula does. If a `=COPILOT()` call sits inside a workbook that other cells reference, calculate against, or build reports on, this isn't a minor inconvenience. It's a countdown.

Most of the coverage of this shutdown has focused on the "why" — Microsoft is consolidating its AI entry points. Almost none of it walks through what to actually do about it before the deadline hits. Here's that part.

What's Actually Happening, in Plain Terms

Detail	What It Means
Shutdown Date	September 14, 2026 — after this, `=COPILOT()` calls stop returning results
Who's Affected	Microsoft 365 Insider and Frontier program users who tested the preview function
Why It's Ending	Microsoft says it has "decided not to move forward with this feature" — a permanent cancellation, not a pause
Original Plan	General availability was expected January 2027 — that rollout has been scrapped entirely
Official Replacement	The Copilot side pane — a chat interface, not a formula

Why the "Official Replacement" Doesn't Actually Replace It

This is the detail that Microsoft's own announcement glosses over. `=COPILOT()` was a worksheet formula — it lived inside a cell, could spill results across a range, recalculated automatically whenever the cells it referenced changed, and stayed visible as part of a workbook's underlying logic. The Copilot side pane is a chat window. You ask it something, it responds, and that response doesn't live inside your spreadsheet's formula structure at all.

That's a meaningful downgrade for anyone who used `=COPILOT()` the way a formula is supposed to work: reference a cell range, run automatically, update when inputs change. A chat sidebar can help you draft a summary or classify data once, but it can't sit inside a workbook recalculating every time someone edits row 12. If your entire workflow depended on that automatic recalculation, the side pane genuinely doesn't do what the formula did.

What to Actually Do Before September 14

• Find every workbook using it. Search across your files for `=COPILOT(` — don't rely on memory, especially for workbooks you didn't build yourself but inherited from a colleague.
• Convert live results to static values now. Copy any cell containing a `=COPILOT()` formula, then paste it back as a value only (Paste Special → Values). This locks in the current output before the formula stops returning anything.
• Check what depends on those cells. If other formulas reference a `=COPILOT()` cell, trace those dependencies before the deadline — a single dead formula can blank out an entire chain of cells that reference it.
• Decide on a genuine replacement for ongoing needs. If you need automatic, recalculating AI output inside a formula going forward — not just a one-time chat answer — you'll need a third-party add-in that provides an equivalent function, since Microsoft's own side pane doesn't offer this.
• Don't wait until the last week. Microsoft gave roughly a month's notice from the announcement to shutdown — treat this like any hard deadline with dependencies you don't fully know about yet.

💡 AI Tech Safar Insight
The detail worth sitting with isn't the shutdown itself — preview features get cancelled regularly, and this one never left testing. It's that Microsoft cancelled a feature it had told users to expect in general availability by January 2027, with barely a month's warning, and offered a chat window as the replacement for something that behaved like a formula. That mismatch matters beyond this one feature: it's a reminder that experimental AI functions sitting inside preview or "Insider" programs are genuinely not safe to build real, ongoing workflows around, no matter how useful they seem in testing. If your team is currently piloting any AI feature still labeled "preview" or "experimental" in any Microsoft 365 app, this is a concrete example of what happens when that label turns out to mean exactly what it says.

Frequently Asked Questions (FAQs)

Q1: Will my existing =COPILOT() formulas show an error immediately on September 14, or stop working gradually?
Based on Microsoft's guidance, the function becomes fully unavailable starting that date — existing formula calls will stop returning results rather than phasing out gradually, so treat it as a hard cutoff rather than a gradual decline.

Q2: Is there any way to keep using =COPILOT() past the deadline if I'm on the Insider or Frontier channel?
No. Microsoft has explicitly stated it's abandoning the feature entirely rather than transitioning it to general availability, so there's no channel or setting that will preserve access past September 14, 2026.

Q3: Does this affect regular Excel users who never enabled preview features?
No. This only affects Microsoft 365 Insider and Frontier program users who specifically opted into testing the experimental `=COPILOT()` function — it was never available to standard Microsoft 365 users.

Q4: What's the actual difference between the COPILOT() formula and Google Sheets' equivalent AI() function?
Google's AI() function in Sheets is still in active testing through Workspace Experiments and hasn't been discontinued, making it currently more stable for anyone specifically relying on an in-cell AI formula workflow, though it remains an experimental feature there too.

What Do You Think?
Does this make you more cautious about building real workflows around any "preview" or "Insider" AI feature, or is this just normal course-correction from Microsoft? Share your take in the comments below!

Related Reading:

• How to Use Claude Code: A Complete Beginner's Guide (2026) — Another practical walkthrough for a tool built to stay stable, not vanish after a preview period.

Source: Reporting based on Microsoft 365 Message Center notice MC1454373, with additional context from The Register, Windows Central, and Neowin.