You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/ai-services/agents/concepts/agents.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,9 +24,9 @@ Azure AI Agent Service is now available in public preview. The service makes it
24
24
25
25
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.
26
26
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.
27
+
Azure AI Agent 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.
28
28
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.
29
+
Azure AI Agent 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.
30
30
31
31
> [!IMPORTANT]
32
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.
@@ -75,7 +75,7 @@ When using the File Search tool, we recommend setting the `max_prompt_tokens` to
75
75
76
76
## Truncation strategy
77
77
78
-
You can also specify a truncation strategy to control how your thread should be rendered into the model's context window. Using a truncation strategy of type `auto` will use OpenAI's default truncation strategy. Using a truncation strategy of type `last_messages` will allow you to specify the number of the most recent messages to include in the context window.
78
+
You can also specify a truncation strategy to control how your thread should be rendered into the model's context window. Using a truncation strategy of type `auto` will use Azure OpenAI's default truncation strategy. Using a truncation strategy of type `last_messages` will allow you to specify the number of the most recent messages to include in the context window.
79
79
80
80
## See also
81
81
* Learn more about [agents](../overview.md). <!--and [File Search](../how-to/tools/file-search.md)-->
Copy file name to clipboardExpand all lines: articles/ai-services/agents/concepts/model-region-support.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,11 +13,11 @@ ms.custom: azure-ai-agents
13
13
14
14
# Models supported by Azure AI Agent Service
15
15
16
-
Agents are powered by a diverse set of models with different capabilities and price points. Model availability varies by region and cloud. Certain tools and capabilities require the latest models. The following models are available in the available SDKs. The following table is for pay-as-you-go. For information on Provisioned Throughput Unit (PTU) availability, see [provisioned throughput](../../openai/concepts/provisioned-throughput.md) in the OpenAI documentation. You can use [global standard models](../../openai/concepts/models.md#global-standard-model-availability) if they're supported in the regions listed here.
16
+
Agents are powered by a diverse set of models with different capabilities and price points. Model availability varies by region and cloud. Certain tools and capabilities require the latest models. The following models are available in the available SDKs. The following table is for pay-as-you-go. For information on Provisioned Throughput Unit (PTU) availability, see [provisioned throughput](../../openai/concepts/provisioned-throughput.md) in the Azure OpenAI documentation. You can use [global standard models](../../openai/concepts/models.md#global-standard-model-availability) if they're supported in the regions listed here.
17
17
18
18
## Azure OpenAI models
19
19
20
-
Azure AI Agent service supports the same models as the chat completions API in Azure OpenAI, in the following regions.
20
+
Azure AI Agent Service supports the same models as the chat completions API in Azure OpenAI, in the following regions.
In addition to the supported Azure OpenAI models, you can also use the following 3rd party models with Azure AI Agent Service.
33
+
The Azure AI Agent Service also supports the following models from the Azure AI Foundry model catalog.
34
34
35
35
* Llama 3.1-70B-instruct
36
36
* Mistral-large-2407
37
37
* Cohere command R+
38
38
39
39
To use these models, you can use Azure AI Foundry portal to make a deployment, and then reference it in your agent.
40
40
41
-
1. Go to the [Azure AI Foundry portal](https://ai.azure.com/) and select **Model catalog** in the left navigation menu, and scroll down to **Meta-Llama-3-70B-Instruct**. You can also find and use one of the models listed above.
41
+
1. Go to the [Azure AI Foundry portal](https://ai.azure.com/) and select **Model catalog** in the left navigation menu, and scroll down to **Meta-Llama-3-70B-Instruct**. You can also find and use one of the models listed previously.
42
42
43
43
1. Select **Deploy**.
44
44
45
45
1. In the Deployment options screen that appears, select **Serverless API** with Azure AI Content Safety.
46
46
47
47
:::image type="content" source="../media/llama/llama-deployment.png" alt-text="An image of the llama model project selection screen.":::
48
48
49
-
1. Select your project and click**Subscribe and deploy**.
49
+
1. Select your project and then select**Subscribe and deploy**.
50
50
51
51
:::image type="content" source="../media/llama/llama-deployment-2.png" alt-text="An image of the llama model deployment screen.":::
52
52
53
-
1. Add the serverless connection to your hub/project. The deployment name you choose will be the one you reference in your code.
53
+
1. Add the serverless connection to your hub/project. The deployment name you choose is the one that you reference in your code.
54
54
55
55
1. When calling agent creation API, set the `models` parameter to your deployment name. For example:
Copy file name to clipboardExpand all lines: articles/ai-services/agents/faq.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ sections:
19
19
- question: |
20
20
Do you store any data used in the AI Agent Service API?
21
21
answer: |
22
-
Yes. Unlike Chat Completions API, Azure OpenAI AI Agent Service is a stateful API, meaning it retains data. There are two types of data stored in the AI Agent Service API:
22
+
Yes. Unlike Chat Completions API, Azure AI Agent Service is a stateful API, meaning it retains data. There are two types of data stored in the AI Agent Service API:
23
23
* Stateful entities: Threads, messages, and runs created during AI Agent Service use.
24
24
* Files: Uploaded during AI Agent Service setup or as part of a message.
25
25
- question: |
@@ -41,7 +41,7 @@ sections:
41
41
- question: |
42
42
Where is data stored geographically?
43
43
answer: |
44
-
Azure OpenAI AI Agent Service endpoints are regional, and data is stored in the same region as the endpoint. For more information, see the [Azure data residency documentation](https://azure.microsoft.com/explore/global-infrastructure/data-residency/#overview).
44
+
Azure AI Agent Service endpoints are regional, and data is stored in the same region as the endpoint. For more information, see the [Azure data residency documentation](https://azure.microsoft.com/explore/global-infrastructure/data-residency/#overview).
The Azure AI Agents service integrates with Azure Functions, enabling you to create intelligent, event-driven applications with minimal overhead. This combination allows AI-driven workflows to leverage the scalability and flexibility of serverless computing, making it easier to build and deploy solutions that respond to real-time events or complex workflows.
20
+
The Azure AI Agent Service integrates with Azure Functions, enabling you to create intelligent, event-driven applications with minimal overhead. This combination allows AI-driven workflows to leverage the scalability and flexibility of serverless computing, making it easier to build and deploy solutions that respond to real-time events or complex workflows.
21
21
22
22
Azure Functions provide support for triggers and bindings, which simplify how your AI Agents interact with external systems and services. Triggers determine when a function executes—such as an HTTP request, message from a queue, or a file upload to Azure Blob Storage and allows agents to act dynamically based on incoming events.
23
23
@@ -31,7 +31,7 @@ Meanwhile, bindings facilitate streamlined connections to input or output data s
31
31
32
32
## Prepare your local environment
33
33
34
-
The following examples highlight how to use the Azure AI Agent service function calling where function calls are placed on a storage queue by the Agent service to be processed by an Azure Function listening to that queue.
34
+
The following examples highlight how to use the Azure AI Agent Service function calling where function calls are placed on a storage queue by the Agent Service to be processed by an Azure Function listening to that queue.
35
35
36
36
You can find the template and code used here on [GitHub](https://github.com/Azure-Samples/azure-functions-ai-services-agent-python).
37
37
@@ -136,7 +136,7 @@ Start by defining an Azure Function queue trigger function that will process fun
136
136
137
137
```python
138
138
# Function to get the weather from an Azure Storage queue where the AI Agent will send function call information
139
-
# It returns the mock weather to an output queue with the correlation id for the AI Agent service to pick up the result of the function call
139
+
# It returns the mock weather to an output queue with the correlation id for the AI Agent Service to pick up the result of the function call
run = project_client.agents.create_run(thread_id=thread.id, assistant_id=agent.id)
248
-
# Monitor and process the run status. The function call should be placed on the input queue by the Agent service for the Azure Function to pick up when requires_action is returned
248
+
# Monitor and process the run status. The function call should be placed on the input queue by the Agent Service for the Azure Function to pick up when requires_action is returned
249
249
while run.status in ["queued", "in_progress", "requires_action"]:
250
250
time.sleep(1)
251
251
run = project_client.agents.get_run(thread_id=thread.id, run_id=run.id)
0 commit comments