Copilot in Excel Collaborative Workbooks: Edit Tracking Gaps

Microsoft has turned Copilot in Excel from a chat-based advisor into a tool that edits workbooks directly. For anyone relying on Copilot in Excel collaborative workbooks, that shift, paired with a set of new controls meant to make those edits visible, is what changed, according to Microsoft's Excel blog, published in April 2026.

Some of what Microsoft has published documents that visibility piece closely. Far less of it addresses a second, separate question: what data Copilot can already reach through permissions a person already holds, quietly, before any editing happens at all.

This article treats those as two distinct questions: what Copilot changed inside a workbook, and what Copilot can see because of access that predates it. That split is this article's organizing frame, not a distinction Microsoft draws in its own materials.

Native edits arrive inside Microsoft Copilot for Excel

Excel now shows a Chat/Edit switcher above the prompt box. "Chat only" limits Copilot to answering questions and offering suggestions without changing the file; "Allow editing" lets it create content, apply formatting, build formulas, and make native edits directly in the workbook, per Microsoft's Excel blog. Allow editing is turned on by default for many users who already have Copilot access, the same post notes.

The update also lets Copilot use Python from inside the workbook, either at a user's request or when Copilot judges it useful for the task, Microsoft says. Copilot can apply Python-powered techniques as part of an edit, transforming data and generating charts without a detour to a separate tool.

Paired with editing, Microsoft introduced Plan Mode. Before Copilot changes anything, it lays out the steps it intends to take, including which data or capabilities it plans to use, so a user can review or adjust the plan first, according to the same post. During a Copilot turn, Copilot also highlights affected cells on the grid and marks changed sheets with a green tab; those visual cues persist while the turn is active and clear once the user is done.

Plan Mode's rollout: in development, no confirmed GA

A Message Center posting from two weeks before the blog announcement listed Plan Mode as "in development" for Current Channel on Desktop, Mac, and Web, with general availability targeted for May 2026.

That target month has come and gone. The April announcements supplied for this article don't establish whether Plan Mode later reached general availability, or which channels have it now. Microsoft's current Message Center feed is the best place to verify tenant-specific status, though nothing in the reviewed research confirms that feed as authoritative beyond ordinary practice.

Can you see what Copilot changed?

Microsoft presents the plan and the grid highlights as ways to review and understand edits during a Copilot interaction, per the Excel blog. Those cues exist while a session is active, which raises an obvious follow-up: active for whom, and for how long.

Microsoft's published material does not say whether version history labels Copilot edits separately from a person's own changes. It also doesn't explain how the highlights behave when more than one person edits the workbook simultaneously, whether a coauthor sitting in a different cell sees the same green tab, or how any of it interacts with existing comment and approval workflows. Microsoft's April announcement describes visibility for the user running Copilot; it does not explain what coauthors see.

It helps to be specific about what "visibility" could mean here, because the term covers several different things with very different staying power. A temporary visual cue, the kind Excel now shows, is an in-session prompt that disappears once the work is finished. Ordinary workbook version history is a separate mechanism that typically records who saved a file and when, independent of any AI involvement. Comments and approval workflows are a manual layer teams add on top, requiring someone to flag and sign off on a change. A formal audit log, the strictest of the four, would tie a specific edit to a specific actor, human or otherwise, in a record that persists after everyone has closed the file.

Microsoft's April materials describe the first item on that list. The reviewed research doesn't say whether Copilot's edits register in the second or third, and it says nothing about the fourth. That's a gap in the available documentation, not evidence the gap can't be closed.

Can Copilot surface data you forgot you had?

Microsoft confirms one piece of this directly: if an organization turns off connected experiences that analyze content, Copilot becomes unavailable in Excel specifically, meaning the privacy control and the product feature run through the same switch, according to Microsoft Learn. Microsoft also states that under Enterprise Data Protection, tenant prompts and responses aren't used to train its foundation models and stay within the Microsoft 365 compliance boundary, per the same source.

The sharper argument about permissions comes from a security vendor, not Microsoft. Strac says Microsoft 365 Copilot is grounded through Microsoft Graph and argues that, in principle, its context can include files a signed-in user already has permission to open: old SharePoint files, "anyone with the link" shares, folders nobody locked down, Strac writes. Strac says Copilot does not grant new access; it removes the friction that used to keep forgotten or overshared files practically invisible.

That's a vendor's analysis of how a permission-aware AI tool behaves inside a tenant, not an audited finding, and the Microsoft materials reviewed for this piece don't make that claim themselves. Strac frames the resulting risk as a governance failure rather than a security breach, since every permission check technically passes, and recommends discovering and remediating overshared files before turning Copilot loose rather than after.

None of Microsoft's edit-visibility work, Plan Mode included, was built to answer this question. It concerns tenant-wide file permissions that predate Copilot, and a green tab on a modified sheet has no bearing on them.

What Excel Copilot collaboration features don't touch

Microsoft says Copilot chat experiences in Word, Excel, and PowerPoint vary by tenant configuration and license, according to Microsoft Learn. The April feature announcement and the Message Center entry don't establish identical availability for every tenant, channel, or platform, so administrators should verify Edit mode and Plan Mode separately rather than assuming one covers the other.

Licensing adds another layer worth separating out. Copilot Chat, the web-facing version that pulls from the open internet, comes automatically with an eligible Microsoft 365 subscription at no extra cost. Work-based chat, the version grounded in a tenant's own files and permissions, requires a Microsoft Copilot license, according to Microsoft's licensing documentation. The editing and Plan Mode features described in this article sit on the work-based side of that line, so having "Copilot" turned on somewhere in a tenant doesn't guarantee an individual user has these capabilities in Excel.

For Copilot shared Excel workbooks specifically, that variability compounds the permissions question already outlined above: two people in the same organization may see different Copilot behavior in the same file, for reasons that have nothing to do with the workbook itself.

What to watch next

The open items are specific enough to track. Whether Copilot's edits eventually appear in Excel or Microsoft 365 version history, whether Plan Mode reaches general availability across desktop, Mac, and web on schedule, and whether Microsoft or an administrator publishes anything showing these controls actually reduce errors or disputes in shared workbooks are all things worth checking back on, not conclusions this reporting can draw.

What's already documented is narrower than the feature announcement might suggest. Microsoft has built a switch for direct edits and temporary indicators tied to a single active session. It hasn't, in the materials reviewed, documented how those indicators become a durable record once a coauthor logs off, or how they interact with permissions that were set long before Copilot arrived. Until that documentation exists, treating the current controls as a review step for one person's session, rather than a governance system for a shared file, is the more accurate reading of what Microsoft has actually shipped.