Diagnose Azure OpenAI latency issues, identify noisy-neighbor effects, and improve application performance
Diagnostic Playbook Azure OpenAI Standard / PAYG Azure Monitor Front Door Failover How To Diagnose Noisy-Neighbor Latency in Azure OpenAI Standard Deployments Your p99 tripled overnight. You changed nothing. The status page is green. This is the failure mode nobody wants to admit is real on a shared platform — regional demand from other tenants degrading your latency — and the fix isn't to complain, it's to prove it with the right metric, then route around it. The failure signature this guide resolves # Azure Monitor — the metric that reveals it (measured on the Azure OpenAI resource): Metric: AzureOpenAITimeToResponse split by ModelDeploymentName aggregation Avg + P99 P50 P95 P99 yesterday 09:00-10:00 340 ms 1,240 ms 1,880 ms today 09:00-10:00 410 ms 3,910 ms 8,720 ms <-- 4.6x on P99 # Prompt/completion token counts unchang...