AI & Agentic Weekly Update — November 2, 2026

Autopilot (Formerly Scout) Heads to Frontier in November

The biggest agentic storyline heading into November is Autopilot, the always-on, cloud-hosted personal agent that Microsoft first introduced as Scout. Microsoft's October 2026 Copilot roundup describes it as an agent with its own account, mailbox, files, and remote computer, and says it rolls out to the Frontier early-access program in November. Coverage of the September 25 Copilot app relaunch describes Autopilot as an agent you give a name, role, and goal, which then handles recurring work and follow-ups without waiting for prompts, while following the same permission and audit rules as Microsoft 365.

For administrators, the key point is that an agent with its own mailbox, files, and compute behaves like a new identity in your tenant. Identity, licensing, and governance teams should settle policy before anyone enrolls in Frontier, rather than discovering the questions after agents are already running. Some sources also indicate usage may sit behind a spending gate, so cost controls belong in the same conversation.

What to do: Before November Frontier enrollment opens to your users, decide who may use Autopilot, which data it may reach, and who owns its spending policy, and document those rules alongside your existing agent governance.

The New Copilot App: Home, Code, and a Two-Part Pricing Model

The rebuilt Copilot app, announced September 25, opens on three tabs: Home, Code, and Autopilot. Home merges quick Chat with multi-step Cowork tasks, and per the October roundup it reaches worldwide availability in November after a Frontier period. Code lets non-developers describe an app, dashboard, or automation and have Copilot build it in a sandbox, with hosting controlled by IT through Copilot Managed Runtime.

Pricing is split in two. A fixed per-user license covers everyday Chat and Copilot inside the Office apps, while advanced capabilities such as Cowork, Code, and Autopilot use usage-based Copilot Credits on top of that license. Microsoft did not publish credit rates in the announcement, and for enterprise customers usage-based services stay off until an admin sets a spending policy. Cowork itself has required a Copilot license plus usage billing since its June general availability, with no Cowork usage bundled into the license.

What to do: Use Microsoft's Cowork Cost Estimator to model likely credit consumption for a pilot group, and set an explicit spending policy before turning usage-based services on.

Cowork: Governance Catches Up

Copilot Cowork continues to gain depth. The October roundup lists OneNote and Planner support in Cowork (Frontier in October, worldwide in November, with user approval required for changes), Projects for grouping chats, tasks, files, and instructions, and role-based plugins and a task catalog. Microsoft's release notes also show Cowork adoption and impact analytics in the Copilot and Consumption dashboards (October 6), which gives admins a way to see who is actually using it and at what cost.

On the control side, Purview DLP for Cowork is in public preview, letting a single policy cover both Copilot Chat and Cowork. The caveats matter: changes can take up to four hours to apply, sensitive information type and sensitivity label conditions need separate rules, directly uploaded files are not scanned (only typed prompt text), and label-excluded items can still appear in citations. The roundup also conflicts with Microsoft Learn on whether Purview retention policies can preserve Copilot memories, and Learn says they cannot, so verify this in your own tenant rather than assuming.

What to do: Extend your existing Copilot DLP policy to cover Cowork, test the upload and citation gaps with realistic documents, and confirm memory retention behavior before you make any compliance commitments.

Admin-Built MCP Connectors and Work IQ APIs

The October 27 Microsoft 365 Copilot release notes include two items that matter for anyone building on Copilot. Admins can now create and deploy custom Model Context Protocol (MCP) connectors from the Microsoft 365 admin center, surfacing internal data to Copilot across the organization. Separately, Work IQ APIs gained usage-based billing, so developers can invoke Work IQ agents and models without pre-assigned licenses, and a new endpoint lets applications trigger first-party and tenant-defined declarative agents programmatically.

Together these lower the barrier to connecting Copilot to your own systems, but they also widen the surface area an admin must govern. A connector deployed organization-wide can expose data to every Copilot user, and per-request billing means automated callers can generate spend without a license assignment to point at.

What to do: Restrict who may create and deploy MCP connectors, require a review of the data source and permissions for each one, and set billing alerts for any application calling Work IQ APIs.

Copilot Studio: Workflows, Computer Use, and Skills

Per the Copilot Studio what's-new page (last updated October 22, with September as the most recent section), computer use reached general availability in May, letting agents operate web and desktop apps, and a standalone computer-use tools preview adds reusable UI automation with governance and observability. In September, workflows gained an extract node for pulling values and tables from invoices and contracts, and a preview Copilot node that runs a Copilot Chat or Cowork task grounded in the connected user's mail, files, calendar, and chats.

Other recent additions include Dataverse and Azure SQL tables as knowledge sources, reusable skills and per-user memory for agents (June), and an Entra Agent ID created automatically for every new agent (July). We did not find a Copilot Studio entry dated within the past week, so treat this as the current baseline rather than breaking news.

What to do: Review which Copilot Studio agents use computer use or the new Copilot node, confirm each has an owner and an Entra Agent ID, and check the Microsoft 365 roadmap for November Studio changes.

Skills in Copilot Chat Arrive in November

The October roundup says Skills in Copilot Chat arrive in November, allowing users to write skills in plain language and admins to deploy them. For organizations focused on shaping how AI behaves, this is the feature to watch: well-designed skills encode your prompting standards, tone, and process once and make them reusable across the workforce, while ungoverned skills can drift into inconsistent or risky behavior.

Note that Microsoft describes many of these dates as tentative and several features remain in Frontier, Insiders, or public preview, so confirm availability for your tenant before planning around any of them.

What to do: Draft a small library of approved, reviewed skills for common tasks now, and decide who is allowed to publish skills to the wider organization once the feature lands.

Sources

Back to all news