Pro User
  • All of Microsoft
  • My Role
    • All in My Role
    • Pro User
    • Administrator
  • Focus
    • All in Focus
    • Microsoft Ignite 2026
    • Microsoft Copilot
    • All about AI
    • M365 Admin
    • What's Hot
    • M365 Release
Timespan
explore our new search
Microsoft Autopilot: delegate ongoing work
Microsoft Copilot

Microsoft Autopilot: delegate ongoing work

Microsoft Autopilot lets Frontier customers delegate ongoing work to a proactive digital teammate across Teams, Outlook, and the Copilot app.

Key insights

  • Autopilot is rolling out to public customers in the Frontier program.
  • Users can give Autopilot a long-running goal, such as organizing travel and follow-up.
  • Autopilot has its own identity, mailbox, calendar, and files.
  • Crosscheck auto-approves clear matches to a user's request and escalates ambiguous actions.
  • Payments and other high-impact actions always require approval.

Microsoft Autopilot is a proactive digital teammate that can carry a goal forward across work apps instead of waiting for a prompt at every step. It matters to Microsoft 365 users who need help coordinating ongoing work, such as travel, meeting preparation, and expense tracking. Microsoft Events demonstrates the approach through an end-to-end work scenario and describes the trust controls behind it.

What's new

Autopilot is designed for follow-through: a user sets a broad objective, and the agent breaks it into tasks and continues working as the objective progresses. That differs from a typical chat interaction, where the user asks for an answer or a single action and then needs to prompt again for the next step. The session describes Autopilot as personal, persistent, and proactive.

Personal means it can use context about the user's work and preferences. Persistent means it carries context forward rather than treating every interaction as a fresh start. Proactive means it can take a next step and check in, rather than only returning a response. It also has its own identity, mailbox, calendar, and files, and can appear in Teams, Outlook, and the Copilot app.

In the demonstrated travel scenario, the user gives Autopilot the goal “get me to Ignite and back.” It creates a goal with multiple parts, including travel planning, meeting coordination, preparation, and work coverage. The agent can use the user's stated preferences to offer travel options, send a readiness update, prepare a document, arrange a meeting, and help assemble an expense draft.

Who it is for and what you need

Autopilot is aimed at people who want to delegate connected work rather than just generate text. The examples are relevant to employees coordinating trips, managing a calendar, preparing for meetings, or handling follow-up while away. Colleagues can also interact with an Autopilot in a work setting, as shown when a teammate asks it a question in a Teams channel.

Microsoft is rolling Autopilot out to public customers in its Frontier program. Frontier is an early-access program for emerging Copilot capabilities, so this is not presented as a generally available feature for every Microsoft 365 customer. The session does not identify a specific license or setup requirement; the concrete starting point shown is interacting with an Autopilot in the Copilot app, Teams, or Outlook.

For administrators, the design described is relevant because the agent has its own identity and operates within defined permissions and policy guardrails. The demo also shows the agent using work context and a browser to complete tasks. An organization considering this model should pay attention to what data and capabilities are permitted for its agents, and to how approval and oversight are handled.

How it works

The workflow begins with an outcome, not a detailed sequence of clicks. Autopilot translates that outcome into a longer-running goal, carries out component tasks, and can return to the user for decisions or progress updates. The travel demonstration illustrates one possible pattern:

  1. Give Autopilot a broad goal, such as getting you to a conference and back. It creates a goal made up of related tasks.
  2. Review the work it proposes or the options it prepares. In the example, it uses travel preferences to suggest flights and a hotel.
  3. Continue the conversation through a surface such as the Copilot app or email. The demo shows the user replying to an email from the agent to make a decision.
  4. Let it handle follow-through, such as preparing a trip document, scheduling a dinner invitation, responding to a work question, or drafting expense records.
  5. Review requests that need human input and inspect completed work, such as the expense draft and spreadsheet shown in the scenario.

Crosscheck is the approval mechanism described in the session. Before an action, it compares the action with the user's original request. If the action clearly fits, it can be auto-approved so work continues while the user is away. If intent is unclear, it escalates and asks rather than guessing. Payments and other high-impact actions always require approval, and users can see approvals and provide feedback.

The architecture separates the agent's runtime from the trusted service that manages capabilities, approvals, and requests for data. The session describes the runtime as an untrusted sandbox, with an isolated container for each user and no credentials held inside it. A trusted service brokers access and applies permissions and policy guardrails.

Limitations and alternatives

Autopilot is in Frontier rollout, so organizations should treat it as an early-access capability rather than assume it is available across their environment. Its useful scope also depends on the work context and capabilities it can access. The session's examples rely on calendar, email, Teams, documents, and browser access, but they do not establish that every task can be completed without user involvement.

Autonomy is bounded by Crosscheck: clear matches can proceed, ambiguous actions wait for the user, and payments or high-impact actions always prompt for approval. That is a meaningful distinction from unrestricted automation. For work that should not proceed without a decision, the approval checkpoint remains part of the process.

For a task that does not need persistence or multiple steps, a regular Copilot prompt may be the simpler approach. For an ongoing objective, users should give Autopilot a clear goal and preferences, then review its updates and approvals. This makes it easier to distinguish work it can safely continue from decisions that still need a person.

Sources

Frequently asked questions

Is Microsoft Autopilot generally available?

Microsoft is rolling Autopilot out to public customers in the Frontier program, an early-access program for emerging Copilot capabilities.

Where can users interact with Autopilot?

The session describes Autopilot in Teams, Outlook, and the Copilot app.

How does Autopilot decide when to ask for approval?

Crosscheck compares each action with the user's original request. Clear matches can proceed automatically, while ambiguous actions are escalated; payments and other high-impact actions always require approval.

Does Autopilot have its own identity?

Yes. It has its own identity, mailbox, calendar, and files, and its actions are governed through permissions and policy guardrails.