An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
Hi Rahul Shah,
This behavior is expected and is tied to how Azure OpenAI model versioning and upgrade policies work.
In Azure OpenAI, deployments are created against a model family (for example, GPT‑4) and can be configured to either:
- Automatically move to the latest default version, or
- Stay pinned to a specific version until that version is retired.
If your GPT‑4.0 deployment was created with the default (auto‑update) policy, Azure will automatically upgrade it when:
- A newer version becomes the default, or
- The currently deployed version reaches its retirement date.
Microsoft documents this behavior clearly: Azure notifies customers ahead of time when a new version becomes the default, and older versions are kept available only until their scheduled retirement. Once retired, deployments are automatically moved forward to a supported version to avoid service disruption. [techcommun...rosoft.com]
What you can do going forward
- If you need strict behavior consistency, deploy a specific model version and choose an update policy that does not auto‑upgrade.
- Plan for periodic validation, as response quality and behavior can change slightly between model versions.
- Keep an eye on the official model retirement and upgrade announcements so you can test newer versions before they become mandatory.
In short: Nothing is “wrong” with your deployment this is standard lifecycle management for Azure OpenAI models. Pin versions when needed and treat upgrades as part of normal operational planning.
Hope this helps clarify things. Do let me know if you have any further queries.
Thankyou!