On October 15, 2026, Microsoft announced agent accounts, business-process memory, and triggers for Copilot Studio, saying the features are rolling out through its Frontier program. The account gives an agent its own identity and mailbox; it does not automatically authorize every connected tool. Microsoft’s announcement and account documentation describe a preview with specific setup requirements and operational limits.
An agent account is an identity, not a blank check
An account-based agent gets its own Microsoft Entra ID identity, mailbox, and Microsoft 365 presence after publication. Makers still have to configure the permissions for each tool; a tool acting as an end user may also require that person’s authentication and consent.
Microsoft’s preview documentation sets further boundaries: account-based agents cannot respond to people outside their tenant or read documents protected by labels such as “Confidential” or “Internal Only.” They can generate new documents, but cannot make targeted edits to or co-author existing ones. Email responses are limited to conversations within the tenant with up to 250 people.
What publishing an account-based agent requires
The preview requires an early-release-cycle environment, administrator activation of the Copilot Studio agent template and account setting, and a tenant enrolled in Frontier. Makers must have Microsoft 365 E5 with the Microsoft Agent 365 add-on or Microsoft 365 E7. Each published agent account also needs an available Microsoft 365 Frontier for AI Teammates license.
Usage-based billing applies to building, using, testing, and evaluating agents, and those activities may consume Copilot Credits. The required account license and metered usage make licensing and permissions separate pieces of deployment planning.
Memory depends on the configuration
Memory for an agent with its own account is shared among the people who work with it. Microsoft says this preview has no user privacy boundary for that memory and no option to opt out. Its separate general memory documentation describes a different setup: a private store for each user, which makers can enable or disable per agent.
| Memory configuration | Who can access it | Controls |
| Account-based agent | Shared among people who work with the agent | No user privacy boundary or opt-out in the preview |
| General agent memory | A separate private store for each user | Makers can toggle memory; users can review or delete their memories |
For general per-user memory, Microsoft says a user’s memories are deleted after 28 days without interaction. Turning memory off does not itself delete stored memories. That retention rule applies to the general memory feature, not the shared memory described for account-based agents.
Triggers can start a cycle without another prompt
Microsoft says a configured external signal, such as an email, or a set cadence can start an agent cycle without a new prompt. The trigger starts the cycle; the agent’s access to tools still depends on configured permissions.
Microsoft identifies Ooredoo Qatar as an early customer using a Copilot Studio agent across Outlook, Teams, and Word to review business cases, apply company policies and precedents, and prepare briefs for executive review. Microsoft also described agent refinements and use of an agent’s own browser-enabled cloud computer as future plans in its October 15 announcement.
