Microsoft Gives Copilot Coding And An Always-On Agent
Microsoft has announced a redesigned Copilot app that can build software and keep working while users are away, bringing AI further into everyday business operations while raising questions about permissions, costs and responsibility when delegated work goes wrong.
What Is Changing?
The new experience brings together Home, Code and Autopilot, covering everything from answering questions and preparing documents to creating applications and managing ongoing tasks.
Home combines Chat, for conversational assistance, with Cowork, which handles delegated tasks involving several steps. For example, users can request a customer briefing or financial reporting package, rather than repeatedly asking the AI to complete each stage separately.
Word, Excel and PowerPoint are also being built into the experience, allowing Copilot to create and update editable files that colleagues can work on together. The aim is to reduce the copying, app switching and repeated explanations that can otherwise interrupt AI-assisted work.
Building Software By Describing It
Code extends that approach to software, allowing employees to describe a tracker, dashboard or internal application in ordinary language and have Copilot build it.
Microsoft is presenting this as a way for people outside software development teams to create tools for particular jobs, saying “Code moves solution-building outside the realm of developers alone.”
For example, a team repeatedly updating a spreadsheet could try building an application that collects information and displays outstanding work. However, creating something that appears to function is only the beginning, because someone still needs to check its calculations, access permissions and behaviour when information is missing or incorrect.
Code uses the same underlying technology as GitHub Copilot, Microsoft’s coding assistant, which remains available for professional developers. It runs in a sandbox, an isolated environment that limits interaction with surrounding systems, and applications can be hosted within an organisation’s Microsoft 365 environment.
What Makes Autopilot Different?
While Code creates tools, Autopilot is intended to continue carrying out work over time, remembering its role and returning to tasks without waiting for another prompt.
Previously called Scout, the agent runs in the cloud with its own identity, memory, computer and workspace. Microsoft says it can follow conversations, carry out recurring work and resume a project days later, with employees interacting through familiar services such as Teams and Outlook.
The company gives supplier reviews as an example, describing an agent that organises schedules, prepares meetings and contacts people for updates. Its promise is that “You set the objective and boundaries”, with the agent handling subsequent work.
It seems Autopilot could actually save employees time by chasing updates and organising work while they are away, but businesses need to be clear about how far it can act on their behalf. For example, an agent asked to collect information for a supplier review should still seek approval before agreeing to a deadline or making a commitment to that supplier.
What Is Available Now?
Microsoft’s latest announcement suggests a phased rollout, rather than immediate access to every capability. Home and Code are entering Microsoft’s Frontier early-access programme, while Autopilot’s private preview expands at the end of September.
Code is also scheduled to reach Microsoft 365 Premium and Pro subscribers in preview later this year. Automatic routing between Chat, Cowork and Code is described as coming soon, so businesses should check their actual access before planning deployments.
Microsoft’s new Copilot Managed Runtime, the infrastructure for hosting generated applications under IT control, is already in preview. Its role is to give organisations a managed place to run these tools as employees become more able to create them.
How Will Businesses Pay?
Microsoft says everyday Copilot use is covered by a subscription, but businesses will be charged according to how much they use Cowork, Code and Autopilot.
This means businesses shouldn’t assume that an existing per-user subscription covers unlimited background activity. For example, an agent repeatedly checking information or pursuing an unsuccessful task could consume resources even when it produces little useful work.
Microsoft is expanding controls for spending policies, approval requests and usage visibility, giving administrators and employees ways to track consumption. Those controls will matter most when budgets are linked to completed work rather than simply to how often people open Copilot.
What Does This Mean For Your Business?
For businesses, a sensible starting point is a repetitive task with clear inputs, a measurable result and limited consequences if something goes wrong. Preparing an internal briefing may be easier to assess than allowing an agent to manage supplier relationships independently. A trial should compare the time saved with the effort needed to review, correct and supervise its work.
Organisations should also decide who owns any applications employees create and who can stop an agent once it starts running. Access should match the task, with human approval before important commitments and records showing what happened. Faster software creation will provide limited value if it leaves behind tools that nobody maintains or understands.
The broader opportunity is to remove routine coordination while preserving accountability. Businesses should expand autonomy only when results show that an agent works reliably within its instructions, rather than assuming that an always-on service deserves always-on permission.
