Copilot Studio gets a Microsoft 365 agent identity
Microsoft documents a persistent Microsoft 365 identity for Copilot Studio agents, including an account, mailbox, Teams presence and Office access.
Microsoft documents a persistent Microsoft 365 identity for Copilot Studio agents, including an account, mailbox, Teams presence and Office access.
Agents primarily operated through user, maker or connection identities.
Microsoft documents a dedicated, manageable Microsoft 365 identity for Copilot Studio agents.
Microsoft describes a persistent identity for agents in the Copilot Studio roadmap. Makers can give a Copilot Studio agent its own account that functions as a managed Microsoft 365 identity for shared business processes.
According to the roadmap, that identity can include a dedicated mailbox, Teams presence and Office access. Administrators can control access, policies and how the identity is used. Microsoft lists preview availability from September 2026 and a rollout beginning in November 2026.
This matters for governance because agents can be treated more clearly as technical actors separate from individual user accounts. Identity, permissions, policies and auditability can therefore be managed at an agent-specific level rather than being tied entirely to a person.
AgentenCode does not turn the roadmap entry into a blanket availability claim. Exact use still depends on tenant configuration, rollout phase, region and administrative enablement. The profile therefore records the identity capability primarily as a governance and permission signal.
Primary source
What this update is based on
AgentenCode publishes product changes only after source-first review. The original provider source remains authoritative for current details.
Continue checking
Full context in the Agent Profile.
The profile, trust evidence and history separate documented properties from Unknown.