Microsoft Copilot Studio Launches Agent Accounts: Own Credentials, Shared Business Memory, Auto Triggers

What happened

Microsoft wrote in the blog post that the new Copilot Studio capabilities are meant to build "managed agents that belong to the organization, persist beyond any one individual's role or tenure": working where the process happens, starting when needed, carrying context forward, and improving over time.

Agent accounts let agents work in Microsoft 365 with their own credentials, like any person: they can be invoked in Teams and Outlook, assigned work, and @mentioned in comments in Word, Excel and PowerPoint to join in. Agents collaborate with other agents, tools, apps and services using their own approved credentials and scoped permissions, without borrowing any individual user's or maker's credentials; actions are clearly attributable — which were taken by agents and which by people.

Business process memory lets agents carry user preferences and business-process context into each new cycle: a quirk of the process that one person tells the agent becomes a shared resource for everyone. Triggers in the GitHub Copilot harness keep agents "always on": an external signal such as an email, or a set cadence, automatically starts an agent's cycle. Microsoft also previewed agent refinements (recommending improvements to makers based on activity) and a browser-enabled cloud computer of the agent's own.

The capabilities are rolling out now through the Frontier program. Early customers are already using them: at Ooredoo Qatar, an executive business-case review agent works across Outlook, Teams and Word to review incoming proposals, apply company policy and precedents, and prepare decision-ready briefs for executives.

Key facts

1. Announcement: Oct 15, 2026, Microsoft Copilot Blog
2. Agent accounts: Entra identity, own credentials and scoped permissions — no more borrowing individual or maker credentials; @mentionable in Teams, Outlook, Word, Excel and PowerPoint
3. Business process memory: Carries user preferences and business context across cycles; makers designate which business records and policies are authoritative
4. Triggers: Inside the GitHub Copilot harness; external signals or a set cadence automatically start an agent cycle
5. Rollout: Rolling out now through the Frontier program
6. Governance: Admins can scope access and manage agent lifecycle; more access policies and cost controls coming in the next few months