The agents got accounts, the metrics got unlocked
Microsoft spent this week giving agents what employees already have: an account, a memory, a shared knowledge base, and metrics somebody can actually see.
Agents stopped being features
Every item below treats an agent as something you staff rather than something you ship. An identity inside Microsoft 365, context that survives the cycle, a knowledge base it writes to, and usage numbers that no longer sit behind a licence.
Signal of the week
Agent metrics stop needing an Agent 365 licence
Message Center post MC1506727 opens Agent 365 usage and activity insights in the Microsoft 365 admin center to every tenant, regardless of Agent 365 licensing. Active users, total sessions, exception rate and run time, for agents Microsoft built or built on Microsoft platforms. Rollout began late October and completes late November.
Why it matters
I can inventory a client's agent sprawl before asking them to buy the thing that governs it. Check the date carefully: the roundups said late November, the Message Center post says rollout began late October.
1The agents got accounts
Copilot Studio agents get their own Microsoft 365 account
Agent accounts give a Copilot Studio agent its own credentials in Microsoft 365. People invoke it in Teams and Outlook, and @mention it in Word, Excel and PowerPoint comments. It calls tools on scoped permissions of its own rather than a maker's. Business process memory carries context between cycles. Rolling out through Frontier.
Why it matters
Attribution is what I care about: actions land on the agent, not whoever built it. Access policies, cost and lifecycle controls are promised for the coming months, so I would pilot one process rather than ten.
2Somewhere to put what they learn
A team knowledge base that Copilot writes
Copilot and agents can create, curate and reference a shared knowledge base stored in SharePoint, on any site including those behind Teams channels and Microsoft 365 Groups. Copilot in SharePoint and Autopilot in the Copilot app both reach it, and you can use it from Teams or by emailing your Autopilot. Frontier preview.
Why it matters
Shared memory a team can read and correct beats a per-user store nobody can inspect. I do not know yet how it behaves when two people curate the same page.
Agent Framework for Python gets vector stores
Vector store support lands in Agent Framework for Python, ported from Semantic Kernel: typed records, collections, batch upsert, embedding generation and vector search. The addition that earns attention is context providers, which hand a collection to an agent as tools or keep conversation history searchable without growing the context window.
Why it matters
Retrieval you no longer bolt on yourself. The APIs are still experimental and the integration packages alpha or beta, so I would build against this in a branch rather than a client deadline.
3And a badge for the people running them
An Expert certification for agentic DevOps
Microsoft Certified: Agentic DevOps Engineer Expert is live, with Exam AZ-401 in beta. It covers weaving AI assistance into continuous integration, delivery and monitoring, and expects YAML, KQL and Bicep across Azure DevOps and GitHub. The first 300 candidates who sit it by 2 November get 80% off.
Why it matters
Microsoft putting this at Expert level tells me where it thinks DevOps hiring goes next. The discount is the reason to move now instead of waiting for December.
4Also this week
- QuickSkills reach Microsoft 365 Copilot Chat: users create and share them, admins deploy or block them, and they work in Cowork.
- QuickDataverse gains a management MCP server that discovers, assembles and deploys MCP servers from one endpoint.
- QuickPower Automate process mining adds object-centric analysis and a Process Intelligence Studio to go with it.
- QuickFrom 4 November any Microsoft Entra user can create agent blueprints, unless an admin sets that control to No.
- QuickA Visio desktop MCP server lets AI clients create, read and update diagrams in natural language, in preview from November.
- QuickAgent 365, Microsoft Foundry and Defender were quiet on the agent surface this week.
Voices to follow
- Microsoft EVP - Copilot, Agents & PlatformCharles Lamanna
Executive Vice President for Copilot, Agents, and Platform at Microsoft. He owns the strategy behind Copilot Studio, Agent 365, and the Power Platform, so when the agent stack's direction shifts, it usually shifts because of a decision his org made.
Microsoft EVP - Copilot, Agents & Platform - Microsoft Partner Director - Foundry Agent ServiceJeff Hollan
Partner Director of Product at Microsoft, leading the Foundry agent platform: Agent Service, the Agent Framework, and the SDKs. The clearest source on how agents actually go from prototype to a hosted production runtime.
Microsoft Partner Director - Foundry Agent Service + Agent Framework - Microsoft Principal Cloud Advocate - Power Platform + agentsDaniel Laskewitz
Principal Cloud Advocate at Microsoft, ex-Power Platform MVP and co-founder of Forward Forever. One of the clearest voices on multi-agent systems and Power Platform governance - the bridge between the maker community and the product teams.
Microsoft Principal Cloud Advocate - Power Platform governance + agents - Copilot Studio MVPLisa Crosbie
6x Microsoft MVP, Practical AI for Business with Copilot and Agents at Barhead. Calm, hands-on voice on production-grade agent design - the one to follow when you want patterns you can ship, not just demo.
6x Microsoft MVP - YouTuber + International Speaker - ~21K followers - Microsoft Software Engineer - CoworkBas Brekelmans
Software Engineer at Microsoft, started the Copilot Cowork project and previously CTO of Copilot Studio. The clearest voice on why Microsoft chose multi-model, MCP, and A2A architecture across the agent stack.
Microsoft Software Engineer, Cowork - ex-CTO Copilot Studio - Microsoft Principal PM - Copilot Studio (Power CAT)Henry Jammes
Principal Program Manager for Copilot Studio on the Power CAT team at Microsoft. Deep on agent-building mechanics, governance, and the release roadmap - a first-party source on what Copilot Studio can actually do.
Microsoft Principal PM - Copilot Studio (Power CAT) - Microsoft Principal Cloud Developer Advocate - AISeth Juarez
Principal Cloud Developer Advocate at Microsoft on AI. One of the most watchable explainers of Foundry, the Agent Framework, and GitHub Copilot for developers - deep technical content that stays accessible.
Microsoft Principal Cloud Developer Advocate - AI - Copilot Studio MVPMikko Koskinen
AI & Copilot Lead at Forward Forever, 20+ years in the Microsoft ecosystem. Hands-on Copilot Studio and Power Platform architect with a strong governance lens - the right voice for scoping CS at enterprise scale.
Microsoft MVP Copilot Studio - AI & Copilot Lead at Forward Forever
Coming up
- 2 November 2026 · AZ-401 beta discount closesfirst 300 candidates.
- 4 November 2026 · Entra agent blueprints open to all userscheck the control.
- Mid-November 2026 · Skills in Copilot Chat completes rolloutworldwide.
- 17-20 November 2026 · Microsoft Ignitethe agent stack's big week.
- Late November 2026 · Agent 365 insights finish rolling outno licence needed.
- December 2026 · AZ-401 reaches general availabilityafter beta rescoring.
This week's question
Agent accounts make an agent a participant with credentials of its own. If it books the meeting, writes the document and @mentions you for the decision, who is the author of that work? I lean towards the process owner, and I am not sure that answer survives an audit.
Get Agentic Weekly in your inbox
Every Monday morning. Unsubscribe any time.