Copilot Autopilot needs a permissions check first

Autopilot is Microsoft's new name for the Copilot agent once called Scout, and it is built to keep working on a task after you log off, tagged into a project chat the way you would tag a coworker. Microsoft folded it into a bigger Copilot relaunch today, alongside a coding tool, a unified home screen, and a feature that pulls updates from your Microsoft 365 data without being asked.

CEO Satya Nadella described the release as a new operating system for work, not just another Copilot update. The bundle brings four pieces together. Home merges the Chat and Cowork modes into one starting screen. Office puts Word, Excel, and PowerPoint directly inside Copilot. Code is a GitHub Copilot powered tool that builds apps, trackers, and automations from a plain language description. Autopilot is the long running agent. A fifth piece, Today, proactively surfaces information from across your Microsoft 365 data onto that home screen.

What actually ships and when

• Home and Code roll out over the coming weeks through Microsoft's Frontier early access program
• Autopilot moves to private preview at the end of September
• Code runs hosted inside your own company tenant, not a shared environment
• Code and Autopilot are billed on usage, based on the scope and complexity of each task, not a flat per seat price

Where Copilot Autopilot needs access

An agent that keeps running after you log off and gets tagged into a chat needs standing permission to read, and likely write, across whatever it touches: email threads, shared files, chat history, and any app you have connected to Microsoft 365. That is a wider and steadier form of access than a chat window you only use when you actively type into it. For a small business, that means the decision to enable Autopilot is a data access decision first and a productivity decision second.

1. 1

   Audit before preview

   Before Autopilot reaches your account, check what it would inherit from your existing Microsoft 365 Copilot license: which mailboxes, drives, and connected apps it can already see.

2. 2

   Set a usage ceiling

   Since Code and Autopilot bill by task scope and complexity, set a spending alert or hard cap in the admin center before anyone assigns either tool real work.

3. 3

   Decide who can tag it in

   Treat Autopilot like a new hire with undefined boundaries. Limit at the start which chats and files it can be added to, then widen once you have seen what it actually does with a task.

4. 4

   Pilot on something low stakes

   Give it a task with a visible outcome and an easy human check, not something touching invoicing, payroll, or client contracts on day one.

The billing catch: usage based, not per seat

Most of what a small business budgets for Microsoft 365 is predictable: a flat price per seat, per month. Code and Autopilot break that pattern. A task that touches more files, runs longer, or loops through more steps will simply cost more, and neither tool publishes a flat rate yet. Until Microsoft shares clearer pricing detail, the safer move is to scope Autopilot's first few tasks narrowly and watch what they actually cost before handing it anything open-ended.

If your business runs client work, invoicing, or scheduling through Microsoft 365, the permissions and billing questions here are worth working through before Autopilot leaves preview. Happy to take a look at your setup and map out what it would actually need access to.