Microsoft announced a redesigned Copilot yesterday, but the sentence that matters most wasn't in the demo. Autopilot, Microsoft's revamped persistent agent (previously called Scout), "will carry its own identity in the company directory and have specific permissions that users can control." Annie Pearl, the corporate VP running Copilot Product, said in an interview why this is the feature: "It's been very hard for many organizations to bring agents into the enterprise because of security, compliance and governance concerns." Microsoft didn't build Autopilot to be smarter. They built it to have an employee ID.
That's the tell. A chatbot doesn't need a directory entry. A directory entry is what you give something that acts on your systems, holds permissions, and needs to be tracked when it starts, changes scope, or gets shut off. Microsoft just admitted, in product form, that the blocker to enterprise AI adoption was never capability. It was that IT had no way to govern an agent the way it governs a person.
So now agents get an Entra identity, role-based access, the whole apparatus built for humans. Problem solved, according to the press release.
Here's the problem the press release doesn't mention: giving an agent a directory identity doesn't govern it by itself. A directory entry is a hook to hang governance on. Somebody still has to do the governing — decide what permissions a given agent gets on day one, review whether it still needs them ninety days later, and pull the plug when the project ends or the agent starts reaching for data it shouldn't. That's not a feature Microsoft ships. That's a job.
And it's the same job security teams have been failing to staff for human accounts for a decade. Nobody wants to own access review, offboarding, and the audit trail. It's unglamorous, and it's the first budget line cut when things get tight. Now you're not just failing to deprovision the intern who left in June. You're failing to deprovision an agent that can trigger workflows and touch protected APIs at machine speed, with nobody's calendar reminder telling them it's still running.
I'd bet money on what happens next at most companies that adopt Autopilot or a competitor's version of it: IT stands up the directory entry because the product requires it, sets broad permissions because narrow ones slow down the rollout, and never revisits either decision. That's not a hypothetical. It's the exact failure mode security researchers at Token Security have already documented in Copilot Studio, where agents can create their own Entra app registrations and connect to outside services, and autonomous access paths grow faster than identity teams can reliably inventory or review. Microsoft's new directory-identity feature is the fix for the visibility problem. It is not the fix for the staffing problem underneath it — nobody's job is to actually run that governance loop day to day.
This is a hiring gap with a name, and it's not "AI engineer." It's identity and access management, applied to a new class of directory entry that doesn't take vacation, doesn't forget its own permissions, and doesn't stop working at 5pm. If you already have an IAM function, this is a scope expansion for that team, not a reason to leave it alone — agent accounts need the same lifecycle discipline as human ones: provisioned with least privilege, reviewed on a cadence, deprovisioned on a trigger, logged for audit. If you don't have that function staffed for your human accounts today, adding a fleet of agent identities on top of it doesn't create the gap — it just makes the existing gap load-bearing for something that can act faster than a person can notice it's gone wrong.
The org chart question I keep coming back to in this space is "who owns this," and Microsoft just handed every enterprise customer a very concrete version of it: who owns the Autopilot entry in your directory once it's created? If the honest answer is "IT will figure it out when something breaks," that's the req you should be writing this quarter, not next year's. The agents are getting employee IDs. Somebody needs to be the person who actually manages employees.
Sources: Reuters via Investing.com — Microsoft revamps Copilot with code generation, agentic AI tools, BNN Bloomberg — Microsoft revamps Copilot with code generation, agentic AI tools, NHI Mgmt Group (summarizing Token Security research) — Copilot agents expand the NHI governance gap in Microsoft environments
VC5 Consulting staffs the identity and access management roles most companies skip until an audit forces the question — including the lifecycle discipline agent accounts now require. If your directory is about to fill up with entries that don't take a lunch break, let's talk.