This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 44%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMB%3C/text%3E%3C/svg%3E)
We are currently working on a production workload on Azure OpenAI in the Switzerland North region using any GPT Version that can be deployed with the Standard deployment type.
About one to two weeks ago, GPT-4.1 was available in the Switzerland North region with the Standard deployment type. However, this is no longer the case. Currently, no GPT large language models (LLMs) are available for Standard deployments in Switzerland North—only embedding and speech recognition models are listed.
Could you clarify when GPT LLMs will be available again in the Switzerland North region with the Standard deployment type?
An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
Those are the only models available when filtered Region Switzerland North, Deployment SKU Standard, Lifecycle Generally available. For DataZone Standard there are available gpt 5 series that would be fine, but for Deyployment SKU Standard there are only the listed model available .
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 82%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWW%3C/text%3E%3C/svg%3E)
Same issue here. According to the official docs, GPT-4o and GPT-4.1 shouldn't be deprecated until October this year — so either Microsoft moved the date up without telling anyone, or this is a bug.
If the timeline was changed, the documentation needs to be updated immediately so people stop relying on wrong info. If it wasn't changed, then this is clearly a bug and it needs to be fixed ASAP.
This is already seriously affecting our work. We shouldn't have to find out about critical changes through broken deployments instead of proper communication. Please fix this or update the docs — this isn't acceptable as it stands.