Skip to content

Clarify authentication options for agent applications #611

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+7 −3
Open

Clarify authentication options for agent applications #611

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions articles/ai-foundry/default/agents/how-to/publish-agent.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,12 +116,16 @@ Foundry agents can also expose the [Activity Protocol](https://github.com/micros
For applications this is exposed at: https://{accountName}.services.ai.azure.com/api/projects/{projectName}/applications/{applicationName}/protocols/activityprotocol

### Authentication
There are two options for inbound end-user authentication that can be configured on the application:
- Default: The caller must have the Azure RBAC (Role-Based Access Control) permission /applications/invoke/action on the application resource.

Inbound end-user authentication for the application is configured as follows:
- Default: The caller must have the Azure RBAC (Role-Based Access Control) permission /applications/invoke/action on the application resource.

API key authentication is not supported for agents through projects or through applications.

<!--
- Channels (Azure Bot Service): Requests from a linked Azure Bot Service instance are permitted. This is used for M365 and Agent365 integration, and for scenarios where an upstream service interacts with the application through Activity Protocol.
-->
API key authentication is not supported for agents through projects or through applications.


## Publish an agent

Expand Down