How to find which Azure OpenAI Assistants APIs in my subscription needs to upgrade to Microsoft Foundry Agent Service

Question

How to find which Azure OpenAI Assistants APIs in my subscription needs to upgrade to Microsoft Foundry Agent Service

NAVEEN Mittal 130 Microsoft External Staff

How to find which Azure OpenAI Assistants APIs in my subscription needs to upgrade to Microsoft Foundry Agent Service. could you please suggest

Subscription : K2 PubPlanning (ARM)

Subscription Id: c75c4131-b27e-47e8-bca6-2f2908215bd6

Anshika Varshney 12,115 Reputation points Microsoft External Staff Moderator

2026-05-28T08:13:30.81+00:00

Hi @NAVEEN Mittal

To identify which Azure OpenAI Assistants APIs in your subscription need to be upgraded to Microsoft Foundry Agent Service, there is currently no direct or built-in option in the Azure portal that lists all such usages in one place.

You can follow these approaches to identify them:

First, review your existing Azure OpenAI deployments. Check all Azure OpenAI resources in your subscription and verify if you are using Assistants APIs (such as assistant creation, threads, or runs). These are the components that are being transitioned.

Second, analyze your application code. Search your codebase for Assistants-related APIs or SDK usage. This will help you identify where Assistants APIs are being used so you can plan migration accordingly.

Third, check usage through logs and monitoring. Use Azure Monitor, diagnostic logs, or Application Insights (if enabled) to review API calls made to Azure OpenAI. Look specifically for Assistants-related operations.

Fourth, review API versions. Check if your application is using older preview APIs related to Assistants. These are more likely to require migration to the new Foundry Agent Service.

Fifth, validate against documentation and announcements. Compare your current implementation with the latest Microsoft guidance for Azure AI Foundry Agent Service to confirm which features are impacted and need upgrade.

In short, there isn’t an automatic detection tool yet, so you need to identify usage manually by checking deployments, code, and logs.

Please let me know if there are any remaining questions or additional details, I can help with, I’ll be glad to provide further clarification or guidance.

Thankyou!

Anshika Varshney 12,115 Microsoft External Staff Moderator

Hello @NAVEEN Mittal

The Azure OpenAI Assistants API (classic) is deprecated and will be retired on August 26, 2026. You must migrate to the Microsoft Foundry Agent Service (generally available).learn.microsoft

How to Identify Assistants Needing Migration

Check Your Azure Portal Resources

Go to Azure Portal → Your Azure OpenAI resource
Navigate to Assistants in the left menu
Assistants created through the classic Assistants API will show as "classic" assistants
These are the ones that need migration learn.microsoft

Check Your Code for Classic SDK Usage

Look for these indicators in your codebase:

Classic (Needs Migration)	Foundry Agent Service (New)
`azure-ai-projects` version 1.x	`azure-ai-projects` version 2.x+ or `azure-ai-agents` 1.0.0+ learn.microsoft+1
--------	--------
`azure-ai-projects` version 1.x	`azure-ai-projects` version 2.x+ or `azure-ai-agents` 1.0.0+ learn.microsoft+1
`from azure.ai.projects.models`	`from azure.ai.agents.models` learn.microsoft
`AgentsClient`	`PersistentAgentsClient` learn.microsoft
Connection string authentication	Endpoint URL authentication learn.microsoft
`CreateAgentAsync()`	`Administration.CreateAgentAsync()` learn.microsoft

3. Azure Resource Graph Query (Recommended for Subscriptions)

Run this Azure Resource Graph query to find all Azure OpenAI resources:

text
resources
| where type == "microsoft.cognitiveservices/accounts"
| where properties.kind contains "OpenAI"
| project name, resourceGroup, location, properties

Then check each resource's Assistants usage through:

Azure Monitor logs for Assistants API calls
API usage logs filtered by /assistants endpoint

Check API Version in Your Requests

Classic Assistants API uses:

api-version parameter in requests

Endpoint format: https://{resource}.openai.azure.com/openai/assistants?api-version={version}

Foundry Agent Service uses:

v1 API (no api-version parameter)learn.microsoft+1
Endpoint format: https://{resource}.services.ai.azure.com/api/projects/{project-name}

I hope this has been helpful! In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Thankyou!

2 answers

Your answer

Anshika Varshney 12,115 Reputation points Microsoft External Staff Moderator

2026-05-28T08:13:30.81+00:00

Hi @NAVEEN Mittal

To identify which Azure OpenAI Assistants APIs in your subscription need to be upgraded to Microsoft Foundry Agent Service, there is currently no direct or built-in option in the Azure portal that lists all such usages in one place.

You can follow these approaches to identify them:

First, review your existing Azure OpenAI deployments. Check all Azure OpenAI resources in your subscription and verify if you are using Assistants APIs (such as assistant creation, threads, or runs). These are the components that are being transitioned.

Second, analyze your application code. Search your codebase for Assistants-related APIs or SDK usage. This will help you identify where Assistants APIs are being used so you can plan migration accordingly.

Third, check usage through logs and monitoring. Use Azure Monitor, diagnostic logs, or Application Insights (if enabled) to review API calls made to Azure OpenAI. Look specifically for Assistants-related operations.

Fourth, review API versions. Check if your application is using older preview APIs related to Assistants. These are more likely to require migration to the new Foundry Agent Service.

Fifth, validate against documentation and announcements. Compare your current implementation with the latest Microsoft guidance for Azure AI Foundry Agent Service to confirm which features are impacted and need upgrade.

In short, there isn’t an automatic detection tool yet, so you need to identify usage manually by checking deployments, code, and logs.

Please let me know if there are any remaining questions or additional details, I can help with, I’ll be glad to provide further clarification or guidance.

Thankyou!

Answer 1

Hello NAVEEN Mittal,

Greetings! Thanks for raising this question in Q&A forum.

This is a very timely and important question. The Azure OpenAI Assistants API is deprecated and will be retired on August 26, 2026 all workloads using it must be migrated to the generally available Microsoft Foundry Agents service. Since there is no single automated discovery tool that scans a subscription and lists all Assistants API usages, you need to use a combination of approaches. Let me walk you through exactly how to find what needs migration.

Step 1: Check Foundry (classic) portal for existing Assistants resources

Go to the Foundry classic portal at ai.azure.com and toggle to the classic view using the banner at the top
Navigate to each of your Azure OpenAI resources associated with the subscription
Look for any projects or deployments that have Assistants configured these will be listed under the Assistants section in the left navigation
Note down each Assistant name, its resource name, and the resource group it belongs to

Step 2: Use the Azure OpenAI Assistants REST API to list all Assistants programmatically For each Azure OpenAI resource endpoint in your subscription, run this API call to list all existing Assistant objects:

GET https://<your-resource-name>.openai.azure.com/openai/assistants?api-version=2025-04-01-preview

With Azure CLI authentication:

az rest --method GET \
  --url "https://<resource-name>.openai.azure.com/openai/assistants?api-version=2025-04-01-preview" \
  --resource "https://cognitiveservices.azure.com/"

If this returns any Assistant objects, those workloads need migration.

Step 3: Find all Azure OpenAI resources in your subscription using Azure CLI Run this to list all Azure OpenAI resources across the subscription so you know which endpoints to check:

az cognitiveservices account list --subscription c75c4131-b27e-47e8-bca6-2f2908215bd6 \
  --query "[?kind=='OpenAI' || kind=='AIServices'].{Name:name, RG:resourceGroup, Endpoint:properties.endpoint}" \
  --output table

Then repeat Step 2 for each endpoint returned.

Step 4: Search your application code and infrastructure for Assistants API usage Search your code repositories for any of the following patterns — these are all signs that a workload is using the Assistants API and must be migrated:

/openai/assistants
/openai/threads
create_assistant
beta.assistants
AzureOpenAI().beta

Also search your Bicep, Terraform, or ARM templates for these same patterns in any deployment scripts or configurations.

Step 5: Use Azure Monitor / Log Analytics to find active Assistants API traffic If your Azure OpenAI resources have diagnostic settings enabled, go to Log Analytics and run a query to find recent API calls to the Assistants endpoints:

AzureDiagnostics
| where ResourceType == "ACCOUNTS"
| where requestUri_s contains "/openai/assistants" or requestUri_s contains "/openai/threads"
| summarize count() by requestUri_s, Resource

This will surface active Assistants API usage even for workloads you may have forgotten about.

Step 6: Understand what changes are needed for migration The migration from Assistants API to the Foundry Agents service involves rewriting agents that use the Assistants API to use the Responses API before the August 2026 sunset. Key concept changes include: Threads become Conversations, Messages become Items, Runs (async, polled) become Responses (sync by default), Assistants/Agents become Agent Versions, and the create_agent() method becomes create_version() using PromptAgentDefinition.

Step 7: Follow the official migration guide Once you've identified all Assistants API usages, follow the step-by-step migration guide at: https://learn.microsoft.com/en-us/azure/foundry/agents/how-to/migrate

This covers migrating each classic Assistant to a new Foundry Agent, updating SDK packages from azure-ai-projects 1.x to 2.x, and updating your endpoints.

Important note about the deadline The August 26, 2026 Assistants API sunset deadline means all workloads must be migrated to the Microsoft Foundry Agents service before that date. Given that this is less than 3 months away, it is important to start the discovery and migration process as soon as possible to avoid any service disruption.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.

Answer 2

Azure OpenAI Assistants API is deprecated and will be retired on August 26, 2026, and workloads using it must be migrated to Microsoft Foundry Agent Service.

From the provided information, there is no subscription-level discovery API or portal view documented that lists “all Assistants API usages” across a subscription. The available guidance focuses on:

Recognizing that Assistants is a legacy capability in the Foundry (classic) portal and must be migrated to Agents.
Using the migration guide for moving each workload from Assistants to Agents.

Based on the documentation, the practical way to identify what needs migration is:

Check for use of Assistants (classic) in Foundry:
- In the Foundry (classic) portal, look for any solutions or projects that use the Azure OpenAI Assistants feature (Assistants, Threads, tools like code interpreter and file search). These are the workloads that must be migrated.
Check application code and infrastructure definitions:
- Search code repositories and IaC (Bicep/Terraform/ARM) for usage of the Assistants REST endpoints or SDKs (for example, /openai/assistants, Threads, tools, or Assistants-specific client classes). Any such usage indicates an application that must be migrated to Agents.
Plan migration to Microsoft Foundry Agent Service:
- For each identified Assistants-based workload, follow the documented migration guidance to move to the generally available Microsoft Foundry Agents service. The documentation explicitly states that Assistants is deprecated and points to Agents and its migration guide as the path forward.

Because the documentation does not expose a subscription-wide inventory mechanism for Assistants, identification must be done via portal inspection of classic Assistants resources and code/configuration search for Assistants APIs.

References:

Share via

How to find which Azure OpenAI Assistants APIs in my subscription needs to upgrade to Microsoft Foundry Agent Service

3. Azure Resource Graph Query (Recommended for Subscriptions)

2 answers

Your answer