AI · Sep 27, 2026
Microsoft's new Copilot: Home, Code, and Autopilot explained for small businesses
On September 25, Microsoft announced a new version of Copilot built around three ideas: Home, Code, and Autopilot. If your business runs on Microsoft 365, this is the AI that will show up inside the tools your team already uses, so it is worth understanding before it arrives.
The three new pieces
Home is the new starting point in the Copilot app, where Chat and Cowork come together. Chat is for quick questions and drafts. Cowork is for work you delegate and want returned finished, like a customer briefing or an RFP response. Microsoft also announced Office in Copilot, which creates real, editable Word, Excel, and PowerPoint files from inside the Copilot experience.
Code lets people describe an app, tracker, dashboard, or automation in plain language and have Copilot build it. Microsoft says it runs in a sandboxed environment, can be hosted inside your company's Microsoft 365 tenant, and is powered by the same technology as GitHub Copilot.
Autopilot, previously called Scout, is a persistent agent. You give it a name, a role, and a goal, and it keeps working: watching channels, following up on threads, and running recurring work. Microsoft says it has its own identity, memory, and workspace inside your tenant, with permissions and audit behind it.
Microsoft said Home and Code would roll out through its Frontier early-access program first, with Autopilot moving to private preview at the end of September.
Code is the one to watch
Code is the most interesting piece for small businesses, and the one that needs the most thought.
Microsoft describes small, purpose-built solutions as a new unit of knowledge work, alongside documents, spreadsheets, and decks. That is a real shift. It means someone in your accounting team could build a dashboard, or someone in operations could build a tracker, without a developer.
That is powerful. It is also how you end up with dozens of small apps that nobody documented, connected to live data, and owned by someone who left last spring. Microsoft's answer is that IT governs where these apps run. Someone in your business still has to decide what gets built and who maintains it.
Microsoft is splitting AI spending into two buckets
Buried in the announcement is a pricing change worth understanding. Microsoft describes two types of spend. A per-user subscription covers everyday Copilot use like chat and help inside Office apps. Usage-based billing covers agentic work like Cowork, Code, and Autopilot, along with the most advanced models.
In plain terms, the more your team hands off long-running work to agents, the more your bill depends on usage rather than headcount. Microsoft introduced cost management tools to help admins set limits. Use them.
What this means for your business
- If you use Microsoft 365, these features will reach your team over the coming months. Decide now who is allowed to turn them on.
- Set a simple rule for apps built with Code: who can build, where they live, and who owns each one.
- Expect part of your AI spending to become usage-based. Set spending limits before usage grows, not after the first surprise bill.
- Autopilot-style agents need clear goals and boundaries. Treat setting one up like onboarding a new hire.
Microsoft 365 is the backbone for many of the businesses we work with. If you want help planning how these features roll out, with sensible permissions and spending limits, our Managed IT and AI teams can help.
