The Pulse
Microsoft Gives Copilot Studio Agents Their Own Accounts
Microsoft is adding agent accounts and business-process memory to Copilot Studio so organization-managed agents can work across Microsoft 365. The features are rolling out through the Frontier program, while additional administrative contro
AI.info Team · Written with AI ·
“Agent accounts allow agents to work in Microsoft 365 with their own credentials, similar to how any person would.”
Jason Moore, vice president of product, Microsoft Copilot Studio
Microsoft is adding organization-owned accounts and persistent memory to Copilot Studio agents, giving businesses a way to assign shared processes to agents that can continue working between employee interactions. The company announced the features on October 15, describing agents that can operate across Microsoft 365 apps with their own approved credentials rather than relying on an individual employee’s identity.
The announcement positions the accounts as a way to make agents participants in ongoing work, not merely chat windows employees must return to for each task. Microsoft says the features are rolling out through its Frontier program, an early-access program for new capabilities.
Agents can join work in Teams and Office files
Employees will be able to invoke an agent in Teams and Outlook to ask questions, assign work or provide updates. Microsoft says agents can also be mentioned in comments in Word, Excel and PowerPoint, letting teams bring them into documents they already use. A worker can delegate a task through Teams or email and continue with other work while the agent carries it forward.
Agent accounts also give agents credentials and scoped permissions for interacting with other agents, tools, apps and services. Microsoft says actions can then be attributed to the agent rather than to a person whose account it borrowed, while process owners retain control over the agent’s approved scope. The distinction is intended to make it easier for organizations to track which steps people took and which the agents performed.
Memory keeps process context between reviews
Microsoft paired agent accounts with business-process memory and triggers built around the GitHub Copilot harness in Copilot Studio. The company says the combination can let agents carry forward relevant context and start work when needed. Its example is a budget agent that prepares for a weekly review, gathers planning records, compares forecasts with explanations and asks budget owners to clarify changes it cannot account for.
In that scenario, finance staff contribute through Teams or Outlook, while the agent prepares a summary of figures, explanations and unanswered questions. The team—not the agent—decides whether to revise the forecast, seek more information or approve a plan. Microsoft says an early customer, Ooredoo Qatar, is using a Copilot Studio agent across Outlook, Teams and Word to review executive business cases and prepare briefs.
Identity does not remove the need for oversight
Microsoft says administrators can scope access and manage agent lifecycles, but it describes additional policies and controls for access, quality and cost management as planned for the coming months. The announcement also points to a future capability that would let agents use their own browser-enabled cloud computer; Microsoft presents that as upcoming, not part of the features now rolling out.
Those qualifications matter because an account gives an agent a clearer identity, not independent authority to make consequential business decisions. The model Microsoft describes keeps people responsible for approvals while agents handle preparation, follow-up and routine coordination. For now, the practical test is whether organizations can give an agent enough access to keep a process moving while keeping its actions visible and its permissions bounded.