Azure OpenAI "GPT 5.6-sol" models report errors in various regions

Denniver Reining 0 Reputation points
2026-07-24T14:14:19.3766667+00:00

We have several deployments in multiple regions (Germany, France, Sweden) of multiple models, including GPT 5.6 SOL.

Since yesterday, there has been a decrease in performance with lots of disconnects. A few hours ago, they stopped working altogether.

Even in foundry playground, you only get "there was an issue with your request"-errors, when trying a simple "test"-prompt.

All other deployments (GPT 5.4, 5.5 etc) work fine.

Is anyone else experiencing this?

Foundry Models
Foundry Models

A catalog of AI models in Microsoft Foundry that you can discover, compare, and deploy using Azure’s built‑in tools for evaluation, fine‑tuning, and inference

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Allan Solomon Mejia 730 Reputation points
    2026-07-24T19:29:29.44+00:00

    Hi Denniver,

    Yes, we're seeing similar reports from other customers.

    Since the issue is occurring across multiple Azure regions (Germany, France, and Sweden), affects the Azure AI Foundry playground, and GPT-5.4/GPT-5.5 deployments continue to work normally, this points more toward a service-side issue affecting GPT-5.6 Sol rather than a deployment or configuration problem. The symptoms you describe was intermittent disconnection followed by "There was an issue with your request" for even simple prompts are consistent with a backend service degradation.

    In the meantime, I'd recommend:

    Checking Azure Service Health for any advisories related to Azure OpenAI or Azure AI Foundry in your affected regions.

    Capturing the x-ms-request-id and timestamp from failed API calls (or the browser's developer tools if reproducing the issue in the playground) to assist Microsoft Support.

    Temporarily routing production traffic to GPT-5.5 or another unaffected deployment until the issue is resolved.

    If the issue persists and no advisory is posted, opening a Microsoft Support request with the affected regions, deployment names, timestamps, and request IDs.

    Since the problem reproduces in the Foundry playground, it provides a strong indication that the issue is not application-specific and should help Microsoft narrow down the investigation.

    Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.