noviembre 19, 2026

Microsoft Autopilot, the always-on agent: what was announced at Ignite 2026

Microsoft Autopilot en Ignite 2026

On 17 November 2026, at Microsoft Ignite, Jared Spataro presented the latest wave of Copilot news. Among it, Autopilot began rolling out that same day to customers in the Frontier programme. It is not a chat you ask a question and wait for an answer: Microsoft describes it as a trusted, personal autonomous agent that is always on and works for you. It lives in the organisation’s tenant, has its own identity, memory and tools, and appears where people already work — Teams, Outlook, chats, channels and documents — so it can be mentioned like a colleague.

According to the official announcement, Autopilot can monitor Teams channels, follow up on emails, run recurring jobs and manage a project without waiting for someone to give it another instruction. Microsoft gives the example of setting up and running a complete supplier review process. The user decides what work the agent takes on and can ask it to check in before important actions.

Identity, manager and audit trail

The most relevant part for a company is not the task list but governance. Each Autopilot has its own Microsoft Entra Agent ID and a named manager. IT can limit its access or block it at any time. Sign-ins and actions are logged in its name, giving the security team an audit trail. Microsoft stresses that the agent relies on Work IQ and respects the permissions the organisation already has in place.

At the same event, Microsoft made Home generally available — the Copilot starting point where Chat and Cowork live side by side — along with automatic model routing: Copilot can choose the model and effort for each task, or the organisation can let employees choose OpenAI or Anthropic models according to its policy. Autopilot, the company insists, is not yet for everyone: the initial rollout is limited to Frontier.

What an SME already using Microsoft 365 should consider

Even if you are not in Frontier today, the announcement previews the way of working Microsoft wants to make standard: people and agents sharing inboxes, channels and documents, with a directory identity behind each agent. That requires deciding carefully which processes can be delegated, who the human owner is, what data the agent can see and which actions always require confirmation. Without that policy, an “always-on” agent can become just another user — with too many permissions — inside the company.

It is also worth reviewing licences and spending. Autopilot is presented as tied to Copilot and to intelligence consumption controls; it is not a free extra switched on in every mailbox. Before requesting it, it is worth choosing two or three repetitive processes — following up quotes, reconciliation, internal alerts — and measuring whether the agent really saves time.

At Digitacode we help companies integrate this kind of agent into their processes, not just switch on a feature of the office suite. If you want to design that governance and integration layer, tell us about your case.

Sources