Azure OpenAI retires Assistants API next week
Reviewed by Helen Jones
Microsoft states that the Azure OpenAI Assistants API is deprecated and retires on 26 August 2026. Its current guidance is to move affected workloads to the generally available Microsoft Foundry Agents service.
Teams can mistake an agent feature name for a stable platform commitment. If a pilot or production workflow still depends on the classic Assistants API surface, the deadline is now a service-continuity issue rather than a future architecture tidy-up. A migration is more than pointing old prompts at a new endpoint. Owners need to identify the API surface their apps use, check equivalents for threads, tools and evaluation cases, then retest the workflow’s permissions, output checks and failure handling.
Analysis
Ask the owner of every Azure OpenAI agent workflow whether it calls the Assistants API. For any yes, create a dated migration test to the current Foundry Agents path and run it against a representative workflow before 26 August.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Azure OpenAI Assistants API reaches its retirement deadline", Collab365 Spaces.