Don't stop here
Hand-picked guides our readers explore right after this one.
AI prompts for Excel formulas, macros, data analysis, automation, and dashboards
Read the guideExpert guide to Claude prompts with XML tags, artifacts, and complex reasoning
Read the guideAI prompts for legal research, contract drafting, case analysis, and client communication
Read the guideCopilot in Excel fails in two distinct ways, and they need completely different fixes. The first is refusal: the button is greyed out or missing, and that is almost always an unmet requirement rather than a bug. Copilot in Excel needs a modern file format (.xlsx, .xlsb, or .xlsm), the file saved to OneDrive or SharePoint, and AutoSave switched on. Legacy .xls files and local-only workbooks are simply out of scope. The second failure is worse because it looks like it worked: Copilot edits the wrong columns, drops rows, or writes a formula referencing a table that does not exist. That one is almost always structure. Copilot has to infer where your data starts and ends, and merged cells, blank rows, missing headers, and several datasets on one sheet make that inference wrong. Fixing structure once fixes every future request against that workbook. Always review Copilot's edits against a saved copy before accepting them, since generated formulas and transformations can be confidently wrong.
The Copilot button is greyed out, missing, or says the file must be saved first
Copilot answers questions but refuses to make changes to the sheet
Edits land in the wrong columns or overwrite data you needed
Rows are dropped or ignored in summaries and totals
Generated formulas reference table or column names that do not exist
Copilot only sees part of your data and reports incomplete numbers
Copilot in Excel requires .xlsx, .xlsb, or .xlsm. Legacy .xls workbooks and CSV files opened in Excel are not supported, and the feature will be unavailable rather than explain why. Save As to .xlsx first.
Copilot needs the file stored in Microsoft 365 cloud storage with AutoSave enabled so it can read and write reliably. A workbook sitting on your local drive or a network share will show Copilot as unavailable or read-only in behavior.
Copilot infers the shape of your data. Without a formatted Excel table and clear single-row headers, it guesses the boundaries, and that guess is how edits land in the wrong columns or exclude rows entirely.
Merged cells break the row and column grid Copilot relies on, blank rows read as the end of a dataset, and two tables on one sheet make it ambiguous which one you mean. These are the top three causes of wrong-range edits.
Microsoft states plainly that Copilot can produce inaccurate formulas. A formula that references the wrong table or a column name that does not match your headers will still be inserted, and the resulting numbers look plausible.
When to try: First, whenever Copilot is greyed out or missing
Confirm the file is .xlsx, .xlsb, or .xlsm (File, then Save As if not), that it is stored in OneDrive or SharePoint, and that AutoSave is toggled on in the top left. If any of the three is missing, Copilot will be unavailable or unreliable no matter what you prompt.
When to try: Before asking Copilot to change or analyze anything
Select the data and press Ctrl+T, confirm 'My table has headers', and give the table a meaningful name in Table Design. This removes all ambiguity about where your data starts and ends, and it is the single highest-impact change for edit accuracy.
When to try: If Copilot edits the wrong columns or misses rows
Unmerge every cell in the data area (Home, then Merge and Center to toggle off), delete blank rows and blank columns inside the table, and make sure every column has a single clear header with no duplicates. Put separate datasets on separate sheets.
When to try: Every request, as a habit
Instead of 'summarize the sales data', say 'using the table named SalesQ2 on the Data sheet, sum the Revenue column grouped by Region'. Naming the table, sheet, and columns removes the inference step where Copilot goes wrong.
When to try: Before any request that modifies the sheet
Because AutoSave is required, Copilot's changes write straight to the live file. Duplicate the workbook (or use File, then Version History to recover) before running transformations. Version History in OneDrive is your undo when Copilot rewrites more than you expected.
When to try: Every time Copilot writes a formula
Click into the inserted formula and check that the table name and every column reference match your actual structure. Microsoft explicitly warns that generated formulas can be inaccurate. Spot-check the result against a manual calculation on a few rows.
When to try: For anything more complex than a single operation
Ask for one transformation at a time and check the result before the next. A single prompt asking Copilot to clean, pivot, and chart in one pass gives you no point at which to catch the mistake, and compounding errors are much harder to unwind.
When to try: If requirements are met but Copilot still does not appear
Copilot in Excel requires an eligible Microsoft 365 Copilot licence assigned to your account, and you must be signed in with that account. Then update Office (File, Account, Update Options, Update Now) and restart. Feature availability also varies by update channel, so the Current Channel gets capabilities before Semi-Annual.
Store working workbooks in OneDrive or SharePoint with AutoSave on by default
Format every dataset as a named Excel table with single-row headers before using Copilot
Keep one dataset per sheet and never merge cells inside a data range
Check OneDrive Version History exists before letting Copilot make bulk edits
Contact your Microsoft 365 administrator first if Copilot is missing entirely, since licence assignment and tenant policy are the most common blockers and only an admin can check them. Escalate to Microsoft support if the licence is confirmed, the file meets all format and storage requirements, Office is fully updated, and Copilot still does not appear or consistently corrupts data. Include the build number, the channel, the file location, and a reproducible example.
Almost always an unmet requirement. The workbook must be .xlsx, .xlsb, or .xlsm, saved to OneDrive or SharePoint, with AutoSave turned on, and your account needs an assigned Microsoft 365 Copilot licence. Legacy .xls files and locally stored workbooks are not supported, and Excel does not explain the reason.
Because it has to infer where your data begins and ends. Loose ranges, merged cells, blank rows, missing or duplicate headers, and two datasets on one sheet all make that inference wrong. Converting the range to a named Excel table with clean single-row headers fixes it for every future request.
Yes, through OneDrive or SharePoint Version History (File, then Info, then Version History), which is important because AutoSave writes changes immediately. Standard Ctrl+Z works within the session but is not reliable after saving and closing. Duplicate the file before bulk transformations.
Treat them as drafts. Microsoft states that Copilot can generate inaccurate formulas and content, and the common failure is a formula referencing a table or column name that does not match your workbook. Check the references and spot-check the output against a manual calculation before relying on it.
No. The workbook must be stored in OneDrive or Microsoft 365 SharePoint with AutoSave enabled. Files on a local drive, a network share, or a non-Microsoft cloud service will not work with Copilot in Excel.
Product behavior and limits can change. These primary sources were used to verify this guide.