LectureRechercheRadarCadre d'investissement
Connexion / Inscription
← Retour à la lecture
ActualitésMatériel4 min de lectureRédaction DisconfirmAI

Microsoft Foundry Gives AI Agents Their Own Entra Identity to Work in Team Contexts Without Borrowing Credentials

Microsoft Foundry Technical Program Manager Amanda Foster explains why enterprise AI agents stall in single-player mode: without their own identity, they either cannot act in group chats or must borrow one participant's credentials, leaking permissions. The solution is an Entra agent identity plus an Entra agent user account, provisioned through a blueprint model that lets each approved person hire their own governed instance.

2026-11-20 03:53 GMT+8

Enterprises are all-in on AI agents, but the ROI hasn't followed. Amanda Foster, a Technical Program Manager at Microsoft Foundry, argues that the bottleneck isn't capability — today's agents can solve hard math problems and build operating systems. The bottleneck is that agents cannot work in the places enterprise work actually happens: group chats, shared calendars, team SharePoint sites.

The specific failure mode Foster identifies is credential inheritance. Unless an agent has a Microsoft 365 account of its own, the only way it can act in Outlook or Teams is with a signed-in user's permissions. This breaks in two common scenarios. First, an agent triggered by an event has no signed-in user to act for, so it either cannot take Microsoft 365 actions or must store someone's credentials. Second, in a group chat with many users, the agent must guess on whose behalf to act, and it could pick someone who didn't ask. That person's permissions then apply to the whole thread, and members can see content they don't have access to.

Foundry's answer is to give each agent its own identity as a named member of the organization. Every Foundry agent receives a Microsoft Entra agent identity, and these new agents also receive an Entra agent user account that lets them perform Microsoft 365 actions as themselves. They get their own email, calendar, and OneDrive. You grant them permissions the same way you would a person. They have a manager who is accountable for them, visible in the org chart. Every action is attributed to the agent, not to whoever happened to be in the conversation.

Connexion / Inscription
LectureRechercheRadarCadre d'investissement

The deployment model uses blueprints. You don't build an agent directly; you build a template that defines what the agent can do — which APIs it can call, which MCP tools it can access — and deploy it as a Foundry hosted agent. Once an admin approves the published blueprint, your entire organization benefits: each approved person hires their own instance, with its own identity, agent user account, and access to their resources. The blueprint never grants access to any specific team's business resources; each manager decides which Azure DevOps project or SharePoint site their instance can reach.

Foster draws an important distinction that separates this from treating agents as employees. She notes that giving an agent a user identity lets you govern it like an employee, not because it is one. Agents have no stakes of their own, so the consequences that shape human behavior don't shape them. They don't notice when they're past what they know and keep going confidently where a person would stop and ask. And where a thousand employees make a thousand different mistakes that partly cancel out, a thousand copies of one agent share the same blind spots and fail together. That's why every agent is an instance of a blueprint, so one kill switch can disable an entire class of agents in one action.

The article introduces Hermes Enterprise on Microsoft Foundry as a concrete example. Nous Research's Hermes Agent, which launched in March 2026 and became the top agent on OpenRouter by token usage, can now work as an AI coworker with its own Microsoft 365 account, identity, and access. Each Hermes instance gets its own email, calendar, OneDrive, chat profile, and manager. Coming soon, companies will have two ways to run Hermes: as a SaaS agent hosted by Nous, or self-hosted in their own Azure tenant as Foundry hosted agents with a control plane that governs them.

At Microsoft itself, any employee can build and deploy these agents internally today without a formal IT review, provided the blueprint stays within bounds developed with Microsoft IT. Employees have already built more than 30 blueprints on Foundry. Foster describes two she works with: a personal AI chief of staff that manages her calendar and action items through Exchange delegation permissions, and a team-level workstream manager that collaborates in a Teams group chat, draws on shared context, and manages an Azure DevOps board.

The governance controls are not new systems. These agents are governed with the same tools enterprises already use to manage people: Entra for identity and access, Purview for compliance, and Defender for threat protection. The reusing-what-we-have approach is what lets this scale; extending it for what's different — the kill switch, the shared-blind-spot awareness — is what makes it safe.

Sources

  • devblogs.microsoft.comMicrosoft Foundry Blog↗
Continuer la recherche →