From the field: How agentic AI is reshaping adoption at Microsoft

Microsoft reports that staff in its Europe South region now take up AI agents without being pushed, and that the hard part has moved to governing them.

Microsoft's rollout of its AI assistant, Microsoft 365 Copilot, to over 200,000 staff depended on teaching people to write good prompts, and the gains faded. In an account on Microsoft's own blog about its internal use of AI, Poly Palaiogeorgou describes what changed in the company's Europe South region once agents could take whole tasks. Staff passed agents on from colleague to colleague, and a pilot in Spain sent every idea for a new agent through a triage step first.

• The triage, called Build, Reuse, or Prompt, sends each idea to a better prompt, an existing tool or agent, or a new agent. The report says it reduced duplicated work and made ownership clearer.
• The report says the strongest ideas for agents came from the people closest to the work, rather than from technical teams.
• Every agent at Microsoft must pass five checks before it can be published: service registration, security validation, a privacy assessment, accessibility checks and a responsible-AI review.
• This is Microsoft's account of its own products in use inside the company.

A team that builds agents can publish its approval checks at the start, so that builders know the path to release before they begin. The report says that showing the process early reduced uncertainty, and applying it outside Microsoft is an inference.

Derived by Working Surface from the article. Source line: the harder questions are shifting towards governance, trust, and helping teams navigate a safe path from experimentation to production.

26 September 2026: when agents can finish whole tasks, teams redesign the work, the checks and the roles around them.