A new kind of agent can work alongside your team in Microsoft 365, with its own identity, permissions, and a manager accountable for its work.
Enterprises are all-in on AI agents, but the ROI hasn’t followed. What’s holding those agents back isn’t capability. Today’s agents can do remarkable work on their own. They can start on a bug as soon as it’s assigned, turn a finished design into a working app, learn a task by watching you do it once, and spend the night researching and testing ideas so results are waiting by morning.
The gap shows up when you ask one of those agents to work with your team. Today, unless an agent has an account of its own, the only way it can work in Outlook or Teams is with your permissions. That works for a personal assistant, but it breaks down in two common scenarios:
- No user is signed in. An agent triggered by an event has no signed-in user to act for, so it either can’t take Microsoft 365 actions at all or has to hold on to someone’s credentials to do it.
- Group settings. In a group chat, the agent must guess on whose behalf to act, and there’s no right answer. Whoever it picks, that person’s permissions apply to the whole thread: actions get attributed to someone who didn’t ask, and members can see content they don’t have access to.
So most agents stay single-player: one user, one agent, one private conversation. But enterprise work rarely happens alone. Shipping a feature, launching a campaign, closing a deal, or leading a workstream happens across teams, meetings, documents, channels, SharePoint sites, and group chats. Agents won’t deliver business value until they can work there, safely.
A trusted member of your team
Foundry now lets you build agents that bring that autonomy to the enterprise. Each one works under its own identity as a named member of your organization, in a standing role rather than performing one request at a time.
You may have seen Autopilot in Microsoft 365 Copilot. These agents are the same type: Autopilot comes out of the box, and in Foundry you build your own.
What makes them trustworthy is identity and the governance controls that come with it. Identity is what makes any actor in an enterprise governable, because every action traces back to it. It’s how an organization answers three questions: who took this action, were they authorized to, and can we prove it afterward? An agent you build in Foundry is a member of your organization in the ways that count:
- Its own identity. It acts as itself and never borrows anyone’s credentials. Every Foundry agent has a Microsoft Entra agent identity, and these agents also have an Entra agent user account that lets them perform Microsoft 365 actions as themselves.
- Its own access. You grant it permissions the same way you would a person.
- Its own manager and place in the org. It has an accountable manager, and its spot in the org chart shows everyone who that is. It also has its own email, calendar, OneDrive, and Teams presence, like any colleague.
- Its own audit trail. Every action is attributed to the agent, not to whoever happened to be in the conversation.
Build it once, hire it across your organization
You don’t build this kind of agent directly. You build an agent-as-a-service: a blueprint that people then use to create their own instances. The blueprint is a template that defines what the agent can do, such as the APIs it can call and the MCP tools it can access. You write custom code to shape that behavior, like when it responds, and deploy it as a Foundry hosted agent. Once the published blueprint is approved by an admin, your entire organization benefits: each approved person in your org hires their own instance, with its own identity, agent user account, and access to their resources.
Capability and access are separate
A blueprint never grants access to any specific team’s business resources. Say I build a release captain tailored to my company’s release process. It knows how to update Azure DevOps work items and write to SharePoint, but each manager decides which Azure DevOps project and which SharePoint site their instance can reach.
The benefits of build, the simplicity of buy
Foundry gives you the benefits of building an agent with the simplicity of buying one.
The benefits of building one
- Built for your process. You build a blueprint specific to your company’s business processes.
- You own your IP. Every time your agents work, they create intelligence. The business process your blueprint encodes and the learning loop it builds are both yours.
- Complete control and visibility under the hood. These agents act on their own across your organization, so you get granular control of how they behave, down to whether one responds to a given message.
The simplicity of buying one
Once your blueprint is approved, your whole company can use it as easily as software you bought. It’s hired, governed, and managed exactly like employees, through the same Entra and Agent 365 controls your admins already use.
Built on enterprise primitives, extended for what’s different
What it reuses. Everything above runs on primitives enterprises already manage: Entra for identity, the access controls your admins already use, the places your people already work, and Agent 365 for governance.
What it adds. There’s an important catch. Just because an agent can operate like a user doesn’t mean it has the same incentives, judgment, or failure modes. We gave it a user identity so we could govern it like an employee, not because it is one.
It has no stakes of its own, so the consequences that shape how people behave don’t shape it, and accountability has to sit with the people around it. It doesn’t notice when it’s past what it knows, so it keeps 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 autopilot share the same blind spots and fail together.
That’s why we’ve built controls people never needed. Every one of these agents is an instance of a blueprint, so one kill switch can disable an entire class of agents in one action, and Agent 365 gives you a full control plane for managing your fleet.
Reusing what we have is what lets this scale. Extending it for what’s different is what makes it safe.
This is happening now
Organizations already have these agents in production today. We have seen Autopilots fall into three types, which differ in who they serve.
- Personal: works for one person, as an isolated instance created and used by that person only.
- Team: works for a team. It lives where the team works, holds context the whole team shares, and coordinates across people instead of serving one at a time.
- Organization-wide: provides a centrally managed capability available to everyone in the organization, typically as one production instance per business process.
Nous Research
The Hermes Agent is getting a new capability powered by Microsoft Foundry: it can now work as an AI coworker with its own Microsoft 365 account, managed like any other member of your staff.
Nous Research knows the hard part of bringing agents into an organization today is doing it securely, in a way admins trust. So the idea is simple: each Hermes agent gets its own work account, complete with email, a cloud drive, a calendar, a chat profile, and a manager, and joins the company much as a new hire would. IT governs it with the tools it already uses for staff, and employees work with it as they would any colleague, by sending it a message or sharing a folder. With nothing new to build or learn, adoption takes care of itself.
Companies will soon be able to get Hermes two ways: Hermes Business or Hermes Enterprise. Hermes Business is a SaaS agent that Nous hosts, and Hermes Enterprise is self-hosted in the company’s own Azure tenant as Foundry hosted agents, with a control plane that governs them. Both give every member of a team a self-improving agent, and the skills one agent learns are shared with everyone else’s. To self-host today, you can get started with Nous’s open-source cookbook on GitHub.
“Hermes Enterprise is the agent platform a company can fully own: it writes its own skills as people work, so the know-how compounds inside your tenant. Hosted agents on Microsoft Foundry give that agent its own identity and a place to run around the clock while giving you the freedom to use any model provider.”
Jeffrey Quesnelle, Co-Founder & CTO, Nous Research
Microsoft
An auto-approval path for any Microsoft employee. Because it runs on infrastructure we already trust, any Microsoft employee can build their own agent like this and deploy it inside Microsoft today. If it stays within the bounds we developed with Microsoft IT, it’s approved automatically: no reviews, no waiting.
Meet Office of Amanda, my AI chief of staff, running in production at Microsoft. It takes the follow-ups and coordination off my plate so I can spend my time on the work that needs me. It acts for me, not as me. I give it access to my calendar and mailbox the same way I would a human assistant: through the Exchange delegation permissions that already exist. I can add it to security groups and Microsoft 365 groups, assign it access packages, and share documents with it. When it sends an email, it sends it as itself, under its own identity, with its own audit trail.
Office of Amanda is one of more than 30 blueprints Microsoft employees have already built on Foundry.
What comes next
Giving agents their own identity gets them out of single-player mode and into the places enterprise work actually happens. That’s the first step.
Now we’re also rethinking the work itself. What should agents take on? Where should human judgment stay? And how do humans and agents work as one team? Nobody has the answer yet, but we’re building to find out, and we want you building with us.
Get Started
The post Build trusted autonomous agents for your team with Microsoft Foundry appeared first on Microsoft Foundry Blog.