Copilot & AI
How does authentication work in Copilot Studio?
Quick answer
Authentication in Copilot Studio has two halves. End-user authentication signs the person in — typically Microsoft Entra ID on Teams and web channels — so knowledge retrieval respects what that user may access. Action authentication covers what the agent touches: Power Automate flows and connectors run under configured connection identities with their own credentials and consent. Production design means choosing per-action identities deliberately, scoping least privilege, and testing every path as a non-maker user.
Key takeaways
- Users authenticate via Entra ID; actions run under connection identities.
- Knowledge trimming follows the signed-in user where supported.
- Service-owned identities survive staff departures.
Detailed Explanation
Authentication in Copilot Studio has two halves. End-user authentication signs the person in — typically Microsoft Entra ID on Teams and web channels — so knowledge retrieval respects what that user may access. Action authentication covers what the agent touches: Power Automate flows and connectors run under configured connection identities with their own credentials and consent. Production design means choosing per-action identities deliberately, scoping least privilege, and testing every path as a non-maker user.
Limitations and considerations
Anonymous channels weaken user-scoped enforcement — never attach sensitive knowledge or privileged actions to them. Connection-owner departures silently break actions; service-owned identities prevent it.
This Q&A page is the short-answer layer for “How does authentication work in Copilot Studio?” Use the related guides below when you need implementation steps, architecture trade-offs, or troubleshooting detail.
For broader context, visit the Copilot Studio Hub. It connects this topic to surrounding Microsoft 365, Power Platform, SharePoint, Copilot Studio, Dataverse, migration, and Dynamics 365 guidance.
When to use it
Map authentication before publishing: which channels sign users in, which knowledge is user-trimmed, and which identity each action runs under.
Practical example
An HR agent on Teams authenticates employees via Entra ID for salary-policy answers, while its ticket-creation flow runs under a service identity that can write to the HR system.
Related Questions
Related nextM365 Guides
Sources
- Microsoft Learn: Copilot Studio documentation, Microsoft
- Microsoft Learn: Fundamentals Get Started, Microsoft
- Microsoft Learn: Microsoft Copilot Studio, Microsoft
- Microsoft Learn: Copilot Studio, Microsoft
- Microsoft Learn: Security And Governance, Microsoft