Bemærk
Adgang til denne side kræver godkendelse. Du kan prøve at logge på eller ændre mapper.
Adgang til denne side kræver godkendelse. Du kan prøve at ændre mapper.
Microsoft Agent 365 is Microsoft's enterprise control plane for AI agents. It treats agents as first-class Microsoft Entra identities through Entra Agent ID. This identity model lets organizations apply authentication, authorization, and lifecycle governance directly to agent identity objects. Agent 365 gives IT teams a single place to observe, govern, and secure every agent across an organization, regardless of where that agent was built or acquired. Microsoft Foundry agents integrate with Agent 365 so organizations can apply consistent identity, security, and lifecycle management policies to agents built in Foundry.
This article explains what Agent 365 provides, how it connects to Foundry, and how data flows between the two platforms. It also explains when you need additional setup for hosted agent telemetry.
Agent 365 core capabilities
Agent 365 is built on five pillars:
| Capability | Description |
|---|---|
| Registry | Provides a complete inventory of all agents in the organization, including agents built in Foundry and Copilot Studio, agents registered by administrators, and shadow agents discovered in the tenant. The registry also tracks ownership details that support governance and attestation workflows. |
| Access control | Brings agents under management and limits access to only required resources by using Microsoft Entra identity-based authorization. Supports role-based and attribute-based access control (RBAC and ABAC), plus risk-based Conditional Access policies. |
| Visualization | Enables organizations to explore connections between agents, people, and data, and to monitor agent behavior and performance in real time. |
| Interoperability | Equips agents with access to Microsoft 365 apps and organizational data so they can participate in real workflows. Agents can also connect to Work IQ for organizational context. |
| Security | Protects agents from threats and vulnerabilities through Microsoft Defender for threat detection and behavior monitoring, and Microsoft Purview for data protection and compliance controls on agent activity and data. |
For the full list of Agent 365 capabilities and prerequisites, see the Agent 365 overview.
With the Entra Agent ID model, organizations can apply governance workflows such as periodic access reviews, lifecycle policies for provisioning and deprovisioning, and owner attestation for high-impact agents.
How Foundry integrates with Agent 365
Foundry and Agent 365 connect in two ways:
Registry sync — Every Foundry agent you publish appears in the Agent 365 registry automatically, giving administrators one inventory of every agent without manual registration.
Autopilots — You create an autopilot blueprint from a Foundry hosted agent. An autopilot acts as itself under its own identity rather than on behalf of a user, because it has an Entra agent user account in addition to the agent identity that every Foundry agent has. You set that identity when you create the agent, not when you publish it. After publishing and administrator approval, the blueprint appears in the Agent 365 registry, and people can hire autopilot instances from it in Microsoft Teams and other Microsoft 365 surfaces. For the identity model, see What is an autopilot in Microsoft Foundry?
For step-by-step instructions, see Quickstart: Build your first autopilot.
Supported agent types
Not all Foundry agent types support the full set of Agent 365 integration features. The following table summarizes current support:
| Agent type | Registry sync | Autopilot publishing | Activity data collection |
|---|---|---|---|
| Prompt agent | ✅ | ❌ | ✅ |
| Hosted agent | ✅ | ✅ | Supported using the Agent 365 SDK |
Hosted agent telemetry export requires explicit configuration in your hosted agent and Microsoft Entra permissions for the Agent 365 observability service. For the procedure, see Grant Agent 365 observability permissions.
Enablement and data collection
Before Foundry can send agent activity data to Agent 365, your organization must complete two steps:
Obtain a license — Your tenant needs at least one Microsoft 365 Copilot license and enrollment in the Frontier preview program. For licensing details and enrollment FAQs, see Agent 365 prerequisites.
Enable Agent 365 and accept terms — A global administrator signs into the Microsoft 365 admin center, and selects which users or groups get access. The administrator is prompted to agree to the terms of service before Agent 365 is activated. For the full walkthrough, see Enable Agent 365.
Both steps are required before any data flows from Foundry to Agent 365, even if the Azure Resource Manager properties on a Foundry resource are set to enabled for Agent 365.
After these steps are complete, agent activity data from Foundry is ingested into the Agent 365 control plane, powering the registry, analytics dashboards, and security features. Logging options are controlled per Foundry resource through the agent365Config resource provider configuration. For details on how logging works and how to opt out, see Configure Agent 365 data collection for Microsoft Foundry.
Note
Even if the logging property is set to enabled on a Foundry resource, no data is ingested unless your tenant has a valid Agent 365 license and the administrator has accepted the Agent 365 terms of service.
Data residency
Microsoft Foundry and Agent 365 follow different data residency models, so data processing and storage might happen across geographic regions.
| Platform | Data residency model |
|---|---|
| Microsoft Foundry | Data residency follows the Azure region you select when creating the Foundry resource. All agent data, model deployments, and logs are stored in the resource region. |
| Microsoft Agent 365 | Data residency follows the storage location of the Microsoft Entra tenant. Agent inventory, analytics, and governance data are stored in the geography associated with the tenant. |
When agent activity data flows from Foundry into Agent 365, it moves from the Azure region-based residency model to the Entra tenant residency model. For workloads with specific data residency requirements, you can opt out individual Foundry resources from Agent 365 data collection while keeping other resources enabled.
This approach lets you restrict data flows where compliance regulations might require it. For details, see Configure Agent 365 data collection for Microsoft Foundry.