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-foundry/agents/how-to/use-your-own-resources.md
+33-2Lines changed: 33 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ services: cognitive-services
6
6
manager: nitinme
7
7
ms.service: azure-ai-agent-service
8
8
ms.topic: how-to
9
-
ms.date: 06/18/2025
9
+
ms.date: 07/23/2025
10
10
author: aahill
11
11
ms.author: aahi
12
12
ms.reviewer: fosteramanda
@@ -19,7 +19,38 @@ Use this article if you want to set up your Foundry project with your own resour
19
19
20
20
## Limitations
21
21
22
-
**Use Azure Cosmos DB for NoSQL to store threads**
22
+
There are some limitations you should be aware of when you plan to use existing resources wtih the Azure AI Foundry Agent Service
23
+
24
+
### If previously were using a hub-based project or Azure OpenAI Assistants
25
+
26
+
At this time, there is no direct upgrade path to migrate existing agents or their associated data assets such as files, threads, or vector stores from a hub-based project to an Azure AI Foundry project. There is also no upgrade path to convert existing Azure OpenAI Assistants into Foundry Agents, nor a way to automatically migrate Assistants' files, threads, or vector stores.
27
+
28
+
You can reuse your existing model deployments and quota from Azure AI Services or Azure OpenAI resources within a Foundry project.
29
+
30
+
If you want to create a [basic agent setup](#choose-basic-or-standard-agent-setup), you can create a new project in the Azure AI Foundry by selecting **AI Foundry** > **Create new**, or using the bicep template later in this article.
31
+
32
+
:::image type="content" source="../media/new-project.png" alt-text="A screenshot of a new project in Azure AI Foundry.":::
33
+
34
+
If you want to create a [standard agent setup](#choose-basic-or-standard-agent-setup), setup steps are described later in this article.
35
+
36
+
### SDK usage with hub-based projects
37
+
38
+
Starting in May 2025, the Azure AI Agent Service uses an endpoint for [Foundry projects](../../what-is-azure-ai-foundry.md#project-types) instead of the connection string that were used for hub-based projects before this time. Connection strings are no longer supported in current versions of the SDKs and REST API. We recommend creating a new foundry project.
39
+
40
+
If you want to continue using your hub-based project and connection string, you will need to:
41
+
* Use the connection string for your project located under **Connection string** in the overview of your project.
42
+
43
+
:::image type="content" source="../../media/quickstarts/azure-ai-sdk/connection-string.png" alt-text="A screenshot showing the legacy connection string for a hub-based project.":::
44
+
45
+
* Use one of the previous versions of the SDK and the associated sample code:
46
+
*[C#](https://github.com/Azure/azure-sdk-for-net/tree/feature/azure-ai-agents/sdk/ai/Azure.AI.Projects/samples): `1.0.0-beta.2` or earlier
47
+
*[Python](https://github.com/Azure/azure-sdk-for-python/tree/feature/azure-ai-projects-beta10/sdk/ai/azure-ai-projects/samples/agents): `1.0.0b10` or earlier
48
+
49
+
50
+
51
+
52
+
### Azure Cosmos DB for NoSQL to store threads
53
+
23
54
- Your existing Azure Cosmos DB for NoSQL account used in a [standard setup](#choose-basic-or-standard-agent-setup) must have a total throughput limit of at least 3000 RU/s. Both provisioned throughput and serverless are supported.
24
55
- Three containers will be provisioned in your existing Cosmos DB account, each requiring 1000 RU/s
Copy file name to clipboardExpand all lines: articles/ai-foundry/agents/includes/connection-string-deprecation.md
+1-10Lines changed: 1 addition & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,13 +8,4 @@ ms.date: 07/23/2025
8
8
---
9
9
10
10
> [!IMPORTANT]
11
-
> Starting in May 2025, the Azure AI Agent Service uses an endpoint for [Foundry projects](../../what-is-azure-ai-foundry.md#project-types) instead of the connection string that were used for hub-based projects before this time. Connection strings are no longer supported in current versions of the SDKs and REST API. We recommend creating a new foundry project.
12
-
>
13
-
> If you want to continue using your hub-based project and connection string, you will need to:
14
-
> 1. Use the connection string for your project located under **Connection string** in the overview of your project.
15
-
>
16
-
> :::image type="content" source="../../media/quickstarts/azure-ai-sdk/connection-string.png" alt-text="A screenshot showing the legacy connection string for a hub-based project.":::
17
-
>
18
-
> 2. Use one of the previous versions of the SDK and the associated sample code:
19
-
> *[C#](https://github.com/Azure/azure-sdk-for-net/tree/feature/azure-ai-agents/sdk/ai/Azure.AI.Projects/samples): `1.0.0-beta.2` or earlier
20
-
> *[Python](https://github.com/Azure/azure-sdk-for-python/tree/feature/azure-ai-projects-beta10/sdk/ai/azure-ai-projects/samples/agents): `1.0.0b10` or earlier
11
+
> Starting in May 2025, the Azure AI Agent Service uses an endpoint for [Foundry projects](../../what-is-azure-ai-foundry.md#project-types) instead of the connection string that were previously used for hub-based projects. See [SDK usage with hub-based projects](../how-to/use-your-own-resources.md#sdk-usage-with-hub-based-projects)
0 commit comments