New ESW Guide Explains Copilot Studio Agent Pricing and the Controls to Set First
After Microsoft's October 15 preview of autonomous agents in Copilot Studio, ESW explains Copilot agent pricing and
Press Release Disclaimer: This is a press release distributed through the XPR Media network. It has not been independently verified by our newsroom.

![]()
New York, NY, Oct. 19, 2026 (GLOBE NEWSWIRE) — eSoftware Associates Inc. (ESW), a Microsoft 365, Copilot and SharePoint consultancy, has published a guide to Copilot agent pricing and governance, with a focus on autonomous agents in Copilot Studio. The guide follows Microsoft’s October 15, 2026 preview of agent accounts, shared memory and new triggers that let Copilot Studio agents take on more work without a user prompt. The features are in preview through Microsoft’s Frontier program. Agent runs are billed in Copilot Credits, even for organizations that already pay for Microsoft 365 Copilot licenses, so pricing has to be planned before the agent is built.

ESW’s guide to deploying autonomous Copilot Studio agents with cost and governance controls.
What an autonomous Copilot agent costs depends mostly on how often it runs and what it does each time. Under Microsoft’s published list rates as of October 2026, which may change, every trigger counts as a billable agent action, a generative answer uses 2 credits, an agent action uses 5, and reasoning models add premium charges on top. Credit packs are sold at 25,000 credits for $200 a month, and unused credits do not roll over.
In an illustrative example in ESW’s guide, an agent scheduled to run every 10 minutes, with one trigger, two tool calls and one answer per run, would use about 73,000 credits a month, close to three packs. The same agent running once a day would use about 510.
“The schedule tends to be the biggest cost decision, and someone makes it in five seconds,” said Russell Kommer, CEO of ESW. “My concern is what happens once an agent has a mailbox. People will start handing it work nobody scoped.”
The guide recommends that organizations put AI agent governance in place before the first Copilot agent goes live:
- A credit cap with a hard stop on each agent
- A capacity cap on the environment the agent runs in
- A schedule that matches how often the work actually needs to happen
- A named owner for every agent
- Microsoft Purview auditing turned on
- A review before publishing any agent that runs on a schedule, sends email or writes to a system of record
ESW recommends starting with one process.
“One recurring process with a clear owner and a person who signs off. Not five agents. One,” Kommer said.
Since 2006, ESW has delivered more than 1,000 projects for more than 1,500 clients and trained more than 10,000 employees on Microsoft 365 and related tools. The full guide, How to Deploy Autonomous Copilot Studio Agents Without a Surprise Bill, is available on the ESW website, along with ESW’s broader Microsoft 365 Copilot agents implementation guide.
About eSoftware Associates Inc (“ESW”)
ESW is a US-based Microsoft partner specializing in Microsoft 365, SharePoint, Power Platform, AI-driven automation, and workforce enablement. Through consulting, automation, and training services, ESW helps organizations modernize operations and build durable technology capabilities.
Press Inquiries
Russell Kommer
contact [at] eswcompany.com
8006820882
https://www.eswcompany.com
228 Park Ave South
New York, NY 10003
A video accompanying this announcement is available here: https://youtube.com/watch?v=3dWBqqYnABU


