Microsoft just shipped its first always-on personal agent. It's called Scout, announced June 2 at Build — the first of a category Microsoft calls Autopilots: agents that work autonomously, with their own identity, on your behalf. It lives in Microsoft 365 — Teams, Outlook, OneDrive, SharePoint — works in the background, unprompted, and remembers how you work. Early access is open now through the Frontier program.

The speed of the supply chain behind it is the real story. Seven months ago Scout's engine, OpenClaw, was a developer's side project. Security researchers spent the spring cataloguing the risks: prompt injection, leaked credentials, malicious third-party skills. NVIDIA hardened it in March. Now Microsoft has wrapped it in enterprise controls — governed Entra identities, Purview labels and DLP enforced in real time, human sign-off on sensitive actions, audit trails. Always-on agents are becoming standard workplace equipment.

What this means inside a bank

Scout does not enable itself. An admin has to enroll in Frontier, configure Intune, sign an attestation, and license it. Notice what that list is missing — a committee decision. At most community banks, one or two people with admin rights stand between the bank and an always-on agent.

And every one of Microsoft's controls enforces your configuration. Sensitivity labels protect nothing if you never deployed them. Approval gates approve everything if nobody defined which actions need one. A lightly governed tenant gets that same light governance — at machine speed, from an actor that never logs off.

A lightly governed tenant gets that same light governance — at machine speed, from an actor that never logs off.

There is no autopilot regulation; April's model-risk update left agentic AI outside its scope. Examiners will still ask: What is it? What can it touch? Who approved it? How fast can you turn it off?

The response fits on one page

  • Posture decided in committee — block, monitor, or pilot — with a revisit date.
  • Agent features on the AI inventory; your core provider's version is coming.
  • Tenant audit: sensitivity labels, DLP, conditional access.
  • Agent identities reviewed like service accounts.
  • AUP updated: agents prepare and recommend; a human approves anything that moves money, touches a customer, or leaves the bank.
  • Vendor file, kill switch, one honest paragraph the board can challenge.

This technology ships first and makes readiness your problem. Banks that write their agent rules now will pilot on their own terms. The ones that don't will end up writing rules for an agent someone already switched on.

Sources

From the Toolkit

The Agentic-AI Guardrail Checklist is in the Toolkit.

The Community Bank AI Governance Toolkit includes an Agentic-AI Guardrail Checklist, an AI inventory with auto-tiering, and the acceptable-use policy language for agents — the documents this readiness plan calls for, ready to edit.

See the Toolkit →

About the author. John Humphrey is the founder of Evenstar Advisory Group and Vice President of Information Technology & Information Security Officer at a community bank, where he owns the bank's AI governance program end to end. He writes about the regulatory and operational realities of running governance inside community institutions.