MQTT Broker Data Panel 500 Error and Routing Update Failure in Azure Portal

Question

MQTT Broker Data Panel 500 Error and Routing Update Failure in Azure Portal

RAJNI SINGH 5

In Azure Portal, the MQTT Broker data panel is returning a 500 error. Also, any attempt to update routing on the namespace fails with an internal server error.

This issue has been occurring since 26/07.

Error: "Update of your namespace failed with the following error: The operation failed due to an internal server error. The initial state of the impacted resources (if any) are restored. Please try again in a few minutes. If the error still persists, report be42e7ce-00b6-414e-9c34-8914664f1b7f:7/27/2026 11:13:22 AM (UTC) to our forums for assistance or raise a support ticket."

Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-07-27T11:48:52.3366667+00:00

Hello @RAJNI SINGH

Welcome to Microsoft Q&A, Thank you for your question.

To help investigate further, could you please share the Azure region of the Event Grid Namespace and confirm whether the issue affects only this namespace or multiple namespaces?

Additionally, if available, please share the Activity Log error details or Correlation ID associated with the failed routing update operation in the private chat.

This information will help determine whether the issue is related to the namespace configuration or a service-side problem.

Thank you.
RAJNI SINGH 5 Reputation points

2026-07-27T11:59:42.06+00:00

Azure region - West Europe
This issue is affecting all namespaces. I created a new one and then simply navigating to any options under Mqtt broker (Clients/Client groups/Topic Spaces section) in the portal it shows below error
Error:
Something went wrong with fetching clients.."Batch response item http error 500"

Not able to create new clients in new namespace as well.

Activity log shows the Write Namespace - failed with this error, nothing more.
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 be42e7ce-00b6-414e-9c34-8914664f1b7f:7/27/2026 11:13:22 AM (UTC) to our forums for assistance or raise a support ticket .
RAJNI SINGH 5 Reputation points

2026-07-27T12:03:19.39+00:00

Azure region - West Europe This issue is affecting all namespaces. I created a new one and then simply navigating to any options under Mqtt broker (Clients/Client groups/Topic Spaces section) in the portal it shows below error Error: Something went wrong with fetching clients.."Batch response item http error 500"

Not able to create new clients in new namespace as well.

Activity log shows the Write Namespace - failed with this error, nothing more. 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 be42e7ce-00b6-414e-9c34-8914664f1b7f:7/27/2026 11:13:22 AM (UTC) to our forums for assistance or raise a support ticket .

Michael Walser 0

We are experiencing the same issue here. We are also located in the West Europe region. All MQTT topic-spaces child operations (clients, caCertificates, clientGroups, topicSpaces, permissionBindings) are failing with an internal server error:

> GET /subscriptions/[HIDDEN]/resourceGroups/[HIDDEN]/providers/Microsoft.EventGrid/namespaces/[HIDDEN]/clients?api-version=2025-11-15-preview
> Host: management.azure.com
> Accept: */*
> Authorization: Bearer [HIDDEN]

< HTTP/1.1 500 Internal Server Error
< x-ms-request-id: 4000177b-000b-fc00-b63f-84710c7967bb
< x-ms-failure-cause: service
< x-ms-ratelimit-remaining-subscription-resource-requests: 1099
< x-ms-correlation-request-id: 59b815ba-578d-4a23-a8c7-d7cd444eb5ee
< x-ms-routing-request-id: WESTEUROPE:20260727T165850Z:59b815ba-578d-4a23-a8c7-d7cd444eb5ee
< x-ms-request-id: 4000177b-000b-fc00-b63f-84710c7967bb

Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-07-28T09:25:49.3033333+00:00

Hello @RAJNI SINGH ,

Just checking if there is any update on this issue. Please let us know if you are still experiencing the problem or if the suggested guidance helped resolve it.

Thank you.
RAJNI SINGH 5 Reputation points

2026-07-29T08:54:55.03+00:00

I checked a while ago. It seems to be resolved by Azure. I didn't do anything explicitly.
Thanks for the help.

2 answers

Your answer

Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-07-27T11:48:52.3366667+00:00

Hello @RAJNI SINGH

Welcome to Microsoft Q&A, Thank you for your question.

To help investigate further, could you please share the Azure region of the Event Grid Namespace and confirm whether the issue affects only this namespace or multiple namespaces?

Additionally, if available, please share the Activity Log error details or Correlation ID associated with the failed routing update operation in the private chat.

This information will help determine whether the issue is related to the namespace configuration or a service-side problem.

Thank you.
RAJNI SINGH 5 Reputation points

2026-07-27T11:59:42.06+00:00

Azure region - West Europe
This issue is affecting all namespaces. I created a new one and then simply navigating to any options under Mqtt broker (Clients/Client groups/Topic Spaces section) in the portal it shows below error
Error:
Something went wrong with fetching clients.."Batch response item http error 500"

Not able to create new clients in new namespace as well.

Activity log shows the Write Namespace - failed with this error, nothing more.
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 be42e7ce-00b6-414e-9c34-8914664f1b7f:7/27/2026 11:13:22 AM (UTC) to our forums for assistance or raise a support ticket .
RAJNI SINGH 5 Reputation points

2026-07-27T12:03:19.39+00:00

Azure region - West Europe This issue is affecting all namespaces. I created a new one and then simply navigating to any options under Mqtt broker (Clients/Client groups/Topic Spaces section) in the portal it shows below error Error: Something went wrong with fetching clients.."Batch response item http error 500"

Not able to create new clients in new namespace as well.

Activity log shows the Write Namespace - failed with this error, nothing more. 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 be42e7ce-00b6-414e-9c34-8914664f1b7f:7/27/2026 11:13:22 AM (UTC) to our forums for assistance or raise a support ticket .
Michael Walser 0 Reputation points

2026-07-27T17:06:57.17+00:00

We are experiencing the same issue here. We are also located in the West Europe region. All MQTT topic-spaces child operations (clients, caCertificates, clientGroups, topicSpaces, permissionBindings) are failing with an internal server error:

> GET /subscriptions/[HIDDEN]/resourceGroups/[HIDDEN]/providers/Microsoft.EventGrid/namespaces/[HIDDEN]/clients?api-version=2025-11-15-preview > Host: management.azure.com > Accept: */* > Authorization: Bearer [HIDDEN] < HTTP/1.1 500 Internal Server Error < x-ms-request-id: 4000177b-000b-fc00-b63f-84710c7967bb < x-ms-failure-cause: service < x-ms-ratelimit-remaining-subscription-resource-requests: 1099 < x-ms-correlation-request-id: 59b815ba-578d-4a23-a8c7-d7cd444eb5ee < x-ms-routing-request-id: WESTEUROPE:20260727T165850Z:59b815ba-578d-4a23-a8c7-d7cd444eb5ee < x-ms-request-id: 4000177b-000b-fc00-b63f-84710c7967bb
Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-07-28T09:25:49.3033333+00:00

Hello @RAJNI SINGH ,

Just checking if there is any update on this issue. Please let us know if you are still experiencing the problem or if the suggested guidance helped resolve it.

Thank you.
RAJNI SINGH 5 Reputation points

2026-07-29T08:54:55.03+00:00

I checked a while ago. It seems to be resolved by Azure. I didn't do anything explicitly.
Thanks for the help.

Answer 1

Zulqarnain Hussain 0

This looks like a server-side issue because both the MQTT Broker panel and namespace routing are returning a 500 Internal Server Error. I suggest checking Azure Service Health and the Activity Log first. If the issue has been happening since 26/07, it would be best to open a Microsoft Support ticket with the error details and correlation ID if available.

0 comments

Answer 2

Hello,

Thank you for your question.

Based on the information provided, the issue was occurring across multiple Azure Event Grid namespaces, including newly created namespaces in the West Europe region. The behavior included HTTP 500 errors when accessing MQTT Broker resources (such as Clients, Client Groups, and Topic Spaces) as well as failures when updating namespace routing configurations. These observations indicated that the issue was not limited to a single namespace configuration.

When troubleshooting similar issues, it is helpful to:

Verify whether the issue affects a single namespace or multiple namespaces.
Test the behavior in a different browser or an InPrivate/Incognito session.
Check whether the same operation reproduces through Azure CLI or REST APIs.
Review Activity Logs, Correlation IDs, and Request IDs associated with failed operations.
Confirm whether the impact is limited to portal management operations or also affects MQTT message publish/subscribe functionality.

These checks help determine whether the behavior is related to a specific resource configuration or a broader service-side condition affecting management operations.

If the assistance was helpful, kindly take a moment to click on Accept Answer and click on Yes. It will be helpful for other community members.

Thank you.