An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
A timeout in preprod usually indicates a network path or endpoint configuration problem rather than a model-specific issue.
- Verify DNS resolution for the Azure OpenAI endpoint.
Expected result: the endpoint resolves correctly. If a private endpoint is configured, the private IP should match the private IP in the DNS configuration of the private endpoint.nslookup <azure-openai-endpoint> - Test HTTPS connectivity to the resolved private IP on port 443.
Expected result: this succeeds only from a machine on the same private network as the Azure OpenAI resource. If it fails, check these common causes:Test-NetConnection <private-ip> -Port 443- DNS is resolving incorrectly.
- The preprod machine is not on the same private network.
- A customer firewall is blocking port 443.
- If the workload runs on AKS, check for blocked outbound traffic.
- Ensure outbound HTTPS traffic on port 443 is allowed to the Azure OpenAI endpoint.
- Check NSG, firewall, and network policy rules.
- If using network policies:
kubectl get networkpolicies -n kube-system
- Check the exact error pattern in logs if available.
-
401 Unauthorized: managed identity might be missing theCognitive Services OpenAI Userrole. -
404 Not Found: endpoint URL or deployment name might be wrong. -
Connection refusedorName resolution failed: DNS or network issue. -
Token acquisition failed: workload identity configuration issue.
-
- If this is an intermittent server-side
500 Unexpected special tokenerror rather than a pure timeout, reduce prompt temperature to less than 1 and use client retry logic. Reattempting the request often succeeds. - If the issue is isolated to one Azure region while another region works, it can be a regional service incident. One documented case in East US was mitigated after a service-side issue.
For this preprod timeout scenario, the fastest end-to-end path is:
- Run
nslookupon the Azure OpenAI endpoint from preprod. - Run
Test-NetConnection <private-ip> -Port 443from preprod. - If that fails, fix DNS, private network routing, NSG/firewall, or proxy rules.
- If connectivity succeeds, verify the endpoint, deployment name, and identity permissions.
References: