Copilot Studio agents can now hold memory and work without being asked

Microsoft announced on 15 October that Copilot Studio now supports persistent agent accounts and business process memory, letting organisations delegate recurring work to an agent (AI that completes a task with several steps for you, not just one answer) that keeps running even when individual staff members change roles or leave.

What happened

Jason Moore, Vice President of Product at Microsoft Copilot Studio, published details of three new capabilities coming to Copilot Studio.

Agent accounts give an agent its own credentials inside Microsoft 365. The agent can be @mentioned in comments in Word, Excel and PowerPoint, or assigned tasks via Teams and Outlook, the same way you would involve a colleague. Work is attributed to the agent rather than to any individual user, which makes it easier for managers to see what the agent did versus what a person did.

Business process memory lets the agent carry preferences and process context forward from one cycle to the next. If someone on your team tells the agent about an exception or a quirk in a process, that information becomes available to everyone who works with the same agent going forward. You no longer need to re-explain the same background each time you delegate a task.

Microsoft also announced agent refinements, a planned feature that will watch how an agent works over time and suggest improvements to whoever built it. Those suggestions are intended to help convert repeated steps into automations (workflows that run by themselves when something happens) and capture reusable approaches as skills (saved sets of instructions that teach AI to do one job your way). Agent refinements are described as coming in the months ahead, not available now.

Separately, ERP Today reported that Microsoft is bringing 30 Dynamics 365 CRM skills into Copilot Cowork, extending what agents can do inside sales and customer-service processes. The details of those skills are not public yet.

Triggers in the Microsoft Copilot harness are also announced. A trigger means an external signal, such as an incoming email, or a set schedule can start an agent's work automatically, with no manual prompt needed.

What it means for your work

• An agent can now be a named participant in a shared process, not just a chatbot you open separately.
• Context built up over weeks or months stays with the agent, reducing repeated briefing.
• Administrators get new controls to scope what an agent can access and manage its lifecycle.
• Agents can work with other agents using their own approved permissions, without borrowing a staff member's login.
• The 30 Dynamics 365 CRM skills point to deeper coverage for sales and support teams, though details are not yet confirmed from a primary source.

What to do now

1. If your organisation uses Copilot Studio, ask your IT or Microsoft admin whether agent accounts are available on your plan. Rollout timing has not been announced.
2. If your team runs recurring processes in Teams or Outlook, note which ones require someone to re-explain context each time. Those are candidates for business process memory once it reaches you.
3. If you use Dynamics 365 for CRM, watch for the 30 new skills in Copilot Cowork and ask your admin when they will appear in your environment.
4. Register for Microsoft Ignite, scheduled for 17 to 20 November 2026, where more details are likely to be shared.

The features that matter most for day-to-day work are agent accounts and business process memory. Both are announced now, but confirm availability with your admin before planning any process changes around them.