Skip to content

Routing and reliabilityChecklist

What an Azure OpenAI deployment does on retirement day

A retiring Azure OpenAI model does not always fail. Depending on deployment type and upgrade policy, the deployment may be swapped to another model without an error, or return 410 Gone. This checklist maps each behaviour to a routing rule for the Nov 19, Dec 15 and Feb 9 dates.

By INFRO Editorial

Published

7 min read

Luminous routing paths connecting one application node to many AI model endpoints

In short

On retirement day a Standard-type deployment is either auto-upgraded to another model with no error, or, if its policy is NoAutoUpgrade or it is provisioned, it returns 410 Gone. The two outcomes need different routing rules: a canary before the date for the silent swap, an explicit fallback target for the hard failure.13

Key takeaways

  • Retired Azure models return 410 Gone, but Standard-type deployments can instead be auto-upgraded to a replacement, so a quiet swap is as likely as an error.
  • Provisioned deployments are never auto-upgraded, and NoAutoUpgrade deployments stop working at the date, so both need a fallback target before it.
  • Auto-upgrades roll out region by region, so deployments in different regions can answer with different models during the window.
  • Whisper, tts, tts-hd, gpt-5 and gpt-5-nano list no replacement on Microsoft's schedule, so plan for a hard failure, not a swap.
  • Quota is pooled per model and version per subscription, and the replacement's Tier 1 limits are lower than the o-series it replaces, so check headroom before shifting traffic.

What the date does to a deployment

Azure's lifecycle has five stages, and the last one is blunt: once a model is Retired, every inference request returns 410 Gone, and no new deployments can be created.1 That is the failure you can alert on. The other outcome produces no error at all. For Global Standard, Data Zone Standard and Standard deployments, Microsoft manages automatic upgrades when a version retires, rolling out region by region.1 The deployment name stays the same and the model behind it changes.

Which of the two you get depends on three things you can read today: the deployment type, the version upgrade option, and whether the schedule lists a replacement. Dates alone do not tell you that. This checklist starts from the behaviour and derives the routing rule, then applies it to the three dates in play.

Today is 2026-11-05. The o-series date is 14 days away, whisper and tts are 40 days away, and GPT-5 is 96 days away.

The three dates and what Microsoft lists

The schedule page, last updated 2026-09-23 when read, gives these rows.2

Deployed modelRetiresListed replacement
o1, o1-pro, o3, o3-pro, o3-deep-research2026-11-19gpt-5.6-sol
o3-mini, o4-mini2026-11-19gpt-5.6-terra
whisper 001, tts 001, tts-hd 0012026-12-15none listed
gpt-5 and gpt-5-nano, 2025-08-072027-02-09none listed
Azure OpenAI retirement rows for the three dates, from Microsoft's schedule.

Microsoft says the replacement column is its recommended target and, where supported, the target for automatic upgrades.2 A dash therefore means you cannot read an upgrade target off the page. Microsoft also says it names the official replacement roughly 90 to 120 days before retirement, not sooner.1 For Dec 15 that window has already passed with nothing listed. For Feb 9 it runs from about Oct 12 to Nov 11, so a row could appear any day. Re-read the page before you finalise the GPT-5 rule.

Four deployment states, four routing rules

The row to find first is your deployment's own state. The upgrade option has three values: OnceNewDefaultVersionAvailable, OnceCurrentVersionExpired and NoAutoUpgrade. A missing value is null and behaves as OnceCurrentVersionExpired.3 Under NoAutoUpgrade the deployment stops working at the retirement date.3

State on the dateWhat Azure doesWhat your client seesRouting rule
Standard-type, null or OnceCurrentVersionExpiredUpgrades to the default version at retirement3, region by region1Success, different modelCanary the replacement before the date; watch for a changed model, not for errors
Standard-type, NoAutoUpgradeStops working3410 Gone1Explicit fallback target on a different deployment
ProvisionedNot auto-upgraded; you migrate manually1410 Gone after the dateReplacement deployment plus a Standard overflow target
PreviewForce-upgraded or terminated, at least 30 days notice1Swap or 410 GoneDo not route production traffic here
Retirement-day behaviour by deployment state, and the routing rule it implies.

I could not confirm from the pages read how the Standard-type auto-upgrade and a NoAutoUpgrade setting interact beyond the sentence quoted above. Test it on one non-production deployment rather than assuming.

Why the silent swap is the dangerous one

A fallback rule fires on failure. An auto-upgrade is a success with a different model: different reasoning behaviour, token usage and output shape, and nothing to retry. Microsoft notes upgrades can happen even if the new version is not yet separately available in that region.1 Because they roll region by region, two regional deployments behind one route can answer with different models for a while. If you want determinism, set NoAutoUpgrade on deployments you have not evaluated, and accept that you then own the failure path.

Checklist: before the date

Run these per deployment, not per model.

  • List every deployment of the retiring models, with its deployment type (Global Standard, Data Zone Standard, Standard or provisioned), region and subscription.
  • Read each deployment's versionUpgradeOption. The Azure CLI can read it but cannot update it; use REST, PowerShell or the portal to change it.3
  • Query lifecycle fields from the Models API (lifecycleStatus, deprecation.inference, per-SKU deprecationDate) and diff them against your own registry nightly.1
  • Decide per deployment: move it yourself to an evaluated replacement, let Azure upgrade it, or set NoAutoUpgrade and fail over.
  • Create the replacement deployment now, in each region and deployment type that serves traffic, and send it a small share of real traffic.
  • Confirm API compatibility, feature support, regional availability, capacity and quota for the target, as Microsoft advises.1
  • Forward retirement notices to the route's owner: Microsoft emails subscription owners, which may be a different team.1
read the upgrade policy
az cognitiveservices account deployment show \
  --resource-group "$RG" --name "$ACCOUNT" --deployment-name "$DEPLOYMENT" \
  --query "properties.{model:model.name,version:model.version,upgrade:versionUpgradeOption}"

A null upgrade value means the option was never set, which behaves as OnceCurrentVersionExpired.3

Quota: the replacement is a different pool

Since May 7, 2026 Foundry tracks quota at the subscription level. Global Standard deployments of the same model and version share one pool across all regions; Data Zone Standard shares one per data zone.4 By that rule a deployment moved to a different model draws on the replacement's pool, not the o-series pool it came from. I could not confirm how capacity is carried across an auto-upgrade, so check the assigned capacity after the move. A capacity value of 1 equals 1,000 tokens per minute.3

Tier 1 Global Standard limits show why this matters:4

ModelRPMTPM
o31,0001,000,000
o4-mini1,0001,000,000
o3-mini5005,000,000
gpt-5.6-sol250250,000
gpt-5.6-terra250250,000
Tier 1 Global Standard quota, from Microsoft's quota reference.

Quota tiers rise automatically with usage, and your subscription may sit higher than Tier 1.4 Look up your tier through the control plane API before assuming. If the replacement's limits are lower than your peak, an upgrade turns into 429 responses on the day, which is exactly the case a fallback target should absorb.

Failover rules that fit each behaviour

Keep the application calling a stable name rather than a deployment id. In INFRO a route is a name your application sends as model, resolving to an ordered list of your own connections and the model each should serve.5 Priority routes walk targets in order; weighted routes choose the first target in proportion to weight and still fail over, and a weight-0 target is a standby.5

An illustrative layout, not INFRO's configuration syntax:

YAML
route: support-reasoning
phase_1_before_nov_19:
  primary: azure-o3-deployment          # retiring
  canary:  azure-gpt-5-6-sol-deployment # small weight, measured
phase_2_after_cutover:
  primary:  azure-gpt-5-6-sol-deployment
  standby:  second-region-or-provider   # different failure domain
  rule: on 429 or 5xx before first token -> next target

Three points follow from the behaviours above.

  1. Put the canary before the date. It is the only control that touches the silent-swap case.
  2. Make the standby a different failure domain. A second deployment of the same retiring model fails with the first. Connection failover is same-model, and model fallbacks are a separate, opt-in list of up to five catalog models.6
  3. Do not assume 410 triggers failover. INFRO's docs list 5xx, timeout, 429, 401/403, 404 and 400/422 as upstream failures that move on to the next connection.6 A 410 is not named on the page I read. Test it in a drill, and if it does not move on, add a failure rule for that kind; failure rules decide per failure kind whether to retry, move on or stop.

For whisper, tts and tts-hd, the fallback must be an audio model that takes the same request shape. A text model cannot stand in, so verify the standby accepts your voice, format and language parameters before the date. The same goes for GPT-5 with no listed replacement: pick the target by evaluating it on your prompts, as Microsoft advises.1

Verify after the date

  • Count requests by status for each deployment for 24 hours: any 410 means a deployment you missed.
  • Compare the model and version each deployment reports against the one you expected, in every region.
  • Check latency, output length and cost per request against the week before; an upgrade shifts all three without an error.
  • Confirm the standby took traffic in a forced test, not only on paper.

Applying this with a gateway

INFRO's model retirements capability records each vendor's deprecations, warns organizations still sending a retiring model, and refuses it from the shutdown date before any provider call, naming the replacement. Those are vendor dates, and Azure keeps its own, so keep the Azure rows above in your own registry too. Routes, failover and routing rules apply the layouts in this article over your own Azure connection. Traffic changes flags a model answered by a new snapshot and longer answers, with an estimated weekly cost change; it sees request metadata, not answers, so it does not judge quality. The INFRO docs overview (opens in a new tab) describes the control plane;7 request failures that reach you use one error shape.8

Questions readers ask

Can a deployment stay on a retiring version past the date?
No. At retirement the model version is removed from service and all inference requests return 410 Gone.1 The only choices are which replacement the deployment moves to and whether you or Azure make the move.
Who is told about an upcoming retirement?
For GA models, Microsoft sends a notice at least 60 days before retirement to subscription owners with active deployments, and posts a health advisory in Azure Service Health.1 Those owners are often not the application team, so forward the alert to whoever owns the route.

From the team that builds it

Where this shows up in INFRO

INFRO is a control plane in front of the provider accounts you already hold. The capabilities below are the parts of it this article touches, each with the documentation that defines its behaviour.

  • Health-aware routing

    Available with a plan

    Named routes use priority or weighted targets over your own connections, with health checks, retries and failover.

    Read the documentation for Health-aware routing
  • Automatic failover

    Available with a plan

    A route that times out or 5xxs before the response starts is retried elsewhere without your client seeing it.

    Read the documentation for Automatic failover
  • Routing rules

    Available with a plan

    If-rules on a route send matching requests to their own targets, by metadata, feature, end user, key, project, prompt size, streaming, images, tools or time of day. Failure rules decide per failure kind whether to retry, move on or stop.

    Read the documentation for Routing rules
  • Traffic changes

    Available with a plan

    Changes in your traffic that come with no error: a model answered by a new snapshot, longer answers, a lost prompt cache, more fallbacks, answers cut off by the length limit, slower responses or a new error mix. Each finding names the likely cause and the estimated weekly change in provider cost. INFRO sees request metadata, not answers, so it does not judge answer quality.

    Read the documentation for Traffic changes
  • Model retirements

    Available with a plan

    INFRO records each vendor's model deprecations and shutdown dates, warns organizations still sending a retiring model, and from the shutdown date refuses it before any provider call, naming the replacement.

INFRO accounts are self-serve. Provider usage is billed to you by your providers; INFRO charges a software subscription and takes 0% of model spend. See plans.

Sources

Numbered in order of first citation. Each was opened and checked against the claim on the date shown.

  1. 1.Microsoft Foundry Models lifecycle and support policy (opens in a new tab) — Microsoft Learn. Accessed Nov 5, 2026.
  2. 2.Model retirement schedule - Microsoft Foundry (opens in a new tab) — Microsoft Learn. Accessed Nov 5, 2026.
  3. 3.Azure OpenAI in Microsoft Foundry Models working with models (opens in a new tab) — Microsoft Learn. Accessed Nov 5, 2026.
  4. 4.Azure OpenAI in Microsoft Foundry Models quotas and limits (opens in a new tab) — Microsoft Learn. Accessed Nov 5, 2026.
  5. 5.Routes (opens in a new tab) — INFRO. Accessed Nov 5, 2026.
  6. 6.Failover & fallbacks (opens in a new tab) — INFRO. Accessed Nov 5, 2026.
  7. 7.INFRO documentation overview (opens in a new tab) — INFRO. Accessed Nov 5, 2026.
  8. 8.Errors (opens in a new tab) — INFRO. Accessed Nov 5, 2026.

About this article

Read on 2026-11-05: Microsoft's Foundry lifecycle policy, model retirement schedule (last updated 2026-09-23), working-with-models and quotas pages, plus INFRO's docs overview, routes, failover and errors pages. Left out as unconfirmed: how an auto-upgraded deployment's capacity is carried over, and whether INFRO's failover treats an upstream 410 as a failover trigger.

Last checked against its sources on . The next review is due by . No separate named reviewer is recorded for this article.

How articles are written, sourced and corrected is set out in the editorial standards.