By Russell Kommer, CEO of eSoftware Associates (ESW). Last updated October 16, 2026
If you’ve been in r/copilotstudio this week, you’ve seen the reaction. Microsoft says Copilot Studio agents can now get their own Microsoft 365 account, remember how a process works, and start on their own from an email or a schedule. Most of the comments come back to two worries. What does each run cost, and who stops the agent when it runs far more than anyone planned?
Key takeaways
- Autonomous runs of Copilot Studio agents are billed in Copilot Credits, even when users have Microsoft 365 Copilot licenses.
- The schedule is usually the biggest cost decision. A run every 10 minutes is 144 runs a day.
- Set a monthly credit limit with Stop usage on each agent and cap the environment in the Power Platform admin center.
- Turn on Microsoft Purview auditing before the first publish, and review anything that runs on a schedule or sends email.
We’ve been hearing the same thing from IT directors and CFOs all year. An agent that waits for someone to type is easy to budget. One that wakes up every ten minutes is not.
What are autonomous Copilot Studio agents?
They’re agents that start work from an event or a schedule instead of a user prompt. A typical one reads an incoming email or checks a tracker, calls a couple of tools and hands a draft to a person who decides.
Microsoft announced three additions for this kind of work on October 15, 2026. They’re agent accounts, business process memory, and triggers for agents built on the GitHub Copilot harness. They’re rolling out through the Frontier program. Whether your tenant has them today depends on enrollment and licensing.
What does it mean for an agent to have its own identity?
The agent gets its own identity in Microsoft Entra ID, so you can scope and audit its access separately from the person who built it. There are two layers here, and people mix them up all the time.
Every new Copilot Studio agent now gets a Microsoft Entra Agent ID automatically. You can’t opt out anymore. Admins can see which connectors each agent can call and apply Conditional Access to it. Older agents keep their app registrations until someone migrates them.
Agent accounts go further. The agent gets its own Entra account and mailbox, plus Teams presence and a directory entry. It’s a Frontier preview, and you’ll need an early release environment, Microsoft Agent 365 licensing for makers, and a Frontier for AI Teammates license for each agent.
I think this is good for governance, because the work is tied to the agent and not the builder. My concern is what happens once an agent has a mailbox. People will start handing it work nobody scoped.
How does business process memory work, and what’s the risk?
An agent with an account keeps one shared memory across everyone it works with. Context one person explains carries forward for the whole team, and there’s no privacy boundary between users.
Microsoft’s documentation doesn’t soften this. Summaries of files and chats shared with the agent can show up in answers to other users, even users who can’t open the original. You can’t opt out in the preview. And agents with accounts can’t read documents protected by sensitivity labels.
We’d treat the agent’s audience like a distribution list. Keep it to a team that already shares the same access, and write down what people shouldn’t paste into it.
What can trigger an agent to start on its own?
An event or a schedule. Event triggers fire on things like a new email, file or record, and recurrence triggers fire on a set cadence. The new harness triggers work the same way.
Two details catch people. Event triggers currently run on the maker’s credentials, so if the builder can see the whole finance share, so can the agent. Every trigger payload also counts as a message for billing. A recurrence every 10 minutes is 144 runs a day, whether or not there’s anything to do.
How much do Copilot Studio agents cost in Copilot Credits?
Autonomous runs are billed in Copilot Credits, even when every user has a Microsoft 365 Copilot license. That license covers interactive use. It doesn’t cover agents running on their own. Agents built on the GitHub Copilot harness are billed for all usage, building and testing included.
Here are Microsoft’s published rates for standard agents.
| Agent feature | Copilot Credits |
|---|---|
| Generative answer | 2 |
| Agent action (includes triggers and tool calls) | 5 |
| Tenant graph grounding | 10 |
| Agent flow actions, per 100 actions | 13 |
A Copilot Credit pack is 25,000 credits for $200 a month. Unused credits don’t roll over.
This is an illustration from those rates, not a quote. Say each run is a trigger plus two tool calls (three agent actions, 15 credits) and one generative answer (2 credits). That’s 17 credits a run. At every 10 minutes you’re near 73,000 credits a month, close to three packs, for one agent that mostly finds nothing to do. Run it once each morning and it’s about 510. Reasoning models add premium token charges on top of that.
The schedule tends to be the biggest cost decision, and someone makes it in five seconds. Run Microsoft’s agent usage estimator before you build, then check it against real consumption.
How do you keep an agent from running up a surprise bill?
Put a monthly credit limit with a hard stop on each agent, and cap the environment it runs in. You’ll find both in the Power Platform admin center.
- Agent limit. Go to Licensing, Copilot Studio, Manage Agents. Set a monthly limit and an alert, and turn on Stop usage.
- Environment cap. Allocate credits and clear “Draw from the available capacity in my tenant.”
- Pay as you go. Azure budgets alert on spend but won’t stop it, so pair them with agent limits.
- Right size the schedule. Daily is often plenty. Filter triggers down to the records the agent actually needs.
- Name an owner. Someone looks at consumption every week for the first month.
There’s another reason not to put this off. On prepaid capacity, Microsoft disables custom agents once the tenant pool hits 125% of capacity, so one runaway agent can knock out the ones your team depends on.
Who should be allowed to build Copilot Studio agents?
Fewer people than have access today, at least for anything autonomous. The Copilot Studio authors security group grants access under pay as you go, but it doesn’t block users who already hold a Microsoft 365 Copilot or Copilot Studio license.
The controls that actually work are trial settings, environment security roles and sharing limits, along with Microsoft’s zoned governance model. Only users an admin selects can create agent accounts.
Our rule of thumb is simple. Anyone can build a personal agent over content they can already see. If it runs on a schedule, sends email or writes to a system of record, it gets reviewed first.
Plenty of ideas shouldn’t be agents at all, honestly. A one time question is a saved prompt. A fixed set of steps is often a Power Automate cloud flow, which runs on Power Automate licensing instead of Copilot Credits. If people need a screen to work in, a Power Apps solution is often the better fit.
How do you audit what a Copilot Studio agent did?
Turn on Microsoft Purview auditing before the first publish. Purview logs Copilot Studio events like agent creation, deletion, publishing and user interactions, and Agent 365 activity records show when an agent is invoked and when it runs a tool.
Use the agent’s activity page in Copilot Studio too. It lists each trigger and what followed. When something breaks, you’ll want to know which agent acted, under which identity, and what it touched.
Where should you start?
One recurring process with a clear owner and a person who signs off. Not five agents. One.
That’s how we run Copilot work for clients. A construction and industrial group got agents for safety manual questions and contract risk review, grounded on approved content, with people making the calls. On a Dynamics 365 and Copilot Studio pilot for a trade association, the acceptance test was the staff’s own list of 18 real questions. If the agent couldn’t handle those, it wasn’t done.
Frequently Asked Questions About Autonomous Copilot Studio Agents
Do autonomous agents use Copilot Credits if our users have Microsoft 365 Copilot licenses?
Yes. Scheduled runs and event triggered runs are billed in Copilot Credits.
What are Copilot Credits?
Copilot Credits are the billing unit for Copilot Studio agents, including autonomous runs. Microsoft sells packs of 25,000 credits for $200 a month, and unused credits don’t roll over.
Can we cap spending for a single agent?
Yes. Set a monthly limit in the Power Platform admin center and turn on Stop usage.
Is agent identity on by default?
New Copilot Studio agents get a Microsoft Entra Agent ID automatically. Full agent accounts with a mailbox and Teams presence need Frontier enrollment and extra licensing.
Can we stop employees from creating agents?
Mostly. Licensing, trial settings, environment roles and sharing limits do the work. The authors security group on its own won’t block licensed users.
Does shared memory respect file permissions?
Not fully. In the preview, summaries of shared files and chats can appear in answers to users who can’t open the originals.
Are these features generally available?
Agent accounts, business process memory and harness triggers are rolling out through Frontier under preview terms, and availability varies by tenant.
Get the guardrails in before the first agent goes live
ESW has delivered Microsoft 365 work for 1,500+ clients since 2006, and every Copilot engagement we run starts with governance. Our Copilot Studio consulting team sets up identity, maker controls and credit limits, then builds the first scoped agent. Our AI adoption and change management work helps the people who use those agents trust them. Copilot Orbit™ keeps agents tuned and monitored month to month.
If you’re looking at Frontier features now, talk to our team and we’ll go through your tenant settings with you.
About the author. Russell Kommer is CEO of eSoftware Associates (ESW). Since 2006 ESW has worked with 1,500+ clients, delivered 1,000+ projects and trained 10,000+ employees on Microsoft tools.