---
title: "What's Left of Copilot After the Excel Pane Disappears"
date: 2026-09-13T00:00:00Z
updated: 2026-09-13T03:06:32Z
tags: ["AI & Copilot", "Excel, Formulas & Functions", "Microsoft 365 Apps", "Automation", "Career & Workplace"]
canonical: https://bianca.codes/blog/whats-left-of-copilot-after-the-pane-disappears/
---

# What's Left of Copilot After the Excel Pane Disappears

_The pane closing was a surface change, not a licence change. Here is the tested map of what an unlicensed account can still do, and what it never could._

The morning the button went missing, I did what I suspect most people did. I checked the other tabs in case it had moved, checked File and Account in case a licence had lapsed overnight, and then quietly concluded that Copilot was over for me. Not removed from Excel. Over. The whole thing.

That conclusion lasted about a day and a half, until I opened Outlook for an unrelated reason and found a thread summary sitting there working perfectly, on the same account, on the same machine, in the same tenant that had just told me I had no Copilot. Which is a strange feeling, and also the most useful thing that happened that week, because it meant the question I had been asking was wrong.

The question is not whether you have Copilot. It is which doors are still open, and what is behind each one. This is that map, tested on an unlicensed account at an organisation over the 2,000-seat line, which is the least generous configuration there is. If it works here, it works for you.

## A pane is a doorway, not a room

What disappeared on 15 April 2026 was a surface. A button, a task pane, a place to type. The model behind it did not get switched off, your account did not get downgraded, and the underlying service kept running the entire time. Microsoft closed one entrance to a building that has several.

This sounds pedantic until you watch what it costs people who miss it. I have had three separate conversations with colleagues who stopped using Copilot entirely in April, not because the thing they needed had gone, but because the place they were used to finding it had. They had bound a capability to a location, which is a reasonable thing to do when a product ships as a button, and then the button became the whole product.

So the useful move is to stop thinking about Copilot as a feature you either have or do not have, and start thinking about it as three separable things that happened to arrive in one place: a model that can answer questions, a mechanism that lets it see your data, and a set of permissions that decide whose data it can see. April touched exactly one of those. Working out which one is most of the work.

## Three things were wearing the same coat

**The model.** Whatever is answering you, it is still there and you still have access to it. Worth noting that "the model" is not a fixed thing: Bloomberg reported in July that Microsoft has been swapping its own in-house MAI models in behind Excel and Outlook prompts specifically, to cut inference costs. Microsoft has not disputed it. That is a quality variable nobody puts in a release note, and a good reason to keep testing rather than trusting a result you got in March.

**The mechanism that lets it see your file.** This is the part that changed. In the pane, Excel handed the model your workbook because you had it open. Outside the pane, nothing hands it anything until you do. The capability survived, the convenience did not.

**The permissions.** Grounding in your organisation's content, the emails and files and meetings that make Copilot feel like it works at your company rather than at a company, is a paid add-on and has been from the start. It did not go anywhere in April because it was never in the free tier to go.

Sort any Copilot refusal you hit into one of those three buckets and it stops being mysterious. It is either a surface that closed, a mechanism you have not replaced yet, or a permission you never had.

## The doors that are still open

Here is the honest inventory. Every row below is something an unlicensed account can actually do today.

**The standalone Microsoft 365 Copilot app, with file upload.** This is the big one and it is the reason this post exists. Copilot Chat on the free tier accepts file uploads: up to 20 files in a conversation, 50 MB each, covering XLSX, CSV, PDF, DOCX, PPTX and JSON. You upload the workbook and ask about it. The answers quote real values out of your file, because the file is genuinely there. Everything the pane did to a workbook, you can still do to a copy of that workbook, one hallway over.

**Outlook, entirely.** Outlook was carved out of the removal, so inbox and calendar grounding kept working for unlicensed users while the four Office apps lost theirs. This is why the same account can be simultaneously "Copilot is gone" and "Copilot is fine" depending on which window has focus. If you want the version of this with technique attached rather than just a status, I wrote up turning a forty-email thread into three lines in August.

**Web-grounded chat with enterprise data protection.** Less glamorous, genuinely useful. It will read a public page and reason about it, and your prompts stay inside the commercial data boundary rather than wandering off into a consumer service. That last part is the difference between "I can ask an AI about this" and "I can ask an AI about this at work".

**In-app Copilot Chat, if your organisation is under 2,000 seats.** The 2,000-user threshold is the whole story of who lost what. Under it, Word, Excel and PowerPoint kept in-app Copilot Chat under standard access, which means the same features with throttling at peak times and periodic upgrade prompts. Over it, unlicensed users lost the in-app surface outright. Your experience of April depends almost entirely on a number nobody told you.

If you have not confirmed which side of that line you are on, that is worth twenty minutes with a spreadsheet before you take any of this personally. I have written the [five-minute audit that establishes it](/blog/what-survived-the-copilot-cull-fast-excel-audit/), with a build number column, because a capability recorded without a build number is a rumour.

## The doors that were never open

Equally important, and the source of most of the bad advice circulating right now.

**Grounding in your tenant's content.** Asking about a SharePoint file, a colleague's workbook, a Teams channel, last quarter's deck that lives somewhere in OneDrive. That is the paid Microsoft 365 Copilot add-on and always was. A refusal here is the product working correctly.

**Writing into the file.** Copilot Chat reads and talks. It does not make multi-step edits inside your workbook. That boundary deserves its own post and is getting one, but for now: if you are waiting for the free tier to start applying changes for you, stop waiting.

**Agents over your own data.** Same reason as grounding. The interesting agent scenarios all assume the model can see your organisation's content, which loops back to the licence.

The reason to write these down explicitly, rather than just letting them fail, is that a refusal you misclassify costs you twice. You raise a ticket for something that was never broken, and somewhere in the same week a colleague tells you confidently that it used to work, and now you are both wrong together. A refusal is not always a removal, and it is not always a licence either. Often enough it is a thin question, an argument I have already made at length.

## Handing over the file is a different act than pointing at it

The map above makes the standalone app sound like a drop-in replacement. It is not, and the differences are worth understanding before you build a habit on top of it.

You are giving it a copy, not a view. The pane looked at the live workbook. An upload is a snapshot, frozen at the moment you sent it. Change a cell and the conversation you are in is now discussing a file that no longer exists. This is fine as long as you know it, and quietly maddening for the twenty minutes before you work it out.

You choose the scope now. In the pane, "the file" meant whatever was open, all forty tabs of it, including the three nobody has touched since 2023. Uploading forces a decision about what you actually want looked at. That is friction, and it is also the single biggest quality improvement available to you, because a focused upload of two clean sheets outperforms a vague question about a sprawling workbook almost every time. The constraint made me better at asking, which is not a sentence I expected to write about a feature removal.

You lose the ambient case. The pane's real advantage was never capability, it was proximity. It was there while you were already working, so you used it for small things you would never bother uploading a file for. Those small uses are genuinely gone, and no workflow gets them back. It is worth being honest about that rather than pretending the replacement is seamless. Some of what I liked in [a week of actually driving Copilot](/blog/a-week-of-actually-using-copilot/) was exactly this kind of low-stakes proximity, and it is the part I miss.

The upload route is a workflow rather than a button, which means it can be built deliberately, and built once. That is the file-upload workflow that replaces the pane, later this month.

## Everything above has a shelf life

This set of answers has moved twice in the twelve months to September 2026. The July pricing reset folded Copilot Chat baseline features into most base tiers. The model routing changed underneath without an announcement. April closed a surface that had been open since launch.

None of it was communicated in a way an ordinary user would encounter. The clearest public description of the April removal I could find was [a university IT helpdesk notice](https://its.wsu.edu/2026/04/29/copilot-chat-removed-from-word-excel-powerpoint-and-onenote/), not anything on Microsoft's own site, because the change went out through admin Message Center notices aimed at tenant administrators. It is why I keep coming back to the same complaint: the product arrived as an expectation rather than as a feature, and it changes the same way.

So treat this map as tested rather than permanent. Re-run the rows that matter to you when your build number changes, and do not let a result from six months ago make a decision for you today.

## Frequently Asked Questions

### **Can I still use Copilot on an Excel file without a paid licence?**

Yes, but not from inside Excel. Upload the workbook to the standalone Microsoft 365 Copilot app or Copilot Chat on the web and ask your questions there. The free tier accepts up to 20 files per conversation at 50 MB each, and XLSX and CSV are both supported formats. The answers are grounded in the file you uploaded, so they quote real values rather than generalities.

### **Why does Copilot work in my Outlook but not my Excel?**

Because Outlook was deliberately excluded from the April 2026 removal. Inbox and calendar grounding continued for unlicensed users at the same time Copilot Chat disappeared from Word, Excel, PowerPoint and OneNote. Having a working Copilot in one Microsoft app and none at all in another, on the same account and the same machine, is expected behaviour rather than a fault.

### **What is the difference between Copilot Chat (Basic) and M365 Copilot (Premium)?**

Basic is what you get without a paid add-on licence: web-grounded chat, file upload, image generation, and enterprise data protection. Premium adds grounding in your organisation's own content, meaning it can answer questions about your emails, files, meetings and SharePoint sites without you uploading anything. Microsoft added those labels in-product, so checking which one you have takes a few seconds.

### **Did everyone lose in-app Copilot in Excel?**

No. The removal applied to unlicensed users at organisations with more than 2,000 Microsoft 365 users. Smaller organisations kept in-app Copilot Chat in Word, Excel and PowerPoint under standard access, which is the same functionality with throttling at busy times and occasional prompts to upgrade. Anyone holding a paid Copilot licence was unaffected either way.

### **Can the free tier read a file stored in SharePoint or Teams?**

No, and it never could. Grounding in your organisation's stored content is the paid Microsoft 365 Copilot capability, separate from the in-app surfaces that were removed in April. If you need a SharePoint file analysed on the free tier, download it and upload it as a file like any other. The refusal is a licence boundary, not a bug.

### **Is uploading a work file to Copilot Chat safe?**

Copilot Chat with a work or school account runs under enterprise data protection, so prompts and uploads stay inside the commercial data boundary rather than being treated like consumer chat. That is a meaningfully different posture from pasting the same data into a public chatbot. It is still worth checking your own organisation's policy, because tenant settings and internal data-handling rules sit on top of whatever Microsoft permits by default.

## The way to think about it

Stop asking whether you have Copilot. It is not a possession and it never was, which is why the April removal felt like a theft rather than a change in a service you rent.

Ask instead which door is open. There is a model, there is a mechanism for showing it your data, and there is a permission that decides whose data it may see. Every Copilot question you will have this year decomposes into those three, and the answers move independently: a surface can close while the capability behind it stays exactly where it was, and a refusal can be a permission you never bought rather than a feature somebody took.

The people who found April disorienting were mostly the ones who had learned a location. The people who barely noticed had learned a capability and simply walked to a different entrance. That is the whole difference, and it is worth building the habit now, because this is not the last time a button is going to move.