Microsoft Copilot Studio October 2026: persistent agents, MCP server, and new cost controls
Copilot Studio's October 2026 release adds an MCP server for dev tools, persistent agent accounts, a customer conversation harness, and credit tracking.
Microsoft’s October 2026 Copilot Studio release is one of the more substantive updates in a while. Rather than incremental polish, it ships four meaningful additions: a new MCP server that lets developers manage agents from tools like Claude Code and GitHub Copilot, persistent agent accounts reachable by @-mention in Teams and Outlook, a purpose-built harness for customer-facing conversations, and clearer visibility into credit consumption. Here is what each of those actually means in practice.
Build and manage agents from your existing dev tools
The Copilot Studio MCP server lets makers connect to Copilot Studio from any MCP-compatible interface, including GitHub Copilot, Claude Code, and OpenAI Codex. Once connected, you can create agents, configure workflows, run tests, publish updates, and troubleshoot issues using natural-language instructions, without leaving the tool you are already working in.
The server uses Microsoft’s published @microsoft/copilot-studio-mcp npm package, launched via npx. Each tool it exposes is automatically added as an action in Copilot Studio and inherits the name, description, inputs, and outputs from the MCP server definition. When those tools are updated or removed upstream, Copilot Studio reflects the changes automatically.
There is also a get_consumption tool built in, which lets you read historical credit consumption for agents or workflows, or check remaining capacity in the current environment. That is a small but useful addition: it means you can query costs without switching to a separate admin view.
For makers who already spend their day in a code editor or agentic CLI, this removes a meaningful context switch. You do not need to open the Copilot Studio web interface to get work done.
Licensing note: you need Microsoft 365 Copilot or Copilot Studio author access to create agents via MCP, Generative Orchestration must be enabled, and your organisation needs a Copilot Credit capacity pack.
Agents with their own identity in Teams and Outlook
Agent accounts give Copilot Studio agents a governed Microsoft 365 identity: their own mailbox, Teams presence, and Office access. That means colleagues can @-mention an agent in a Word comment, reply to it in Outlook, or assign it a task in Teams, exactly as they would with a human teammate.
The practical shift here is persistence. Rather than a one-off chat session, an agent with an account can hold context across interactions, pick up tasks between human check-ins, and work through ongoing responsibilities without waiting for a prompt. Business process memory, approved credentials, and event-based triggers are all part of the picture.
Ooredoo Qatar offers a good example of what this looks like in production. Their executive business-case review agent operates across Outlook, Teams, and Word: it reviews incoming proposals, applies company policy, and prepares decision-ready briefs. The finance team feeds it updates by @-mentioning it in Teams or replying in Outlook, contributing context in the same tools they already use.
Administrators retain full control. The agent account is a first-class entity with its own policies, access controls, and governance settings.
Agent accounts entered private preview on 15 October 2026, with general availability targeted for November 2026.
A dedicated harness for customer conversations
From 21 October 2026, Copilot Studio has a third harness: the customer conversation harness, now in public preview. It sits alongside the Microsoft Copilot harness and the Standard harness, and is built specifically for customer-facing voice and chat agents.
The harness is designed around a few things that matter for customer service: the ability to coordinate multiple specialist agents working together, the flexibility to mix scripted topics with generative responses, memory for returning customers, and a clear path to hand off to a human agent in Teams or a contact centre when needed. Work IQ is also baked in, so agents can draw on context from Microsoft 365 to inform their responses.
One constraint worth noting: speech channels do not support end-user sign-in, so knowledge that requires authentication credentials is limited to chat.
Microsoft’s own Customer Service and Support team built a dynamic resolution agent that uses reasoning to analyse support cases and draw on existing knowledge and tools. By August 2026, it was achieving a fully autonomous resolution rate of over 35%, meaning more than a third of cases resolved without any human involvement.
Credit tracking that actually helps during development
As agent usage scales, understanding where credits go becomes important. The October release adds two layers of visibility.
For makers, new workflow-level reporting shows credit consumption for individual workflow runs and individual nodes, making it straightforward to identify what is driving costs. You can also query consumption directly from the MCP server using the get_consumption tool during development and testing.
For administrators, a preview Copilot Credit cost management experience in the Microsoft 365 admin centre brings together usage, spending trends, and remaining capacity across Copilot Studio agents, workflows, apps, Cowork, and Work IQ APIs in one place.
Copilot Credits are priced at $0.01 per credit on pay-as-you-go meters, with prepurchase plans and prepaid pack subscriptions also available.
What to pay attention to
The MCP server is the most developer-facing of these additions, and it reflects a broader direction: Microsoft wants Copilot Studio to be reachable from wherever makers already work, rather than requiring a dedicated interface. The persistent agent accounts are the most visible change for everyday Microsoft 365 users, and they represent a meaningful step toward agents that behave more like colleagues than tools. The customer conversation harness gives contact centre and service teams a more structured starting point than the general-purpose harnesses.
If your organisation is already building in Copilot Studio, the credit tracking improvements are worth exploring immediately. The workflow-level reporting addresses a real gap, and the admin centre view makes it easier to have sensible conversations about capacity before costs become a surprise.
The full release notes cover additional detail on all of these capabilities, including the A2A interoperability additions and Work IQ general availability.