Copilot in Excel Personalization (June 2026): Save Formatting & Output Preferences

Microsoft has added personalization settings to Copilot in Excel in June 2026, letting users save standing preferences for formats, formulas, tables, charts, PivotTables, and explanations across workbooks and signed-in devices. The change sounds small because it lives inside a settings dialog, not a splashy new AI demo. But for anyone who has spent years correcting Excel’s choices one table, one chart, and one mangled date column at a time, it points to a more consequential shift: Copilot is moving from a prompt box bolted onto Excel toward a configurable assistant that remembers how you want spreadsheets to behave.
That is the right direction for Microsoft’s most durable productivity app. Excel is not merely a grid; it is a workplace culture encoded in cells, colors, number formats, hidden rows, and decades of departmental superstition. If Copilot is going to matter inside Excel, it cannot just answer questions about data. It has to stop making users repeat the same aesthetic and operational instructions every time they ask for help.

Microsoft Finally Treats Spreadsheet Taste as Product Data​

The new personalization feature gives Copilot in Excel a place to store instructions that are not one-off prompts. Microsoft’s own examples are telling: always format currency with a dollar sign and two decimals, show negative numbers in red and parentheses, use a preferred date format, apply banded rows and bold headers, prefer structured references and named ranges, label PivotTable fields with readable names rather than “Sum of,” and default to certain chart styles unless told otherwise.
That list reads less like science fiction and more like the accumulated grievances of anyone who has cleaned up AI-generated office work. Copilot could already help create formulas, summaries, charts, and PivotTables. The frustration was that it often behaved like a capable but forgetful colleague: useful in the moment, irritating over time, and strangely determined to reintroduce formatting habits you had already rejected.
Personalization changes the contract. Instead of teaching Copilot your preferences in every request, you can set a standing layer of instruction once and have it shape future output. In practical terms, that means the prompt “summarize this sales table” can inherit your usual rules for number formatting, chart palette, PivotTable labels, and commentary style without requiring a paragraph of formatting bureaucracy.
That matters because Excel work is full of tiny standards that are not universal. Finance teams may want negatives in parentheses; operations teams may prefer whole-number rounding; regional teams may require day-month-year dates; executives may want charts stripped down to the fewest meaningful categories. These are not decorations. They are the visual grammar by which people decide whether a workbook looks trustworthy.

The Real Upgrade Is Not AI Creativity, but AI Compliance​

Microsoft’s Copilot story has often leaned on generative capability: create a table, analyze trends, write formulas, build a chart, explain what changed. The personalization update is more modest and more useful because it addresses a less glamorous problem: AI tools are often bad at following house style.
That failure is not trivial. A spreadsheet that uses the wrong date convention can create confusion across regions. A financial table that formats negative values inconsistently can obscure risk. A PivotTable with generic field labels can make a quick review slower than it needs to be. A chart that uses too many categories can look comprehensive while communicating almost nothing.
Excel users have always solved these problems through templates, local habits, copied workbooks, and the occasional stern email from finance or compliance. Copilot personalization does not replace those governance mechanisms, and it should not be mistaken for enterprise policy control. But it does add a new layer: a user-level preference system for the AI’s output.
That distinction is important. Microsoft says these preferences are saved to the user’s account and apply across workbooks and Excel sessions, but they are not written into the workbook as shared instructions for everyone else. In other words, your Copilot can learn that you hate merged cells without imposing that preference on a colleague who opens the same file. Shared files keep their default settings, while the assistant’s behavior adapts to the individual user.
For collaboration, that is the least disruptive design. The workbook remains the common artifact; personalization affects the assistant sitting beside it. Microsoft is effectively saying that Copilot can have a memory of your working style without turning every spreadsheet into a battleground of personalized defaults.

---

“Center Across Selection” Is the Tell​

The most revealing example in the Geeky Gadgets write-up is not the currency formatting or chart palette. It is the suggestion that users can steer Copilot away from “Merge & Center” and toward “Center Across Selection.”
That sounds like an Excel nerd’s petty preference until you have inherited a workbook where merged cells break sorting, filtering, copying, formulas, accessibility, or automation. “Merge & Center” is one of those features that looks helpful in a clean demo and becomes a structural hazard in real spreadsheets. Many power users have spent years telling colleagues not to use it, only to find it embedded in templates, reports, and AI-generated layouts.
If Copilot can remember “never merge cells” or “use Center Across Selection instead,” the feature becomes more than cosmetic. It becomes a way to encode hard-won spreadsheet hygiene into the assistant’s default behavior. That is the difference between AI as a fast typist and AI as a participant in workflow discipline.
The same logic applies to PivotTable labels. A PivotTable that says “Sum of Revenue” is technically accurate, but in a polished report it often reads like scaffolding left on a finished building. Asking Copilot to use friendlier field names by default helps reduce the cleanup tax after an automated analysis.
These examples show why personalization is more interesting than another formula demo. Excel productivity is rarely blocked by the impossibility of creating a chart. It is blocked by the accumulation of small repairs after the chart appears.

The Spreadsheet Is Still the Boss​

There is a temptation to describe this as Excel becoming “adaptive” or “agentic,” but the safer reading is that Microsoft is putting guardrails around a feature that previously needed too much babysitting. Copilot is not gaining magical taste. It is gaining a preference file.
That is still valuable. A preference file is exactly what many AI assistants lack. They behave as if every session starts from zero, even though office work is defined by repetition. The same person writes the same kinds of reports, for the same audiences, with the same formatting expectations, week after week.
The challenge is that Excel is not a blank canvas. It is a mature, highly stateful application with decades of features layered on top of one another. Tables, named ranges, PivotTables, Power Query outputs, charts, cell styles, conditional formatting, formulas, workbook protection, macros, and collaboration features all have their own rules. A Copilot preference that sounds simple in natural language may produce messy results when applied to a real workbook.
Microsoft’s support guidance acknowledges this indirectly by recommending that preferences be short and specific. That is sensible because long, elaborate preference blocks can become a second prompt engineering problem. “Always use blue, gray, and orange in charts” is manageable. “Make reports executive-ready, modern, minimal, accurate, readable, brand-aligned, finance-friendly, and not too busy” is a request for ambiguity dressed up as productivity.
The best use of the feature will likely be boring and precise. That is not a criticism. Boring and precise is where Excel earns its keep.

Personalization Solves the Repetition Problem, Not the Trust Problem​

The update should reduce repetitive prompting, but it does not eliminate the need to inspect Copilot’s work. Microsoft says specific instructions in a prompt can override personalization settings, and users may need to restate a preference if Copilot does not follow it. That is a polite way of saying the system is advisory, not deterministic.
For casual users, that may be fine. If Copilot creates a chart in the wrong palette, the fix is annoying but not catastrophic. For business users, especially in finance, operations, legal, healthcare, or regulated environments, the difference between “usually follows my preference” and “always enforces policy” is the difference between convenience and control.
This is where administrators should resist the urge to overread the feature. Personalization is not a substitute for templates, data validation, sensitivity labels, document retention policies, protected sheets, or formal review. It is a user-experience improvement, not a compliance framework.
That does not make it unimportant. Many workplace errors begin as small acts of convenience: a copied formula, a manually adjusted date, a merged header, a chart that hides a category, a negative number formatted like a positive one. If Copilot can reduce some of those habits by defaulting to safer preferences, it helps. But the workbook still needs human review, and the organization still needs standards outside the AI prompt box.

---

Cross-Device Sync Makes the Assistant Feel Less Disposable​

One of the stronger parts of Microsoft’s design is that personalization follows the signed-in account across devices. That matters because Microsoft 365 work increasingly moves between desktop Excel, Excel for the web, laptops, tablets, and managed corporate environments. A preference that only worked on one machine would quickly become another local setting to forget.
Account-level sync makes Copilot feel more like part of the user’s working identity. If your default is day-month-year dates, concise explanations, structured references, and simple clustered column charts, those preferences should not disappear because you opened a workbook on a different device. The assistant should travel with you.
This also reflects Microsoft’s broader bet on Microsoft 365 as an identity-bound productivity environment. The file matters, but the signed-in user increasingly defines the experience around the file. Copilot personalization fits that architecture neatly: the workbook remains shareable, while the AI layer adapts to the user.
There is a trade-off. Personal preferences that do not travel with the workbook may surprise users who expect a team-standard behavior. If two analysts ask Copilot to work on the same file, they may receive differently formatted outputs because their assistants are carrying different standing instructions. That is not necessarily wrong, but it is another reason organizations will need to distinguish personal productivity settings from official workbook standards.
The likely future is a layered model. Individuals will have preferences, teams will have templates, and enterprises will want administrative controls that define acceptable boundaries. Microsoft has started with the least controversial layer because it improves the experience without requiring an IT governance war on day one.

Excel’s AI Problem Has Always Been Context​

Copilot in Excel has had a harder job than Copilot in Word or PowerPoint because spreadsheet intent is less visible. A Word document gives the model paragraphs. A slide deck gives it layouts and titles. A spreadsheet gives it cells, and cells can represent raw data, formulas, labels, temporary scratch work, hidden assumptions, or a report meant for the board.
Personalization helps with one kind of context: the user’s preferred output style. It does not automatically solve the deeper context problem of understanding what a workbook means. If a table is poorly structured, if headers are inconsistent, if dates are stored as text, or if business logic lives in undocumented formulas, Copilot still has to infer too much.
That is why the feature is most compelling when paired with clean workbooks. A user who already works with structured tables, named ranges, clear headers, and consistent formatting will get more value from saved preferences because Copilot has a stable surface to operate on. A user whose workbook is a museum of pasted exports and manual fixes may still experience inconsistent results.
There is an uncomfortable lesson here for organizations: AI does not make spreadsheet debt disappear. It can accelerate cleanup, suggest formulas, and produce summaries, but it also exposes the cost of years spent treating Excel as an infinitely forgiving dumping ground. Personalization makes Copilot more pleasant; data discipline makes it more reliable.

The Update Also Admits Prompting Has a Ceiling​

For the last two years, much of the practical advice around office AI has boiled down to better prompting. Be specific. Provide context. Say what format you want. Ask for the output style. Iterate. Correct the model.
That advice is true and exhausting. It turns routine office work into a miniature performance of managerial clarity. Users do not want to brief an assistant on their formatting preferences every time they need a sales summary. They want the assistant to remember.
Copilot personalization is Microsoft conceding that prompt craft should not carry the entire interface. The product needs memory, defaults, and settings, just like every serious productivity tool before it. Nobody expects Excel users to manually explain their regional separators every time they type a number. AI output should move toward the same expectation.
The danger is that Microsoft could still make personalization feel like prompt engineering in disguise. If users must constantly tweak phrasing to get reliable behavior, the feature will become another panel that power users configure and everyone else ignores. The bar is not whether Copilot can store preferences. The bar is whether it follows them often enough that users stop thinking about them.
That bar will be especially high in Excel because formatting errors are visible. A clumsy paragraph in Word can be rewritten. A wrong number format in Excel can quietly change how a reader interprets a report. The assistant’s memory has to be good enough to reduce vigilance, not merely relocate it.

---

Where IT Should Pay Attention Before the Help Desk Tickets Arrive​

For administrators, this update is not a crisis, but it is worth understanding before users start asking why Copilot behaves differently across accounts. Personalization creates a new class of “it works differently for me” reports. The workbook may be identical; the Copilot layer may not be.
That means support teams will need to ask about saved preferences when troubleshooting Copilot output. If a user complains that Copilot keeps rounding values, choosing a particular chart type, using certain colors, or formatting negatives in a specific way, the answer may live in the personalization dialog rather than the workbook. This is a subtle but real shift in diagnostic thinking.
Training materials should also change. Rather than teaching users only how to write better prompts, organizations should teach them which preferences are safe to save and which should remain task-specific. A standing preference for concise explanations is harmless. A standing preference that always rounds outputs may be dangerous in certain analytical workflows.
There is also a governance conversation waiting in the wings. If Microsoft expands personalization into richer behavioral memory, enterprise administrators will want visibility and controls. They may not need to read every user’s preferences, but they will care about data handling, consistency, auditability, and whether AI-generated changes can be traced and reviewed.
For now, the practical advice is simple: treat Copilot personalization as a user-level convenience, not an organizational standard. Encourage users to save preferences that improve readability and reduce cleanup, but keep formal reporting requirements in templates, documented procedures, and governed workflows.

The Feature’s Weak Spot Is Consistency​

The Geeky Gadgets summary notes user reports of occasional inconsistencies, especially around table formatting across devices or workbooks. That caveat is important because personalization features live or die on predictability. A setting that works nine times out of ten is useful; a setting that works unpredictably becomes a new thing to check.
Some inconsistency is expected in an evolving Copilot feature. Excel itself has different surfaces, build channels, license states, and web-versus-desktop behaviors. Microsoft 365 features often roll out gradually, and users in different tenants or update channels may not see identical behavior at the same time.
Still, Microsoft should be careful here. Personalization is a promise of reduced repetition. If users save a preference and then have to verify it manually in every output, the product has not removed friction; it has made friction more passive-aggressive.
The best version of this feature would include clearer feedback. Copilot should be able to explain which saved preferences it applied to a given result, which ones it could not apply, and why. That would turn personalization from a mysterious influence into an inspectable layer of the workflow.
Without that transparency, users are left guessing whether a bad output reflects a vague preference, a workbook limitation, a temporary model failure, or a feature gap. Excel users are accustomed to auditing formulas. They will eventually want to audit AI behavior, too.

Microsoft Is Building Memory One Office App at a Time​

The Excel update fits a broader pattern in Microsoft 365: Copilot is becoming less of a chat window and more of an ambient control layer across apps. The company has already been pushing Copilot deeper into editing workflows, not just Q&A. In Excel, that means building and modifying workbooks with tables, charts, formulas, and PivotTables rather than merely explaining what the data might show.
Personalization is a necessary step in that evolution. An assistant that edits documents and workbooks needs something like taste, and in business software taste usually means defaults, rules, and conventions. The assistant must know not only what it can do, but how the user expects it to do it.
The risk is that Microsoft’s AI layer becomes another sprawling settings universe. Office already has decades of options, some beloved, some buried, some inexplicable. If Copilot personalization expands without discipline, it could become a prompt-shaped version of the old Options dialog: powerful, obscure, and unevenly understood.
But the opportunity is larger. If Microsoft can make user preferences portable, understandable, and governable, Copilot could reduce one of the oldest forms of office waste: the endless reformatting of work that was technically correct but stylistically wrong. That is not the futuristic version of AI. It is the useful one.

---

The Excel Users Who Benefit First Will Be the Ones With Strong Opinions​

This update is most immediately valuable to users who already know what they want. The analyst who hates merged cells, the accountant who cares about negative-number presentation, the project manager who wants concise summaries before detailed tables, and the consultant who uses a consistent chart palette will all get more from personalization than someone who simply asks Copilot to “make this better.”
That is not a flaw. Expert tools often reward explicit preferences. Excel itself has always been more powerful in the hands of users who understand its conventions, shortcuts, and traps.
The difference is that Copilot can now absorb some of those preferences as standing instructions. That lowers the cost of expertise. A user does not need to manually enforce every rule if the assistant can remember part of the rulebook.
The feature may also help newer users learn better habits, provided Microsoft and trainers promote the right examples. “Never merge cells” is a useful preference. “Use readable PivotTable labels” is a useful preference. “Start with a short summary before detailed tables” is a useful preference. These are not just personal quirks; they are patterns that make workbooks easier for other humans to consume.
The more Microsoft frames personalization around clarity, accuracy, and maintainability rather than mere aesthetics, the more valuable it becomes.

The Small Settings That Will Decide Whether This Matters​

This is the kind of Excel update that will not look dramatic in a keynote. There is no cinematic moment in which a spreadsheet builds itself from a sentence and the audience applauds. Instead, the payoff comes in the third week, when Copilot stops making the same formatting choice you always corrected.
That is how productivity software usually improves: not by eliminating work in one leap, but by shaving down repeated annoyances until the tool feels less resistant. Excel’s formatting frustrations are not new, and they are not glamorous. They are just everywhere.
The most concrete implications are straightforward:

• Copilot in Excel can now save user-level personalization preferences that apply across workbooks and signed-in Excel sessions.
• The feature is best suited to recurring preferences such as date formats, currency formats, negative-number display, table styles, chart defaults, PivotTable labels, formula style, and explanation length.
• Personalization affects Copilot’s output for the individual user rather than changing shared workbook defaults for every collaborator.
• Users should keep saved preferences short and specific because vague instructions are more likely to produce inconsistent results.
• Administrators should treat the feature as a productivity aid rather than a policy mechanism, especially for regulated reports or standardized templates.
• The feature’s long-term value depends on whether Copilot applies preferences predictably enough that users can stop repeating themselves.

Microsoft’s Excel Copilot personalization update is not the end of spreadsheet cleanup, and it does not turn AI output into audited truth. But it does move Copilot in the direction office software has always had to go: from flashy capability to reliable habit. If Microsoft can make those habits consistent, transparent, and eventually governable, the most important AI feature in Excel may not be that it can generate more work faster, but that it can finally remember how not to make you fix the same thing twice.

---

References​

1. Primary source: Geeky Gadgets
   Published: Mon, 29 Jun 2026 13:21:38 GMT
   
   

   Microsoft Copilot for Excel Adds Custom Formatting Rules - Geeky Gadgets

   Learn how to customize Copilot in Excel to automatically apply your preferred date formats, table styles, and modern formulas like XLOOKUP.

   www.geeky-gadgets.com
2. Official source: support.microsoft.com
   
   

   Copilot dalam personalisasi Excel | Microsoft Support

   Pelajari cara mempersonalisasi Copilot di Excel untuk mengembalikan hasil berdasarkan preferensi Anda.

   support.microsoft.com
3. Official source: microsoft.com
   
   

   Copilot is now included in Microsoft 365 Personal and Family | Microsoft 365 Blog

   Get access to Copilot with your Microsoft 365 Personal and Family subscription. Learn more.

   www.microsoft.com
4. Official source: learn.microsoft.com
   
   

   Release Notes for Microsoft 365 Copilot | Microsoft Learn

   Lists the features that reach General Availability in each release of Microsoft 365 Copilot.

   learn.microsoft.com
5. Related coverage: office-watch.com
   
   

   Center Across Selection vs Merge & Center in Excel

   There are two similar text formatting options in Excel. The well-known Merge & Center and the hidden away Center across selection. Both have their advant

   office-watch.com
6. Official source: techcommunity.microsoft.com
   
   

   Tag:"copilot in excel" | Microsoft Community Hub

   Find all posts, articles, and events tagged with "copilot in excel" in Microsoft Community Hub. Stay informed with the latest updates from our community

   techcommunity.microsoft.com

Spoiler: Additional references (4)

1. Official source: cdn-dynmedia-1.microsoft.com
   
   

   Slide 1: Using Copilot to Look at Data in Excel

   PDF document

   cdn-dynmedia-1.microsoft.com
2. Related coverage: amanet.org
   
   

   </rdf:Alt> </dc:title> <dc:description> <rdf:Alt> <rdf:li xml:lang="x-default"/> </rdf:Alt> </dc:description> <dc:creator> <rdf:Seq> <rdf:li>Naveen

   </rdf:Alt> </dc:description> <dc:creator> <rdf:Seq> <rdf:li>Naveen Murarka

   www.amanet.org
3. Related coverage: aldridge.com
   
   

   MICROSOFT COPILOT IN EXCEL

   </rdf:Alt> </dc:description> <dc:creator> <rdf:Seq> <rdf:li>Mason Cone

   aldridge.com
4. Related coverage: blacksheepsupport.co.uk
   
   https://blacksheepsupport.co.uk/wp-content/uploads/2023/10/A-Guide-to-Microsoft-365-Copilot.pdf

 

[ChatGPT]

Microsoft’s June 2026 Excel update added Copilot personalization, workbook-level Copilot rules, broader file grounding for commercial users, support for more than 30 additional analysis file types, better PivotTable spill diagnostics, navigable Copilot Chat links, and Insider-only custom Copilot skills across Excel on Windows, Mac, and the web. The headline is not that Excel gained another batch of features. The headline is that Microsoft is turning the spreadsheet from a blank computational canvas into a rules-aware, organization-aware AI workbench. That shift is useful, overdue, and risky in precisely the places where Excel matters most.

Excel’s June Was Really a Copilot Release in Disguise​

Microsoft still calls these Excel features, and technically they are. They live in Excel, affect workbook editing, and change how people build models, summaries, tables, charts, and PivotTables. But June’s update list makes one thing hard to ignore: the center of gravity in Excel development has moved from formulas and grids toward Copilot as the operating layer above them.
That does not mean formulas are dead, or that the spreadsheet has become a chatbot with cells attached. Excel’s durability comes from the fact that it remains both a calculator and a programming environment for people who do not think of themselves as programmers. What Microsoft is doing now is inserting Copilot into that long-standing habit: the user describes intent, and Excel turns that intent into tables, formulas, charts, and analysis.
June’s changes matter because they focus less on raw AI spectacle and more on the mundane irritations that determine whether Copilot survives contact with real work. A model that can generate a plausible variance analysis is impressive once. A model that remembers the house style, respects workbook-specific conventions, reads the right supporting files, and shows exactly where it made changes is the difference between a demo and a workflow.
That distinction is especially important in Excel. Word can tolerate a clumsy paragraph. PowerPoint can survive a mediocre slide draft. Excel, by contrast, punishes ambiguity with silent errors, bad assumptions, and misplaced confidence. If Copilot is going to live in spreadsheets, it needs something closer to operating discipline than conversational charm.

---

Personalization Turns Preferences Into Product Surface​

Copilot personalization is the most user-facing part of the June update, and it sounds deceptively small. Users can define preferences that shape Copilot’s responses across Excel sessions: date formats, currency formatting, preferred chart styles, PivotTable labeling, table conventions, formula style, tone of explanations, and similar working habits. These preferences are saved to the user’s account rather than embedded into each workbook.
That account-level design is the tell. Microsoft is not merely letting users customize one file. It is giving Copilot something like an Excel personality profile, a lightweight memory of how a person wants spreadsheet work to look and sound. For anyone who spends the day cleaning reports, rebuilding recurring models, or producing management packs, that is more than cosmetic.
The old Excel bargain was that the user encoded preferences manually. You set number formats, renamed value fields, adjusted chart colors, cleaned headings, and repeated those moves until muscle memory took over. Personalization aims to move some of that repetition into a standing instruction layer, letting Copilot default toward the user’s usual approach unless a prompt says otherwise.
There is a productivity argument here, but also a governance one. The more Copilot writes or edits workbooks, the more important it becomes that its output not feel like a different analyst touched the file every time. Formatting consistency is not mere vanity in finance, operations, HR, or IT reporting. It is one of the signals people use to decide whether a workbook is trustworthy.
Still, personalization has a ceiling. A user preference is not a policy, and it is not a substitute for review. If someone tells Copilot to prefer rounded numbers, simplified explanations, or a certain chart type, that may improve readability while also hiding nuance. Microsoft’s challenge is to make personalization feel like assistance without letting it become a quiet source of distortion.

Workbook Rules Move the AI Contract Into the File​

If personalization is about the individual, workbook rules are about the artifact. Microsoft’s June update adds the ability to define rules for Copilot in a workbook, documented in a separate .Rules sheet. That sounds like a niche implementation detail, but it may be one of the more consequential Excel changes in the batch.
A workbook is often not just a file. It is a process, a control surface, a recurring report, or a business system pretending to be a document. It may have naming conventions, protected assumptions, helper tabs, staging areas, refresh routines, sign-off cells, and formulas that should not be touched unless someone knows exactly why. Putting Copilot rules inside the workbook acknowledges that context.
This is Microsoft admitting, implicitly, that generic AI behavior is not enough for spreadsheets. A workbook may need Copilot to avoid editing certain sheets, preserve named ranges, use a particular table structure, apply regional formats, or follow departmental reporting conventions. Those instructions should travel with the file, not vanish when a different user opens it.
The .Rules sheet also fits Excel’s culture. Excel users already hide assumptions in tabs, document logic in worksheets, and turn files into self-contained systems. A rules sheet is a natural extension of that habit, even if it will need careful management. It lets the workbook say, in effect: this is how work is done here.
The obvious risk is that a natural-language rules layer becomes another place for ambiguity to hide. If rules are vague, stale, contradictory, or written by someone who does not understand the workbook, Copilot may produce output that appears compliant while drifting from the model’s real intent. In serious environments, workbook rules will need ownership just like macros, Power Query transformations, and protected ranges.

Microsoft Is Giving Copilot More of the Organization to Read​

For commercial customers, June’s update expands how Copilot in Excel can be grounded in work data through a file picker. Microsoft says users can connect Copilot’s analysis to more organizational context, including people, emails, meetings, channels, the web, Loop, and related work material. The company also added support for more than 30 additional file types for analysis, including JSON, XML, GIF, BMP, SVG, SQL, and ASPX.
This is the point where Excel starts to look less like a spreadsheet app and more like a front end for Microsoft 365’s knowledge graph. A user does not just ask Copilot to analyze the table in front of them. They can ask it to reason over the workbook while drawing on a broader universe of supporting material: messages, meeting artifacts, web content, files, and structured or semi-structured data.
That is powerful because Excel has always been the place where outside reality gets flattened into rows and columns. Sales exports, inventory logs, survey results, ticket queues, CSV dumps, SQL extracts, project notes, and finance assumptions all end up in Excel eventually. Microsoft is trying to shorten that path by letting Copilot ingest and connect more of the raw material.
The addition of formats like JSON, XML, and SQL is especially important for IT pros and analysts who live between business users and systems of record. These are not glamorous file types. They are the connective tissue of modern work: API payloads, configuration exports, database snippets, application data, and logs. If Copilot can help turn those into intelligible spreadsheet analysis without a brittle import dance, it will save real time.
But broader grounding also expands the blast radius of mistakes. If Copilot pulls from the wrong meeting, misreads a JSON file, overweights an old email, or interprets a SQL script without understanding the production schema behind it, the resulting spreadsheet may look more authoritative than it deserves. The interface must make provenance visible, not merely promise that more context produces better answers.

---

The PivotTable Spill Fix Is Small, Practical, and Very Excel​

The least flashy June feature may be one of the most recognizably Excel-like. When a PivotTable cannot expand because something is blocking its output range, Excel will collapse the failure into a single #SPILL! error cell. The goal is to make the obstruction easier to diagnose instead of leaving users to hunt across a messy grid.
This is not an AI feature, and that is part of why it matters. Excel remains a dense, physical environment where cells occupy space, tables grow, formulas spill, and output can collide with existing content. Dynamic arrays made Excel more fluid, but they also introduced a class of errors where the problem is not the formula’s logic but the grid’s real estate.
PivotTables are especially vulnerable because users expect them to expand and contract as data changes. A report that worked yesterday can fail today because a refreshed category list is longer, a filter changed, or someone typed notes into what used to be empty space. The resulting obstruction is not conceptually difficult, but it can be maddening to locate.
By collapsing the issue into a focused #SPILL! cell, Microsoft is making Excel’s error behavior more legible. That is the kind of work mature software has to do: not just add capabilities, but reduce the cost of diagnosing failure. In a month dominated by Copilot, this small improvement is a reminder that Excel’s core value still depends on grid mechanics being understandable.
It also shows the difference between intelligence and usability. Copilot may eventually explain why a PivotTable cannot expand, identify the obstructing cells, and offer to move the output. But the spreadsheet itself still needs sane failure states. AI does not remove the need for good application design; it raises the penalty when that design is unclear.

Navigable Copilot Chat Links Address the Trust Problem​

Microsoft also added navigable links in Copilot Chat, allowing users to jump directly to specific changes referenced in a Copilot response. The company marked the feature as feedback-driven, which is not surprising. If Copilot edits a workbook and then describes those edits in prose, users need a fast way to verify what actually changed.
This is one of those features that sounds minor until you imagine the alternative. In a large workbook, “I updated the revenue assumptions and added a trend analysis” is not enough. Which sheet? Which range? Which formulas? Which chart? Which assumptions? The more Copilot does, the more dangerous it becomes for the explanation to be detached from the workbook.
Navigable links are therefore less about convenience than accountability. They make Copilot’s response behave more like a change map, giving the user a path from summary to evidence. That matters because spreadsheet trust is built through inspection. Users do not merely read an answer; they click through the cells, check the formulas, and look for the place where a model’s logic may have bent.
This is also where Microsoft’s Excel AI strategy becomes visibly different from a standalone chatbot. A chatbot can provide an answer and move on. Copilot in Excel has to coexist with the artifact it modifies. Its claims must be anchored in ranges, sheets, charts, tables, and formulas that the user can inspect.
There is still a long way to go. Serious spreadsheet review needs version history, diffing, formula lineage, dependency tracing, and clear separation between suggested and applied changes. Navigable links do not solve all of that. But they are a practical step toward the right model: Copilot should not merely say what it did; it should take users there.

Custom Skills Push Excel Toward Shared Expertise​

Custom Copilot skills for Excel, currently available only to Insiders, are the most ambitious part of the June story. Microsoft has described skills as reusable processes that can encode team expertise for recurring spreadsheet work. In practice, that could mean a finance team defining a discounted cash flow workflow, a monthly variance analysis, a forecast refresh, or a standardized management report routine.
This is where Copilot starts to look less like an assistant and more like an automation substrate. Excel already has several automation layers: formulas, macros, Office Scripts, Power Query, Power Pivot, add-ins, and external integrations. Custom skills appear to sit in a different space, packaging intent and procedure in a way that business teams may be able to reuse without writing traditional code.
That is attractive because much spreadsheet work is repetitive but not simple. A monthly report is rarely just “refresh the data.” It involves checking source files, applying assumptions, cleaning categories, adding commentary, comparing against prior periods, flagging exceptions, and formatting the final output for a specific audience. These are procedural workflows with judgment calls embedded throughout.
If custom skills can capture those steps reliably, Excel becomes a distribution channel for institutional knowledge. New analysts could run processes built by senior teammates. Teams could standardize recurring work without relying on a single macro wizard. Departments could reduce the gap between “the way Sarah does it” and “the way the organization does it.”
The danger is that skill reuse can launder fragile judgment into apparent automation. A bad skill is worse than a bad prompt because it carries the aura of sanctioned process. Insiders testing this feature should be asking uncomfortable questions now: who can create skills, who can approve them, how changes are tracked, how failures are surfaced, and how organizations prevent a library of half-maintained AI procedures from becoming the new macro swamp.

---

Excel’s AI Future Runs Through Governance, Not Demos​

Microsoft’s June update lands at an awkward but important moment for workplace AI. The novelty phase is over. Most organizations have seen enough demos to understand that generative AI can summarize, draft, classify, and transform information. The question now is whether it can do those things inside business-critical workflows without creating new control problems.
Excel is a particularly severe test because it sits at the intersection of productivity and risk. It is used for budgets, forecasts, pricing models, compliance trackers, audits, capacity plans, customer lists, hiring models, incident reviews, and countless unofficial systems that keep organizations running. Many of those files were never designed with enterprise-grade governance in mind, yet they influence enterprise-grade decisions.
That is why Microsoft’s emphasis on rules, grounding, navigability, and reusable skills is more significant than another clever prompt demo. The company appears to understand that Excel users do not only need Copilot to be smarter. They need it to be more predictable. Predictability is what lets admins write guidance, trainers build materials, and teams decide where AI belongs in the workflow.
For IT departments, the administrative questions will come quickly. Which users get these capabilities? Which tenants allow Copilot to ground Excel work in emails, meetings, channels, and web content? How do sensitivity labels, retention policies, data loss prevention, and conditional access interact with these new flows? What happens when Copilot-generated analysis crosses boundaries that humans would have recognized but the model does not?
For spreadsheet owners, the questions are more local but just as important. Which workbooks deserve rules? Which reports should use personalization and which should enforce standardized formatting regardless of user preference? Which Copilot outputs require review before distribution? How should teams document when AI changed formulas, added tables, or generated commentary?
The best organizations will not treat these June features as toys or threats. They will treat them as a new layer of Excel behavior that needs the same discipline they already apply, at least in theory, to macros, external connections, protected sheets, and shared workbooks. The worst organizations will discover, months later, that Copilot made spreadsheet work faster without making spreadsheet accountability any clearer.

The Spreadsheet Is Becoming a Negotiation With an Assistant​

For individual users, the practical experience of Excel is changing in a subtle way. The old model was command-driven: click this, type that, drag here, write a formula, refresh the query, build the chart. The new model is conversational but constrained: tell Copilot what you want, then inspect, correct, and refine what it does.
That changes the skill profile of Excel work. Knowing formulas still matters. Understanding data structure still matters. Knowing when a PivotTable is lying to you still matters. But users will also need to become good at specifying intent, writing durable instructions, maintaining rules, and reviewing AI-generated changes.
This may flatten some barriers for casual users. Someone who understands the business question but lacks advanced Excel technique may get farther with Copilot than they could with formulas alone. That is the optimistic version: Copilot as a bridge between domain knowledge and spreadsheet implementation.
The less comfortable version is that users may accept plausible output too easily. Excel already has a long history of errors caused by hidden rows, broken formulas, copied ranges, stale links, and misunderstood assumptions. Copilot does not eliminate those failure modes. It may add new ones while making the workbook look cleaner.
The June features attempt to reduce that risk by adding memory, rules, grounding, and navigation. But the basic contract remains unchanged: Excel is a tool for calculation and analysis, not an oracle. Copilot can accelerate work, but it cannot assume responsibility for the decision that follows.

The June Update Rewards the Careful and Punishes the Casual​

The most concrete lesson from Microsoft’s June Excel release is that Copilot is becoming more useful in proportion to the structure around it. Personalization works best when users can articulate stable preferences. Workbook rules work best when teams understand their own conventions. File grounding works best when source material is organized and permissions are sane. Navigable links work best when users actually review the changes.
That means the benefits will not be evenly distributed. A well-run finance team with standardized workbooks, clean file storage, and review habits may get real leverage from these updates. A chaotic department with duplicate files, unclear ownership, inconsistent naming, and no model review process may simply give Copilot more ways to inherit the mess.
Excel has always reflected the organization using it. A disciplined team can build durable systems in it. A disorganized team can create an archaeological site of broken links and undocumented assumptions. Copilot does not change that. If anything, it makes the underlying culture more visible.
This is why Microsoft’s steady Excel updates deserve attention from Windows enthusiasts and IT pros, not just spreadsheet specialists. Excel is often where Microsoft 365’s grand platform ideas either become useful or become annoying. If Copilot can earn trust in Excel, it has a stronger claim elsewhere. If it cannot, users will notice quickly.

June’s Excel Release Draws a New Line for Admins and Power Users​

Microsoft’s June feature set is not a single dramatic reinvention of Excel. It is a collection of changes that point in the same direction: more persistent AI behavior, more context, more reusable process, and more need for verification. That makes the update easy to underestimate and risky to ignore.

• Copilot personalization lets users define account-level preferences that shape Excel responses across workbooks and devices.
• Workbook rules let teams document file-specific Copilot instructions in a .Rules sheet, moving some AI guidance into the workbook itself.
• Commercial users can ground Copilot in a broader range of work data, including organizational content such as files, communications, meetings, channels, Loop, and web material.
• Excel can now analyze more than 30 additional file types, making Copilot more useful for semi-structured and technical data sources.
• PivotTable obstruction errors should be easier to diagnose because blocked expansions collapse into a single #SPILL! cell.
• Navigable Copilot Chat links and Insider-only custom skills show Microsoft trying to make AI edits more inspectable and repeatable.

The through-line is clear: Microsoft is trying to make Copilot less like a clever guest in Excel and more like a managed participant in spreadsheet work. That is the right ambition, but it raises the bar for everyone else. Users will need better review habits, admins will need clearer policies, and teams will need to decide which spreadsheet conventions are important enough to teach the machine before the machine starts teaching them back.

---

References​

1. Primary source: Neowin
   Published: 2026-07-01T03:12:07.346712
   
   

   Here are all the new features Microsoft added to Excel in June 2026 | Neowin

   Excel gets a packed June update with smarter AI and long requested improvements that could make everyday spreadsheet work easier.

   www.neowin.net
2. Official source: support.microsoft.com
   
   

   Copilot in Excel personalization | Microsoft Support

   Learn how to personalize Copilot in Excel to return results based on your preferences.

   support.microsoft.com
3. Related coverage: windowsreport.com
   
   

   Copilot in Excel Gets Smarter With Personalized Rules &amp; Shared Workbook Standards

   Copilot in Excel now supports personalization and workbook rules, helping users automate formatting and team standards.

   windowsreport.com
4. Related coverage: windowsforum.com
   
   

   Copilot Excel Personalization &amp; Workbook Rules: Persistent AI Formatting | Windows Forum

   Microsoft has added personalization and workbook-level rules to Copilot in Excel in June 2026, letting users define persistent natural-language instructions...

   windowsforum.com
5. Related coverage: digitaltrends.com
   
   

   Microsoft Copilot can now handle more of your finance work in Excel with reusable skills and data connectors - Digital Trends

   Microsoft added reusable Skills, new financial data connectors, and traceability features to Copilot in Excel, built specifically for finance teams.

   www.digitaltrends.com
6. Official source: learn.microsoft.com
   
   

   Release Notes for Microsoft 365 Copilot | Microsoft Learn

   Lists the features that reach General Availability in each release of Microsoft 365 Copilot.

   learn.microsoft.com

Spoiler: Additional references (6)

1. Related coverage: computerworld.com
   
   

   Microsoft adds new skills — and more oversight — for Copilot in Excel – Computerworld

   The new features, including connectors to third-party data sources, are aimed at making the AI assistant more useful for finance professionals.

   www.computerworld.com
2. Related coverage: windowscentral.com
   
   

   Microsoft Excel Agent Mode: Features, Models, and Availability | Windows Central

   Copilot is graduating from a basic chat interface to a full-blown agent that can autonomously edit workbooks and toggle between GPT-5.2 and Claude 4.5.

   www.windowscentral.com
3. Related coverage: geeky-gadgets.com
   
   

   Microsoft Copilot for Excel Adds Custom Formatting Rules - Geeky Gadgets

   Learn how to customize Copilot in Excel to automatically apply your preferred date formats, table styles, and modern formulas like XLOOKUP.

   www.geeky-gadgets.com
4. Related coverage: supersimple365.com
   
   

   Copilot entry points in Excel are changing - Super Simple 365

   Short VersionExcel&#039;s Copilot entry points are being consolidated into a single location in the bottom-right corner. Due late April to early June 2026. DetailsMicrosoft is updating how you access Copilot in Excel to provide a more consistent experience across Microsoft 365 apps. This change...

   supersimple365.com
5. Official source: cdn-dynmedia-1.microsoft.com
   
   

   Slide 1: Using Copilot to Look at Data in Excel

   PDF document

   cdn-dynmedia-1.microsoft.com
6. Related coverage: techriver.com
   
   

   Microsoft Word - Microsoft O365 November 2025 Updates.docx

   PDF document

   www.techriver.com