Back to feed

On September 25 Microsoft turned Copilot into one work platform with Home, Code and Autopilot; everyday work stays on a fixed fee while agent work is metered in Copilot Credits.

Copilot Becomes a Work Platform: Home, Code and Metered Agents

Imported to Nodesdaily: (UTC+03:00)
Watch the video — kantan.news
Reading options

Device speech is unavailable in this browser.

Concept lens

Choose a technical term in this view to read its general definition, teaching example and use in the article.

No terms from our glossary were found in this view. The glossary does not cover every term yet.

On September 25 Microsoft rebuilt Copilot and turned the chat box into a work platform. The new structure rests on three capabilities, Home , Code and Autopilot , and Word, Excel and PowerPoint files are now produced as real documents inside Copilot. According to Microsoft, the goal is a single hub where everyone can ask, delegate, build and hand long-running work to an agent. According to Reuters, the company wants to make the assistant a one-stop shop for office workers.

The heart of daily work is the Home screen. Chat answers quick questions while a whole job, an RFP response, a launch kit or a financial close package, goes to the delegation mode called Cowork and comes back finished. Because Office files are born inside Copilot, copy-paste between windows disappears; underneath sits Fabric IQ, fed by more than 20 million semantic models on Power BI. VentureBeat notes that mode-picking will soon vanish too: you state the outcome and Copilot routes the work to Chat, Cowork or Code itself. The Today view, entering private preview in October, gathers mail, calendar and Teams signals and lays the draft written and the schedule proposed in front of you.

A build bench for people who never code

The most unusual piece lets non-developers build their own tools. In Code mode you describe a tracker, dashboard, automation or small internal web app in plain words and Copilot builds it; underneath runs the same technology as GitHub Copilot, but the audience is not developers. Everything is produced in a sandbox, an isolated space where code cannot touch the rest of the system, and the finished product is hosted inside the company's own Microsoft 365 tenant. Neowin reports that this hosting layer is called Copilot Managed Runtime : IT governs it while teams share an app like a Word document and connect it to live data, and third-party tools join the same path through an SDK. Code reaches the Frontier program at the end of September and Microsoft 365 Premium and Pro subscribers as a preview toward year end.

The most talked-about piece is Autopilot , the new name of the Scout concept from June. You give it a name, a role and a goal; it watches channels, follows up on threads, runs recurring work and picks a shelved project back up days later on its own. Microsoft illustrates it with a supplier review: schedule, prep, meetings and stakeholder chasing included. Because the agent is cloud-hosted it keeps working while you are offline, living in the tenant with its own identity, memory, computer and workspace, callable via @mention in Teams and Outlook. According to Microsoft, permissions, audit and governance are enterprise-grade from day one, and the private preview expands at the end of September.

Fixed fee plus metered consumption

On cost, Microsoft built a two-layer model. Everyday work is covered by the fixed-fee user subscription license, USL : Chat, Copilot across Office apps and Auto , the automatic model router, sit inside it; Auto weighs accuracy, speed and cost per request and picks the model itself, with GPT 5.6 and Sonnet on fair use and models like Opus on limited inclusion. In contrast Cowork , Code , Autopilot and frontier models such as Astra and Fable run on consumption-based UBB and burn Copilot Credits . The Microsoft Learn docs put the pay-as-you-go credit at $0.01, with a prepaid P3 plan discounting from 5 percent at 300 thousand credits to 20 percent at 300 million. UBB requires a USL first, and the meter does not run until an admin defines a spending policy in the Microsoft 365 admin center.

Agents that work overnight also meter overnight, so FinOps tooling ships inside the package. Cost management in Agent 365 grows beyond Cowork and Work IQ APIs to cover Code and the Managed Runtime, with Copilot Studio agents joining in October. Admins can cap departments and users, route credit requests into approval workflows and restrict which model families each group may touch; those settings also shape what Auto may select. As VentureBeat highlights, users see their own usage and balances inside Copilot while leaders track which Cowork tasks produce outcomes and decide where to sustain or cut spend.

The rollout is staggered: Home and Office integration reach the Frontier program within weeks, Code lands in Frontier at September's end, Autopilot expands in private preview at month end, and the picture should widen at Ignite on November 17-20. My read: Microsoft is leaving the chatbot race and betting on the enterprise agent platform where identity, permission and billing are solved. As Neowin's roundup hints, the real test is Autopilot: an agent that mails colleagues and chases meetings will print bills instead of value unless tightly bounded, so starting with private preview and limits is the right call.

Visualization: nodesdaily AI

AI commentary

"The real story is not the interface but the billing: organizations that cannot govern the overnight agent's meter will collect bills instead of value. Those who set up FinOps first will win."

AI assessment

The strongest counter-view comes from the transparency camp: autonomous work is welcome, but an IT team that cannot audit on whose behalf and on what data decisions were made will not trust it. The one-stop vision Reuters sketches may backfire on teams already suffering agent fatigue; an @mention in every channel becomes a new flood of notifications. Microsoft promises permissions and audit, yet the promise will be judged against private-preview logs in the field.

The gaps are also clear: no technical detail on the frontier models Astra and Fable, no Turkey pricing, and almost everything carries a Frontier or preview label. VentureBeat's schedule analysis gives two different dates for Code, and the overlap confuses. As Neowin's roundup reminds, what ships by general availability may differ from what was announced, so enterprises should not lock their plans today.

The practical takeaway is threefold: start with one team and a capped pilot; write down who pays the UBB meter up front, or the agent working at night becomes a surprise at month end; measure Cowork output, scale what produces results and shut down what does not. The policy screens in the Microsoft Learn docs are not paperwork but the core of the job. Organizations that start bounded will enter the post-Ignite expansion ready.

Sources

6 links; 2 of them also cited by 3 other stories. Stories sharing a link do not confirm each other; a source's origin is not inferred from how often it is cited.

microsoft copilot · autopilot · ai agents · usl ubb · finops

Follow the topic

Before this story

A short reading order from earlier stories linked to this event by an editor.

Evidence and sources

Review permitted source passages, versions and origins.

KAYNAKLARLA OKU

Bu haberi açalım.

Hesap kontrol ediliyor…