AI Foundry Model Availability¶
Real-time tracking of Azure AI Foundry model availability across regions and deployment types.
Recent Availability Changes
| Date | Change | Model | Region | SKU Type |
|---|---|---|---|---|
| 2026-05-13 | Added | australiaeast | gpt-4.1 | Deployments Batch |
| 2026-05-13 | Added | australiaeast | gpt-4.1-mini | Deployments Batch |
| 2026-05-13 | Added | australiaeast | gpt-4.1-nano | Deployments Batch |
| 2026-05-13 | Added | australiaeast | gpt-4o | Deployments Batch |
| 2026-05-13 | Added | australiaeast | gpt-4o-mini | Deployments Batch |
| 2026-05-13 | Added | australiaeast | gpt-5 | Deployments Batch |
| 2026-05-13 | Added | australiaeast | gpt-5.1 | Deployments Batch |
| 2026-05-13 | Added | australiaeast | o3 | Deployments Batch |
| 2026-05-13 | Added | australiaeast | o3-mini | Deployments Batch |
| 2026-05-13 | Added | australiaeast | o4-mini | Deployments Batch |
… and 4816 more — see full change history
Deprecation & Retirement Notices¶
Retiring Within 30 Days — 1 model version
These models require immediate migration. After the retirement date, API calls will return errors.
| Model | Version | Category | Retirement Date | Status | Replacement |
|---|---|---|---|---|---|
| gpt-4o | 2024-11-20 | Text Generation | 2026-06-05 | Retiring Soon | gpt-5.1 |
Upcoming Retirements (31-90 Days) — 2 model versions
Plan and test your migration to the replacement model.
| Model | Version | Category | Retirement Date | Status | Replacement |
|---|---|---|---|---|---|
| o1 | 2024-12-17 | Text Generation | 2026-07-15 | Retiring | o3 |
| o3-mini | 2025-01-31 | Text Generation | 2026-08-02 | Retiring | o4-mini |
Already Retired — 8 model versions
These models are no longer available. Migrate to the listed replacement.
| Model | Version | Category | Retirement Date | Status | Replacement |
|---|---|---|---|---|---|
| gpt-5-chat | 2025-08-07 | Text Generation | 2026-03-01 | Retired | gpt-5.2-chat |
| gpt-5-chat | 2025-10-03 | Text Generation | 2026-03-01 | Retired | gpt-5.2-chat |
| gpt-4o | 2024-05-13 | Text Generation | 2026-03-31 | Retired | gpt-5.1 |
| gpt-4o | 2024-08-06 | Text Generation | 2026-03-31 | Retired | gpt-5.1 |
| gpt-4o-mini | 2024-07-18 | Text Generation | 2026-03-31 | Retired | gpt-4.1-mini |
| gpt-4o-audio-preview | 2024-12-17 | Audio | 2026-02-02 | Retired | gpt-audio |
| gpt-4o-realtime-preview | 2024-12-17 | Audio | 2026-02-02 | Retired | gpt-realtime |
| dall-e-3 | 3 | Image And Video | 2026-02-18 | Retired | gpt-image-1-mini |
Deprecation vs Retirement — What's the Difference?
Deprecation marks a model version as no longer recommended. It still works, but no new deployments can be created. After deprecation you should begin migrating to the replacement model.
Retirement means the model version is fully removed. API calls will return errors after the retirement date. Always migrate before the retirement date.
| Phase | New Deployments | Existing Deployments | API Calls |
|---|---|---|---|
| Active | Allowed | Running | Working |
| Deprecated | Blocked | Running | Working |
| Retired | Blocked | Removed | Errors |
See full retirement details and Microsoft's model lifecycle docs.
Browse By¶
| View | Description |
|---|---|
| All Models | Complete model catalog with SKU details |
| By Region | Find what's available in your region |
| By SKU Type | Filter by deployment type |
| Change History | Recent availability changes |
Last updated: 2026-05-19 11:18 UTC