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
+25-3Lines changed: 25 additions & 3 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,29 @@ 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 with the Azure AI Foundry Agent Service.
23
+
24
+
### If you are 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
+
### SDK usage with hub-based projects
31
+
32
+
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 was 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.
33
+
34
+
If you want to continue using your hub-based project and connection string, you will need to:
35
+
* Use the connection string for your project located under **Connection string** in the overview of your project.
36
+
37
+
:::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.":::
38
+
39
+
* Use one of the previous versions of the SDK and the associated sample code:
40
+
*[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
41
+
*[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
42
+
43
+
### Azure Cosmos DB for NoSQL to store threads
44
+
23
45
- 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
46
- Three containers will be provisioned in your existing Cosmos DB account, each requiring 1000 RU/s
25
47
@@ -70,7 +92,7 @@ Includes everything in the basic setup and fine-grained control over your data b
70
92
71
93
## Basic agent setup: Use an existing Azure OpenAI resource
72
94
73
-
Replace the parameter value for `existingAoaiResourceId` with the full arm resource ID of the Azure OpenAI resource you want to use.
95
+
Replace the parameter value for `existingAoaiResourceId`in the [template](https://github.com/azure-ai-foundry/foundry-samples/tree/main/samples/microsoft/infrastructure-setup/42-basic-agent-setup-with-customization) with the full arm resource ID of the Azure OpenAI resource you want to use.
74
96
75
97
1. To get the Azure OpenAI account resource ID, sign in to the Azure CLI and select the subscription with your AI Services account:
> 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 was previously used for hub-based projects. If you're using a hub-based project, you won't be able to use the current versions of the SDK and REST API. For more information, see [SDK usage with hub-based projects](../how-to/use-your-own-resources.md#sdk-usage-with-hub-based-projects).
Set this endpoint as an environment variable named `PROJECT_ENDPOINT` in a `.env` file.
65
+
Save the name of your model deployment name as an environment variable named `MODEL_DEPLOYMENT_NAME`.
66
66
67
67
> [!IMPORTANT]
68
68
> * This quickstart code uses environment variables for sensitive configuration. Never commit your `.env` file to version control by making sure `.env` is listed in your `.gitignore` file.
0 commit comments