An Azure event routing service designed for high availability, consistent performance, and dynamic scale.
Hi @Han Tu ,
Thank you for reaching out to Microsoft Q & A !
And Thanks for providing the error details and for confirming that the same MQTT namespace configuration works in East US.
The error you received:
The operation failed due to an internal server error.
The initial state of the impacted resources (if any) are restored.
does not identify a specific configuration or quota problem. Since the same configuration works in East US, a transient regional or service-side issue is one possibility, but I would avoid concluding that it is definitively a Central US backend failure without additional service-side evidence.
A few things I would check:
Retry the operation after some time and see whether the same error occurs.
Check Azure Service Health for Event Grid in Central US during the affected time window.
Check the namespace's Resource Health if the namespace was partially created.
If the operation continues to fail only in Central US, provide the correlation ID, timestamp, subscription/resource details, and the exact API/provider version when opening a support request. The correlation ID in the error is particularly useful for service-side investigation.
Because the same configuration works in East US, if the issue persists in Central US after retries and the configuration has been verified, the correlation ID and timestamp can be provided to Azure Support for further investigation of the provisioning failure.
Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.