Share via

Azure API returns 500 when creating a webhook subscription on an eventgrid using pulumi

Mohammad Alinia 20 Reputation points
2025-12-26T01:52:20.99+00:00

Hi there,

I'm getting this error while trying to create a resource:

error: Status=500 Code="InternalServerError" Message="The operation failed due to an internal server error. The initial state of the impacted resources (if any) are restored. Please try again in few minutes. If error still persists, report 79865511-55c8-4dc1-aefd-27f28ec95ac1:12/2/2025 5:20:49 AM (UTC) to our forums for assistance or raise a support ticket ."

I have tried a few times over the course of a few days.

I am using an IaC tool (pulumi) to create/update a webhook subscription for an event grid topic. Azure API is returning a 500 with no further details.

Any ideas why this might be happing?

Azure Event Grid
Azure Event Grid
An Azure event routing service designed for high availability, consistent performance, and dynamic scale.
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-12-26T01:53:28.4633333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error you're encountering (Status=500) indicates an internal server error when trying to create a webhook subscription for an Azure Event Grid topic. This type of error can occur for various reasons, including temporary issues with the Azure service itself or misconfigurations in the request.

    Here are a few steps you can take to troubleshoot this issue:

    1. Check Azure Status: Sometimes, Azure services may experience outages or issues. You can check the Azure status dashboard to see if there are any ongoing incidents affecting Event Grid.
    2. Review Diagnostic Logs: Enable diagnostic settings for your Event Grid topic to capture and view logs related to publish and delivery failures. This may provide more insight into what is causing the error.
    3. Validate Configuration: Ensure that the configuration of your webhook subscription is correct. This includes checking the webhook URL and any associated authentication settings.
    4. Retry the Operation: Since the error message suggests trying again later, it may be a transient issue. Wait a few minutes and attempt the operation again.
    5. Contact Support: If the issue persists, consider raising a support ticket with Azure support, providing them with the error code and the correlation ID mentioned in the error message for further assistance.

    By following these steps, you may be able to identify the cause of the internal server error and resolve the issue.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.