Event grid System.Net.Http.HttpRequestException: Response status code does not indicate success: 500

Question

Event grid System.Net.Http.HttpRequestException: Response status code does not indicate success: 500

Tobias Axelsson 0

Getting an error message when trying to send event grid event.
It looks like it is on the Azure side of things as I'm instructed to write here.

System.Net.Http.HttpRequestException: Response status code does not indicate success: 500 (An unexpected error has occurred. Please report the x-ms-request-id header value to our forums for assistance or raise a support ticket. Report '088fe5ba-66bb-432f-ba8e-b99e2fad75c1:11:6/8/2026 11:18:20 AM (UTC)' to our forums for assistance or raise a support ticket.).

Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-09T17:26:02.3666667+00:00

@Tobias Axelsson , following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.
Tobias Axelsson 0 Reputation points

2026-06-15T06:49:34.45+00:00

The Issue seem to have been on the Azure side of things as things solved itself after a while without my interaction.
Everything is now back in working order!
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-16T00:59:53.7433333+00:00

@Tobias Axelsson , Thanks for the confirmation. Looks like it was a transient issue, glad the issue is resolved.

2 answers

Your answer

Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-09T17:26:02.3666667+00:00

@Tobias Axelsson , following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.
Tobias Axelsson 0 Reputation points

2026-06-15T06:49:34.45+00:00

The Issue seem to have been on the Azure side of things as things solved itself after a while without my interaction.
Everything is now back in working order!
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-16T00:59:53.7433333+00:00

@Tobias Axelsson , Thanks for the confirmation. Looks like it was a transient issue, glad the issue is resolved.

Answer 1

The 500 status code indicates an internal error on the Event Grid service side. The error message explicitly asks to report the x-ms-request-id to Microsoft support or forums for investigation.

For this specific case, the appropriate actions are:

Verify that the Event Grid service is healthy in the target region using the Azure status dashboard.
Enable diagnostic logs and metrics on the Event Grid topic/namespace to confirm that the failure is not due to configuration, payload, or endpoint issues.
Since the service has already returned a 500 with a request ID and timestamp, open a support ticket with Microsoft (or post on the official forums) and include:
- The full x-ms-request-id value: 088fe5ba-66bb-432f-ba8e-b99e2fad75c1:11
- The timestamp: 6/8/2026 11:18:20 AM (UTC)
- The region, topic name, and operation being performed (for example, SendEvents or HTTP publish).

If the 500 error persists, diagnostics and support escalation are required because 500 responses are not caused by client-side validation errors (such as 400/403/413) and are handled by Event Grid’s internal retry and delivery mechanisms.

References:

Answer 2

Hi @Tobias Axelsson ,

A 500 from Event Grid generally means the service hit an unexpected error and the request didn’t complete successfully. In cases like this, the most useful next steps are to check whether it’s a transient platform issue and to verify your Event Grid request/configuration, using the request ID you were given.

Steps to do next:

Check Azure Service Health / regional issues
- Look at the Azure Status / Service Health dashboard to see if there’s an ongoing disruption or degradation in the region that hosts your Event Grid resources.
- (This is specifically recommended for 500 Internal Server Error troubleshooting.)
Enable and review diagnostic logs
- Turn on Azure Monitor diagnostic logs for the relevant Event Grid resources (namespace/topic/domain where applicable).
- Search for log entries around the same timestamp as your failure and look for the HTTP 500 entries plus any correlated request IDs / correlation IDs.
- This helps determine whether the backend failed due to transient conditions vs. a request/config problem.
Retry with exponential backoff (transient errors are common with 500s)
- If this is intermittent, implement a retry policy with exponential backoff.
- This aligns with guidance to handle transient platform/backend failures.
Validate configuration and connectivity
- Confirm the publishing endpoint, credentials/access keys, and event payload/format are correct.
- Also verify any network access controls involved (for example, firewall/IP restrictions on the target).
- If you recently changed routing/settings, temporarily revert to the last known working configuration to isolate the cause.

Notes specific to Event Grid:

In general, Event Grid publishing returns standard HTTP codes, where failures include structured error bodies (for many client errors). For 500, it’s typically a backend/internal condition rather than a simple validation issue, so the diagnostic logs + request id are the key path forward.

Hope this helps!

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

Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-12T17:38:14.89+00:00

@Tobias Axelsson , Following up to see if the provided answer was helpful. If this answers your query, do click Accept Answer =>Yes, and upvote it. If you have any further queries do let us know.