Agents built in Foundry, each with an identity in Entra.
Microsoft Foundry, formerly Azure AI Foundry, is where agents are built and deployed in an Azure tenant, often for use from Microsoft 365 Copilot and Teams. Atlas Bench governs those agents through Entra Agent ID and designs how they reach Jira and Confluence.
Microsoft Foundry is where an Azure estate builds the agents people meet inside Microsoft 365 Copilot and Teams. Each can carry an Entra Agent ID, and that identity is where its access should be granted, reviewed, and taken away.
What it is
Microsoft Foundry, formerly Azure AI Foundry, is Microsoft's platform for building agents on models from several providers and publishing them where people already work: Microsoft 365 Copilot, Teams, and custom applications. An agent that raises a Jira ticket from a Teams thread is a common first project.
Entra Agent ID is what makes that governable. The agent exists in the directory as its own object with an owner, so it can be reviewed, held to Conditional Access, and disabled without touching anyone's personal account.
What it does
An agent is a directory object
Entra Agent ID gives each Foundry agent its own entry, so its permissions sit in the same review as people rather than in an app registration.
Copilot and Teams are the front door
Agents published to Microsoft 365 Copilot and Teams reach users where they already work, which is also where an unscoped agent surprises them most.
Conditional Access reaches agents
Sign-in rules written for people can be extended to agent identities, so the same engine blocks risky agent activity.
Where it fits
L4, agents and automation, governed from L1. The agent is assembled in Foundry, but its identity lives in Entra, and Entra is where its access to Atlassian is granted and withdrawn.
What we do with it
Agent identity in Entra
Owners assigned, permissions scoped, and Conditional Access applied to each agent's Entra Agent ID before it is published.
Copilot workflows into Jira and Confluence
Agents that create and chase Jira work and read Confluence from a Teams conversation, connected through a designed identity.
Reviewing the agent population
A standing review of which agents exist in the tenant, who owns each one, and which have fallen out of use.
Where it earns its place
A Teams-first organization piloting agents
People want to raise and follow up Jira work from chat, and security wants every agent accounted for in Entra.
Agents multiplying across a tenant
Several teams have published agents to Copilot, and nobody can yet list them alongside their owners.
Proof
AI Innovator Finalist, 2026
Atlassian Partner Awards, 2026