Skip to content

Commit 87d0f3a

Browse files
Merge pull request #1999 from aahill/agents
updating agents article
2 parents 2e6836c + 45a03e6 commit 87d0f3a

File tree

1 file changed

+7
-15
lines changed
  • articles/ai-services/agents/concepts

1 file changed

+7
-15
lines changed

articles/ai-services/agents/concepts/agents.md

Lines changed: 7 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -24,42 +24,34 @@ Azure AI Agent Service is now available in public preview. The service makes it
2424

2525
Previously, building custom AI agents needed heavy lifting even for experienced developers. While many APIs are lightweight and powerful like Azure OpenAI's chat completions API, it's inherently stateless which means that developers had to manage conversation state and chat threads, tool integrations, retrieval documents and indexes, and execute code manually.
2626

27-
Azure AI Agents Service, as the evolution of the chat completion API and Assistants, provides a solution for these challenges. Agents support persistent automatically managed threads. This means that as a developer you no longer need to develop conversation state management systems and work around a model’s context window constraints. Agents will automatically handle the optimizations to keep the thread below the max context window of your chosen model. Once you create a thread, you can append new messages to it as users respond. Agents can also access multiple tools in parallel, if needed. These tools include:
27+
Azure AI Agents Service, as the evolution of the chat completion API and Assistants, provides a solution for these challenges. Agents support persistent automatically managed threads. This means that as a developer you no longer need to develop conversation state management systems and work around a model’s context window constraints. Agents will automatically handle the optimizations to keep the thread below the max context window of your chosen model. Once you create a thread, you can append new messages to it as users respond. Agents can also access multiple [tools](../how-to/tools/overview.md) in parallel.
2828

29-
- [Code Interpreter](../how-to/tools/code-interpreter.md)
30-
- [Function calling](../how-to/tools/function-calling.md)
31-
- [Grounding with Bing](../how-to/tools/bing-grounding.md)
32-
33-
Azure AI Agents Service is built on the same capabilities that power Azure OpenAI's assistants. Some possible use cases range from AI-powered product recommender, sales analyst app, coding assistant, employee Q&A chatbot, and more. Start building on the no-code agents playground on the Azure AI Studio or start building with the API using the [quickstart](../quickstart.md).
29+
Azure AI Agents Service is built on the same capabilities that power Azure OpenAI's assistants. Some possible use cases range from AI-powered product recommender, sales analyst app, coding assistant, employee Q&A chatbot, and more.
3430

3531
> [!IMPORTANT]
36-
> Retrieving untrusted data using Function Calling, Code Interpreter or File Search with file input, and agent threads functionalities could compromise the security of your agent, or the application that uses the agent. Learn about mitigation approaches [here](https://aka.ms/oai/assistant-rai).
37-
38-
## Agents playground
39-
40-
We provide a walkthrough of the agents playground in our [quickstart guide](../quickstart.md). This provides a no-code environment to test out the capabilities of agents.
32+
> Retrieving untrusted data using Function Calling, Code Interpreter or File Search with file input, and agent threads functionalities could compromise the security of your agent, or the application that uses the agent.
4133
4234
## Agents components
4335

4436
<!-- :::image type="content" source="../media/agents/agents-overview.png" alt-text="A diagram showing the components of an agent." lightbox="../media/agents/agents-overview.png"::: -->
4537

4638
| **Component** | **Description** |
4739
|---|---|
48-
| **Agent** | Custom AI that uses Azure OpenAI models in conjunction with tools. |
40+
| **Agent** | Custom AI that uses models in conjunction with tools. |
4941
|**Thread** | A conversation session between an agent and a user. Threads store Messages and automatically handle truncation to fit content into a model’s context.|
5042
| **Message** | A message created by an agent or a user. Messages can include text, images, and other files. Messages are stored as a list on the Thread. |
5143
|**Run** | Activation of an agent to begin running based on the contents of the Thread. The agent uses its configuration and the Thread’s Messages to perform tasks by calling models and tools. As part of a Run, the agent appends Messages to the Thread.|
5244
|**Run Step** | A detailed list of steps the agent took as part of a Run. An agent can call tools or create Messages during it’s run. Examining Run Steps allows you to understand how the agent is getting to its final results. |
5345

5446
## Agents data access
5547

56-
Currently, agents, threads, messages, and files created for agents are scoped at the Azure OpenAI resource level. Therefore, anyone with access to the Azure OpenAI resource or API key access is able to read/write agents, threads, messages, and files.
48+
Currently, agents, threads, messages, and files created for agents are scoped at the resource level. Therefore, anyone with access to the resource or API key access is able to read/write agents, threads, messages, and files.
5749

5850
We strongly recommend the following data access controls:
5951

6052
- Implement authorization. Before performing reads or writes on agents, threads, messages, and files, ensure that the end-user is authorized to do so.
61-
- Restrict Azure OpenAI resource and API key access. Carefully consider who has access to Azure OpenAI resources where agents are being used, and the associated API keys.
62-
- Routinely audit which accounts/individuals have access to the Azure OpenAI resource. API keys and resource level access enable a wide range of operations including reading and modifying messages and files.
53+
- Restrict resource and API key access. Carefully consider who has access to resources where agents are being used, and the associated API keys.
54+
- Routinely audit which accounts/individuals have access to the resource. API keys and resource level access enable a wide range of operations including reading and modifying messages and files.
6355
- If you're using Azure OpenAI models, enabling [diagnostic settings](../../openai/how-to/monitor-openai.md#configure-diagnostic-settings) to allow long-term tracking of certain aspects of the Azure OpenAI resource's activity log.
6456

6557
## Parameters

0 commit comments

Comments
 (0)