There was a problem updating your IoT hub to add a new endpoint

Dennis Preatto 0 Reputation points
2025-01-09T09:31:11.3533333+00:00

Good morning,

I am writing this post since we are experiencing difficulties with our newly purchased Azure IoT Hub subsrcription (B1 Tier): every time we try to create a custom endpoint to route messages to other services, like Cosmos DB, we receive the following error message:

There was a problem updating your IoT hub to add a new endpoint. An unexpected error occurred while updating your IoT hub. Error message: Internal Error. If you contact a support representative please include this correlation identifier: 6348deb4-a35e-410a-8a17-f4fc25443ced, timestamp: 2025-01-09 08:43:50Z, errorcode: IH500019.

The issue has been persisting for over 48 Hours. We managed to succesfully use this functionality during our thorough testing of the Iot Hub Free Tier, now that we switched to the paid plan, that particular functionality doesn't work as expected.

Has anyone experienced this issue before, or has any idea about how to solve it?
Any help or suggestion will be greatly appreciated.

Best Regards,

Dennis Preatto

Azure IoT
Azure IoT
A category of Azure services for internet of things devices.
409 questions
Azure Cosmos DB
Azure Cosmos DB
An Azure NoSQL database service for app development.
1,720 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Sander van de Velde | MVP 34,201 Reputation points MVP
    2025-01-09T19:07:42.13+00:00

    Hello @Dennis Preatto ,

    welcome to this moderated Azure community forum.

    Although the free tier IoT Hub is a Standard tier version, the Basic tier version should support message routing.

    It seems you tried multiple kinds of outputs (eventhub, blobstorage, etc.) already?

    As a test, doe you see the same behavior if you create a Standard tier IoT hub in the same region?

    Additionally, this could be an Azure portal UI issue, please try to add an IoT Hub custom output via Bicep or the CLI.

    If this does not provide insights in the behavior seen, you could create an Azure support ticket so that team can check the backend.


    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.

    0 comments No 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.