Office moves into Copilot: what is available and what remains in preview after Ignite
Word, Excel and PowerPoint move directly into the Copilot app, but the features presented at Ignite do not all share the same availability: on 17 November Microsoft announces general availability for Home and Office in Copilot while giving other components different timelines and audiences.
The development is more than a chat tool that writes: it is an attempt to keep conversation, file editing and delegated work in one environment.
## From a message to a document, without blurring products
The official presentation says Home brings Chat and Cowork together; Office in Copilot lets people create, edit and coauthor documents with colleagues using Office capabilities.
Microsoft says files inherit Microsoft 365 permissions, sensitivity labels and compliance controls.
That describes the product’s protections; it does not certify that a particular organisation’s configuration is correct.
The operational point is to prevent a convenient interface from displacing review. Before sharing a workbook or presentation, an organisation should check recipients, permissions and content just as it would outside a chat.
A supplier’s general-availability announcement does not, by itself, show that every account holds the same licence or that every feature is enabled in a particular environment.
## The timelines are not interchangeable
Copilot Code is described as reaching general availability in the following weeks; Copilot Managed Runtime, for hosting and managing applications, is announced as generally available.
Autopilot begins rolling out to Frontier customers, while Today, the experience combining activities and priorities, is in private preview in the Copilot app and Outlook.
Saying that everything has arrived would erase those distinctions.
For Autopilot, Microsoft describes a dedicated Entra Agent ID, a named manager, access that IT can limit, and logged actions.
An agent operating within a tenant does not establish that every computation happens on the local computer: the announcement also discusses selecting models from different providers and hybrid Windows capabilities.
We therefore do not attribute a blanket guarantee of entirely local inference to the package.
## Cost claims still need measurement
In his 17 November note, The Verge’s Nilay Patel reports Judson Althoff’s competitive claim and identifies dynamic routing between models as the logic behind the proposition.
Microsoft describes Auto as choosing models and effort according to the task, balancing quality, speed and cost.
This verification has not measured the actual savings for any specific business.
Microsoft distinguishes a per-user subscription from consumption-based access for more demanding work and presents spending-control tools.
An internal trial should therefore compare a repeatable task, a correct outcome and the total cost, rather than assume that integration makes every agent workflow free.
The announcement dates from 17 November, not this morning: at the 18 November cutoff, the useful distinction is between what Microsoft declares generally available, limited rollouts and promises that still need testing in practice.
