Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Copilot Studio approval flow in Teams still prompts users for connection despite using flow author credentials

Aperta
#430 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Ferma

Direzione di ricerca

Non sono stati identificati file del repository, test o punti di ingresso; inizia riproducendo il flusso tramite Copilot Studio in Teams e confrontalo con un’esecuzione manuale di Power Automate. Il lavoro sarà completo quando sarà determinato se la richiesta di connessione è una limitazione documentata o un difetto e sarà identificato un approccio supportato per le credenziali dell’autore.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

I am facing an issue while using Copilot Studio with a Power Automate flow that includes Approvals in Microsoft Teams.

Scenario

The flow is triggered from a Copilot Studio agent.
The flow contains a Teams approval (Standard Approvals) action.
Under Run-only permissions, I have configured:
✅ Use flow author’s connection for new actions
✅ For Connections Used → Standard approvals, selected Use this connection (Standard approvals)
The flow owner (author) has a valid and active connection.
End users should not be required to authenticate or provide their own connections.

Expected Behavior

When the flow runs from Copilot Studio:
The approval request should be created and sent using the flow author’s credentials
Users interacting with the Copilot should not be prompted to sign in or manage connections

Actual Behavior

When the flow reaches the Approval step, it redirects to Connection Manager
Users are prompted to authenticate or are blocked due to missing permissions
This happens even though the flow is explicitly configured to use the author’s connection

Additional Notes

This issue occurs specifically when the flow is executed via Copilot Studio (Teams channel, M365 Chat)
The same flow works correctly when triggered manually from Power Automate
The problem appears to be related to how Copilot Studio handles approval connectors and run-only connections

Impact

This blocks production usage because:
End users should not be asked to authenticate
The agent is intended to run using service/author credentials only

Request

Please clarify:
Whether this is a known limitation or bug in Copilot Studio approvals
If there is a recommended or supported approach to ensure approvals always use the flow author’s credentials
Whether a service principal or alternative approval pattern is required for Copilot StudioI am facing an issue while using Copilot Studio with a Power Automate flow that includes Approvals in Microsoft Teams.

Scenario

The flow is triggered from a Copilot Studio agent.
The flow contains a Teams approval (Standard Approvals) action.
Under Run-only permissions, I have configured:

✅ Use flow author’s connection for new actions
✅ For Connections Used → Standard approvals, selected Use this connection (Standard approvals)

The flow owner (author) has a valid and active connection.
End users should not be required to authenticate or provide their own connections.

Expected Behavior

When the flow runs from Copilot Studio:
The approval request should be created and sent using the flow author’s credentials
Users interacting with the Copilot should not be prompted to sign in or manage connections

Actual Behavior

When the flow reaches the Approval step, it redirects to Connection Manager
Users are prompted to authenticate or are blocked due to missing permissions
This happens even though the flow is explicitly configured to use the author’s connection

Additional Notes

This issue occurs specifically when the flow is executed via Copilot Studio (Teams channel)
The same flow works correctly when triggered manually from Power Automate
The problem appears to be related to how Copilot Studio handles approval connectors and run-only connections

Impact

This blocks production usage because:
End users should not be asked to authenticate
The agent is intended to run using service/author credentials only

Request

Please clarify:
Whether this is a known limitation or bug in Copilot Studio approvals
If there is a recommended or supported approach to ensure approvals always use the flow author’s credentials

Image Image Image
Lingua principale
TypeScript
Stelle
797
Fork
491
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Non abbiamo ancora controllato i file di configurazione di questo progetto. Parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/CopilotStudioSamples

Tutte le issue di microsoft/CopilotStudioSamples

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.