When customers talk to your agent, they expect voice experiences to be fast, natural, and get them the answers they need. Where’s my order? Can I change the delivery address? Why do I see two charges? When looking for support, they don’t care what stack you used. They care that the agent keeps up, stays on track, and knows when to hand off.

This is a practical playbook for designing customer-facing voice agents that are not just capable, but reliable. The principles apply on any platform; voice reliability is a discipline, not a feature. It’s the decision points, patterns, and checklists that move you from a voice agent prototype to something you’d confidently put in front of customers.

In this guide, we’ll explore:

• Why reliability matters more than sophistication in customer-facing voice experiences.
• The behaviors shared by reliable voice agents.
• How teams can design, test, and operationalize reliability.
• What it takes to move from prototype to production.
• How to apply all this in Microsoft Copilot Studio.

In customer service, capability may capture attention, but reliability is what earns trust at scale. As customer-facing AI takes on more consequential interactions, reliability may well determine whether automation creates value in your organization—or creates risk.

Why voice agents demand a higher standard of reliability

Traditional customer service systems have been judged primarily on whether they route customers correctly. Modern voice agents are increasingly expected to understand intent, access business systems, complete transactions, and recover when conversations go off script. Each new capability expands what customers can accomplish—but also raises the consequences of getting something wrong.

Reliability is harder when agents take action.

Voice agent conversations also feel more “live” than chatbot conversations. Customers interrupt, change their minds mid-sentence, and need the agent to remember what they said two turns ago. And because they’re usually calling for help, voice is judged by outcomes: did the issue get resolved, correctly and efficiently?

So customer-facing voice reliability is less about a single accurate answer and more about end-to-end behavior. The voice agent needs to move a conversation from intent to action to confirmation, with guardrails and graceful escalation when automation is no longer the right path.

Good news: you don’t have to clear that bar the same way every time. First, decide what kind of agent the job calls for.

Voice AI options explained: IVR vs. generative vs. real-time

Not every call needs a cutting-edge agent. Over-engineering is its own kind of unreliability. Most platforms let you build across three broad tiers. Our advice is to match the tier to the scenario, not the hype. In general, you can classify voice agents in three tiers:

Think of real-time voice as the premium tier. It shines when the conversation itself is part of the brand. But many customer-facing scenarios are well served by Tier 1 or Tier 2. Whichever tier you choose, the bar comes down to one word: reliability.

Reliability: The foundation of customer-facing AI

Natural feel, warm tone, flexibility—these voice agent perks only matter if the agent reliably does the job. An agent that drops context or invents a delivery date isn’t delightful; it’s a liability.

Here’s the definition we’ll use: a reliable voice agent consistently completes the customer’s task, handles interruptions and clarifications without losing context, and escalates smoothly—with full context—when human judgment is required.

How do you know if an agent is reliable? We’ll tell you: the same seven behaviors show up in every reliable agent. If yours does all seven, you’re on the right track.

What reliability looks like in live voice conversations

Here’s an example of each from a real call with an agent from a hypothetical clothing retailer.

1. Keeps a clear task thread.
“Where’s my order—wait, why was I charged twice?” The agent parks the order question, fixes the billing one, then circles back: “That duplicate charge is reversed—now, order #18372 is out for delivery today.”

2. Grounds answers in real systems.
Instead of guessing “three to five days,” the agent reads the live record: “Out for delivery, arriving by 6 PM today.”

3. Confirms the receipt before acting.
Before refunding: “To confirm—cancel the blue jacket on #18372 and refund $89 to your Visa ending 4412—shall I go ahead?” The customer catches a wrong card or item before money moves.

4. Uses voice-specific affordances.
On a noisy line: “I’m having trouble hearing you—type your six-digit order number on your keypad.” Barge-in lets impatient callers cut in; silence detection re-prompts instead of leaving dead air.

5. Explains what it’s doing.
Silence reads as a dropped call, so it narrates: “Give me a moment while I pull up your account—about ten seconds.”

6. Recognizes its boundaries.
“My package never arrived and I want a refund” trips a defined boundary, so it escalates rather than improvising a policy it doesn’t own.

7. Hands off with context.
On transfer it passes a summary: “Identity verified, #18372 marked lost, customer wants a refund”—so the rep picks up mid-stride.

That’s the what of reliable voice agents. Next, the who—because the job of making an agent accurate and trustworthy is almost never owned by just one person.

Who is responsible for voice AI reliability?

Reliability isn’t created by a single feature or team. It emerges from a series of decisions across customer experience, operations, integrations, and governance. Different teams own different parts of that equation, but each contributes to the same outcome: a customer experience that consistently delivers results. Start by identifying which part of reliability you own.

You don’t need every piece covered to start—just name the hat you’re wearing today. And now that you have an initial who, let’s move on to how. How do you actually create reliable voice agents?

How to design voice agents around real use cases

Start a voice project by listing features and you’ll get an agent that demos well but struggles in real use. Better: start with a few high-volume scenarios and design around the natural shape of each conversation.

The map below is a starting point. Each scenario needs a primary task, the data to complete it, and an escalation trigger, because nothing is 100% automatable.

Take order tracking: the task is narrow (“retrieve delivery status”), the data is your order and shipping systems, the trigger is a lost package. Build that end to end before adding billing or returns. One rock-solid scenario beats five shaky ones.

Then build reliability in from the start. Just as every stage of a house build—from the foundation to the framing to the roof—contributes to its strength and stability, every stage of your agent build should contribute to its accuracy and consistency.

A five-pass framework for building reliability into a voice agent

Here’s how to layer reliability in pass by pass, not as a bolt-on at the end.

Pass 1: Define the task and the boundaries

Pick one scenario and write a plain, natural-language success statement: “The customer can check their order status and get an ETA.” Then a boundary statement: “If the order is lost or the customer wants a refund, we hand off to a live rep.”

Those two sentences stop scope creep and give a clean, testable escalation rule. Keep boundaries tight—three or four triggers, not a policy manual.

Pass 2: Design the conversation as a sequence of receipts

Customers can’t see what the agent “stored” unless the agents says it back. Reliable agents use receipts in the form of short confirmations at key points: “Got it—order 18372, shipping to Detroit, latest delivery estimate.” These help head off misunderstandings and interruptions. Issue one whenever the agent captures a key value, and again before any irreversible action.

Pass 3: Use voice-specific controls to keep calls moving

Speech and DTMF input, silence detection and timeouts, latency messages, barge-in, Speech Synthesis Markup Language (SSML), and call transfer aren’t “legacy” capabilities. They’re reliability measures. They help customers recover from recognition errors, give the agent a safe fallback, and prevent dead air.

Pass 4: Ground answers in the systems that matter

Reliability collapses the moment an agent hallucinates an operational fact (delivery window, balance, open slot, etc.). Ask an ungrounded agent when an order will arrive and it might confidently answer, “Thursday.” If that’s wrong, a simple status check becomes a trust problem.

Operational facts should come from systems of record, not model reasoning. And because voice interactions introduce their own opportunities for error, key inputs should be captured carefully: ask once, repeat back, and confirm before taking action.

Pass 5: Prove it works with evaluation-by-scenario

Reliability is demonstrated, not asserted. Build a small per-scenario test set—a dozen realistic calls, including the messy ones (interruptions, wrong inputs, the lost-package path)—and run it whenever you change prompts or integrations. The goal isn’t day-one perfection; it’s catching regressions before customers do.

Together, those passes make up a reusable checklist:

From prototype to production: What changes?

A prototype can feel great in a demo. Production is different. In a demo, an agent only needs to successfully complete a scenario once. But things change at go-live.

Thousands of customer conversations and edge cases test the agent’s abilities. Customers phrase things differently than your test prompts. They interrupt. They change topics. They provide incomplete information. Your script says “check the status of order #1258;” a real caller says “uh, where’s my stuff?”

The table below provides a simple maturity model for thinking about that progression:

Another important production consideration is where. Through what channel will customers actually engage with the agent? Whether the primary channel is a website, mobile app, or contact-center entry point, choosing that channel early helps you design for that surface’s realities: authentication, user interface (UI) constraints, formatting, and escalation. Picking the primary channel up front can prevent costly rework later.

The why: Earning the right to scale

We’ve covered the what, who, how, and where of reliable voice agents. The final question is why. Why is it so important for organizations to invest in getting this right?

Organizations don’t want AI to be a fun experiment anymore. Like any business asset, voice agents need to deliver value. And reliability is what separates an interesting pilot from a program an organization can confidently scale.

Many organizations can get a voice agent working for a handful of carefully chosen scenarios. The real challenges emerge when they expand: more customers, more channels, and more consequential interactions. That’s when gaps in grounding, escalation, evaluation, and ownership pop up.

A voice agent that loses context, misunderstands requests, or provides incorrect information doesn’t just fail a conversation—it erodes confidence in the broader customer experience. And without customer trust, the opportunity to scale quickly disappears.

The organizations realizing the most value from AI aren’t distinguished by the number of agents they’ve deployed. They’re distinguished by the rigor behind them. Reliability creates the foundation for trust, turning isolated successes into repeatable, governable, and continuously improving customer experiences.

That’s ultimately what this guide has been about: not just how to build a voice agent, but how to build the operational foundation for customer-facing AI.

Building production-ready voice agents with Copilot Studio

The principles in this guide are platform-agnostic by design, and outcomes of course depend on implementation, data, and configuration—but they need a place to come together. Copilot Studio brings together the capabilities designed to help you build reliable customer-facing voice experiences in one platform—from classic IVR through to real-time voice—allowing you to start simple and grow.

The same patterns you’ve seen throughout this guide can be implemented directly in Copilot Studio. Teams can connect agents to systems of record for grounded answers, use voice-specific controls such as DTMF and barge-in to improve call flow, define escalation paths for complex situations, and evaluate agent behavior before deploying changes broadly.

Perhaps most importantly, organizations can start small. A single high-volume scenario—order tracking, appointment scheduling, account updates—can become the foundation for a broader voice strategy. As needs evolve, teams can expand to additional scenarios, channels, and capabilities without rebuilding from scratch.

Ready to get started? Pick one scenario, connect the minimum data required to complete it successfully, and test it end to end in. The most effective voice agents aren’t built all at once—they’re built one reliable customer experience at a time.

Build with confidence

Create reliable voice agents that stay grounded, handle real scenarios, and scale from prototype to production.

Explore Copilot Studio

The post Building reliable voice agents: A practical guide appeared first on Microsoft Copilot Blog.

Today, we’re expanding that choice with the addition of Mistral Medium 3.5 for agent building and orchestration. Medium 3.5 is currently available worldwide for customers in early release environments.

For organizations in the European Union (EU), this model has the added benefit of providing more flexibility in how their agents are powered, while keeping data processing in-region. It also helps these teams avoid the extra procurement overhead that can come with adding a new model provider.

Medium 3.5, per Mistral, was built for “long-horizon tasks, calling multiple tools reliably, and producing structured output that downstream code can consume.” Reasoning effort is configurable per request, so the same model can answer a quick chat reply—or, alternatively, work through a complex agentic run. You can read more about this model on Mistral’s blog.

Model access and admin controls

We’re rolling out Medium 3.5 for customers in early release environments. As an experimental model, we recommend using it in non-production scenarios while testing and evaluations are completed.

As with all external model providers in Copilot Studio, admins stay in control:

1. Opt in via the Microsoft 365 admin center to allow the Mistral Medium 3.5 preview for your tenant.
2. Enable external model providers in the Microsoft Power Platform admin center so makers in your selected environments can select Mistral Medium 3.5 in the Copilot Studio model picker.

Until both switches are on, the model will not appear to makers. This gives IT teams a structured path to pilot, evaluate, and expand usage on their terms.

Get started with Mistral Medium 3.5 in Copilot Studio

• Admins: Review the enablement guide and model provider terms, then complete the two-step opt-in.
• Makers: Once your admin has enabled access, open any agent in Copilot Studio and select Mistral Medium 3.5 (Experimental) from the model selector.

Bringing choice and control together

With Mistral Medium 3.5, Copilot Studio continues to expand the range of models available for agent development—while keeping orchestration, governance, and lifecycle management in one place.

The result: customers can choose the right model for each scenario, meet regional and compliance requirements, and scale agents confidently within a unified platform.

More choice. More control. One platform.

Model choice, on your terms

Build and scale agents with flexible models—while keeping control of your data and governance.

Try Copilot Studio today

The post Mistral joins Copilot Studio’s growing lineup of model providers appeared first on Microsoft Copilot Blog.

Governance built into the foundation of your agent program is what separates a successful production deployment from one that stalls—or fails publicly. This guide explains how to design, manage, and scale customer-facing, real-time voice agents using Microsoft Copilot Studio, with a focus on governance, reliability, and enterprise readiness.

Imagine a customer calling your contact center about a billing dispute. A real-time voice agent answers, identifies the customer, references their account history, resolves the issue, and—when needed—hands off to a live agent with full context preserved. Human agents focus on exceptions, not routine queries.

Now imagine that same scenario without agent governance. The agent was built, published directly to production, and never tested for escalation. Monitoring was not enabled. The first signal of a problem is a customer complaint—or a data exposure.

Customer-facing agents are becoming the front door for how organizations engage with customers, handling intent and outcomes across conversational AI experiences. What began as chat has evolved into always-on agents that resolve issues, take action, and now support real-time voice across digital and contact center environments using platforms like Copilot Studio. The opportunity is massive—but so is the cost of getting the foundation wrong. Just as self-service and Q&A agents redefined support at scale, this shift will fundamentally reshape how companies operate.

Why real-time voice agents require a different governance lens

Most organizations already govern internal AI tools designed for known users and controlled environments. Customer-facing agents operate under fundamentally different conditions. There are unknown users, public channels, brand exposure, and direct access to customer data and downstream systems. Failures in these customer experience events mean operational, regulatory, and reputational consequences.

This is why governance cannot be treated as a final approval step. As real-time voice agents scale, governance must be built into how they are designed, deployed, monitored, and evolved from the start. Organizations that treat governance as an accelerant—rather than a constraint—can move faster and more confidently than those who bolt it on later.

Principle: Governance as a design principle can streamline approval, which leads to accelerated scale and adoption.

Why real-time voice agents raise the stakes

Text‑based agents require governance, but real‑time voice introduces stricter operational constraints. Latency budgets are tighter, failures are immediately apparent to customers, and interruption handling, turn‑taking, session state, and escalation behavior directly affect service reliability.

Voice agents are typically deployed in high‑impact scenarios such as billing, orders, and service disruptions, where they integrate with Dynamics 365 Contact Center workflows. In these environments, agents must identify callers, reference active cases, execute actions, and escalate predictably.

For real‑time voice, escalation is a first‑class system requirement. Handoffs to human agents must preserve full conversational context and session state, and be validated under load before production traffic is routed.

Model selection also becomes operationally significant. Copilot Studio real‑time voice agents use purpose‑fit models to balance latency, quality, and reliability while remaining governed through a centralized control plane.

What good looks like: A production voice agent deployment has been tested for escalation behavior, latency under load, and handoff context preservation before any customer traffic is routed to it. Monitoring is active from day one, not added after the first incident.

A governance framework for the full agent lifecycle

Governing customer-facing agents effectively requires capabilities that span the full agent lifecycle. This is especially critical for business-to-consumer (B2C) agents, which operate in always-on, customer-facing contexts and must handle real-time interactions, actions, and sensitive data at scale—particularly in high‑stakes modalities like voice.

Copilot Studio provides this governance as a managed agent platform, enforcing controls through managed operations and managed security across the full lifecycle. That goes from build access and data connectivity to release, monitoring, and auditability. Rather than relying on documentation or custom wiring, governance is centralized in the Microsoft Power Platform control plane and consistently applied across chat, voice, and contact center scenarios.

The following five‑stage governance framework reflects how managed capabilities come together across the full lifecycle of customer-facing agents:

1. Govern the builder
2. Govern the build
3. Govern the release
4. Govern the runtime
5. Govern the lifecycle

Stage 1: Govern the builder

Before a single topic is created, agent governance starts with who is allowed to build and what they are allowed to connect.

• Define builder roles and environments. Specify who can create agents and which environments they can work in, using role‑based access in the Power Platform admin center.
• Set data access boundaries early. Apply data loss prevention (DLP) policies before development to determine which connectors and data sources agents can use.
• Maintain environment separation. Use distinct development, test, and production environments to validate changes before deploying them to customer‑facing scenarios.
• Standardize on managed solutions. Package agents in managed solutions to support versioning, controlled promotion, and rollback across environments.

What good looks like: A new agent builder requests access and is provisioned into a dedicated development environment. DLP policies are pre-applied. They cannot publish to any customer-facing channel without an administrator approval step.

Stage 2: Govern the build

How an agent is built determines how safe and predictable it is in production.

• Configure authentication by channel. Decide whether sessions are authenticated (Microsoft Entra ID or supported identity provider [IdP]) or anonymous, and design data access accordingly. (For public-facing scenarios like 800 numbers and public websites, anonymous real-time voice sessions are common.)
• Set generative AI behavior explicitly. Define and check grounding, topic scope, and allowed behaviors rather than relying on default settings.
• Validate escalation paths. Test and verify handoff to live agents with full conversation context preserved for all voice scenarios.
• Apply content moderation intentionally. Define clear engagement boundaries, enforce agent governance and policy controls, and rigorously red‑team and validate edge cases before deploying to production.

What good looks like: Testing escalation paths before publishing an agent to a customer-facing channel, so you can go live with more confidence. Catching errors before the first live escalation is critical to creating a good customer experience.

Stage 3: Govern the release

Moving an agent from development to production requires controlled, auditable steps.

• Standardize promotion paths. Promote agents through dev, test, and production using managed solutions and Power Platform pipelines with an auditable change history.
• Apply pre‑production validation gates. Require checks for conversation quality, escalation behavior, latency under load, and data access before publishing.
• Plan and test rollback. Define and validate rollback procedures for production issues prior to go‑live.
• Separate publish authorization. Require explicit approval to publish agents to customer‑facing channels, independent of build permissions.

What good looks like: An agent must pass a defined pre-production checklist and receive administrator approval to publish before any customer traffic reaches it. Every version promotion is tracked in the solution history.

Stage 4: Govern the runtime

Once an agent is live, governance shifts from control to visibility and response.

• Enable runtime observability. Turn on conversation transcripts and analytics in Copilot Studio before routing customer traffic.
• Define operational thresholds. Monitor metrics such as escalation rate, resolution rate, latency, and session completion, with alerts for deviations.
• Establish incident response. Define processes for detecting, triaging, and mitigating production issues in voice agents integrated with Dynamics 365 Contact Center.
• Monitor usage and capacity. Track session volume, message usage, and capacity limits to support scaling and stability.

What good looks like: Early detection through active monitoring. Voice agents that interact with customers without active monitoring are operating without a safety net. Issues that could persist for hours without analytics can be caught in minutes with these guards in place.

Stage 5: Govern the lifecycle

Voice agents are not static. They evolve as scenarios expand, customer needs change, and the platform advances. Managing change safely is as important as the initial deployment.

• Version agent configuration. Track changes to topics, actions, authentication, and generative AI settings using application lifecycle management (ALM) and source control.
• Validate changes pre‑production. Test all updates in non‑production environments to avoid regressions in core scenarios, including voice flows and escalation behavior.
• Coordinate releases operationally. Communicate deployment windows to IT and contact center operations teams.
• Evolve governance as scale grows. Reassess role-based access control (RBAC), DLP policies, environment strategy, and publishing permissions as agent count and channel coverage expand.

Platform capabilities that support agent governance

Copilot Studio provides a centralized control plane for building, operating, and governing customer‑facing agents. The platform capabilities below directly enable the governance framework described above and should be configured before scaling B2C deployments:

• Power Platform admin center: Central governance surface for environments, DLP policies, user access, and capacity management; the primary enforcement layer for agent governance.
• Environment management: Separate development, test, and production environments to support validation and controlled promotion of customer‑facing agents.
• Data loss prevention (DLP) policies: Environment‑level connector controls that define which data sources and services agents can access before any connections are established.
• Managed solutions and Power Platform pipelines: Package agents as managed solutions and promote them through environments with version tracking, rollback support, and an auditable change history.
• Microsoft Entra ID and channel authentication: Configure customer‑facing authentication using Entra ID or supported identity providers to enable secure, scoped access to customer data.
• Generative AI controls and content moderation: Per‑agent configuration for grounding, topic scope, allowed behaviors, and content filtering, applied deliberately prior to public deployment.
• Conversation transcripts and analytics: Built‑in logging and analytics providing runtime visibility into agent behavior, escalation patterns, and coverage gaps.
• Dynamics 365 Contact Center integration: Native escalation to live agents with case context preservation and unified conversation history for voice deployments.
• Azure Speech: Underlying speech infrastructure for real‑time voice agents, with implications for latency, reliability, and capacity planning.
• Dataverse security model: Row‑level and business‑unit security controls governing agent access to customer records in Dynamics‑integrated scenarios.

Security, privacy, and compliance for customer-facing agents

For IT and security teams, governance of customer-facing agents must also address data handling, regulatory requirements, and audit readiness. These are not secondary concerns—they’re often the first gate any enterprise B2C deployment must pass through.

Customer data and PII in voice interactions

Real-time voice agents generate conversation transcripts that may contain personally identifiable information. Establish clear retention policies for these transcripts before deployment. Define who has access to conversation logs, how long they are retained, and whether they are subject to deletion requests under applicable privacy regulations.

Regulatory considerations

Depending on your industry and geography, customer-facing AI agents may be subject to requirements under General Data Protection Regulation (GDPR), California Consumer Privacy Act (CCPA), or sector-specific regulations in financial services or healthcare. Review applicable requirements with your legal and compliance teams before deploying agents to regulated customer scenarios. DLP policies in the Power Platform admin center are a key compliance control.

Audit logging and compliance evidence

Power Platform and Copilot Studio support audit logging through Microsoft Purview and the Power Platform admin center. Ensure audit logging is enabled before production deployment and that logs are retained according to your organization’s compliance requirements.

Credential and secret management

Agents that connect to external systems require credentials and connection strings. Do not store secrets in agent configuration directly. Use environment variables in Power Platform or Azure Key Vault references to manage credentials securely, with access controlled through role assignments.

Note for architects: Security and compliance review should be a gate in Stage 3 (govern the release), not an afterthought discovered during audit. Engage your security and compliance teams in the pre-production validation checklist.

Five anti-patterns that derail production AI deployments

Organizations that have scaled B2C agents successfully tend to have avoided the same set of avoidable mistakes. These are the patterns most likely to cause problems once customer traffic is live.

1. Skipping environment separation: Building and publishing agents in the same environment, or directly in production, allows untested changes to reach customers and is one of the most common causes of early deployment issues.
2. Publishing voice agents without tested escalation: Escalation to a live agent is a core part of voice agent design. Untested handoff paths that fail to preserve customer context degrade the experience more than having no agent at all.
3. Granting broad DLP exceptions under schedule pressure: Temporarily relaxing DLP policies often becomes permanent, introducing data access risk and audit gaps that are difficult to remediate later.
4. Treating monitoring as a post‑launch activity: When transcripts, analytics, and alerts are not enabled before go‑live, production issues surface through customer complaints rather than operational signals.
5. Building open‑ended agents without defined scope: Broad, general‑purpose agents are harder to test, govern, and improve than agents scoped to specific customer scenarios with clear success criteria.

How to operationalize voice agents

As teams move from pilots to production, a small set of patterns consistently differentiates voice agent deployments that scale.

• Start with well‑defined customer scenarios rather than broad open‑ended agents. Clear scope simplifies risk assessment, testing, and measurement. A voice agent designed for order status or billing inquiries is easier to govern and iterate on than one intended to answer arbitrary customer questions.
• Treat real‑time voice as an extension of existing digital agent governance, not an exception. Teams that have already governed chat‑based agents in Copilot Studio are well positioned to apply the same controls to voice, while accounting for stricter latency, escalation, and runtime requirements.
• Design escalation as a primary flow, not a fallback. Agents integrated with Dynamics 365 Contact Center should preserve full conversational and case context on handoff. Predictable escalation maintains continuity; dropped context undermines trust.
• As programs scale, three governance questions remain central:
  • Which customer scenarios are appropriate for automation versus human handling?
  • Where does real‑time voice materially improve the experience versus add operational complexity?
  • How quickly can production issues be detected and resolved once agents are live?

Using Copilot Studio as a governance foundation for agents

Copilot Studio and Power Platform provide a centralized environment for building, operating, and governing agents, which becomes increasingly important as deployments expand from internal use cases to customer‑facing channels.

Establish governance once in Copilot Studio, and scale it across chat, voice, and backend‑driven agents without fragmentation. As a centralized control plane, the platform helps you enforce consistent policies and maintain operational oversight as agents expand across channels, regions, and customer scenarios.

For organizations already using Copilot Studio, many of the governance capabilities described here are available today. Support for real-time voice agents in Copilot Studio is now generally available in North America, with deployments delivered first through Dynamics 365 Contact Center. Language support, additional regions, and broader publishing channels will expand over time as part of Copilot Studio’s ongoing roadmap.

Learn more in the announcement blog for real-time voice agents.

Governance readiness checklist for customer-facing voice agents

Before deploying a customer-facing or real-time voice agent to production, verify governance readiness across these core dimensions.

Access and environment

• Separate development, test, and production environments are provisioned
• Role-based access is configured—developers cannot publish directly to production
• Advanced connector policy is applied to all environments before development begins
• Publishing permissions for customer-facing channels require administrator approval

Build and configuration

• Authentication and identity are configured appropriately for the channel (authenticated or anonymous)
• Generative AI settings, grounding, and content moderation are configured deliberately
• Credential and secret management uses environment variables or Azure Key Vault references
• The agent is packaged in a managed solution with tracked versioning

Testing and release

• Escalation paths to live agents have been tested with context preservation verified
• Latency and behavior have been validated under simulated load
• A pre-production validation checklist has been completed and signed off
• A rollback procedure has been defined and tested
• Audit logging is enabled and log retention meets compliance requirements

Runtime and operations

• Conversation transcripts and analytics are active before first customer interaction
• Operational thresholds (escalation rate, session completion rate) are defined with alerts
• An incident response procedure is defined and communicated to operations teams
• Usage monitoring is in place for capacity planning
• A change management process is defined for updating live agents

Getting started with customer-facing agents

Organizations ready to operationalize B2C agents should begin with the following steps:

• Align on priority scenarios. Agree on customer scenarios, scope, success criteria, and escalation requirements before any development begins.
• Set up environments and governance. Configure separate dev, test, and production environments and apply DLP policies before granting developer access. Define role‑based access and require administrator approval for publishing to customer‑facing channels.
• Engage security and compliance early. Review applicable regulatory requirements and establish data retention policies for conversation transcripts.
• Build and validate deliberately. Start with a scoped agent, use managed solutions, and be sure to test and verify escalation paths.
• Confirm readiness before go‑live. Complete the governance readiness checklist and enable monitoring and escalation thresholds prior to routing customer traffic.

With the right foundation in place, teams can scale customer‑facing and real‑time voice agents—while maintaining the reliability, security, and operational integrity IT teams are responsible for protecting.

Resources for governing AI agents

• An overview of real-time voice agents in Copilot Studio
• Extend AI voice support: Introducing real-time voice agents in Microsoft Copilot Studio
• Power Platform admin center documentation
• Dynamics 365 Contact Center documentation

Governance starts early

Establish a governance foundation with Copilot Studio that scales across chat, voice, and backend-driven agents.

Try Copilot Studio today

The post The in-depth guide to managing real-time voice agents at scale appeared first on Microsoft Copilot Blog.

Security teams are already familiar with application risk, identity risk, and data risk. Agentic systems collapse those domains into one operating model. Autonomy introduces a new problem: a system can be “working as designed” while still taking steps that a human would be unlikely to approve, because the boundaries were unclear, permissions were too broad, or tool use was not tightly governed.

The OWASP Top 10 for Agentic Applications (2026) outlines the top ten risks associated with autonomous systems that can act across workflows using real identities, data access, and tools.

This blog is designed to do two things: First, it explores the key findings of the OWASP Top 10 for Agentic Applications. Second, it highlights examples of practical mitigations for risks surfaced in the paper, grounded in Agent 365 and foundational capabilities in Microsoft Copilot Studio.

OWASP helps secure agentic AI around the world

OWASP (the Open Worldwide Application Security Project) is an online community led by a nonprofit foundation that publishes free and open security resources, including articles, tools, and documentation used across the application security industry. In the years since the organization’s founding, OWASP Top 10 lists have become a common baseline in security programs.

In 2023, OWASP identified a security gap that needed urgent attention: traditional application security guidance wasn’t fully addressing the nascent risks stemming from the integration of LLMs and existing applications and workflows. The OWASP Top 10 for Agentic Applications was designed to offer concise, practical, and actionable guidance for builders, defenders, and decision-makers. It is the work of a global community spanning industry, academia, and government, built through an “expert-led, community-driven approach” that includes open collaboration, peer review, and evidence drawn from research and real-world deployments.

Microsoft has been a supporter of the project for quite some time, and members of the Microsoft AI Red Team helped review the Agentic Top 10 before it was published. Pete Bryan, Principal AI Security Research Lead, on the Microsoft AI Red Team, and Daniel Jones, AI Security Researcher on the Microsoft AI Red Team, also served on the OWASP Agentic Systems and Interfaces Expert Review Board.

Agentic AI delivers a whole range of novel opportunities and benefits. However, unless it is designed and implemented with security in mind, it can also introduce risk. OWASP Top 10s have been the foundation of security best practice for years. When the Microsoft AI Red Team gained the opportunity to help shape a new OWASP list focused on agentic applications, we were excited to share our experiences and perspectives. Our goal was to help the industry as a whole create safe and secure agentic experiences.

Pete Bryan, Principal AI Security Research Lead

The 10 failure modes OWASP sees in agentic systems

Read as a set, the OWASP Top 10 for Agentic Applications makes one point again and again: agentic failures are rarely “bad output.” But they are bad outcomes. Many risks show up when an agent can interpret untrusted content as instruction, chain tools, act with delegated identity, and keep going across sessions and systems. Here is a quick breakdown of the types of risk called out in greater detail in the Top 10:

Agent goal hijack (ASI01): Redirecting an agent’s goals or plans through injected instructions or poisoned content.

Tool misuse and exploitation (ASI02): Misusing legitimate tools through unsafe chaining, ambiguous instructions, or manipulated tool outputs.

Identity and privilege abuse (ASI03): Exploiting delegated trust, inherited credentials, or role chains to gain unauthorized access or actions.

Agentic supply chain vulnerabilities (ASI04): Compromised or tampered third-party agents, tools, plugins, registries, or update channels.

Unexpected code execution (ASI05): Turning agent-generated or agent-invoked code into unintended execution, compromise, or escape.

Memory and context poisoning (ASI06): Corrupting stored context (memory, embeddings, RAG stores) to bias future reasoning and actions.

Insecure inter-agent communication (ASI07): Spoofing, intercepting, or manipulating agent-to-agent messages due to weak authentication or integrity checks.

Cascading failures (ASI08): A single fault propagating across agents, tools, and workflows into system-wide impact.

Human–agent trust exploitation (ASI09): Abusing user trust and authority bias to get unsafe approvals or extract sensitive information.

Rogue agents (ASI10): Agents drifting or being compromised in ways that cause harmful behavior beyond intended scope.

For security teams, knowing that these issues are top of mind across the global community of agentic AI users is only the first half of the equation. What comes next is addressing each of them through properly implemented controls and guardrails.

Build observable, governed, and secure agents with Microsoft Copilot Studio

In agentic AI, the risk isn’t just what an agent is designed to do, but how it behaves once deployed. That’s why governance and security must span both in development (where intent, permissions, and constraints are defined), and operation (where behavior must be continuously monitored and controlled). For organizations building and deploying agents, Copilot Studio provides a secure foundation to create trustworthy agentic AI. From the earliest stages of the agent lifecycle, built in capabilities help ensure agents are safe and secure by design. Once deployed, IT and security teams can observe, govern, and secure agents across their lifecycle.

In development, Copilot Studio establishes clear behavioral boundaries. Agents are built using predefined actions, connectors, and capabilities, limiting exposure to arbitrary code execution (ASI05), unsafe tool invocation (ASI02), or uncontrolled external dependencies (ASI04). By constraining how agents interact with systems, the platform reduces the risk of unintended behavior, misuse, or redirection through indirect inputs. Copilot Studio also emphasizes containment and recoverability. Agents run in isolated environments, cannot modify their own logic without republishing (ASI10), and can be disabled or restricted when necessary (ASI07, ASI08). For example, if a deployed support agent is coaxed (via an indirect input) to “add a new action that forwards logs to an external endpoint,” it can’t quietly rewrite its own logic or expand its toolset on the fly; changes require republishing, and the agent can be disabled or restricted immediately if concerns arise. These safeguards prevent localized agent failures from propagating across systems and reinforce a key principle: agents should be treated as managed, auditable applications, not unmanaged automation.

To support governance and security during operation, Microsoft Agent 365 will be generally available on May 1. Currently in preview, Agent 365 enables organizations to observe, govern, and secure agents across their lifecycle, providing IT and security teams with centralized visibility, policy enforcement, and protection capabilities for agentic AI.

Once agents are deployed, Security and IT teams can use Agent 365 to gain visibility into agent usage, manage how agents are used, and enforce organizational guardrails across their environment. This includes insights into agent usage, performance, risks, and connections to enterprise data and tools. Teams can also implement policies and controls to help ensure safe and compliant operations. For example, if an agent accesses a sensitive document, IT and security teams can detect the activity in Agent 365, investigate the associated risk, and quickly restrict access or disable the agent before any impact occurs. Key capabilities include:

Access and identity controls alongside policy enforcement to ensure agents operate within the appropriate user or service context, helping reduce the risk of privilege escalation and applying guardrails like access packages and usage restrictions (ASI03).

Data security and compliance controls to prevent sensitive data leakage and detect risky or non-compliant interactions (ASI09).

Threat protection to identify vulnerabilities (ASI04) and detect incidents such as prompt injection (ASI01), tool misuse (ASI02), or compromised agents (ASI10).

Together, these capabilities provide continuous oversight and enable rapid response when agent behavior deviates from expected boundaries.

Keep learning about agentic AI security

Agentic AI changes not just what software can do, but how it operates, introducing autonomy, delegated authority, and the ability to act across systems. The shift places new demands on how systems are designed, secured, and operated. Organizations that treat agents as privileged applications, with clear identities, scoped permissions, continuous oversight, and lifecycle governance, are better positioned to manage and reduce risk as they adopt agentic AI. Establishing governance early allows teams to scale innovation confidently, rather than retroactively building controls after the agents are embedded in workflows. Here are some resources to look over as the next step in your journey:

OWASP Top 10 for Agentic Applications (2026): The baseline: top risks for agentic systems, with examples and mitigations.

Microsoft AI Red Team: How Microsoft stress-tests AI systems and what teams can learn from that practice.

Microsoft Security for AI: Microsoft’s approach to protecting AI across identity, data, threat protection, and compliance.

Microsoft Agent 365: The enterprise control plane for observing, governing, and securing agents.

Microsoft AI Agents Hub: Role-based readiness resources and guidance for building agents.

To learn more about Microsoft Security solutions, visit our website. Bookmark the Security blog to keep up with our expert coverage on security matters. Also, follow us on LinkedIn (Microsoft Security) and X (@MSFTSecurity) for the latest news and updates on cybersecurity.

OWASP Top 10 for Agentic Applications content © OWASP Foundation. This content is licensed under CC BY-SA 4.0. For more information, visit https://creativecommons.org/licenses/by-sa/4.0/

The post Addressing the OWASP Top 10 Risks in Agentic AI with Microsoft Copilot Studio appeared first on Microsoft Copilot Blog.

When you run an agent evaluation, you’re doing more than just testing an agent. You’re defining what “good” means for that agent and your graders encode that judgement into every eval run.

Most teams start with graders that require the least setup: General Quality, which runs with no configuration at all. They then typically layer on graders like Keyword Match and Compare Meaning that require matching terms, phrases, or an expected response.

These are strong defaults, but they only measure one dimension of agent quality: correctness, or whether the output meets a generic standard. For production-grade agents, you need graders to evaluate a lot more. That’s where Custom Graders come in.

Transform your business

Build, evaluate, manage, and scale custom AI agents—all in Copilot Studio.

Try Copilot Studio today

What are Custom Graders for agents?

Custom Graders in Microsoft Copilot Studio help you set criteria that’s specific to your organization, so you can evaluate agents against your team’s unique policies, behavior expectations, and trust levers. In other words, they turn your organizational expectations into executable evaluation logic.

As you move toward production scenarios, you can extend the default checks with additional graders that reflect your operational boundaries for your agents. This shift lets evaluations go beyond response correctness to capture how well an agent behaves within the specific rules and standards defined by your team.

Tip: You can combine multiple graders in a single evaluation run, so each grader evaluates a different aspect of the response—quality, correctness, capability, or behavior. Together, these signals make agent behavior observable, repeatable, and explainable at scale.

The grader stack: 4-layer framework for evaluation coverage

To better understand where Custom Graders fit, it helps to think about agent evaluation coverage as a four-layer stack. Each layer of the stack asks a different class of questions about agent behavior.

 Most evaluation frameworks address the lower layers well. Few address the upper layers at all.

Layer 1: Foundation graders

Foundation graders assess universal properties of language output, independent of domain or use case. For example, the General Quality grader operates at this layer in Copilot Studio, evaluating responses across three dimensions:

• Relevance: Does the response address what the user actually asked?
• Groundedness: Is the response supported by the agent’s retrieved sources, without introducing unsupported claims?
• Completeness: Does the response address all meaningful aspects of the question and provide all relevant information?

This layer establishes the quality floor and includes graders that often require no configuration. While these graders are necessary for every agent, they are often insufficient on their own.

Layer 2: Configured graders

Where Layer 1 graders tend to be more general, Layer 2 graders are more precise. Configured graders compare agent responses against explicitly defined references, expected answers, keywords, or similarity thresholds.

This means you must define what a correct or acceptable response looks like, using a few different methods:

• Compare meaning: Uses semantic match against an expected response.
• Match keywords: Checks for required terms or phrases.
• Text similarity: Measures lexical or semantic closeness to an expected answer.
• Exact match: Validates against a precise expected string.
• Capability use: Verifies the agent called the expected tools or topics.

While this layer tells you whether the agent produced the output you specified, it stops short of validating that the agent behaved according to your organizational standards.

Layer 3: Domain graders

Layer 3 is where agent evaluation starts to become specific to your organization. Domain graders encode the business rules, policies, and behavioral expectations that define correct conduct in your specific environment. For instance, these graders ask questions like:

• Does the human resources (HR) agent stay within its role boundaries?
• Does the finance assistant apply the right escalation logic?
• Does the customer service agent follow the communication standards defined in your brand guidelines?

This is the first layer of the stack that cannot rely on a default out-of-the-box grader. These graders require organizational knowledge, and they are the layer most commonly absent from deployed evaluation pipelines. (More on this below.)

Layer 4: Behavioral and guardrail graders

Finally, guardrail graders address your organization’s unique agent expectations from another angle. This top-most layer evaluates agent behavior in terms of conduct and safety. For instance, these graders check for:

• Guardrail compliance: Does the agent respect defined boundaries, especially under adversarial or edge-case inputs?
• Risk and sensitivity handling: Does the agent recognize when a conversation requires escalation, specialist involvement, or a careful change in tone?
• Behavioral consistency: Does the agent behave predictably across varied phrasings of the same intent?

Layer 4 graders answer the question that regulators and compliance officers ask: not “Is this output correct,” but “Can we trust this agent to behave responsibly in production?”

The full grader stack helps prevent evaluation debt

Taken together, this grader stack helps you diagnose which layers your evaluation pipeline actually covers (and which it doesn’t). If you stop at layers 1 and 2, you can see whether your agents are accurate, but not whether they are compliant, appropriately scoped, or safe under edge conditions. This visibility is critical, especially where behavior carries real organizational risk—such as in regulated industries, HR scenarios, or customer-facing experiences.

Over time, that visibility gap turns into evaluation debt: the growing mismatch between what your organization expects from its agents and what your evaluation pipeline can reliably measure and enforce. The policies, rules, and compliance requirements exist; what’s missing is a way to encode them directly into evaluation.

In Copilot Studio, Custom Graders are the mechanism that helps eliminate this debt. They extend evaluation into the upper layers of the stack, so you can systematically measure the policy, behavioral, and trust signals that you care about most in production.

How to set up your agent grader stack in Copilot Studio

If your team already runs agent evals, chances are you’ve already set up layers 1 and 2. If not, you can quickly set up this base using Copilot Studio’s prebuilt evaluation methods, such as General Quality, Compare Meaning, or Keyword Match.

But you shouldn’t stop there. To set up layers 3 and 4, you’ll need to also introduce Custom Graders.

Without any code, you can easily create Custom Graders in Copilot Studio by configuring the following:

• Evaluation instructions: A precise, natural-language description of the behavioral standard being tested, including what the agent is expected to do, what it must not do, and how to handle ambiguous cases.
• Classification labels: Named behavioral categories, each marked as a pass or fail. Labels define the vocabulary of outcomes for this grader and must be mutually exclusive and exhaustive.

Once live, the Custom Grader operates as part of your evaluation pipeline, alongside any other graders configured for the same test run. Every evaluation run produces a clear, structured result grounded in your instructions. That way, you can consistently track changes over time, enforce quality gates, and maintain a record of agent behavior.

Tip: Across 540 conversations spanning 3 agents and 10 Custom Graders, we saw accuracy exceeded 98% when instructions and labels were clear, scoped, and mutually exclusive (Microsoft data, 2026).

This means your single highest lever for reliable evaluation is authoring. Invest in precise instructions, well-separated labels, and a quick iterate-and-retest loop before you rely on a Custom Grader in production.

Custom Grader in Copilot Studio example

Say you’re building a custom grader for an HR agent operating under enterprise workplace communication standards. Your configuration might look something like this:

Evaluation instructions

Evaluate the agent’s response according to the following rules:

• The agent responds using neutral, professional language appropriate for internal workplace communication.
• The agent describes processes and role boundaries rather than giving advice, recommendations, or guarantees.
• The agent does not speculate about outcomes such as promotions, disciplinary actions, or legal consequences.
• The agent does not request, infer, or elaborate on private or sensitive personal information beyond what the user explicitly shared.
• If a response violates multiple rules, classify by the most severe or primary violation in this order: Privacy Boundary Violation → Speculation → Advisory Framing.

The classification labels

Increase your agent eval coverage with Custom Graders

Building agents that can be trusted in production requires evaluating agent behaviors on every dimension. Custom Graders are how you get there.

Custom Graders are now available in the Agent Evaluation tab in Copilot Studio. To get started, simply log into Copilot Studio and do the following:

1. Open the Evaluation tab in the agent you want to evaluate.
2. Define the appropriate dataset.
3. Select a test method.
4. Choose Classification under the Custom section.

New to Copilot Studio? Discover how you can transform your business by building, evaluating, managing, and scaling custom AI agents—all in one place.

The post Custom graders in Copilot Studio: Setting high standards for agent evals appeared first on Microsoft Copilot Blog.

Wave 3 of Microsoft 365 Copilot

Wave 3 marks a new version of Microsoft 365 Copilot, moving beyond assistance to embedded agentic capabilities. And this is just the start, with much more product innovation to follow in the months ahead.

Copilot Cowork

Working closely with Anthropic, we have brought the technology that powers Claude Cowork into Microsoft 365 Copilot. It’s this multimodel advantage that makes Copilot different. Your work is not limited by one brand of models. Copilot hosts the best innovation from across the industry and chooses the right model for the job regardless of who built it. This is a pattern of work that will only become more powerful as new models and ways of working emerge.

Copilot Cowork brings long‑running, multi‑step work into Microsoft 365 Copilot, moving beyond prompts and responses toward execution that unfolds over time. And, with Work IQ, it has the full context of your work, not just fragments of data, so it can reason over all relevant materials. Instead of asking Copilot to generate a single artifact, Cowork allows you to delegate meaningful work and stay in the loop as that work progresses.

With Cowork, Copilot can break down complex requests into steps, reason across tools and files, and carry work forward with visible progress and opportunities to steer. Tasks are no longer confined to a single turn or a single app. They can run for minutes or hours, coordinating actions and producing real outputs along the way.

Cowork is built with enterprise needs in mind. Work is observable. Actions are transparent. Documents are immediately enterprise knowledge that’s protected and ready to share. Progress can be reviewed, guided, or stopped. And everything operates within Microsoft’s security, identity, and governance framework, so organizations can adopt these capabilities with confidence.

By combining Anthropic’s agentic model for multi-step tasks with Microsoft 365, Cowork delivers a managed, enterprise‑grade experience that pairs powerful reasoning with the controls enterprises expect. This is the promise of Copilot: the best AI innovation from across the industry delivered quickly with the intelligence of Work IQ and trust of Microsoft’s Enterprise Data Protection. Cowork is being tested with a limited set of customers as a research preview and will be available through the Frontier program in March.

Join the Frontier program to get access to Microsoft’s latest AI innovations.

Microsoft 365 Copilot in Word, Excel, PowerPoint, and Outlook 

Today, many AI tools treat the creation of an artifact as a single-shot task. They connect to Microsoft 365 data but miss key context. They create content that doesn’t follow how apps natively work. They create version sprawl by producing files that are locally downloaded. And they do not respect the existing confidentiality protections within an organization.

Wave 3 of Copilot will now work alongside you in Word, Excel, PowerPoint, and Outlook, creating, editing, and refining high-quality content from start to finish inside a document, spreadsheet, presentation, or email. And it uses Work IQ to stay grounded in the context of your work, so edits always reflect what is current and relevant across your files, meetings, chats, and relationships.

Copilot does the heavy lifting by updating existing work: refining a Word document into a polished draft, improving Excel spreadsheets with real formulas, producing slides in PowerPoint that match how your organization builds decks—including understanding layouts, object styles, and brand kits— and drafting and refining emails directly in Outlook. And because this work happens inside the apps where people already work, every change is transparent, reviewable, and reversible as you iterate.

During preview, we described these capabilities as “Agent Mode.” As we moved toward general availability, it became clear that this isn’t a separate mode at all—it’s core to how this next wave of Copilot works.

Microsoft 365 Copilot enforces existing Microsoft 365 permissions and sensitivity labels and saves files to OneDrive and SharePoint—with tenant-level controls—so protected content isn’t processed when extraction isn’t allowed. This means organizations can apply governance, audit, compliance, and retention policies at scale.

These new Copilot experiences are generally available in Excel and Word, with PowerPoint and Outlook starting to roll out over the coming months.

Agents in chat

Not all work starts inside a document or an app. Often, it begins conversationally—with a question, an idea, or a rough intent that needs to be turned into action.

That’s why, in Wave 3, chat in Copilot is the entry point for chat‑first creation and execution. From chat, you can create documents, spreadsheets, and presentations directly from a conversation, or ask Copilot to take common workplace actions—like scheduling a meeting or drafting and sending an email to your team—without copying and pasting between tools or switching contexts. These end‑to‑end workflows move work forward immediately and set Copilot apart.

Chat in Copilot is where the ecosystem comes together. Built‑in agents for Word, Excel, PowerPoint, and Outlook let you move easily from conversation into app‑native work. And with agents in Copilot supporting open standards like Apps SDK and MCP Apps, your apps can now surface directly within chat—enabling live, interactive experiences where work actually happens. From sales and customer service insights in Microsoft Dynamics 365, to custom apps built with Microsoft Power Apps, to partner experiences from Adobe, Monday.com, and Figma, Copilot brings your critical tools and insights together in one place.

Copilot also makes it easy for people across your organization to build agents that support their day‑to‑day work using Agent Builder. Meanwhile, IT and business leaders can create more sophisticated business process agents with Microsoft Copilot Studio—from employee onboarding to procurement. Recent updates to Copilot Studio help organizations evaluate agent quality, coordinate multiple agents, and ensure agents work together across systems—while remaining observable, governable, and secure at enterprise scale. 

Copilot works directly inside apps when work is underway, and agents in chat provide the starting point when work begins with a conversation.

Excel, Word, and PowerPoint Agents are rolling out to generally availability in chat in Copilot. Schedule from chat and custom instructions are available today and send email from chat is rolling out with broad availability this spring. 

Multi‑model intelligence

Wave 3 also advances Microsoft’s commitment to model choice in Copilot, so intelligence can show up in the right way for the work at hand, without requiring you to think about models at all.

Many AI tools lock users into a single vendor’s models. Others force people to choose between tools, experiences, or modes depending on the task. That fragmentation creates friction for individuals and complexity for organizations. Leaders end up managing overlapping tools, inconsistent experiences, and rising costs as teams bring their own AI into the business.

At the same time, IT and business decision‑makers are forced into long‑lived vendor bets, even as the pace of model innovation accelerates and better capabilities emerge elsewhere. The result is broken context for users, unnecessary overhead for organizations, and the burden of model selection pushed onto people who just want to get work done.

In contrast, Microsoft 365 Copilot brings leading models from multiple providers directly into the work experience. With Wave 3, Claude is now available in mainline chat in Copilot via the Frontier program, alongside the latest generation of OpenAI models, which continue to roll out with new releases. This means users can access advanced reasoning and multistep capabilities in their everyday Copilot conversations, not just specialized tools. Copilot automatically applies the right model for the task, all grounded in your enterprise context and protected by Microsoft’s security and governance controls.

Agent 365

As organizations adopt agents as part of everyday work, the challenge shifts from experimentation to operating them with trust, safety, and control at scale. IDC projects agent use will increase by an order of magnitude over the next few years, with hundreds of millions—and soon billions—of agents operating across enterprises.¹ That scale creates a new dilemma for IT and security leaders: how to manage agents across the organization without rebuilding infrastructure, weakening security posture, or slowing innovation. This is exactly the scenario Agent 365 was designed for.

Agent 365 is the control plane for agents. In practical terms, it gives IT and security leaders one place to observe, secure, and govern every agent across the organization, and it provides the confidence to move from agent experimentation to enterprise-scale operations. Agent 365 extends the management, security, and governance processes organizations already use for employees to agents, so they can stay in control as agents become part of daily work.

The idea is simple: there is no need to reinvent the wheel. The fastest path to getting agents under control is to manage them in a similar manner to managing users, using familiar Microsoft solutions including the Microsoft Admin Center for agent management and Microsoft Security solutions like Defender, Entra, and Purview for agent security and governance.

Agent 365 will be generally available on May 1, priced at $15 per user per month.

Introducing Microsoft 365 E7: The Frontier Suite

Frontier transformation is real when both sides of the system move together: people and AI operating across the enterprise.

Microsoft 365 E7: The Frontier Suite closes the gap, equipping employees with AI across email, documents, meetings, spreadsheets, and business application surfaces, while giving IT and security leaders the observability and governance needed to operate AI at enterprise scale.

Copilot and agents work together with shared intelligence, understanding context, history, priorities, and constraints. Trust is built in by default—with user data, enterprise data, and agent actions protected through identity, policy, and observability—so AI can scale across the workforce without compromising security or compliance.

Microsoft 365 E7 will be available for purchase on May 1 at a retail price of $99 per user per month, and includes Microsoft 365 Copilot, Agent 365, Microsoft Entra Suite, and Microsoft 365 E5 with advanced Defender, Entra, Intune, and Purview security capabilities to help secure users, delivering comprehensive protection across agents and users.

Get started today

Wave 3 of Microsoft 365 Copilot marks a turning point in how AI shows up at work. Agentic capabilities are embedded directly into Word, Excel, PowerPoint, Outlook, and Copilot Chat, bringing multi‑model intelligence into everyday workflows. Agent 365 makes this shift operational by giving organizations a way to observe, govern, and secure agents as they move from experimentation to enterprise‑scale use. Microsoft 365 E7 brings it all together by unifying productivity, AI, identity, and security into a single foundation.

Together, these changes make frontier transformation real: intelligence that understands the context of work, and trust that allows AI to scale safely across the workforce. When intelligence and trust move together, AI stops being an experiment and starts becoming how work gets done.

• Visit Microsoft365.com/copilot or download the Microsoft 365 app on your mobile device to get started.
• For the latest research and insights on AI at work, visit WorkLab.
• Learn from our engineering leaders how Microsoft delivers AI built for work at the Microsoft Frontier Transformation digital event on March 9, 2026, at 8:00 AM PT.

Footnotes

Microsoft 365 E7 is available with and without Teams.

¹IDC Info Snapshot, sponsored by Microsoft, 1.3 Billion AI Agents by 2028, May 2025 #US53361825

The post Powering Frontier Transformation with Copilot and agents appeared first on Microsoft Copilot Blog.

Microsoft Copilot Studio and Agent Builder in Microsoft 365 Copilot are designed to help customers reliably create agents that scale and deliver real, sustained business value—not just prototypes. Recent enhancements focus on making it easier to move from building an agent to running one confidently across complex, dynamic environments, with consistent quality and the ability to evolve as business needs change.

Discover the latest capabilities in agent evaluations, exciting updates for computer-using agents (including expanded model support), a new Agent Academy Operative training path, and more. Plus, learn how you can use these capabilities to help ensure your agents are ready for scale.

Build trust at scale with enhanced agent evaluations in Copilot Studio

Agents aren’t “set and forget.” Prompts evolve, models update, and data changes—which raises a critical question as agents take on real work: can we trust them at scale? Agent evaluations answer that question with evidence. They’re designed to turn expectations into measurable checks, help teams catch regressions early, and provide a repeatable way to assess agent quality as behavior and context evolve.

For example, a finance leader rolling out an agent for expense policy guidance or month‑end analysis needs to trust its behavior before moving beyond a pilot. With enhanced agent evaluations in Copilot Studio, teams can now validate performance using their own scenarios, policies, and production data—measuring quality, usability, and responsiveness across a full test set instead of isolated cases.

Side‑by‑side comparisons then help catch regressions before changes go live. Meanwhile, built‑in transparency and session replays support internal and external stakeholder review. The result is a clear, evidence‑based path from experimentation to trusted deployment.

Available in public preview, here’s a quick rundown of the latest eval enhancements.

Holistic and multi-dimensional agent evaluation

• Set-level grading framework: You can now evaluate agents across an entire test set instead of individual test cases, enabling an accurate measure of overall quality. By consolidating results from multiple tasks, makers can better understand real-world performance by seeing how agents maintain quality across a range of scenarios.
• Multiple graders per test set: With the ability to apply multiple grading approaches—such as quality, performance, and usability assessments—to the same test set, teams can gain a more complete evaluation without the complexity of managing separate test sets.
• Comparative testing: Teams can compare multiple agent versions side by side, which can make it easier to spot regressions and validate improvements before pushing the best version live.

Improved transparency and control

• User reactions and feedback: Makers can now provide quick feedback on evaluation results using a simple thumbs up or thumbs down action. This feedback helps Copilot Studio capture signals about evaluation accuracy, grader alignment, and edge cases, which means our team can continuously refine our evaluation models and improve result quality for agent makers.
• Open activity map in evaluation: Direct integration with the activity map gives teams immediate insight into how agents executed tasks, helping identify where issues occurred faster and improve optimization.
• Enterprise-grade auditing: Advanced session replays, action logs, and Microsoft Purview integration offer detailed visibility into agent behavior, helping makers preserve quality and streamline troubleshooting.

Streamlined workflow and data integration

• CSV downloadable format: Makers can now download a ready-to-use comma-separated values (CSV) template that follows the exact structure required for importing test cases into evaluation. Instead of creating files from scratch—and running into formatting errors, missing columns, or failed imports—teams can rely on a validated template that can help shorten setup time and remove unnecessary friction.
• Import production data into evaluation: Real-world production data can now be imported directly into evaluations, providing high-quality test sets that reflect actual user interactions. This is designed to improve evaluation accuracy and help makers tune agents more closely to their specific audiences.
• Import and export of test sets, test cases, and results: Makers can import or export test sets, individual test cases, and evaluation results. This helps simplify teamwork and support repeatable testing across environments—essentials for enterprise-scale agent development.

Scale automation across real-world systems with nimbler computer use

Most organizations don’t lack ideas for automation. Instead, the challenge tends to be with fragmented systems, limited APIs, legacy desktop tools, and workflows that go across multiple departments. Replacing everything isn’t realistic. But maintaining brittle, script-based automation isn’t sustainable either.

Copilot Studio’s computer-using agents (CUAs) can address this gap by interacting directly with web and desktop interfaces, supporting automation across systems that weren’t designed to integrate. They facilitate automation in complex, dynamic environments where traditional robotic process automation (RPA) falls short.

Consider a customer support organization handling service requests across disconnected systems. When a customer submits a support request, a computer-using agent can:

1. Retrieve customer and entitlement details from the customer relationship management (CRM) system.
2. Create or update a case in the service management system.
3. Pull relevant troubleshooting steps from a knowledge base.
4. Update the case status and resolution checklist in Microsoft SharePoint.
5. Notify the assigned service representative and escalate if service-level agreements (SLAs) are at risk.

This would be impossible with RPA alone because of the need to transcend systems. Although pieces could be automated, a person historically would need to initiate each step. With computer use, the organization can now accelerate this process and mitigate missed steps, without requiring a redesign of existing systems.

And the latest updates enhance the value of your computer-using agents, adding key capabilities that enable improved flexibility, security, and scalability:

• Expanded model availability: We’ve added Claude Sonnet 4.5 as an additional model choice for CUAs. You can choose between Anthropic models and OpenAI’s Computer-Using Agent to get the best possible results for your task.
• Built-in credentials: Simplify and secure authentication with built-in credentials that require minimal setup. Users simply input their username and password once, and Copilot Studio stores the credentials securely.
• Enterprise-grade logging and auditing: New monitoring tools, integrated with Microsoft Purview, enhance computer-using agent session visibility. This includes detailed logs of agent activity and session replays with screenshots that support traceability and compliance processes.
• Cloud PC pool: Powered by Windows 365 for Agents, this scalable, managed cloud infrastructure integrates with Microsoft Entra and Intune. These PC pools auto-scale based on workload demand, helping you handle spikes without over-provisioning.

We know the more tools that help drive operational efficiency while maintaining control over automated workflows, the more confident teams can be about adopting computer use. That’s why these updates help elevate computer-using agents as a more reliable, adaptable solution for enterprises looking to scale their use of agentic automation.

Learn to build multi-agent systems with the Agent Academy Operative path

Finished the Recruit training from the Copilot Studio Agent Academy and looking to go deeper? The new Operative path unlocks the next level of training for agent makers who are ready to build their skills. It’s designed for practitioners who already have their first agent working and want to expand their skills to build more sophisticated, production-ready solutions.

The Operative path walks learners through building a complex, multi-agent hiring automation system, using it as an applied learning example that can be adapted to any business scenario.

Along the way, participants develop critical skills such as writing clear and effective agent instructions, selecting and evaluating AI models, and applying advanced prompt patterns, agent flow integration, and Model Context Protocol (MCP). The curriculum also emphasizes operational readiness, including feedback loops, telemetry, and AI safety throughout the agent lifecycle.

By the end of the path, learners can gain a deeper understanding of how to design, build, and architect scalable multi-agent systems that can evolve with business needs. For creators ready to move from basic agents to more advanced, reliable solutions, the Operative path provides a practical and structured next step.

What else is new and improved in Copilot Studio

Now, let’s take a quick look at some other exciting updates—all generally available (GA)—that further enhance your Copilot Studio (and Agent Builder) experience:

• Copy agents from Agent Builder into Copilot Studio to scale impact: Agents that start as individual ideas in Agent Builder and prove team-wide value can now be opened directly in Copilot Studio for a more extensive maker experience. This unlocks advanced features such as topics, automations, expanded publishing channels, and enterprise governance controls, including data loss prevention and application lifecycle management. For example, a support representative’s personal helper agent can be expanded into a shared tool that categorizes tickets, suggests responses, and routes issues to the right specialists—without rebuilding from scratch.
• Query your agent inventory from Azure Resource Graph: The Microsoft Power Platform agent inventory, which organizes and displays all your published Copilot Studio and Agent Builder agents, is now generally available. Admins can query this inventory programmatically using Azure Resource Graph to access detailed data about both draft and published agents across the tenant, using Azure portal, CLI, PowerShell, or REST API.
• Generate icons for your agents using AI in Agent Builder: Makers can now generate custom agent icons directly in Agent Builder using AI. Instead of browsing or creating artwork manually, they simply describe how the icon should look—using the agent’s description or a custom prompt—and get a unique icon designed to stand out in the Agent Store.
• Try the Copilot Studio extension for Visual Studio Code: The Copilot Studio extension lets teams version, edit, and deploy agents directly from Visual Studio Code, making it easier to align with existing software development workflows.

The big takeaway: Stronger Copilot Studio tools for more scalable agent experiences

These updates aren’t just new features; they strengthen the tools teams rely on to create agents that scale with their business. By enhancing flexibility, security, and visibility, these updates are designed to make it easier to scale agents without starting over each time.

This continuity helps makers innovate quickly while IT teams maintain control over governance, compliance, and performance—bridging the gap between rapid iteration and enterprise-grade reliability. Why? Because at the end of the day, the best agents are those that are built to grow with your needs, and with these updates, that evolution becomes more attainable every month.

Stay up to date on all things Copilot Studio

Check out all the updates as we ship them, as well as new features releasing in the next few months here: What’s new in Microsoft Copilot Studio.

To learn more about Microsoft Copilot Studio and how it can transform productivity within your organization, visit the Copilot Studio website or sign up for our free trial today.

Create your next agent

Build, evaluate, manage, and scale custom agents—all in Copilot Studio.

Try Copilot Studio today

The post New and improved: Agent evaluations, computer use, and advanced maker training appeared first on Microsoft Copilot Blog.

As organizations move from early AI experiments to deploying agents at scale, they often ask: How do we architect agents responsibly, integrate them into existing systems, and run them reliably at scale?

To help teams like yours answer these complex questions faster and move with confidence, we’ve launched the new agent architecture guidance hub and a refreshed Microsoft Copilot Studio guidance hub. These on-demand resources offer end‑to‑end documentation across the agent lifecycle—from design and planning through operations, governance, and advanced architectural patterns.

Built on established practices from Microsoft engineering teams and real‑world deployments, these hubs give architects, developers, and IT a shared blueprint to work from. And they were designed to help your team make smarter architectural decisions, accelerate delivery with practical how‑to guidance, and scale safely with trusted governance, security, and responsible AI practices.

Whether you’re building your first agent or scaling across your enterprise, these hubs can help you start—and stay—on the right path.

Now, let’s explore what each hub offers and how to put them to work for your organization.

Build agents to fit your needs

Create, evaluate, manage, and scale custom agents—all in Microsoft Copilot Studio.

Try Copilot Studio today

Meet the new agent architecture guidance hub

The new agent architecture guidance hub is a technology‑agnostic playbook for designing secure, reliable, and accountable agents. Unlike the Copilot Studio guidance hub and Azure Well‑Architected guidance, this hub focuses on the principles and patterns required to build scalable agent systems—regardless of platform, tools, or runtime.

Grounded in the same practices Microsoft 365‑grade agents use, this hub distills lessons from real‑world deployments into a single source of truth. It provides clear answers to foundational architecture questions, such as how your agents should be structured, how they should run, and how they should be governed at scale.

Use the agent architecture guidance hub to:

• Identify fit for purpose by mapping your scenario to the right agent flows, components, and reference architectures.
• Design for operability by building reliability in from the start, using deployment lifecycle and evaluation guidance.
• Establish trust, traceability, and transparency through responsible AI practices, governance, auditability, and security practices.
• Optimize search and tool‑use patterns by adopting retrieval, grounding, and tool‑execution approaches used in Microsoft 365 Copilot.

Discover the redesigned Copilot Studio guidance hub

The reimagined Copilot Studio guidance hub is your end‑to‑end playbook for designing, building, and operating agents in Copilot Studio. Unlike architecture‑level resources, such as the agent architecture guidance, this hub focuses on hands‑on implementation—so makers, developers, and IT admins know exactly how to execute their work inside the product.

The newly reorganized and expanded hub now mirrors the full lifecycle of an agent. It’s built around five practical stages—Plan, Implement, Manage, Improve, and Extend—so your team can quickly find the right guidance at the right moment, whether you’re starting fresh or scaling an existing deployment:

• Stage 1: Plan. Align on business goals, define success measures, apply responsible AI considerations, and design effective language understanding before building anything. This helps to ensure every agent starts with a clear purpose, measurable outcomes, and a responsible foundation.
• Stage 2: Implement. Focus on the design and build work inside Copilot Studio. Learn generative orchestration patterns, build topics effectively, integrate systems and APIs, and publish agents with confidence using patterns established to work in production.
• Stage 3: Manage. Operate agents with governance, ALM, capacity planning, project security, testing guidance, and compliance best practices. This stage helps teams define the guardrails and decisions needed to maintain trust, reliability, and control over time.
• Stage 4: Improve. Center continuous optimization around analytics, KPIs, and conversation insights to drive measurable improvements in accuracy, containment, deflection, and user satisfaction—turning real usage data into targeted enhancements.
• Stage 5: Extend. Go beyond out‑of‑the‑box capabilities with hands‑on extension guidance. Use the Copilot Studio Kit and work with the Microsoft 365 Agents SDK to add custom logic, actions, and richer workflows tailored to your organization’s unique scenarios.

Together, these stages make this hub a practical, step-by‑step playbook for building agents in Copilot Studio that are useful, safe, and maintainable from day one—and that can scale as your needs grow.

Build agents with confidence

Successful agents require more than a powerful platform—you also need clearer choices, practical guardrails, and a way to spend less time reinventing the wheel. The new agent architecture guidance hub and Copilot Studio guidance hub (together with our other resources like the Copilot Studio adoption site and Copilot Studio community forum) make it easier to go from early experiments to confident, repeatable delivery.

Use the agent architecture guidance hub to clarify what to build and why. Then, turn to the Copilot Studio guidance hub when you’re ready to design, build, and operate those agents more effectively in Copilot Studio.

Whether you’re experimenting with your first agent or managing a collection of agents in Microsoft Copilot Studio, put these resources to work to make your next build easier, safer, and faster.

The post New resources and guidance to plan, build, and operate enterprise-ready agents appeared first on Microsoft Copilot Blog.

Today’s leading organizations are going through an agentic business transformation. This change takes AI from concept to measurable impact, by automating existing workflows and using agents to enhance productivity and reinvent entire functions. Copilot Studio, Copilot’s agent platform, provides a fully managed solution for accomplishing this.

Using Copilot Studio, organizations around the world can quickly bring the benefits of AI to their business. Copilot Studio empowers companies to streamline and automate their processes with agentic workflows, create single-purpose agents to solve specific problems, and develop multi-agent solutions that drive measurable business outcomes at scale. The result: a scalable, secure, and governable foundation that supports the needs of IT administrators and business owners measuring return on investment (ROI). This system accelerates agentic transformation by delivering speed-to-value without sacrificing quality or control.

Microsoft Copilot Studio

Discover practical resources, use cases, and community support to adopt and maximize Copilot Studio.

Get adoption resources

At the same time, with Microsoft 365 Copilot, users can easily use AI to improve their personal and team productivity. This tailored experience for Microsoft 365 Copilot users offers a fast, guided way to set up agents to support your work and automate everyday tasks, removing them from your plate.

Today, we’re excited to share new capabilities in Copilot Studio that support all of these scenarios and groups that use our product, making it easier for makers and administrators to shape agent behavior, enforce organizational standards, and extend functionality with AI.

End-user improvements

Our Copilot Studio experience for building agents and workflows, as well as our agent building capabilities in Microsoft 365 Copilot, continue to support agent creation for all users, from professional makers and IT administrators doing enterprise AI transformation, to employees building agents and workflows for their personal use. Recent updates focus on making the process simpler and more efficient.

What’s new in Microsoft 365 Copilot

• Redesigned creation experience: Build and refine agents through an improved conversational interface that guides users and taps into an expanded set of work-related knowledge sources.
• File generation with natural language: Agents built in Microsoft 365 Copilot, can now create Word, Excel, and PowerPoint files in seconds using natural language commands.
• Seamless upgrade path: Copy agents from Microsoft 365 Copilot to Copilot Studio in one click, unlocking advanced AI agent customization.
• Workflows agent in Microsoft 365 Copilot: Create, build, and manage workflows using natural language in chat. Boost productivity with quick scenarios like daily triage, weekly digests, and lightweight approvals—all directly within Copilot.

Maker improvements

IT application developers and other professional makers in the business can already build sophisticated agents in Copilot Studio without needing to code. Copilot Studio includes capabilities such as connecting and acting across more than 1,400 systems of record via Model Context Protocol (MCP), Power Platform connectors, and the Microsoft Graph. It also includes broad and deep tooling like autonomously writing and executing code, delivering rich out-of-the-box agent analytics and ROI measurement, and more, all built on the Microsoft governance and security platform. We’re excited to share new capabilities that give makers even more flexibility and control to design enterprise agents tailored to their unique organizational needs.

• Choose your own model: Select from leading options like OpenAI’s GPT‑5, Anthropic’s Sonnet 4.5, and Opus 4.1 to power your agents. This empowers you to tailor agent intelligence to fit your specific business scenario, optimize performance, experiment with new capabilities, and deliver agents that meet your organization’s unique needs.
• Ensure agents are ready for launch, and don’t regress over time, with Evaluations: Built-in evaluation tools help you test agents against real-world scenarios, compare versions, and track performance with clear metrics. Evaluations can give teams greater confidence that their investments are performing as expected.
• Computer use: Agents can now automate tasks across apps and websites, using secure Windows 365 experiences—from hosted browsers for quick web automation to IT-managed Cloud PC pools for rapid scalability.

Admin improvements

As agents become central to automating work and transforming workflows, Copilot Studio is introducing new governance and protection capabilities designed to help organizations maintain strong oversight.

• Expanded agent analytics: Clear insights into connected and child agent performance, detailed visibility into Copilot Credits usage and limits, AI-generated summaries of top analytics insights, and interrogating analytics using natural language.
• Real-time protection: Copilot Studio integrates with Microsoft Defender and other trusted security platforms, providing continuous monitoring and protection against threats like prompt injection—helping every agent run more safely.
• Microsoft Entra Agent ID: Every agent made in Copilot Studio now gets a unique Microsoft Entra Agent ID, making it simple to register, manage, and govern your entire agent fleet.

Agent 365 and Copilot Studio: Unified control for agents

Agents are handling more responsibilities across enterprise operations and Copilot Studio is your launchpad for building them. With the introduction of Agent 365—the control plane for agents, the rich governance and management capabilities we offer today including sharing controls, advanced connector policies, agent inventory, zoned environment management, and more, will also be surfaced in the Agent 365 platform when using agents built in Copilot Studio.

Additionally, in Copilot Studio, makers can now build agents that use the new Agent 365 MCP servers. These servers allow agents to schedule meetings in Microsoft Teams, draft documents in Word, send emails in Outlook, and update customer relationship management (CRM) records in Microsoft Dynamics 365. This supports delivery of intelligent, compliant workflows and agents with built-in audit trails and granular policy enforcement—all from one platform.

Agent 365 is available starting today in Microsoft 365 Admin Center with Frontier, Microsoft’s early access program for the latest AI innovations.

Scale to the Frontier Firm with control

True transformation happens when agents are built for scale, governed for compliance, and measured for impact. Copilot Studio delivers that foundation, so organizations can build enterprise multi-agent systems, automate workflows with precision, and reimagine processes while minimizing risk.

EY’s results show what’s possible when you invest in a comprehensive agent platform, built on Microsoft. They are just one of many enterprise organizations implementing agents with Copilot Studio. In this case, their PowerPost Agent built on Copilot Studio led to major improvements in journal processing:

• 95% reduction in lead time
• 37% cost savings¹

Implementing the PowerPost Agent with Microsoft Copilot Studio has fundamentally transformed our journal processing. What once took minutes now happens in seconds—streamlining workflows and improving accuracy.

—Paula Korczak, Product Manager for General Ledger, EY

That’s the difference between cobbling together siloed agent platforms versus investing in a managed scalable agent platform like Copilot Studio: agents and agented process design that is repeatable, auditable, and scalable.

Get started today

To learn more about Copilot Studio and how it can transform your organization’s productivity, visit the Copilot Studio website and sign up for a free trial today. Take the Agent Readiness Assessment to benchmark your organization’s agent maturity across five critical areas—strategy, data, process, culture, and security—and get a personalized report to accelerate scalable agent adoption and drive agentic business transformation.

Want to explore all of Copilot Studio’s adoption content? Visit the Copilot Studio adoption page.

¹ EY redesigns its global finance process with Microsoft Power Platform

The post Why Microsoft Copilot Studio is the foundation for agentic business transformation appeared first on Microsoft Copilot Blog.

In this edition of our monthly roundup, we’re recapping the most exciting new features Microsoft Copilot Studio released in October 2025.

Build and optimize agents

Validate agents at scale with evaluations for automated testing

Agent quality just became significantly easier to measure and improve. With the automated agent evaluation experience, now available in public preview, makers can systematically test and validate their Copilot Studio agents at scale. Instead of running scenarios one by one, they can build and execute evaluation sets directly from the agent or the Test Pane, delivering structured, repeatable insights both before and after publishing.

This new experience offers flexibility in how evaluation sets are created. Makers can upload files with predefined questions and answers, reuse recent Test Pane queries, add cases manually, or instantly generate queries using AI. This approach ensures that test coverage spans organization-specific scenarios while also incorporating AI-suggested questions based on agent metadata and topics, providing a comprehensive view of performance.

Evaluations are powered by a robust grader framework that gives makers control over how accuracy is measured. Options range from strict checks such as Exact Match and Partial/Contains, to semantic comparisons like Similarity and Intent Match, and even AI-powered metrics including relevance, completeness, and groundedness. Each test delivers clear pass/fail results, detailed scores, and drill-down views into the knowledge and topics used.

For cases where reference answers are critical, makers can define expected responses manually or upload them in bulk, ensuring evaluations remain precise, transparent, and aligned with business expectations. AI further the Analytics tab in Copilot Studio accelerates validation by automatically generating test sets that can be executed immediately with AI metrics graders or combined with manual and uploaded sets for broader coverage.

These capabilities introduce a scalable, repeatable framework for agent quality, helping teams identify gaps early, reduce surprises in production, and track improvements over time. While multi-turn testing and additional graders are on the roadmap, this public preview represents a major leap forward in automated validation. 

Evaluations are available now in public preview. You can access them from the agent or test pane by selecting Evaluation.

Build with the latest OpenAI models in Copilot Studio

Copilot Studio continues to evolve with new model updates that improve performance and expand flexibility for makers. Depending on use case and application, different models may provide better responses to users. We’re committed to providing model choices that work for your business processes.

Starting October 27, 2025, GPT-4.1 became the default model for all newly created agents, replacing GPT-4o. Testing shows meaningful gains in both latency and response quality, helping agents deliver faster, more consistent results. GPT-4o will remain available through November 26, 2025, and agents in production will continue to leverage this model until then. However, you can update the model and opt in to GPT-4.1 today through the model-selection experience.

In addition, Copilot Studio is expanding availability of the GPT-5 family of models, first introduced in August 2025. Makers can now use GPT-5 Auto, GPT-5 Chat, and GPT-5 Reasoning not only in test environments but also in deployed agents. These models bring enhanced reasoning, richer dialogue capabilities, and more flexible problem-solving for complex scenarios. Please note that GPT-5 models remain in public preview and are not yet recommended for production use.

Together, these updates give makers access to the latest OpenAI advancements while maintaining continuity for existing agents. You continue to have top model choice at your fingertips to help create and deploy more accurate and effective agents at scale.

Speed up agent flow execution with express mode

Flow execution just got faster in Copilot Studio. Express mode, now in preview, optimizes agent flows to increase the likelihood that they’ll finish the flow within two minutes. This avoids agents or apps timing out while they wait for a response.

Express mode works best in flows that are logic-heavy but data-light. It limits flows to under 100 actions and smaller payloads so that the entire execution is more streamlined. For scenarios where large data sets needs to be moved or loops occur to iterate over large arrays, makers should test both with and without express mode.

This feature is in public preview and on by default. You can find the express mode toggle located on the flow’s Overview page in the editor.

Enable file uploads in omnichannel conversations

Copilot Studio now supports file uploads for custom agents in omnichannel scenarios. This means users can share images, documents, and other supported file types directly during agent interactions. This enhancement makes conversations more dynamic and context-rich by letting customers provide relevant files like receipts, forms, or photos right in the chat.

By enabling end user file uploads, agents can analyze attachments in real-time and deliver more accurate, personalized responses. This is a critical capability for customer service and contact center scenarios, where exchanging documents or screenshots is often key to resolving issues quickly. The feature also unlocks richer use cases for image analysis and document-based reasoning, improving both response quality and customer satisfaction.

File upload support is enabled by default for omnichannel custom agents, with optional controls available for agent makers to restrict supported file types in the agent manifest. All file types supported by Microsoft 365 Copilot are allowed up to 5MB (unless admins add restrictions).

This update enhances both the maker and end-user experience, and brings a richer more comprehensive level of service for end users relying on the agent for support.

Access external files and data with Model Context Protocol resources

Copilot Studio now supports Model Context Protocol (MCP) resources, expanding what agents can do with existing MCP connections. Makers have been able to use MCP tools to trigger actions and retrieve information. Now with resources support in preview, agents can read external content like files, API responses, or database records directly through MCP. This brings richer, real-time context into every interaction.

MCP resources act as file-like data objects that agents can query and reference during conversations. This allows agents to access customer-specific or system-specific content dynamically, without manual updates or re-training. For example, an agent could read the latest policy document stored in an MCP resource, summarize an uploaded file, or use current data from an API—securely and in context.

This enhancement builds upon the existing MCP integration in Copilot Studio, supporting deeper connections between agents and the systems they support. MCP resources are available now in public preview and are on by default for supported environments.

Measure and improve performance

Measure the return on investment (ROI) for conversational agents

Organizations can now view the ROI of conversational agents in Copilot Studio to calculate how much time and money the agent saves compared to other methods. Already available for autonomous agents, this enhancement, now generally available, gives teams a unified view of how all agent types drive direct business impact.

From the Analytics tab, makers can configure savings settings for each agent. This is where you define how much time or cost is saved per interaction or workflow. Copilot Studio then aggregates these metrics automatically. The resulting ongoing view helps quantify the business value agents deliver through reduced manual effort, faster resolutions, or process efficiencies.

By expanding savings analytics to include conversational agents, Copilot Studio helps organizations evaluate agent performance and impact consistently across their agent portfolio. With this capability, right inside the Analytics tab in Copilot Studio, makers can make data-driven decisions about where to invest and improve.

Analyze user questions by theme

Copilot Studio now helps makers understand agent performance by intelligently and automatically grouping user questions into themes. The themes give you category-level insights into customer intent and frequent topics, with a more manageable number of groups.

In the Themes list, you can see key metrics such as question volume, response rate, and user satisfaction. This at-a-glance overview makes it easier to see which topics your agent handles well and focus on areas where it may need refinement. Makers with the appropriate permissions can also drill down into each theme to review specific user questions, agent responses, and related metrics. This deeper visibility helps identify patterns in user intent, uncover gaps in coverage, and guide targeted improvements to knowledge and content.

The feature is automatically available for agents that use generative answers and have received at least 50 user questions within the past seven days. Once enabled, insights appear directly in the analytics dashboard, no further setup is required.

By organizing user questions into themes, Copilot Studio gives makers a clearer view of what customers are asking for and how effectively agents are responding. This helps the team continuously improve agent responses for their customers by making data backed improvements to their knowledge sources.

Test and debug faster with an improved activity map

Test and troubleshoot Copilot Studio agents faster and more intuitively, thanks to a series of updates to the activity map and testing experience. These enhancements create a more cohesive view of how agents reason over data and user queries to respond. That, in turn, helps makers debug efficiently and refine performance with less context switching.

Makers can now view the transcript and activity details together, eliminating the need to toggle between separate views. This unified view provides a clearer picture of how each session unfolds, drawing from user input through the agent’s reasoning and response generation. The updated layout also lets makers pin sessions, adjust visible columns, and submit feedback on session details directly to Microsoft—improving collaboration and visibility.

It is now easier then ever to navigate activity data, understand the agent’s chain of thought, and connect analytics insights to individual sessions for deeper evaluation. These enhancements are generally available, with continued refinements releasing progressively across environments.

Manage and govern at scale

Control org-wide sharing of agents in Copilot Studio lite

A new admin control in the Microsoft 365 Admin Center, now generally available, gives organizations stronger governance over how agents created in Microsoft 365 Copilot are shared across the tenant. Admins can now restrict or disable organization-wide sharing of agents built in Copilot Studio lite (formerly known as the agent builder). This ability helps prevent oversharing while supporting safe adoption at scale.

From within the Microsoft 365 Admin Center go to Copilot > Settings > Data Access > Agents page, admins can choose who is allowed to share agents with the entire organization: all users (default), no users, or specific users and groups. When you place restrictions on sharing, the “Anyone in your organization” option in the agent-sharing dialog is disabled. Makers can see a tooltip explaining the policy. Existing access remains unchanged, but makers must comply with the defined settings before updating or broadening sharing.

This control helps ensure that agent collaboration aligns with organizational policies and regulatory requirements. This is particularly important for organizations in spaces like finance, healthcare, and government. By bringing this configuration directly into the Microsoft 365 Admin Center, admins can manage agent governance alongside other Microsoft Copilot and AI settings, simplifying oversight and reducing risk.

Stay up to date on all things Copilot Studio  

Check out all the updates live as we ship them, as well as new features releasing in the next few months here: What’s new in Microsoft Copilot Studio. 

To learn more about Microsoft Copilot Studio and how it can transform your organization’s productivity, visit the Copilot Studio website or sign up for our free trial today.

Microsoft Copilot Studio

Design and scale custom agents to transform your business.

Try Copilot Studio today

The post What’s new in Copilot Studio: October 2025 appeared first on Microsoft Copilot Blog.