Microsoft began rolling out Copilot Autopilot on 17 November 2026. It is designed to follow work over time, so it can pick up a thread or run a recurring task without someone entering a fresh prompt each time.
For teams already working in Microsoft 365, one practical use is pulling project updates together for a regular review. A team can keep decisions with the project owner while giving the agent a clearly defined job.
Rollout and access
Microsoft is rolling Autopilot out progressively to eligible Frontier customers. Its rollout guide lists a Copilot licence, usage-based billing and required security controls. Check Microsoft’s Frontier requirements.
Header image: AI-generated editorial illustration for ADJ Systems.
What makes Autopilot different
A chat starts when someone makes a request. Microsoft says Autopilot can carry a goal and context across time within an organisation’s Microsoft environment. It can watch Teams channels, follow up on email threads and return to a project days later. Microsoft describes an agent identity, activity logs and controls that let administrators limit or block access.
Those capabilities make the operating rules part of the workflow design. The team should know which conversation or files the agent can use, what it should do when information is missing, and who reviews anything it prepares.
A pilot for weekly project updates
Imagine a small delivery team that writes a Friday progress note. People post updates in a Teams channel, the lead checks a project tracker, and someone chases missing information. Give the agent a narrow goal: compile the changes and identify gaps for the lead to review.
1. Define the inputs
Use one approved Teams channel and one project tracker. Specify a weekly cutoff and require a link back to each update used.
2. Draft and flag gaps
Group updates by project, surface unresolved risks, and draft suggested follow-ups. Put conflicting or missing information in a review list.
3. Keep the lead in charge
The project lead checks the links, confirms sensitive wording and sends the final update. Record what needed correction.
When a fixed workflow fits better
If the job is simply to remind everyone every Thursday at 3 pm, a scheduled rule is straightforward to test and maintain. Agent-based automation earns a closer look when the work involves interpreting varied messages, spotting gaps across several threads or deciding what deserves to be surfaced. A team can use a fixed schedule for the trigger and an agent for the draft if that division makes the results easier to review.
What New Zealand teams can do now
Check Frontier eligibility with the Microsoft 365 administrator and confirm how usage-based billing would apply. While access is being checked, run the process manually for a week and time the reading, writing and follow-up. Agree on one named owner, suitable source material and which actions are reserved for staff.
During a pilot, count missed updates, unsupported claims and unnecessary reminders alongside minutes saved. If follow-ups create more noise than they remove, tighten the scope before expanding access. Keep the results visible to the team so it can see whether the workflow is helping.
