Using a single Copilot Studio agent in both Microsoft Teams and iFrame without repeated manual authentication

Question

Details

I am using Microsoft Copilot Studio to build an agent that needs to be consumed in two channels:

Microsoft Teams

A web application using iFrame (embedded chat)

Current behavior / limitation

If No authentication is selected:

The agent works correctly in iFrame

  ❌ The agent **cannot be used in Microsoft Teams**
  
  If **Authentication is enabled**:
  
     The agent works in **Microsoft Teams**
     
        For **iFrame**, authentication is required
        

Manual authentication scenario

When using Manual authentication (Client ID + Client Secret):

In the agent chat, a Sign in button is shown

Clicking it opens a new page

The user must:

Copy the authentication code

  Paste it back into the agent chat
  
  Only after this step, the conversation can continue
  

This flow works, but it is not user-friendly, especially for:

Repeated sessions

iFrame-embedded chat experiences

Non-technical end users

Problem statement

I need:

One Copilot Studio agent

That works in both Microsoft Teams and iFrame

Without requiring users to copy-paste authentication codes repeatedly

Preferably with SSO or silent authentication where possible

Questions

1. Is it currently possible to configure a Copilot Studio agent that works in both Teams and iFrame with a single authentication setup?

Are there any recommended authentication patterns (Entra ID, OAuth, SSO, token exchange, etc.) to avoid the manual copy-paste authentication flow?

Is this a known limitation of Copilot Studio channels, or is there a planned improvement on the roadmap?

Any official guidance or best-practice recommendation would be very helpful.

Details

I am using Microsoft Copilot Studio to build an agent that needs to be consumed in two channels:

Microsoft Teams

A web application using iFrame (embedded chat)

Current behavior / limitation

If No authentication is selected:

The agent works correctly in iFrame

  ❌ The agent **cannot be used in Microsoft Teams**
  
  If **Authentication is enabled**:
  
     The agent works in **Microsoft Teams**
     
        For **iFrame**, authentication is required
        

Manual authentication scenario

When using Manual authentication (Client ID + Client Secret):

• In the agent chat, a Sign in button is shown
• Clicking it opens a new page
• The user must:
  1. Copy the authentication code
  2. Paste it back into the agent chat
• Only after this step, the conversation can continue

This flow works, but it is not user-friendly, especially for:

Repeated sessions

iFrame-embedded chat experiences

Non-technical end users

Problem statement

I need:

One Copilot Studio agent

That works in both Microsoft Teams and iFrame

Without requiring users to copy-paste authentication codes repeatedly

Preferably with SSO or silent authentication where possible

Questions

Is it currently possible to configure a Copilot Studio agent that works in both Teams and iFrame with a single authentication setup?

Are there any recommended authentication patterns (Entra ID, OAuth, SSO, token exchange, etc.) to avoid the manual copy-paste authentication flow?

Is this a known limitation of Copilot Studio channels, or is there a planned improvement on the roadmap?

Any official guidance or best-practice recommendation would be very helpful.

Answer 1

Hello Vikas Bij,
No — today it is not possible to configure one Copilot Studio agent that simultaneously:

• Works in Microsoft Teams (which requires authentication), AND
• Works in an iFrame without manual sign‑in / copy‑paste flow

using a single authentication setup.

This is due to architectural differences between:

• The Teams channel (supports Microsoft 365 SSO, token exchange, Teams identity)
• The Web/iFrame channel (does not yet support silent SSO or Teams token bridging)

Right now, the only available authentication mode for iFrame is manual OAuth device‑code flow, which requires users to copy/paste an authentication code.

This is a known platform limitation and is on Microsoft’s internal backlog, but no public ETA is available yet.

**Update:
**Thank you for your patience! We have reported this as a bug for further investigation. 

We will keep you updated as soon as we receive further information. Thank you for bringing this to our attention!