Getting a ton of Server Errors

Question

Getting a ton of Server Errors

Nitin Kumar 0

I am seeing a lot of Server Errors (5xx). It looks like that it started at 3/30/3036 4 AM for my Document Intelligence resources. There are more than 13.1 K errors in past 10 hours..

resource 1

User's image

resource 2

User's image

Can you please advice on this?..

Anshika Varshney 9,740 Reputation points Microsoft External Staff Moderator

2026-04-10T05:16:39.8633333+00:00

Hi Nitin Kumar,

Thanks for sharing the details.

If you are seeing a large number of 5xx Server Errors for your Document Intelligence resource, this usually means the request is reaching the service, but the failure is happening during processing on the service side.

Please try checking the following:

First, verify the current service health to see if there are any ongoing platform issues in your selected region: [status.clo....microsoft]

Sometimes these types of errors can happen due to temporary service unavailability or high request volume.

Next, check your Azure Monitor logs for the resource to see if there are any spikes in request rate, latency, or failure patterns that started around the time the issue began.

If the errors appeared after multiple successful requests, it may also be related to request limits or service throttling. In such cases, reducing the request frequency or retrying after a short delay may help stabilize the requests. [learn.microsoft.com]

You can also review the Usage and Quotas section in your Azure resource to confirm that the service limits have not been exceeded.

Monitoring error patterns and retrying failed requests can help reduce the impact when these types of temporary server-side issues occur.

Hope this helps. Do let me know if you have any further queries.

Thankyou!

1 answer

Your answer

Anshika Varshney 9,740 Reputation points Microsoft External Staff Moderator

2026-04-10T05:16:39.8633333+00:00

Hi Nitin Kumar,

Thanks for sharing the details.

If you are seeing a large number of 5xx Server Errors for your Document Intelligence resource, this usually means the request is reaching the service, but the failure is happening during processing on the service side.

Please try checking the following:

First, verify the current service health to see if there are any ongoing platform issues in your selected region: [status.clo....microsoft]

Sometimes these types of errors can happen due to temporary service unavailability or high request volume.

Next, check your Azure Monitor logs for the resource to see if there are any spikes in request rate, latency, or failure patterns that started around the time the issue began.

If the errors appeared after multiple successful requests, it may also be related to request limits or service throttling. In such cases, reducing the request frequency or retrying after a short delay may help stabilize the requests. [learn.microsoft.com]

You can also review the Usage and Quotas section in your Azure resource to confirm that the service limits have not been exceeded.

Monitoring error patterns and retrying failed requests can help reduce the impact when these types of temporary server-side issues occur.

Hope this helps. Do let me know if you have any further queries.

Thankyou!

Answer 1

Hi Nitin Kumar

A lot of 5xx points towards quota exhaustion, frequent rate limit, unhealthy resources etc.

Quoting them all below for troubleshooting.

1. Check service health

Visit the Azure status page for your region to see if there’s an ongoing platform outage or degradation: https://status.azure.com/en-us/status

2. Review your resource’s health

In the Azure portal, go to your Document Intelligence resource → Resource health.
- Look for any recent incidents or outages in that blade.

4. Verify quotas and throttling

In the portal’s Usage + quotas page for your resource, confirm you haven’t exceeded any request rate or throughput limits.
- If you are close to your quota, consider adding retry logic with exponential back-off or reducing request concurrency and

Please check the file size /request limit here . https://dotnet.territoriali.olinfo.it/en-us/azure/foundry/agents/concepts/limits-quotas-regions#limit-error-reference

5. Consider transient/back-off logic

Many server-side errors are transient. Implement a retry policy (3 – 5 retries with exponential back-off) to smooth out temporary spikes.

6. Check for CMK-related issues (if applicable)

If you’re using customer-managed keys (CMK) for encryption, stale key caches can cause ServiceUnavailable errors. You can refresh the CMK cache or switch to Microsoft-managed keys temporarily.

Opt for Batch request/PTU (Provisioned throughput unit- for dedicated SLA compared to Pay as you go quota)

8. Load balance with multi- region endpoint to reduc

9. Reduce total size of your payload

If you’ve gone through these steps and still see a high volume of 5xx errors, please let us know:

Which region(s) your resources are in
Whether you’re using any custom models or customer-managed keys
Rough request volume or pattern (e.g., bursts vs. steady stream)
Exact error codes you see in the responses (500 vs. 503, etc.)

Hope this helps stabilize things!

Reference list

Azure Status: https://status.azure.com/en-us/status
Azure Monitor Metrics: https://dotnet.territoriali.olinfo.it/azure/azure-monitor/essentials/metrics-overview
Usage and Quotas for Document Intelligence: https://dotnet.territoriali.olinfo.it/azure/ai-services/document-intelligence/quotas-limits
Document Intelligence Known Issues: https://dotnet.territoriali.olinfo.it/azure/ai-services/document-intelligence/reference/known-issues?view=doc-intel-4.0.0
Best Practices to stay in limit

Please help fill the details in support ticket link shared in private message if the issue persists even loading reducing payload and balancing with multi-region endpoints.

Thank you.

Manas Mohanty 16,190 Reputation points Microsoft External Staff Moderator

2026-04-16T01:05:35.0533333+00:00

Hi Nitin Kumar

I have shared all best practices to troubleshoot and tackle internal server error.

Please let us know if you had followed up queries through private message.

Thank you.

Share via

Getting a ton of Server Errors

1 answer

Your answer