Copilot Studio approval flow in Teams still prompts users for connection despite using flow author credentials
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
- Ambito
- authentication, cloud
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
- 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
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/CopilotStudioSamples
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Issue: SharePoint SSO ComponentForse già presa @adilei l’ha presa 25 giorni fa. ApertaSharePointSSOComponent
microsoft/CopilotStudioSamples#537 · 1 assegnatario ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
microsoft/CopilotStudioSamples#532 · 1 commento ·
-
Unable to Deploy SPFx Agent to a Single SharePoint Site (Works Only with Tenant-Wide Deployment)Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
microsoft/CopilotStudioSamples#531 · 1 commento ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
Tutte le issue di microsoft/CopilotStudioSamples
Issue simili
-
module-request
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
ports get and web print 'Port N already in use, trying next...' for every busy port they skipAperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
appandflow/stim#1604 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
lingdojo/kana-dojo#31060 · 1 commento · 5 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
SSH workspace restore rewrites relative symlinks into the deleted sync-back staging directoryAperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
paperclipai/paperclip#14173 ·
I maintainer di solito rispondono entro 1 giorno
-
needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno