Lyron
Airbus cockpit at night with glowing instruments above the horizon, representing autopilot under human control
Practical Guide

The New Microsoft Copilot: What Autopilot, Code and Usage-Based Billing Mean for SMEs

·8 min read
By Editorial quality standard

On September 25, 2026, Microsoft fundamentally rebuilt Copilot: a chat window becomes a workspace with Office apps, an app builder and an agent that keeps working on its own. For SMEs on Microsoft 365, the key news is not the technology, though – it is the question of who gives that agent which permissions and which budget.

In brief

  • Four building blocks in one app: Home (Chat and Cowork), Office in Copilot, Code and Autopilot are meant to become the central surface for work in Microsoft 365.
  • Autopilot is the real leap: A persistent agent with its own identity, memory and workspace inside the tenant, reachable via @mention in Teams and Outlook.
  • Two billing models: The per-user license covers chat and Copilot in the Office apps; Cowork, Code, Autopilot and frontier models run on usage-based billing.
  • No mass launch yet: Home and Code start in the Frontier early-access program; Autopilot expands its private preview at the end of September.
  • Preparing now pays off: Data permissions, a cost limit, plugin approvals and a clearly scoped pilot process decide whether the start stays under control.

What Microsoft announced on September 25

On the official Microsoft blog, Jared Spataro introduced the new Copilot with Home, Code and Autopilot. CEO Satya Nadella called it a “new OS for work” on X. The scale is significant: according to GeekWire, Microsoft counted around 30 million paid Microsoft 365 Copilot seats in July 2026. The redesign aims to shift usage from occasional chat to delegated, longer-running work.

Building blockWhat it doesStatus on Sep 26, 2026
HomeStarting point with Chat for quick questions and Cowork for complex, multi-step tasks such as proposals or briefingsRolling out to the Frontier program in the coming weeks
Office in CopilotWord, Excel and PowerPoint directly inside Copilot – documents are created and changed without switching appsRolling out to Frontier customers in the coming weeks
CodeBuilds widgets, interactive dashboards and internal apps from a description; based on GitHub Copilot technology, runs in a sandbox and can be hosted in your own tenantFrontier from the end of September, broad availability in the following weeks
AutopilotPersistent “digital teammate” with a name, role and goal; monitors channels, manages workflows and follows up – previously known as ScoutExpanded private preview from the end of September
TodayProactive daily overview across mail, calendar, Teams and tasks with pre-drafted responsesPrivate preview in October 2026

Admin building blocks come on top: a plugin registry that lets IT approve Microsoft, partner and custom plugins centrally, plus Fabric IQ, Dynamics 365 and Power Platform as data sources. Microsoft promises more details at Ignite, November 17–20, 2026.

Two billing models: license plus usage

Perhaps the most consequential change concerns the budget. Microsoft separates everyday AI from agentic work and bills them differently.

BillingWhat is includedWhat SMEs should settle
Per-user license (fixed)Copilot Chat plus Copilot in Word, Excel, PowerPoint, Outlook and Teams; model choice with automatic routingWho really needs a license – and for what?
Usage-based (variable)Cowork, Code, Autopilot and the newest frontier modelsWho may enable it, what monthly limit applies, who reviews consumption?

According to GeekWire, usage-based billing is off by default; administrators can set spending limits through Agent 365 management. Microsoft did not publish per-task prices in the announcement. That is exactly why the cost question belongs before the first pilot, not in the first monthly invoice.

Autopilot: a digital colleague needs a job profile

An agent that keeps working without being prompted again is useful – and, from an IT perspective, demanding for exactly that reason. Microsoft promises identity, permissions and audit trails inside the tenant. Which tasks an Autopilot may take on is still the company’s decision. Our suggestion: treat every agent like a new position and write a six-field job profile before it starts.

1. Role and goal

Which single task does the agent own, and how is success measured?

2. Data access

Which teams, mailboxes, SharePoint areas and plugins may it read – and which explicitly not?

3. Allowed actions

Drafting, creating tasks, following up: yes. Payments, deletions, external commitments: no.

4. Approvals

Before which steps does a human confirm, for example before any message to customers or suppliers?

5. Cost limit

Which monthly budget applies, and who is notified when the limit is reached?

6. Owner and log

Who is accountable, reviews the log regularly and can stop the agent?

How to widen write access and approvals step by step is covered in our guide to AI agent permissions and approvals for SMEs.

Code: apps by description – and who runs them

Code lowers the barrier for internal tools considerably: a tracker for open quotes, a dashboard built from Excel data, a small approval tool. The question shifts from “Can we build this?” to “Who will still run this tomorrow?”. This overview helps choose the right tool:

RouteFits when …Focus on
Copilot Codea team quickly needs an internal tool on Microsoft 365 dataowner, data sources, tenant hosting and app lifespan
Power Automate or n8nrecurring processes must run reliably across several systemserror paths, monitoring and versioning
SPFx or custom softwarecustomers, partners or many users are affected, or core processes depend on itarchitecture, tests, security and a maintenance agreement

Our roadmap for SharePoint Copilot Apps and SPFx is worth a look too, because many SME use cases end up on SharePoint data.

Where SMEs stand today

The announcement meets a German Mittelstand that is still cautious with AI agents. A YouGov survey commissioned by Alibaba.com and the German e-commerce association bevh among 438 decision-makers from e-commerce and procurement, published on September 24, 2026, makes this clear:

  • Around two thirds use generative AI tools regularly.
  • 24 percent already use agentic AI; among companies with ten or more employees, it is 45 percent.
  • 32 percent name a lack of trust as a barrier, 31 percent an unclear business case.

A well-prepared pilot addresses exactly these two barriers: trust comes from permissions, approvals and logs; the business case comes from one concrete process with a measurable result instead of a blanket rollout for everyone.

The 30-day plan before your first Autopilot

  1. Week 1 – Inventory: Which Copilot licenses exist, who uses them, and which AI tools are already running unplanned in the company?
  2. Week 2 – Data hygiene: Review sharing in SharePoint, Teams and OneDrive. Whatever an employee can see, an agent acting on their behalf can find.
  3. Week 3 – Guardrails: Set a cost limit for usage-based billing, decide on approved plugins and adopt the agent job profile as a template.
  4. Week 4 – One pilot process: Choose a bounded, reversible process, such as internal follow-up on open quotes or pre-sorting supplier documents. Define the success criterion, owner and stop rule in advance.

In parallel: since February 2025, Article 4 of the EU AI Act has required AI literacy among staff working with AI systems. A short training on working with agents therefore belongs in the same plan. Uncontrolled tools are covered in our article on shadow AI in companies.

Frequently asked questions

Is the new Copilot available to every business yet?

No. As of September 26, 2026, Microsoft is rolling out in stages: Home and Code first reach the Frontier early-access program, while Autopilot expands its private preview at the end of September. Broad availability of Code is announced for the following weeks.

How much does Autopilot cost?

Autopilot, Cowork and Code, as well as the newest frontier models, run on usage-based billing. Microsoft did not publish per-task prices in the announcement. According to GeekWire, usage-based billing is off by default and admins can set spending limits.

Is the standard Microsoft 365 Copilot license enough?

For chat and Copilot in Word, Excel, PowerPoint, Outlook and Teams, the per-user license covers everyday work. Agentic work with Cowork, Code and Autopilot adds usage-based billing.

What should SMEs prepare before an Autopilot pilot?

Review access rights in SharePoint, Teams and OneDrive, set a cost limit, define approved plugins and document the agent’s role, goal, allowed actions, approvals and an accountable owner.

Conclusion: guardrails first, then Autopilot

The new Copilot turns Microsoft 365 into a platform where agents do not just answer but keep working. For SMEs, that is a real opportunity, because recurring coordination work happens where the data already lives.

The difference between a helpful digital colleague and an expensive surprise lies in preparation: clean data permissions, a fixed cost limit, approved plugins and a job profile per agent. Use the next four weeks for that, and you can start as soon as the features are broadly available.

Sources and photo credit

Status and review date: September 26, 2026. Features, availability and the billing model come from official Microsoft sources and the linked reporting. The agent job profile, decision matrix and 30-day plan are Lyron’s practical working aids derived from those sources.

Should Copilot start under control in your Microsoft 365?

Lyron reviews data permissions, sets up guardrails for costs and plugins and supports your first agent pilot through to a measurable handover – complemented by Power Automate, n8n or custom software where Copilot alone is not enough. Learn more on our Microsoft 365 page.

Discuss Copilot rollout

Share this article: