Microsoft 365 Copilot for Excel — What Works, What Doesn’t
If you bought Microsoft 365 Copilot at $30/seat last quarter and discovered three months later that everyone needs the next M365 SKU up, that your Postgres data needs an ODBC driver IT has blocked, and that shipping a code fix from your Excel analysis requires another $19–$39/seat for GitHub Copilot — you’ve found the structural limits of the Microsoft-stack approach. Copilot for Excel is genuinely the best in-workbook AI surface in the category. The trade-offs sit elsewhere: locked to Microsoft data, locked to Microsoft / OpenAI bundled models, scaling per-seat with the team, and a multi-product story for anything outside one .xlsx in the tenant. This is the honest map of what Copilot does well, where the bill creeps up, and what to use instead when Excel work crosses the workbook edge.
Where M365 Copilot wins for Excel
Copilot is genuinely the best in-Excel authoring surface in the category. If your week is dominated by these workflows, keep it.
In-workbook authoring help
Copilot lives in the Excel ribbon (Microsoft 365 desktop + web with the right SKU). Plain-English requests like "add a column with the running total of B grouped by A" produce the right formula in the right cell. Pivot tables, conditional formatting, chart axes — all written and applied natively. For day-to-day Excel-author work, no other tool is closer to the workbook.
Cross-app context across Word, Excel, PowerPoint
Microsoft 365 Copilot shares context across the Office suite. A Copilot session reading your Excel can draft the corresponding deck in PowerPoint and write the executive summary in Word without re-explaining the data. For finance / consulting workflows where the deliverable IS a deck or memo, this end-to-end coverage is real.
Already part of the M365 license your team owns
If your organization already pays for Microsoft 365 Business Standard / E3 / E5, adding Copilot is a $30/user/mo line item on existing contracts — no new vendor, no new procurement, no SSO setup. For enterprise teams with full M365 commitment, the friction to enable Copilot is low.
On-tenant data, on-tenant governance
Files stay in OneDrive / SharePoint inside your Microsoft tenant with existing DLP policies, sensitivity labels, and audit logs. For regulated industries (healthcare, financial services, government) the compliance story is the simplest in the category — same controls you already operate.
Where M365 Copilot for Excel falls short
Six structural limits that turn into daily friction once Excel work crosses the Microsoft-tenant boundary.
- 01
The qualifying-SKU surprise
Copilot for Microsoft 365 is a $30/user/mo add-on that requires a qualifying base license — Business Standard or Business Premium for SMB, or E3 / E5 for enterprise. Many teams discover post-purchase that their existing M365 SKU doesn't qualify, then have to upgrade everyone before Copilot becomes usable. The bill jumps twice.
- 02
Single-workbook, single-source orientation
Copilot reasons over the active range of one Excel workbook stored in OneDrive/SharePoint with AutoSave on. It can't see your Google Sheet sitting in another tab. Postgres, Stripe, GA4, BigQuery — all require Power Query imports first, with ODBC drivers that enterprise IT often blocks.
- 03
Locked to Microsoft / OpenAI bundled models, no BYOK
Copilot runs on Microsoft's bundled models (currently OpenAI GPT-4-class). No model dropdown for users. No bring-your-own-key — billing flows through Microsoft regardless of any enterprise OpenAI / Anthropic / Google contract you already have.
- 04
Wide-table sampling, narrow-row attention
Community reports consistently observe Copilot focuses attention on the first ~50 rows of wide tables when answering general questions, even when the workbook has 100,000+ rows. Excel itself supports 1M+ rows, but Copilot reasons over a much narrower slice. Saying "Copilot read my whole sheet" overstates what it actually attended to.
- 05
No native scheduling — Power Automate is a separate product
Want a 6am Monday Slack report from your Excel? Copilot has no scheduler. You'd build a Power Automate flow (separate product, separate UI, separate license tier) wiring Copilot's output to Teams or Outlook. Slack delivery requires a third-party connector. The schedule + share layer is at least one product hop away.
- 06
Coding workflow lives in a separate license
When the analysis points at code in your repo — meta-tag fix, config update, seed-data tweak — M365 Copilot can't edit it. Code work requires GitHub Copilot, a separate product on a separate license. There's no path inside one conversation from data analysis to merged PR.
4 real Excel tasks where M365 Copilot stops (and what to use instead)
Task 1: Find anomalies in a 50,000-row sales CSV
M365 Copilot
Open the workbook, ask Copilot in the sidebar. Reasons over the active range — typically attends to the first ~50 rows on wide tables. For full-file scanning, you'd run Power Query + a script Copilot writes for you, then re-prompt over the result.
OnlySearch
Drag once, the file persists. Anomaly detection (isolation-forest + IQR + domain rules) runs server-side over the full file every time you ask. Save as a dashboard, schedule weekly.
Task 2: Weekly revenue report from Stripe + Google Sheets
M365 Copilot
No native Stripe or Google Sheets connector. Build Power Query connections (Stripe via custom API, Google Sheets via third-party connector — often IT-blocked), schedule via Power Automate, deliver to Teams. Multi-product setup, one analysis.
OnlySearch
Connect Stripe + Sheets once. Ask once for "weekly revenue from Stripe overlaid with budget from Sheets, top 10 SKUs, Mondays at 6am to #revenue." Schedule from the UI. Slack delivery built in.
Task 3: Compare Excel data to Postgres production data
M365 Copilot
Power Query loads Postgres into a sheet via ODBC (driver install + IT approval). Copilot then reasons over the loaded table inside Excel. The Excel side and Postgres side are in the same workbook only after the import — nothing live, refresh is manual or scheduled via Power Query.
OnlySearch
Both sources native. Single SQL with a CTE pulling one side from the uploaded CSV and the other from Postgres in one round trip. Joined result, chart, savable dashboard.
Task 4: Excel pointed at a stale config — ship the fix
M365 Copilot
Microsoft 365 Copilot can't edit code in your repo. You'd license GitHub Copilot separately ($19/seat for Business / $39 for Enterprise on top of M365 Copilot's $30), or copy the analysis to a developer who runs Cursor / Claude Code.
OnlySearch
Same agent. Edits the repo, runs the test suite, opens a PR — all inside the conversation that surfaced the problem. Data → code → ship.
When to stay with M365 Copilot
We’re not the right tool for everyone. Here’s when Copilot is the better choice — and we’d recommend it.
- Your organization is fully on Microsoft 365 with Copilot licenses already paid, and the day-to-day work happens inside Excel itself — pivot edits, formula composition, chart formatting.
- You're a finance / consulting / corporate user whose deliverables are Word memos and PowerPoint decks driven by Excel data, all on Microsoft 365 — Copilot's shared-context across Word/Excel/PowerPoint is unique to that surface.
- Your data lives entirely inside the Microsoft tenant (SharePoint, OneDrive, Dataverse, Power BI) and the on-tenant governance / DLP / audit story is non-negotiable for compliance.
- You don't have engineering or growth functions on your team — the analysis itself is the deliverable, no code needs to ship from it, no cross-source join, no Slack alert at 6am.
Common questions about M365 Copilot for Excel
What does Microsoft 365 Copilot for Excel actually do?
It's a sidebar inside Excel (desktop + web with the right SKU) that takes plain-English requests and writes them back into the workbook — pivot tables, formulas, conditional formatting, chart edits — with cell-level explanations. It also chains context across Word and PowerPoint inside the same Microsoft 365 session. For in-workbook authoring it's the most native AI surface in the category.
How much does M365 Copilot for Excel cost?
$30/user/month as a Microsoft 365 Copilot add-on, on top of a qualifying base license (Business Standard, Business Premium, E3, or E5). For a 10-person team on E3, the math is $30/user × 10 = $300/mo Copilot, on top of the existing M365 base. If your team is on a non-qualifying SKU (Business Basic, F1/F3 frontline, etc.), you upgrade everyone first before Copilot becomes available.
What's the qualifying-SKU surprise?
M365 Copilot requires Business Standard/Premium or E3/E5 base licenses. Many SMBs run on Business Basic ($6/user) and discover after buying Copilot ($30/user) that they need to upgrade to Business Standard ($12.50/user) — the practical cost is $30 + $6.50 upgrade = $36.50 per user, not $30. For frontline / kiosk users on F1/F3 SKUs the gap is wider. Plan for the SKU upgrade in budget conversations.
Can M365 Copilot connect to Google Sheets, Postgres, or Stripe?
Not natively in the Copilot sidebar. Cross-source data has to be loaded into Excel first via Power Query — Postgres requires an ODBC driver install (often blocked by enterprise IT), Google Sheets requires a third-party connector, Stripe requires custom API setup. Once loaded into a sheet, Copilot reasons over the imported table. Live refresh is manual or scheduled via Power Query, not via Copilot itself.
Can Copilot write Excel formulas from natural language?
Yes — and well. "Give me a formula that returns running revenue grouped by month, ignoring zeros" produces a clean Excel formula in the right cell with an explanation. For in-Excel formula authoring, M365 Copilot, Claude for Excel sidebar, and ChatGPT all do this competently. Copilot's edge is that it writes the formula directly into your active cell rather than into a chat you copy from.
Does Copilot reason over my whole spreadsheet?
Not necessarily. Copilot reasons over the active range of the workbook, but community reports consistently observe attention focus on the first ~50 rows for wide tables when answering general questions. For targeted questions about specific rows ("how many rows have Status=Pending"), it scans the relevant column more thoroughly. Multi-million-row sheets exceed what any AI sidebar attends to in a single response — for those, Power Query pre-aggregation is the workflow.
Do I need GitHub Copilot too?
If your data analysis points at code changes in a repo — yes. M365 Copilot for Excel can't edit files in GitHub. GitHub Copilot is a separate product on a separate license: $19/seat Business or $39/seat Enterprise on top of M365 Copilot's $30/seat. For a developer also doing finance analysis, the combined Microsoft bill is $49–$69/seat just for Copilot products.
How is OnlySearch different from M365 Copilot?
M365 Copilot is the Microsoft-stack solution: best in-Excel authoring, locked to Microsoft data + Microsoft models, $30/seat scaling with team size, separate products for scheduling (Power Automate) and code (GitHub Copilot). OnlySearch is the cross-source solution: native Google Sheets / Postgres / MySQL / Stripe / GA4 connectors with cross-source single-query joins, scheduled runs with Slack/email built in, model freedom (GPT, Claude, Gemini, DeepSeek, local) with bring-your-own-key, and a coding agent that opens GitHub PRs. Flat $59/$159/$299 per account instead of per-seat.
Can I keep M365 Copilot and add OnlySearch?
Yes — the two cover non-overlapping work. Keep Copilot for in-Excel authoring (pivots, formulas, chart formatting), Word memos, PowerPoint decks, and the on-tenant governance story. Add OnlySearch for cross-source analysis (Excel + Google Sheets + Postgres in one query), scheduled reporting with Slack delivery, and the data-to-PR-on-GitHub workflow. Many enterprises run both — Copilot covers the M365-resident work, OnlySearch covers everything outside the tenant.
Cross-source data + Slack + GitHub PRs — one flat plan
Native Google Sheets / Postgres / Stripe. Multi-GB files server-side. Schedule the report, ship the fix as a PR. Flat $59/$159/$299 per account — not per-seat. Free plan refills weekly. Bring your own model key if you want.