Microsoft Copilot Won't Work With Your .xls Files — Here's Why

You upgraded to Microsoft 365. You're paying for Copilot. You open an Excel file and click the Copilot button — and nothing happens. The button is grayed out. Or it's not there at all.

This is one of the most common frustrations IT teams are reporting in 2026: Copilot is installed, licensed, and connected — but it won't activate on huge swaths of their Excel files. The reason is almost always the same: the files are in the legacy .xls format.

This isn't a bug. It's a hard requirement. And it means that if your organization still has .xls files — even a few — those files are locked out of every AI-powered feature in Excel until you convert them. Our complete guide to legacy Excel migration walks through the entire conversion process from start to finish.

Why Copilot Requires .xlsx

Microsoft 365 Copilot uses a cloud-based AI engine that reads and processes your spreadsheet data. To do that, it needs the file in Open XML format — the structured, human-readable ZIP-based format that .xlsx uses.

Legacy .xls files are in BIFF8 format — a binary format Microsoft introduced in 1997. Copilot's AI engine cannot parse BIFF8. There's no compatibility layer, no automatic conversion on open. The file is simply opaque to Copilot.

Two requirements must be met before Copilot will activate on an Excel file:

1. The file must be in .xlsx (or .xlsm for macro-enabled) format
2. The file must be stored in OneDrive or SharePoint (not on a local drive or network share)

Miss either one and the Copilot panel stays dark.

What Copilot Features Are Blocked

It's not just one feature. The entire Copilot experience in Excel is unavailable for legacy files:

Feature	Works with .xlsx	Works with .xls
Copilot Chat (ask questions about your data)	Yes	No
Formula suggestions and generation	Yes	No
Data analysis and insights	Yes	No
Column summarization	Yes	No
Highlight and filter suggestions	Yes	No
Natural language pivot table creation	Yes	No

If your organization is spending money on Microsoft 365 Copilot licenses and your team is using .xls files, you're paying for a feature set that's effectively disabled.

Why "Just Save As .xlsx" Doesn't Work

The obvious fix is to open the file and do File → Save As → Excel Workbook (.xlsx). For simple files, this works fine. But for workbooks with VBA macros, ActiveX controls, or complex form objects, this process is a trap.

Common failures after a naive Save As conversion:

• VBA macros that reference 32-bit Windows API functions fail on 64-bit Office
• ActiveX control events stop firing
• UserForms lose button references
• Named ranges with legacy characters become invalid
• External data connections break

For a file that's been in use for 10 or 15 years, these problems can be extensive — and they're invisible until a macro fails at exactly the wrong moment.

How to Convert Safely

The right approach is to audit first, then convert. You need to know what's in the file before you change the format, so nothing gets silently dropped.

Step 1: Scan for VBA and ActiveX content

Before converting, identify every macro module, every ActiveX control, and every external reference in the file. This tells you the scope of what needs to survive the conversion.

Step 2: Check for 32-bit API declarations

Look through VBA modules for Declare Function or Declare Sub statements without the PtrSafe attribute. These will fail silently or crash 64-bit Office after conversion.

Step 3: Convert with a tool that preserves macro integrity

Use a tool that understands VBA — not just file format conversion. The converter needs to rewrite 32-bit API declarations, preserve ActiveX event bindings, and validate named ranges after format change.

Step 4: Test before distributing

Open the converted file, run each macro once, and verify outputs. For complex workbooks, spot-check a sample of the data outputs against the original file.

The Business Case: Copilot ROI Depends on Clean Files

Microsoft 365 Copilot is not cheap. At current licensing rates, it's an additional $30/user/month on top of your M365 subscription. For a 50-person organization, that's $1,500/month.

If 40% of your team's Excel files are still in .xls format — which is common in organizations that have been running Office since the early 2000s — a significant portion of that Copilot investment is delivering zero value. The math on migrating those files becomes compelling very quickly.

One-time file conversion costs less than a single month of blocked Copilot licenses.

What About .xlsm Files?

If your workbook has macros, the target format after conversion should be .xlsm, not .xlsx. The .xlsm format is the macro-enabled version of Open XML and is fully supported by Copilot. Copilot can read and analyze the data in .xlsm files — it just won't execute the macros directly (that's by design for security).

So the conversion path is:

• .xls with no macros → .xlsx
• .xls with macros → .xlsm

Either format unlocks Copilot. The key is getting off the binary BIFF8 format.

Batch Converting for IT Teams

If you're an IT administrator facing this problem at scale, the question isn't "how do I convert one file" — it's "how do I audit and convert 500 files without breaking the ones that matter."

The first step is an inventory. You need to know:

• How many .xls files exist across your file shares and OneDrive accounts
• Which ones have VBA macros (these need careful conversion)
• Which ones are actively used vs. archived

Files with no macros can often be batch-converted automatically. Files with VBA need individual attention — or a conversion tool that handles macro preservation at scale.

LegacyLeaps is built for exactly this workflow: scan to categorize, then convert the complex ones with macro preservation, and bulk-process the simple ones. See the IT Teams guide for how organizations have structured this process.

The Bigger Picture: Copilot Is Just the First Symptom

Copilot is making .xls files visible again because it creates an immediate, concrete business problem: you're paying for AI features that don't work. But the underlying issue is broader.

Legacy .xls files are also incompatible with:

• Excel Online (web version) — limited editing, no macro support
• Power Automate — can't trigger workflows from .xls file changes
• Power BI data refresh — some connectors require Open XML format
• SharePoint document libraries — version history and co-authoring work poorly on .xls

Every time Microsoft adds a new cloud feature to the M365 ecosystem, it builds on Open XML. Legacy files fall further behind. The conversion work you do today compounds in value as M365 adds more capabilities.

Frequently Asked Questions

Why is the Copilot button grayed out in Excel?

The most common reasons are: the file is in .xls format (not .xlsx), the file is stored locally or on a network share (not OneDrive/SharePoint), or your Microsoft 365 license doesn't include Copilot. If you've confirmed your license includes Copilot, check the file format and storage location first.

Can I convert .xls to .xlsx without losing my macros?

Yes — but not with a simple Save As. Standard conversion will silently break VBA macros and ActiveX controls in many cases. You need a tool that audits and preserves VBA code, module references, and form controls. LegacyLeaps scans for exactly these issues before converting. If you do lose your macros, we'll refund every penny — no questions asked.

What other M365 features require .xlsx format?

Beyond Copilot: Excel Online has severely limited functionality on .xls files. Power Automate triggers don't support .xls changes. Power BI data refresh is unreliable with legacy formats. Co-authoring and real-time collaboration in SharePoint don't work properly on .xls.

Is there a way to use Copilot on a .xls file without converting it?

No. Copilot has no compatibility mode for .xls. The file must be converted to .xlsx or .xlsm and stored in OneDrive or SharePoint. There is no workaround at the application layer.

← Back to all posts