Azure OpenAI Assistants API to Azure AI Foundry Agent Service migration - Why are the Open AI Assistants working with the Azure AI Persistent Agents client?

Siry, Gaetan 220 Reputation points
2025-05-30T02:01:12.1766667+00:00

Hello,

I just got done converting my code base which was using the OpenAI .NET SDK and Assistants API, to the Azure AI Persistent Agents client ..

I have assistants that were created using the OpenAI Assistants API, but they seem to still be working with the Azure AI Persistent Agents client.

I was under the impression that I needed to recreate my old Open AI Assistants using the Azure AI Persistent Agents client, but maybe I do not have to?

It seems that the Azure AI Agents use the same model as the Assistants API and have access to the same files container ?

Azure AI services
Azure AI services
A group of Azure services, SDKs, and APIs designed to make apps more intelligent, engaging, and discoverable.
3,604 questions
0 comments No comments
{count} votes

Accepted answer
  1. SriLakshmi C 6,010 Reputation points Microsoft External Staff Moderator
    2025-05-30T06:46:07.39+00:00

    Hello @Siry, Gaetan,

    The Azure AI Persistent Agents client is designed to be compatible with assistants created using the OpenAI Assistants API. This means that you do not necessarily need to recreate your existing assistants when migrating to Azure. If your assistants were already functioning correctly using the OpenAI .NET SDK and Assistants API, they can continue to work with the Azure AI Persistent Agents client with minimal or no changes.

    This compatibility is intentional and part of Azure’s goal to offer a more unified and seamless developer experience. The Azure AI Foundry Agent Service supports the same underlying models, tools, and conversation management patterns used by the OpenAI Assistants API. It also has access to the same file containers, enabling consistent file handling and memory use across both platforms.

    In short, Azure’s backward compatibility ensures that your existing assistant functionality can carry over during the migration process without requiring you to rebuild everything from scratch. This allows for a smoother transition and faster adoption of Azure AI services while maintaining the core capabilities of your original assistant setup.

    Please refer this:

    I Hope this helps. Do let me know if you have any further queries.


    If this answers your query, please do click Accept Answer and Yes for was this answer helpful.

    Thank you!

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.