Azure OpenAI gpt-5.1, gpt-5-mini, and gpt-5.2-codex retirement on July 13, 2027
The dataset has 3 Azure OpenAI ids with shutdown date 2027-07-13: gpt-5-mini-2025-08-07, gpt-5.1-2025-11-13, gpt-5.2-codex-2026-01-14. The retirement schedule lists that date on each of those rows. Lifecycle is GA. The replacement cell is empty, so those cells say Not published. The lifecycle page says a Retired model is removed from service and all inference requests return 410 Gone. OpenAI's deprecations page says: "The following models are deprecated and will be removed from the API on April 1, 2027, with six months' notice. Migrate to the recommended replacements before the shutdown date." That sentence is the OpenAI API. It names gpt-5.1 and gpt-5.1-2025-11-13. Microsoft's Azure schedule does not print 2027-04-01 as an Azure shutdown. A team that calls both APIs should plan the OpenAI calls for the earlier date.
Last reviewed . Publisher: SunsetDiff.
Steps
Find deployments. Call Deployments List, or Get-AzCognitiveServicesAccountDeployment, for each Azure OpenAI resource. Read properties.model.name and properties.model.version. A deployment name can differ from the model name. gpt-5.1 version 2025-11-13 is the dataset id gpt-5.1-2025-11-13. gpt-5-mini version 2025-08-07 is gpt-5-mini-2025-08-07. gpt-5.2-codex version 2026-01-14 is gpt-5.2-codex-2026-01-14.
Pick a replacement. The replacement cell is empty for gpt-5.1 2025-11-13, gpt-5-mini 2025-08-07, and gpt-5.2-codex 2026-01-14. Microsoft did not name a recommended replacement on these rows. Shortlist a model yourself and test it. The Azure id gpt-5.1 stores shutdown date Not published. The schedule prints the dated version, not an undated gpt-5.1 row.
Test. Send one real request to the model you picked, using a prompt you send now. Do that before July 13, 2027. Check the reply, the tools, and the fields the new model rejects.
Redeploy before the date. Create a deployment of the model you tested and move traffic before July 13, 2027. These rows do not name an automatic-upgrade target. Provisioned deployments are not auto-upgraded. A deployment set to NoAutoUpgrade stops working on the retirement date.
Models and dates
These 3 ids are the Azure OpenAI rows whose shutdown date is 2027-07-13. The model id links to its SunsetDiff model page. Lifecycle is the schedule's Lifecycle column, copied from the source excerpt stored on the row. Shutdown date and replacement are the fields stored on the row. Not published means the replacement field is empty. These rows do not store a deprecation_date. gpt-5-mini-2025-08-07 (GA), gpt-5.1-2025-11-13 (GA), gpt-5.2-codex-2026-01-14 (GA).
The schedule lists gpt-5.1 version 2025-11-13 as GA with retirement date 2027-07-13 and an empty replacement cell. It lists gpt-5-mini version 2025-08-07 the same way. It lists gpt-5.2-codex version 2026-01-14 the same way. Those three rows do not carry footnote 2 or footnote 3.
The lifecycle table says Generally Available means: "Production-ready. Weights and APIs are fixed." New deployments are allowed, and existing deployments work, until the retirement date. The lifecycle page also says: "Check the Model retirement schedule for the current retirement dates and replacement model, since these details are subject to change."
The Azure Government schedule lists gpt-5.1 version 2025-11-13 as GA with retirement date 2027-07-13 and an empty replacement cell. That government table does not list gpt-5-mini or gpt-5.2-codex. The dates in the first table are the public-cloud schedule.
3 Azure OpenAI model ids with shutdown date 2027-07-13.
The schedule says: "The Replacement column identifies Microsoft's recommended replacement and, where supported, the target for automatic upgrades at retirement." It also says: "You don't need to wait for a replacement to be listed before evaluating or manually migrating to another compatible model." The lifecycle page says: "The replacement listed in the Model retirement schedule is Microsoft's recommended migration target and, where supported, the model used for automatic upgrades at retirement. It doesn't limit your manual migration choices."
No row in this table stores a replacement.
The replacement cell is empty on gpt-5-mini-2025-08-07, gpt-5.1-2025-11-13, gpt-5.2-codex-2026-01-14. Empty means Microsoft did not name a recommended replacement on that row. This guide does not add one.
The undated Azure id is gpt-5.1. The shutdown date stored on that id is Not published. The schedule does not print an undated gpt-5.1 row. It prints version 2025-11-13. April 14, 2027 rows that name gpt-5.1 as a replacement are a different date. See Azure OpenAI GPT-4.1 and GPT-4o retirement on April 14, 2027.
OpenAI's API deprecations page says: "The following models are deprecated and will be removed from the API on April 1, 2027, with six months' notice. Migrate to the recommended replacements before the shutdown date." That date is 2027-04-01. The OpenAI rows are on GPT-5.1, gpt-5.3-codex, and gpt-5.4-nano shutdown on April 1, 2027. gpt-5.1 stores shutdown date 2027-04-01 and replacement gpt-6-sol. gpt-5.1-2025-11-13 stores shutdown date 2027-04-01 and replacement gpt-6-sol.
Microsoft's retirement schedule and lifecycle page do not print 2027-04-01 as a shutdown date for Azure gpt-5.1. The Azure row stays 2027-07-13. A team that calls the OpenAI API and Azure should plan the OpenAI gpt-5.1 calls for 2027-04-01. The Azure deployment keeps 2027-07-13.
The same OpenAI page lists an earlier date for the other two names. gpt-5-mini stores shutdown date 2026-12-11 and replacement gpt-5.6-terra. gpt-5-mini-2025-08-07 stores shutdown date 2026-12-11 and replacement gpt-5.6-terra. gpt-5.2-codex stores shutdown date 2026-07-23 and replacement gpt-5.6-sol. Those OpenAI dates are not Azure shutdown dates. Plan each API for the date on that API. The earlier date is the one to plan first.
The schedule and the lifecycle page both say: "Fine-tuned models retire in two phases: training and deployment." And: "Unless explicitly stated, training retires no earlier than the base model retirement date." Both pages say: "For existing customers only. Otherwise, training retirement occurs at base model retirement."
The fine-tune tables on both pages do not list gpt-5.1 version 2025-11-13, gpt-5-mini version 2025-08-07, or gpt-5.2-codex version 2026-01-14. gpt-5-mini-2025-08-07: no fine-tune dates are stored, and the fine-tune tables do not list this version. gpt-5.1-2025-11-13: no fine-tune dates are stored, and the fine-tune tables do not list this version. gpt-5.2-codex-2026-01-14: no fine-tune dates are stored, and the fine-tune tables do not list this version.
A base deployment of these versions uses the retirement date in the first table. Do not borrow a fine-tune date from a different model.
The lifecycle table says Retired means: "Removed from service. All inference requests return 410 Gone." New deployments are not allowed, and existing deployments do not work. The same page says the API value lifecycleStatus Deprecated means the model is retired and inference returns 410 Gone. The docs stage Deprecated is lifecycleStatus Deprecating, and inference still works. The sentences and the status map are on Azure OpenAI retired models return 410 Gone. These three rows are GA now, so inference still works until July 13, 2027.
The lifecycle page says: "For Global Standard, Data Zone Standard, and Standard deployment types, Microsoft manages automatic upgrades when a model version is retired:" It also says: "Provisioned deployments are NOT auto-upgraded. Provisioned customers must manually migrate to the replacement model." The migration page says: "Standard, Global Standard, and Data Zone Standard (pay-as-you-go) deployments are auto-upgraded on a rolling, region-by-region schedule." And: "Provisioned (PTU) deployments are not auto-upgraded." And: "Batch deployments follow the side-by-side path: deploy the new model, resubmit jobs, retire the old deployment."
Working with models says: "Automatic model updates are only supported for Standard deployment types." OnceCurrentVersionExpired means: "Once the retirement date is reached the model deployment automatically upgrades to the current default version." NoAutoUpgrade means: "The model deployment never automatically upgrades. Once the retirement date is reached the model deployment stops working." And: "null is equivalent to OnceCurrentVersionExpired."
The same page says: "When you select a specific model version for a deployment, this version remains selected until you either choose to manually update yourself, or once you reach the retirement date for the model." Then: "When the retirement date is reached the model will automatically upgrade to the default version at the time of retirement." A deployment you pinned to one of these versions can still move on the retirement date unless versionUpgradeOption is NoAutoUpgrade. NoAutoUpgrade does not move, and the deployment stops. The replacement cell is the target where an automatic upgrade is supported. These three rows have an empty cell, so they do not name that target.
The migration page says: "You also need an inventory of the model deployments your workload uses, including their deployment types (Standard, Provisioned, or Batch)." Working with models says: "To query the current model deployment settings including the deployment upgrade configuration for a given resource use Deployments List." If the value is null, you won't see a versionUpgradeOption property. The model versions page says: "Go to your deployment in the Foundry portal, then open the Details tab to see the current model version." And: "Query the deployments endpoint for your resource. The response includes the model version for each deployment."
The example response puts the model name and version on properties.model. The deployment's own name is the name field next to that object. Match properties.model.name and properties.model.version to the ids in the table. gpt-5.1 version 2025-11-13 is the dataset id gpt-5.1-2025-11-13.
Also search the repository. A hit is a candidate, not proof a deployment still uses that version. How to find every model ID in your codebase covers SDK argument names. The scan page builds a search from dataset ids that have a shutdown date.
Azure PowerShell, list deployments for one account
GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CognitiveServices/accounts/{accountName}/deployments?api-version=2023-05-01
Create a deployment of a model you have tested, point traffic at it, and confirm one real request before July 13, 2027. Do that for each of the 3 versions in the table.
Working with models describes two ways to change a provisioned deployment once you have chosen a target. In-place migration keeps the deployment name and moves traffic. Multi-deployment migration creates a second deployment, shifts traffic, then deletes the old one. Neither section names a target for these rows.
The pre-migration test checklist is the longer list: evals, rejected fields, token limits, tools, price, and latency. These Azure rows do not store a price.
Which Azure OpenAI versions retire on July 13, 2027?
The dataset lists gpt-5-mini-2025-08-07, gpt-5.1-2025-11-13, gpt-5.2-codex-2026-01-14. The retirement schedule lists shutdown date 2027-07-13 for each of them. gpt-5-mini-2025-08-07 (GA), gpt-5.1-2025-11-13 (GA), gpt-5.2-codex-2026-01-14 (GA).
What is the official replacement?
The recommended replacement is the official replacement stored on each row. gpt-5-mini-2025-08-07: Not published. gpt-5.1-2025-11-13: Not published. gpt-5.2-codex-2026-01-14: Not published. The schedule says: "The Replacement column identifies Microsoft's recommended replacement and, where supported, the target for automatic upgrades at retirement." The cell is empty on gpt-5-mini-2025-08-07, gpt-5.1-2025-11-13, gpt-5.2-codex-2026-01-14.
Does OpenAI's April 1, 2027 shutdown of gpt-5.1 apply to Azure?
No for the Azure deployment. Microsoft's retirement schedule and lifecycle page do not print 2027-04-01 as an Azure gpt-5.1 shutdown. The schedule lists Azure gpt-5.1 version 2025-11-13 as GA with retirement date 2027-07-13 and an empty replacement cell. OpenAI's deprecations page says: "The following models are deprecated and will be removed from the API on April 1, 2027, with six months' notice. Migrate to the recommended replacements before the shutdown date." That sentence is the OpenAI API. See GPT-5.1, gpt-5.3-codex, and gpt-5.4-nano shutdown on April 1, 2027. A team that calls both APIs should plan the OpenAI calls for 2027-04-01. The Azure id gpt-5.1 stores shutdown date Not published.
What about gpt-5-mini and gpt-5.2-codex on the OpenAI API?
gpt-5-mini stores shutdown date 2026-12-11 and replacement gpt-5.6-terra. gpt-5-mini-2025-08-07 stores shutdown date 2026-12-11 and replacement gpt-5.6-terra. gpt-5.2-codex stores shutdown date 2026-07-23 and replacement gpt-5.6-sol. Those dates are the OpenAI API. The Azure rows for gpt-5-mini-2025-08-07 and gpt-5.2-codex-2026-01-14 store 2027-07-13. Plan the earlier date on the API that lists it.
What does Azure return after retirement?
The lifecycle page says a Retired model is removed from service and: "Removed from service. All inference requests return 410 Gone." See Azure OpenAI retired models return 410 Gone.
Will every deployment upgrade itself?
No. The lifecycle page says: "For Global Standard, Data Zone Standard, and Standard deployment types, Microsoft manages automatic upgrades when a model version is retired:" And: "Provisioned deployments are NOT auto-upgraded. Provisioned customers must manually migrate to the replacement model." Working with models says: "Automatic model updates are only supported for Standard deployment types." NoAutoUpgrade means: "The model deployment never automatically upgrades. Once the retirement date is reached the model deployment stops working." null is equivalent to OnceCurrentVersionExpired. These three rows have an empty replacement cell, so they do not name an upgrade target.
How do I find deployments that still use these versions?
Working with models says: "To query the current model deployment settings including the deployment upgrade configuration for a given resource use Deployments List." Read properties.model.name and properties.model.version. The model versions page says: "Go to your deployment in the Foundry portal, then open the Details tab to see the current model version." The migration page says: "You also need an inventory of the model deployments your workload uses, including their deployment types (Standard, Provisioned, or Batch)."
Do fine-tuned deployments of these versions retire on July 13, 2027?
The base retirement date is 2027-07-13. The fine-tune tables do not list these three versions. gpt-5-mini-2025-08-07: no fine-tune dates are stored, and the fine-tune tables do not list this version. gpt-5.1-2025-11-13: no fine-tune dates are stored, and the fine-tune tables do not list this version. gpt-5.2-codex-2026-01-14: no fine-tune dates are stored, and the fine-tune tables do not list this version. Both pages say: "For existing customers only. Otherwise, training retirement occurs at base model retirement."
Does Azure Government list the same date?
The Azure Government schedule lists gpt-5.1 version 2025-11-13 as GA with retirement date 2027-07-13 and an empty replacement cell. That table does not list gpt-5-mini or gpt-5.2-codex. The public-cloud schedule lists all three ids on 2027-07-13.