Can't enable MQTT for Event Grid Namespace

Jeffrey van Buuren 35 Reputation points
2024-08-13T13:50:16.7+00:00

I have no idea why this is happening. I'm following the documentation (https://video2.skills-academy.com/en-us/azure/event-grid/create-view-manage-namespaces#enable-mqtt) on how to set up a MQTT broker inside of Azure, using the Event Grid Namespace service. Everything works fine up until the point of enabling MQTT broker with a checkbox. Which results in the following error:

Update of your namespace failed with the following error: "Update operation failed for namespace egns-demo under Azure subscription Id ... and resource group myrgname as topic spaces configuration prevalidation failed with error code InternalServerError and error message Invalid UPDATE request. Namespace found in provisioning state .."

Which is not true since the provisioning state says: "Succeeded".

Anything I can do?

Azure Event Grid
Azure Event Grid
An Azure event routing service designed for high availability, consistent performance, and dynamic scale.
376 questions
Accepted answer
  1. Sander van de Velde | MVP 32,011 Reputation points MVP
    2024-08-14T18:59:14.0233333+00:00

    Hello @Jeffrey van Buuren

    welcome to this moderated Azure community forum.

    It seems the portal experience is not perfect at this moment.

    While we are waiting to get this fixed, You could try the CLI solution.

    If you are able to open the Cloud shell, you can create your EventGrid namespace with MQTT support by code.

    Press this button in the right upper corner of the Azure portal:

    User's image

    Once the prompt is available, the command needed is:

    az eventgrid namespace create -g some-resourgroup-name -n your-mqttbroker-name --topic-spaces-configuration "{state:Enabled}"

    My MQTT broker was created in a minute or so:

    enter image description here

    From there, I was able to create a client by hand in the portal.

    If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. JananiRamesh-MSFT 26,546 Reputation points
    2024-08-20T05:05:37.9833333+00:00

    @Jeffrey van Buuren Thanks for your patience! The issue has been fixed and deployed everywhere. please try and let me know if you are still seeing the issues.

    0 comments

Your answer

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