Azure Event Grid – HTTP 500 Error on Domain Endpoint | Central India | 2026-03-09

Hi @Anita Madbhavi,

Thanks for reaching out to Microsoft Q&A.

Here’s how you can dig in and help us find the root cause:

1. Enable and collect diagnostic logs
   • In the Azure portal, go to your Event Grid Domain → Diagnostic settings.
   • Turn on PublishLogs and DeliveryLogs, and send them to a Log Analytics workspace or storage account.
   • Re-reproduce the call in your time window (2026-03-09T20:50:59Z to 20:51:09Z).
2. Retrieve the request/trace ID from the response headers
   • On the client side, capture headers like x-ms-client-request-id, x-ms-correlation-request-id and aeg-event-type.
   • Share those IDs with us so we can search the logs in our backend.
3. Inspect the logs
   • In Log Analytics, run a query in the timeframe you specified:

Example Kusto:

EventGridDeliveryLogs
| where TimeGenerated between (datetime(2026-03-09T20:50:59Z) .. datetime(2026-03-09T20:51:10Z))
| where StatusCode == 500
| project TimeGenerated, OperationName, CorrelationId, StatusCode, Message  

• Look for any exception message or stack trace that points to a misconfiguration or transient issue.

1. Check your payload & quotas
   • Make sure the events you’re sending conform to the Event Grid schema. An unexpected property or too-large payload might trigger internal errors.
   • Verify you haven’t hit any quotas (topics, domains or subscriptions) in Central India.
2. Validate network/connectivity
   • Even though the call reached the service, transient network issues can sometimes manifest as 500s. Review any Azure Firewall or NSG logs if you’re using private networking.

References:

How to enable and view Diagnostic logs for Event Grid topics or domains

Common errors with recommended solutions for Event Grid

How to view metrics for Event Grid topics and subscriptions

Hope this helps!

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.

HTTP 500 responses from an Azure Event Grid domain indicate an internal failure in the Event Grid service while processing the request. The exact server-side cause (for example, internal routing failure, transient platform issue, or backend dependency error) is not exposed in the client response and cannot be determined solely from the HTTP status code.

To investigate and narrow down the cause from the Azure side of the subscription that owns the Event Grid domain:

1. Enable and review diagnostic logs for the Event Grid domain
   • Turn on diagnostic settings for the Event Grid domain to capture publish and delivery failure logs. These logs will show failed publish attempts, including timestamps and error details that are not visible to the caller.
   • Once enabled, review the logs for entries around 2026-03-09T20:50:59Z–2026-03-09T20:51:09Z for this domain endpoint.
2. Check Event Grid metrics
   • In the Event Grid resource, review metrics (for example, publish failures, delivery failures, and throttling) for the same time window. Spikes in failures or throttling can indicate transient platform issues or misconfiguration.
3. Verify regional service health
   • Use the Azure status dashboard to confirm whether there were any known incidents or outages affecting Azure Event Grid in the Central India region during that time.
4. Check for connectivity or network restrictions
   • If the domain uses IP firewall rules or private endpoints, verify that the calling client’s IP address and network path are allowed. Although misconfigured firewall or private endpoint settings typically result in HTTP 403 rather than 500, confirming network configuration helps rule out connectivity-related issues.
5. Implement retry logic for transient 500 errors
   • Because 500 errors can be transient (for example, due to backend upgrades or restarts), implement exponential backoff and retry in the client when a 500 is returned. This is a recommended practice for resilience with Event Grid.
6. Use correlation information and support if needed
   • If diagnostic logs and metrics do not explain the failure, capture the full response (including any Request-Id or correlation headers) from subsequent occurrences and open a support case through Azure Support. Support engineers can then use those IDs and the precise UTC timestamps to inspect internal telemetry for the domain.

The exact internal cause for the specific call at 2026-03-09T20:50:59Z–20:51:09Z can only be determined by examining the Event Grid domain’s diagnostic logs and, if necessary, by Azure Support using internal telemetry.

References:

• Troubleshoot Azure Event Grid issues
• Troubleshoot Azure Event Grid errors
• Troubleshoot connectivity issues - Azure Event Grid
• Publish MQTT messages via HTTP with Azure Event Grid
• Azure Event Grid client library for .NET - version 5.0.0