The AI Formula in Your Spreadsheets Is Being Removed

Microsoft is retiring the COPILOT worksheet function in Excel on September 14, pointing people toward the Copilot side pane instead. If that means nothing to you, you can stop reading and lose nothing. If your finance lead put it inside a live workbook eight months ago because it saved an hour every month, you have about four weeks, and the interesting part is not the deadline. It is that almost nobody can say offhand which files it is sitting in.

Embedded is different from installed

Most AI is something you open. If a chat tool vanished tomorrow, you would grumble and open a different one, and nothing you had already produced would change. A worksheet function is a different animal, because it lives inside documents rather than beside them. It gets saved, emailed, copied into next quarter's version, and inherited by someone who has no idea it is in there. The dependency spreads by ordinary office behaviour, and it spreads silently, which is why the honest first question is not how do we replace this but where actually is it.

What actually breaks

A withdrawn function does not fall back to a manual version. It stops producing values, and everything downstream moves with it.

Where it hurts	Why it is easy to miss
Subtotals and roll-ups	A total still appears, just a different one
Charts and dashboards	They redraw without complaining
Copied template files	Nobody remembers how many copies exist
Reports sent to others	The recipient sees the error before you do

The first row is the dangerous one. A cell that stops returning a number does not always announce itself as a failure; it can simply drop out of a sum, leaving a total that is perfectly formatted and quietly wrong. That is a worse outcome than a visible error, because a visible error gets fixed on the spot and a plausible number gets circulated.

Four steps before the deadline

This is an afternoon of work, not a project, provided you do it before rather than after. Start by searching your shared drives for the function so you are working from a real count rather than a remembered one, and include the workbooks people keep in personal folders, because that is where most of them live. Rank what you find by consequence: a monthly board pack is not the same as somebody's scratch file. Replace the ones that matter by moving the AI step out of the cell entirely, so the sheet holds a plain value that a person or a separate process put there. Then re-check the totals, because that is the failure mode that travels furthest.

The rule worth taking from this

Embedding AI inside something you store is a heavier decision than using an AI tool, and it deserves to be treated as one. A formula in a workbook, a generated field in a database, an AI step buried inside an automation, a block inside a document template: all of these outlive the moment somebody decided to use them, and all of them get inherited by people who never made that decision. It does not mean avoid them. It means write down where you have done it, so a retirement notice is a task rather than a hunt. That register is the same one that makes any AI build maintainable over time.

This is normal, and that is the point

Nothing here is a scandal. Microsoft gave notice and named an alternative, which is how deprecation is supposed to work, and every software vendor retires features. The reason to pay attention is that AI features are arriving faster than any previous category of functionality, which means they will also be withdrawn, renamed, and repriced faster. Being able to answer where is this used, within an hour, is the whole capability. It is the same muscle as knowing what stops when a provider goes down, and it gets easier every time you use it. If you are still exploring what the tool can do, our guide to using Copilot in Excel covers the side pane approach that Microsoft is steering everyone toward.

Frequently Asked Questions

What is being retired?

Microsoft is removing the COPILOT worksheet function from Excel on September 14, and directing people to use the Copilot side pane instead. The function let you call AI from inside a cell the way you would call SUM or VLOOKUP, so a spreadsheet could summarise, classify, or draft text as part of a calculation. The side pane does similar work, but it is a conversation you have beside the sheet rather than something that lives inside the file, which is a meaningful difference if you built anything on it.

Why does removing one function matter?

Because of where it lived. Most AI is a tool you open, and if it disappears you go and use something else. This one was embedded in files, which means it sits inside documents your business keeps, shares, and reuses. When the function is withdrawn, the formulas do not politely degrade into the old manual version. They stop producing values, and every downstream calculation, chart, and report that depended on those cells changes with them. The scope of the problem is defined by how widely the file was copied, not by how important the feature seemed.

What should we do before September 14?

Four steps, and they take an afternoon rather than a project. Search your files for the function so you know the real number rather than the remembered one, including the workbooks staff keep in personal drives. Rank what you find by consequence, because a monthly board pack matters more than someone’s scratch file. Replace the important ones, usually by moving the AI step out of the cell and into a separate process that writes a plain value into the sheet. Then re-check the totals, since a formula that stops returning a number can quietly change a subtotal without any visible error.

Is there a broader lesson here?

Yes, and it is more useful than the migration itself. AI features increasingly arrive embedded inside things you keep: formulas in spreadsheets, fields in a database, steps in an automation, blocks in a document template. Embedded AI creates a dependency that outlives the decision to use it, because the file gets copied, shared, and inherited by people who never chose it. Treat embedding AI into a stored artefact as a different, heavier decision than using an AI tool, and write down where you have done it.

Does this mean we should avoid AI features in Microsoft 365?

No, and overcorrecting would cost you more than the disruption. Vendors retire features constantly, and this one is being handled the normal way, with notice and a stated alternative. The practical response is not to avoid AI features but to know where they sit in your work and how deeply. Use them freely where a withdrawal is an inconvenience. Be deliberate where a withdrawal would break a file that other people depend on, and keep a note of those places so the next retirement notice takes an afternoon rather than a week.