AI Agent News/stories/microsoft-foundry-lets-teams-build-autonomous-agents-with-their-own-microsoft.md

Infrastructure

Microsoft Foundry lets teams build autonomous agents with their own Microsoft 365 identities

Microsoft says Foundry now lets developers build agents that get their own Entra agent identity and Microsoft 365 user account, so they can work in Teams group chats and Office apps without a signed-in user. The post describes a blueprint model in which an admin-approved template is hired by each team member as a separate instance with its own access.

Source: devblogs.microsoft.com/foundry/build-trusted-autonomous-agents-for-your-team-with-microsoft-foundry

Foundry agents can hold an Entra agent user account, which gives them their own email, calendar, OneDrive, Teams presence and a place in the organization chart. The post says such agents can act on their own across Microsoft 365 apps such as Outlook, Excel and PowerPoint, including when no one is signed in, and that each has a named manager accountable for its work. Developers build a blueprint that defines the APIs and MCP tools an agent can use, then deploy it as a Foundry hosted agent. After an admin approves the blueprint, each person in the organization creates their own instance, and managers decide which projects and sites that instance can reach. Microsoft also says one kill switch can disable every instance of a blueprint. Nous Research is using Foundry for its Hermes Agent, which will be offered as Hermes Business, a SaaS product Nous hosts, and Hermes Enterprise, which is self-hosted in a company's Azure tenant. Microsoft says more than 30 custom blueprints built in Foundry are already in use by its employees.

Why it matters if you build agents

Agents that need to act without a signed-in user, or in group chats, can now have their own identity and permissions rather than borrowing a person's credentials, which makes their actions attributable in audit logs.

Teams building on this model should plan for per-instance access grants, manager assignment and admin approval of blueprints before rollout. The post also warns that agents can keep going past what they know, and that agents sharing one blueprint can fail together.

Get stories like this every weekday

One short email with the day's agent tooling news.

Subscribe