Microsoft Copilot Studio Platform - Build 2026.6.2

This article describes the fixes and improvements to existing functionality that are included in this build.

Visit the Microsoft Copilot Studio Blog to stay up-to-date on the latest news!

Version 2026.6.2 updates

Streaming responses can resume after a disconnect and replay missed events when clients reconnect using the Last-Event-Id header.
Per-agent control to require consent cards for AI prompts, independent of connector and flow consent settings.
Analytics enhancements: Maker Evaluation can return per-test set summaries in one call, and end-user message feedback (reactions) is now included in summary reporting for enhanced task completion enabled agents.
Connector actions now surface key details, including whether user approval is required, authentication type, how inputs are filled (custom or automatic), and the connection name.
Breaking changes: Agent identity migration can provision a new identity to support safer rebinding and no longer accepts customer-supplied agent identity identifiers.

Continued improvements to performance and reliability.
Publishing and lifecycle enhancements, including clearer, actionable validation errors and prevention of duplicate skill names during publishing.
Analytics accuracy and experience improvements across evaluation summary formulas (aligned with UI), query end-time boundaries, authentication stability, and standardized connector endpoints.
Tooling and connector usability improvements, including parameter hints in tool schemas, correct handling of nested input-filling settings, and reliable retries using service-to-service authentication when on-behalf-of calls are blocked.
Operational robustness and governance improvements, including automatic detection and deprovisioning of orphaned agents, resilient background job retries, successful un-deploy when SharePoint files are already deleted, Dataverse knowledge source governance connection handling, and reliable cache refresh behavior with empty responses.
Improved localization for user interface and error messages across multiple languages.

Enforced sharing permissions: sharing a connection now requires share permissions, and attempts to share a view-only connection are blocked with a clear access-denied error.
Information Barriers compliance: publishing and sharing are correctly blocked when agents have embedded knowledge files that have already finished syncing.
Government Community Cloud (Government First Release): token acquisition uses federated identity credentials by default to reduce manual configuration.
Greater transparency and control: connector actions clearly indicate approval requirements and authentication details; per-agent consent card requirements can be configured for AI prompts.
Privacy by default for voice scenarios: voice-enabled agents connected to Omnichannel include a consent-based recording template by default.