MC1548034: Copilot Studio Adds In‑Conversation Setup for Third‑Party Agent Connections

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
55
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Microsoft 365 AdminsPower Platform AdminsDevelopersIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This is a planned feature reaching general availability by the end of 2026 that changes how Copilot Studio agents manage third-party connections. Admins may need to review connector and connection policies and update custom web UI implementations using the Standard harness. Users will see a more integrated setup flow within conversations, but workflow disruption is limited. The main work lies with developers and admins configuring or maintaining custom agents.
58
🛡️ Admin Impact
46
👥 User Impact
55
⚡ Urgency
60
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Copilot Studio chats will soon support setting up third-party service connections without leaving the conversation. This simplifies connecting agents and reduces user interruptions.
👥

END USERS

Users may see a new in-chat setup flow when connecting agents to third-party services.
🛡️

IT ADMINS

Review connector access controls and inform users and support teams about the new connection process before general availability.
📅

ROLLOUT TIMELINE

Upcoming:
By Dec 2026

📢 Official Microsoft Message Center Announcement


Copilot Studio – Set up third-party agent connections in conversations
Message ID: MC1548034
We are announcing improvements to the experience of setting up connections in chats with Copilot Studio agents. These improvements will reach general availability by December 31, 2026.

How does this affect me?
Previously, users needed to leave their conversation, go to a separate connection-management experience, complete setup, and then restart their interaction. This feature is introducing a more seamless way for users to connect agents to third-party services. When an agent requires a connection, users will be guided through a focused setup experience without leaving the conversation or being redirected to the full connection-management portal. When possible, the agent will reuse an existing valid connection.

With this update:
  • Users can establish a required third-party connection from their agent conversation.
  • Users complete only the setup required for the service they are using.
  • Users return directly to the conversation after connecting.
  • An eligible existing connection can be reused instead of configuring another connection.
  • Users can continue working with connected agents across Microsoft Copilot, Microsoft Teams, and Web Chat.
  • Existing organizational controls that govern which connectors and connections users can access will continue to determine availability.
Please note that developers of agents published through a custom web UI using the Standard harness will be required to make changes to support the new connection experience.

What action do I need to take?
To prepare for this change, we recommend that you:
  • Inform support teams and agent users about the improved connection experience.
  • Review your existing organizational controls for connectors and connections.
For agents published through a custom web UI using the Standard harness, update your implementation to:
  • Open the new connection window.
  • Continue the conversation after connection setup succeeds.
If you would like more information on this feature, please visit Support connection setup in a custom canvas.

Source: Microsoft Message Center • Analysed by MWPro