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.
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.
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.
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:
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.
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.
Microsoft is rolling Autopilot out to public customers in the Frontier program, an early-access program for emerging Copilot capabilities.
The session describes Autopilot in Teams, Outlook, and the Copilot app.
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.
Yes. It has its own identity, mailbox, calendar, and files, and its actions are governed through permissions and policy guardrails.