Microsoft’s Agentic Push Is Starting to Look Like a Real Operating Model
For the last couple of years, most conversations about AI agents have focused on intelligence: better reasoning, better models, better answers. I think we’re finally reaching the point where that is becoming the less interesting part of the story. If you’re not yet following me on X and LinkedIn, I’ve started building out a daily news summary to share much of the content that I find interesting, and which is applicable to business workers rather than just the IT and dev crowd. On the agentic push, there are three recent Microsoft announcements that, taken together, point to something much more important. Agents are beginning to acquire the basic machinery required to become actual participants in enterprise work.
They’re getting an identity, a repeatable method, and a bill.
That combination changes the conversation. Instead of asking what an agent can generate, we need to start asking what work we are willing to let it perform, what resources it can access, how we know whether it completed that work correctly, and what we are prepared to pay for it.
First, give the agent an identity
Microsoft’s roadmap item 570430 introduces persistent Microsoft 365 identities for Copilot Studio agents. Microsoft describes agents with their own governed Microsoft 365 identity, including a mailbox, Teams presence, and Office access, with administrators able to control their access, policies, and use as first-class entities. General availability is currently targeted for November 2026. (Microsoft 365 Roadmap item 570430)
That may sound like infrastructure plumbing, but I think it represents an important change in how we should think about agents. Microsoft already provides Entra Agent IDs for Copilot Studio agents, bringing identity governance, audit logging, lifecycle management, connector-permission visibility, and Conditional Access into the picture. (Microsoft Learn: Entra Agent IDs for Copilot Studio) A persistent Microsoft 365 identity takes that concept into the collaboration layer. Instead of existing primarily behind somebody’s prompt, an agent can become a recognizable participant in a business process. [learn.microsoft.com]
For governance teams, that should immediately raise familiar questions: What can this identity access? What actions should it be allowed to perform? Who owns it? How is its activity reviewed? And when the process or agent is retired, what happens to that access?
Then give it a repeatable method
The second announcement is Microsoft’s release of 30 prebuilt Dynamics 365 CRM skills in Copilot Cowork, now generally available. Microsoft says the skills span Dynamics 365 Sales, Customer Service, and Customer Insights and work with more than 180 generally available tools across the supported experiences. (Microsoft Dynamics 365 Blog) [microsoft.com]
This is where the distinction between a tool and a skill becomes important. A tool gives the agent something it can work with. A skill gives it a reusable approach to performing work. Microsoft describes scenarios such as developing competitive strategies, investigating deal risks, preparing for reviews, and turning meeting outcomes into proposed CRM records and next actions. (Microsoft Dynamics 365 Blog) [microsoft.com]
That looks much less like smarter chat and much more like codifying work. Personally, I don’t want one enormous, omniscient agent wandering around the tenant with access to everything. I want narrowly defined capabilities that can be tested, governed, improved, and reused. Identity tells us who is doing the work. Skills begin to define how the work should be done.
Finally, give the work a bill
The third piece is the one that will make these discussions much more concrete: consumption. Microsoft describes Copilot Credits as a common currency for usage-based AI capabilities, with consumption depending on the work performed and credits pooled at the tenant level. (Microsoft Copilot Credits Guide) [cdn-dynmed…rosoft.com]
The Sales Development Agent is also scheduled to begin consuming Copilot credits on November 16, 2026. Once agents are performing ongoing work and that activity produces measurable consumption, the economics become part of governance. Someone needs to understand what a successful run looks like, how frequently the agent should operate, when human approval is required, and whether the resulting business value justifies the consumption. [swopi.co]
That is actually healthy. It forces the agent conversation away from novelty and toward operational value.
Treat the first agent like a new process participant
This is why I think governance teams should stop planning agent pilots like chatbot pilots (something I’ll be writing about later this week). Start with one process with a clear owner and measurable outcome. Give the agent a narrow role and the minimum access required to perform it. Define the points where a person must review or approve its work, and establish an acceptable budget for the activity.
Then examine the evidence. What did the agent recommend? What did someone approve? What actually changed? What did the work consume? If those questions are difficult to answer, I would argue that the process isn’t ready for greater autonomy.
Microsoft’s agentic push isn’t interesting simply because AI is getting better at conversation. It’s interesting because agents are acquiring the building blocks of real enterprise work: an identity, a repeatable way to perform a task, and a meter attached to that activity.
That’s an operating model, and governance needs to catch up with it.
