Skip to content

Commit 8ab07ce

Browse files
authored
Merge pull request #4626 from MicrosoftDocs/main
5/7/2025 PM Publish
2 parents 2c90962 + e633d34 commit 8ab07ce

File tree

12 files changed

+138
-130
lines changed

12 files changed

+138
-130
lines changed

articles/ai-foundry/how-to/develop/get-started-projects-vs-code.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,9 @@ manager: mcleans
66
ms.service: azure-ai-foundry
77
content_well_notification:
88
- AI-contribution
9+
ai-usage: ai-assisted
910
ms.topic: how-to
10-
ms.date: 04/28/2025
11+
ms.date: 05/07/2025
1112
ms.reviewer: erichen
1213
ms.author: johalexander
1314
author: ms-johnalex
@@ -30,7 +31,7 @@ With Azure AI Foundry, you can:
3031

3132
With the Azure AI Foundry for Visual Studio Code extension, you can accomplish much of this workflow directly from Visual Studio Code. It also comes with other features, such as code templates, playgrounds, and integration with other VS Code extensions and features.
3233

33-
This article shoes you how to quickly get started using the features of the Azure AI Foundry for Visual Studio Code extension.
34+
This article shows you how to quickly get started using the features of the Azure AI Foundry for Visual Studio Code extension.
3435

3536
[!INCLUDE [feature-preview](../../includes/feature-preview.md)]
3637

@@ -298,14 +299,6 @@ You can also open the model playground using the following steps:
298299

299300
The Azure resources that you created in this article are billed to your Azure subscription. If you don't expect to need these resources in the future, delete them to avoid incurring more charges.
300301

301-
### Delete your agents
302-
303-
1. In the VS Code navbar, refresh the **Azure AI Foundry Extension**. In the **Resources** section, expand the **Agents** subsection to display the list of deployed agents.
304-
305-
1. Right-click on your deployed agent to delete and select the **Delete** option.
306-
307-
:::image type="content" source="../../media/how-to/get-started-projects-vs-code/delete-agent.png" alt-text="Screenshot of the AI Foundry portal with 'Agents' from the navigation menu on the left and the **Delete** button highlighted." lightbox="../../media/how-to/get-started-projects-vs-code/delete-agent.png":::
308-
309302
### Delete your models
310303

311304
1. In the VS Code navbar, refresh the **Azure AI Foundry Extension**. In the **Resources** section, expand the **Models** subsection to display the list of deployed models.

articles/ai-foundry/how-to/develop/vs-code-agents.md

Lines changed: 21 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,9 @@ manager: mcleans
66
ms.service: azure-ai-foundry
77
content_well_notification:
88
- AI-contribution
9+
ai-usage: ai-assisted
910
ms.topic: how-to
10-
ms.date: 04/29/2025
11+
ms.date: 05/07/2025
1112
ms.reviewer: erichen
1213
ms.author: johalexander
1314
author: ms-johnalex
@@ -99,28 +100,39 @@ tools: []
99100
100101
### Add tools to the Azure AI Agent
101102
102-
Azure AI Agent Service has a set of knowledge and action tools that you can use to interact with your data sources, such as:
103-
- [Grounding with Bing search](/azure/ai-services/agents/how-to/tools/bing-grounding?tabs=python&pivots=overview)
104-
- [Azure AI Search](/azure/ai-services/agents/how-to/tools/file-search?tabs=python&pivots=overview)
105-
- [Azure Functions](/azure/ai-services/agents/how-to/tools/file-search?tabs=python&pivots=overview)
106-
- [File retrieval](/azure/ai-services/agents/how-to/tools/azure-functions?tabs=python&pivots=overview)
103+
Azure AI Agent Service has a set of knowledge and action tools that you can use to interact with your data sources.
104+
105+
106+
#### Available tools for Azure AI Agents
107+
108+
The following tools are available:
109+
110+
- Knowledge tools:
111+
- [Grounding with Bing search](/azure/ai-services/agents/how-to/tools/bing-grounding?tabs=python&pivots=overview)
112+
- [File search]( /azure/ai-services/agents/how-to/tools/file-search?tabs=python&pivots=overview)
113+
- [Azure AI Search](/azure/ai-services/agents/how-to/tools/azure-ai-search?tabs=azurecli%2Cpython&pivots=overview-azure-ai-search)
114+
- [Microsoft Fabric](/azure/ai-services/agents/how-to/tools/fabric?tabs=csharp&pivots=overview)
115+
- [Use licensed data](/azure/ai-services/agents/how-to/tools/licensed-data)
116+
117+
- Action tools:
118+
- [Azure AI Agents function calling](/azure/ai-services/agents/how-to/tools/function-calling?tabs=python&pivots=overview)
107119
- [Code interpreter](/azure/ai-services/agents/how-to/tools/code-interpreter?tabs=python&pivots=overview)
108120
- [OpenAPI Specified tools](/azure/ai-services/agents/how-to/tools/openapi-spec?tabs=python&pivots=overview)
121+
- [Azure Functions](/azure/ai-services/agents/how-to/tools/azure-functions?tabs=python&pivots=overview)
109122
110123
#### Configure the tools YAML file
111124
112125
The Agent Designer adds tools to an AI Agent via .yaml files.
113126
114127
Create a tool configuration .yaml file using the following steps:
115128
116-
1. Perform any setup steps that might be required. See the article for the tool you’re interested in using. For example, [Grounding with Bing search](/azure/ai-services/agents/how-to/tools/bing-grounding?tabs=python&pivots=overview#setup).
129+
1. Choose a tool from the [available tools for Azure AI Agents](#available-tools-for-azure-ai-agents). Perform any setup steps that might be required. For example, [Grounding with Bing search](/azure/ai-services/agents/how-to/tools/bing-grounding?tabs=python&pivots=overview#setup).
117130
118131
1. Once you complete the setup, create a yaml code file that specifies the tool’s configuration. For example, this format for Grounding with Bing Search:
119132
120133
```yml
121134
type: bing_grounding
122-
name: bing_search
123-
configuration:
135+
options:
124136
tool_connections:
125137
- >-
126138
/subscriptions/<Azure Subscription ID>/resourceGroups/<Azure Resource Group name>/providers/Microsoft.MachineLearningServices/workspaces/<Azure AI Foundry Project name>/connections/<Bing connection name>

articles/ai-services/openai/concepts/content-filter.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -275,7 +275,7 @@ The table below outlines the various ways content filtering can appear:
275275

276276
**HTTP Response Code** | **Response behavior**
277277
|------------------------|----------------------|
278-
| 200 | If the content filtering system is down or otherwise unable to complete the operation in time, your request will still complete without content filtering. You can determine that the filtering wasn't applied by looking for an error message in the `content_filter_result` object.|
278+
| 200 | If the content filtering system is down or otherwise unable to complete the operation in time, your request will still complete without content filtering. You can determine that the filtering wasn't applied by looking for an error message in the `content_filter_results` object.|
279279

280280
**Example request payload:**
281281

@@ -301,7 +301,7 @@ The table below outlines the various ways content filtering can appear:
301301
"index": 0,
302302
"finish_reason": "length",
303303
"logprobs": null,
304-
"content_filter_result": {
304+
"content_filter_results": {
305305
"error": {
306306
"code": "content_filter_error",
307307
"message": "The contents are not filtered"
@@ -597,12 +597,12 @@ try:
597597

598598
except openai.error.InvalidRequestError as e:
599599
if e.error.code == "content_filter" and e.error.innererror:
600-
content_filter_result = e.error.innererror.content_filter_result
600+
content_filter_results = e.error.innererror.content_filter_result
601601
# print the formatted JSON
602-
print(content_filter_result)
602+
print(content_filter_results)
603603

604604
# or access the individual categories and details
605-
for category, details in content_filter_result.items():
605+
for category, details in content_filter_results.items():
606606
print(f"{category}:\n filtered={details['filtered']}\n severity={details['severity']}")
607607

608608
```
@@ -765,7 +765,7 @@ Blocks completion content when ungrounded completion content was detected.
765765
"status": 400,
766766
"innererror": {
767767
"code": "ResponsibleAIPolicyViolation",
768-
"content_filter_result": {
768+
"content_filter_results": {
769769
"hate": {
770770
"filtered": true,
771771
"severity": "high"
@@ -1040,7 +1040,7 @@ As part of your application design, consider the following best practices to del
10401040
10411041
- Decide how you want to handle scenarios where your users send prompts containing content that is classified at a filtered category and severity level or otherwise misuse your application.
10421042
- Check the `finish_reason` to see if a completion is filtered.
1043-
- Check that there's no error object in the `content_filter_result` (indicating that content filters didn't run).
1043+
- Check that there's no error object in the `content_filter_results` (indicating that content filters didn't run).
10441044
- If you're using the protected material code model in annotate mode, display the citation URL when you're displaying the code in your application.
10451045
10461046
## Next steps

articles/ai-services/openai/concepts/model-retirements.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Azure OpenAI notifies customers of active Azure OpenAI Service deployments for m
3333
2. At least 60 days notice before model retirement for Generally Available (GA) models.
3434
3. At least 30 days notice before preview model version upgrades.
3535

36-
Retirements are done on a rolling basis, region by region.
36+
Retirements are done on a rolling basis, region by region. Notifications are sent from an unmonitored mailbox, `[email protected]`.
3737

3838
## Model availability
3939

@@ -110,7 +110,7 @@ These models are currently available for use in Azure OpenAI Service.
110110
| `gpt-4.1-nano` | 2025-04-14 | No earlier than April 11, 2026 | |
111111
| `gpt-4o` | 2024-05-13 | No earlier than June 30, 2025 | `gpt-4.1` version: `2025-04-14` |
112112
| `gpt-4o` | 2024-08-06 | No earlier than August 6, 2025 | `gpt-4.1` version: `2025-04-14` |
113-
| `gpt-4o` | 2024-11-20 | No earlier than January 30, 2026 | `gpt-4.1` version: `2025-04-14` |
113+
| `gpt-4o` | 2024-11-20 | No earlier than March 1, 2026 | `gpt-4.1` version: `2025-04-14` |
114114
| `gpt-4o-mini` | 2024-07-18 | August 16, 2025 | `gpt-4.1-mini` version: `2025-04-14` |
115115
| `gpt-3.5-turbo-instruct` | 0914 | No earlier than May 31, 2025 | |
116116
| `gpt-image-1` | 2025-04-15 | No earlier than August 01, 2025 | |

articles/ai-services/openai/how-to/provisioned-throughput-onboarding.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -81,15 +81,15 @@ The amount of throughput (measured in tokens per minute or TPM) a deployment get
8181

8282
For example, for `gpt-4.1:2025-04-14`, 1 output token counts as 4 input tokens towards your utilization limit which matches the [pricing](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/). Older models use a different ratio and for a deeper understanding on how different ratios of input and output tokens impact the throughput your workload needs, see the [Azure OpenAI capacity calculator](https://ai.azure.com/resource/calculator).
8383

84+
|Topic| **gpt-4.1** | **gpt-4.1-mini** | **o3-mini** | **o1** | **gpt-4o** | **gpt-4o-mini** |
85+
| --- | --- | --- | --- | --- | --- | --- |
86+
|Global & data zone provisioned minimum deployment|15|15|15|15|15|15|
87+
|Global & data zone provisioned scale increment|5|5|5|5|5|5|
88+
|Regional provisioned minimum deployment|50|25|25|25|50|25|
89+
|Regional provisioned scale increment|50|25|25|50|50|25|
90+
|Input TPM per PTU|3,000|14,900|2,500|230|2,500|37,000|
91+
|Latency Target Value|44 Tokens Per Second|50 Tokens Per Second| 66 Tokens Per Second |25 Tokens Per Second|25 Tokens Per Second|33 Tokens Per Second|
8492

85-
|Topic| **gpt-4o** | **gpt-4o-mini** | **o1**| gpt-4.1 |
86-
| --- | --- | --- | --- | --- |
87-
|Global & data zone provisioned minimum deployment|15|15|15|15 |
88-
|Global & data zone provisioned scale increment|5|5|5| 5 |
89-
|Regional provisioned minimum deployment|50|25|50| 50 |
90-
|Regional provisioned scale increment|50|25|50| 50 |
91-
|Input TPM per PTU |2,500|37,000|230| 3000 |
92-
|Latency Target Value |25 Tokens Per Second|33 Tokens Per Second|25 Tokens Per Second| 44 Tokens Per Second |
9393

9494
For a full list, see the [Azure OpenAI Service in Azure AI Foundry portal calculator](https://ai.azure.com/resource/calculator).
9595

articles/ai-services/openai/how-to/use-blocklists.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -148,7 +148,7 @@ In the below example, a GPT-35-Turbo deployment with a blocklist is blocking the
148148
"status": 400,
149149
"innererror": {
150150
"code": "ResponsibleAIPolicyViolation",
151-
"content_filter_result": {
151+
"content_filter_results": {
152152
"custom_blocklists": [
153153
{
154154
"filtered": true,

articles/ai-services/openai/includes/language-overview/python.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -336,7 +336,7 @@ print(completion.model_dump_json(indent=2))
336336
"prompt_filter_results": [
337337
{
338338
"prompt_index": 0,
339-
"content_filter_result": {
339+
"content_filter_results": {
340340
"jailbreak": {
341341
"filtered": false,
342342
"detected": false
@@ -345,7 +345,7 @@ print(completion.model_dump_json(indent=2))
345345
},
346346
{
347347
"prompt_index": 1,
348-
"content_filter_result": {
348+
"content_filter_results": {
349349
"sexual": {
350350
"filtered": false,
351351
"severity": "safe"

articles/ai-services/openai/includes/model-matrix/datazone-provisioned-managed.md

Lines changed: 16 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -9,18 +9,19 @@ ms.custom: references_regions
99
ms.date: 05/05/2025
1010
---
1111

12-
| **Region** | **gpt-4.1**, **2025-04-14** | **o3-mini**, **2025-01-31** | **o1**, **2024-12-17** | **gpt-4o**, **2024-05-13** | **gpt-4o**, **2024-08-06** | **gpt-4o**, **2024-11-20** | **gpt-4o-mini**, **2024-07-18** |
13-
|:-------------------|:---------------------------:|:---------------------------:|:----------------------:|:--------------------------:|:--------------------------:|:--------------------------:|:-------------------------------:|
14-
| eastus ||||||||
15-
| eastus2 ||||||||
16-
| francecentral ||||||||
17-
| germanywestcentral ||||||||
18-
| italynorth || - | - | - | - | - | - |
19-
| northcentralus ||||||||
20-
| polandcentral ||||||||
21-
| southcentralus ||||||||
22-
| spaincentral ||||||||
23-
| swedencentral ||||||||
24-
| westeurope ||||||||
25-
| westus ||||||||
26-
| westus3 ||||||||
12+
13+
| **Region** | **gpt-4.1**, **2025-04-14** | **gpt-4.1-mini**, **2025-04-14** | **o3-mini**, **2025-01-31** | **o1**, **2024-12-17** | **gpt-4o**, **2024-05-13** | **gpt-4o**, **2024-08-06** | **gpt-4o**, **2024-11-20** | **gpt-4o-mini**, **2024-07-18** |
14+
|:-------------------|:---------------------------:|:--------------------------------:|:---------------------------:|:----------------------:|:--------------------------:|:--------------------------:|:--------------------------:|:-------------------------------:|
15+
| eastus |||||||||
16+
| eastus2 |||||||||
17+
| francecentral |||||||||
18+
| germanywestcentral |||||||||
19+
| italynorth || - | - | - | - | - | - | - |
20+
| northcentralus |||||||||
21+
| polandcentral |||||||||
22+
| southcentralus |||||||||
23+
| spaincentral |||||||||
24+
| swedencentral |||||||||
25+
| westeurope |||||||||
26+
| westus |||||||||
27+
| westus3 |||||||||

0 commit comments

Comments
 (0)