Azure Content Safety internal error

Hello Adam Eleraky,

Welcome to Microsoft Q&A .Thank you for reaching out.

The error shown indicates that Azure AI Content Safety image analysis requests are reaching the service successfully but are failing during internal processing. The response returned is HTTP 500 (InternalServerError) with error code InternalError, along with a request ID and timestamp.

This is happening as Azure AI Content Safety is encountering an internal processing failure while analyzing images, resulting in a fail‑safe rejection of the request. The request is accepted, authenticated, and routed correctly, but an internal dependency fails before moderation results can be produced.

The most common and supported reasons for this behavior can be

• Transient service instability
• Regional service degradation
• Internal scaling or load conditions

For safety‑critical AI services, internal exception details are intentionally not exposed. Only a request ID, timestamp, and generic error code are returned so that failures can be traced internally without exposing platform internals.

Please check if the following troubleshooting steps help

1. Check Azure Service Health
   • Review regional health for Azure AI services in Sweden Central.
   • https://status.azure.com/
2. Retry with exponential backoff
   • Implement retries for InternalError responses (for example: 3 attempts with 1s, 2s, and 4s delays).
3. Validate request basics to confirm
   • Ensure supported image formats (JPEG or PNG) and size limits are respected.
   • When using Base64 encoding, confirm only the raw Base64 string is sent (no data URI prefix).
   • These checks are precautionary, as malformed requests typically return 4xx errors.
4. Cross‑region validation
   • Deploy a temporary Content Safety resource in another supported region (for example, West Europe).
   • If requests succeed there, this confirms a regional service condition.
5. Capture diagnostic identifiers
   • Retain the request ID and timestamp from failed calls.
   • These details are required for backend investigation.

References:

What is Azure AI Content Safety? - Azure AI services | Microsoft Learn

Azure status

Azure reliability documentation | Microsoft Learn

Thank you!

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the response was helpful. This will be benefitting other community members who face the same issue.

The InternalError with HTTP 500 is a server-side issue in Azure AI Content Safety, not a problem with the request payload or your resource configuration.

For InternalError, the documented guidance is:

1. Retry the request after a short delay (implement a small exponential backoff). Transient platform issues are often resolved quickly.
2. If the issue persists, open a support ticket with Azure Support so the service team can investigate using your Request Id, timestamp, region (Sweden Central), and resource name.

Since this was working previously and then started failing without changes on your side, treat it as a transient or regional service issue rather than a client bug. If repeated retries over time still return InternalError, contact support via the Azure portal and include:

• The full error payload (including Request Id and timestamp shown in your logs).
• The region (Sweden Central) and Content Safety resource name.
• The operation type (for example, image analysis) and approximate time window when failures started.

References:

• Azure AI Content Safety error codes
• Azure AI Content Safety client library for .NET - version 1.0.0
• Azure ContentSafety client library for Java - version 1.0.17
• Azure AI Content Safety Frequently Asked Questions