Azure OpenAI's Assistants API Dies August 26 —
What Breaks, and What Doesn't Migrate
Microsoft's documentation says it in one sentence, tucked into a note box: "The Assistants API is deprecated and will be retired on August 26, 2026." That is 19 days from today — a deadline landing in the last week of August, when half the teams who need to act are on vacation. The replacement is the generally available Microsoft Foundry Agents service, and Microsoft publishes a migration guide and an automated migration tool.
If your application creates assistants, appends messages to threads, or executes runs against Azure OpenAI, this is your deadline. And unlike the end-of-life dates we usually track — where unsupported software keeps running, quietly accumulating risk — a retired cloud API is a hard stop. There is no "running unpatched" after August 26. There is only running, or not.
What actually retires
The Assistants API was Azure OpenAI's stateful application layer: Assistants (model + instructions + tools), Threads (server-side persistent conversations), Runs (executing an assistant against a thread), plus hosted tools like code interpreter and file search. Its pitch was that Microsoft managed your conversation state so you didn't have to — persistent threads with automatic context-window truncation were the headline feature.
All of it is superseded by Foundry Agents, which restructures the same ideas: threads become conversations (storing messages, tool calls, and outputs as items), and runs become responses — a simpler request/response pattern on the OpenAI client. The concepts map; the SDK calls do not. Code written against client.agents.threads and friends has to change.
The detail that catches teams out: your data doesn't come along
Microsoft's migration tool rewrites code — agent definitions, thread creation, message creation, run creation. But the migration guide is explicit about its limit: "It doesn't migrate state data like past runs, threads, or messages." And the guide's own caveat table confirms the consequence: old thread data isn't available in the new service; teams should "start new conversations after migration."
The 19-day checklist
1. Find your exposure. Search your codebases for Assistants API calls — assistant creation, thread operations, run polling. This includes the quiet internal tools nobody has deployed in months; they break just as hard as production.
2. Run the migration tool, then treat its output as a draft. The automated tool handles the mechanical SDK translation. Tool configurations (code interpreter, file search, function calling) deserve hand-verification — the hosted-tool semantics are where subtle behavior differences live.
3. Export any thread history you need — this week, not deadline week. Pull the messages you must retain via the existing API while it still answers. Compliance-sensitive teams: conversation records your retention policy covers are state data, and state data does not migrate.
4. Re-test, then cut over with days to spare. August 26 is a Wednesday. A cutover attempted on the 25th, discovering a tool-mapping issue with Microsoft support queues at end-of-summer depth, is the bad version of this story.
The pattern behind the deadline
This retirement is not an outlier; it is the cadence of the AI platform era. GPT-3.5 Turbo retired on a schedule that would have seemed absurd for a database. AWS deprecates Lambda runtimes on clocks measured in months. The Assistants API went from launch to retirement inside roughly two and a half years — and its successor will iterate on a similar clock. We track AI model and platform deprecations across providers on our AI models lifecycle page precisely because this category now turns over faster than any other software we monitor. The operational lesson for teams building on AI platforms: treat API lifecycles as dependencies with expiry dates, the same way you treat runtimes and operating systems — because the vendors already do.
Frequently Asked Questions
When does the Azure OpenAI Assistants API retire?
August 26, 2026 — stated verbatim in Microsoft's documentation. The recommended replacement is the generally available Microsoft Foundry Agents service, with a published migration guide and automated migration tool.
Does Microsoft's migration tool move my Assistants data?
No. It migrates code constructs — agent definitions, thread creation, run creation — but Microsoft states it "doesn't migrate state data like past runs, threads, or messages." Conversation history your application depends on must be exported before the retirement date.
What replaces threads and runs?
Threads become conversations (storing messages, tool calls, and tool outputs as items); runs become responses, a simpler request/response pattern usable alone or with conversations for context.
What happens to applications still calling the API after August 26?
A retired cloud API stops serving — expect failures on Assistants, Threads, and Runs calls once retirement takes effect. Unlike on-premises software past end of life, there is no degraded-but-running state.