iot-hub update operations shows error that another operation is in progress, waited a few days but the problem persists.

Question

iot-hub update operations shows error that another operation is in progress, waited a few days but the problem persists.

Dimitri 20

When updating the enrichment settings of an iot-hub I get the following error message:

There was a problem updating your IoT hub to apply message enrichment settings. An unexpected error occurred while updating your IoT hub. Error message: Another update operation is in progress, retry later. errorcode: IH500005.

I've waited few days, but the same error keeps occuring. I've checked the activity log in the azure portal but there are no operations in a running state only failed or succeeded.

VSawhney 880 Reputation points Microsoft External Staff Moderator

2025-07-08T11:38:46.9266667+00:00
Hello Dimitri,

It seems like you're encountering a persistent issue when updating message enrichment settings in your IoT Hub. This typically indicates that the IoT Hub is locked due to a pending or stuck update operation. Even if the Azure Activity Log doesn’t show any active operations, the backend may still be holding a lock.

You may follow these steps to fix the issue:

Double-Check Activity Logs

In the Azure Portal, go to your IoT Hub → Activity Log.

Filter by “Administrative” operations and look for any “Update IoT Hub” entries that may have failed or are stuck.

Use Azure CLI to Abort the Operation Azure CLI provides a way to abort long-running or stuck operations:
az iot hub operation-abort --name <YourIoTHubName>
Replace <YourIoTHubName> with your actual IoT Hub name. This command attempts to cancel any in-progress operations that may be blocking updates.

Retry the Update After aborting, wait a few minutes and try applying the enrichment settings again via the portal or CLI.

Check for Locks or Policies

Ensure there are no resource locks applied to the IoT Hub (under Settings → Locks).

Also verify that no policies or RBAC restrictions are interfering with updates.

ref docs: https://learn.microsoft.com/en-us/rest/api/iothub/common-error-codes

Hope this helps!
Thank you!
Dimitri 20 Reputation points

2025-07-08T12:04:21.74+00:00

Hello,

Thanks for the prompt reply, I can see some failed operations, but none that are stuck. I tried the operation-abort command, but this is unknown and I cannot find it in the documentation, are you sure it exists?

https://learn.microsoft.com/en-us/cli/azure/iot/hub?view=azure-cli-latest

There are no locks in place.

I've tried removing an enrichment via the command line and that gives me a different error:

az iot hub message-enrichment delete --key connectorType -n <name_of_iot_hub>

(412001) Invalid ETag supplied. If you contact a support representative please include this correlation identifier: 217932d1-2ee9-433e-a2c4-285b9ece6fb9, timestamp: 2025-07-08 11:57:35Z, errorcode: IH412001.

Any more ideas?
VSawhney 880 Reputation points Microsoft External Staff Moderator

2025-07-14T15:11:52.9766667+00:00
Hello Dimitri,

Sorry for the delay in response from our end.
You may use the following code for listing and deleting the keys:

#to find keys az iot hub message-enrichment list -n <iothubname> #to delete the enrichment with keys az iot hub message-enrichment delete --key <keyname> -n <iothubname>

Please let us know if it helped you in deleting the message enrichment.

Thank you!
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Dimitri 20 Reputation points

2025-07-15T07:12:30.6633333+00:00
I tried deleting the enrichment key in this way but it fails with an error.

I tried (i replaced <hubname> with our actual hubname ofcourse):

az iot hub message-enrichment delete --key <hubname> This returned: [{"endpointNames": ["events"], "key": "connectorType", "value": "$twin.tags.connectorType"}] az iot hub message-enrichment delete --key connectorType -n <hubname> This returned: Code: 412001 Message: Invalid ETag supplied. If you contact a support representative please include this correlation identifier: 20a88a87-fa2c-4e62-be50-3465b8a845c8, timestamp: 2025-07-15 07:01:33Z, errorcode: IH412001.

To me it seems some operation on the iot-hub has failed in the past and gut stuck. But I would assume a failing operation should abort and return to the previous state after some time. It has been days now and this is still blocking us from updating the iot-hub. There are no further issues with the operation of the hub.

Any more ideas would be really welcome.
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator

2025-07-15T09:32:18.37+00:00

Hey Dimitri

Strangely the same commands are working at my side to delete enrichment.

You can delete the previous enrichment message from UI too.

Please if the deletion from UI fails too.

Let me check with product team internally on this

Thank you.
Dimitri 20 Reputation points

2025-07-15T12:56:21.59+00:00

Hey Manas,

Using the UI does not work either, I've just tried it again:

It claims there is another update operation ongoing, but there's no recent operation, I've been getting this message for more than a week now. I assume some operation failed in the past, but this should not be blocking new operations for days afterwards.

Adding an enrichment does not work either btw.

Hope you can find a resolution for us.
VSawhney 880 Reputation points Microsoft External Staff Moderator

2025-07-16T10:12:40.6566667+00:00

Hello Dimitri,

We are trying to reach PG group internally; we will let you know once we hear back from them.

Thank you!
Dimitri 20 Reputation points

2025-07-17T15:28:42.2166667+00:00

Hello V, thank you, I hope they can come up with a solution.
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator

2025-07-18T09:03:19.5533333+00:00

Hey Dimitri

Good day.

Need to collect a HAR trace while the issue is replicating from you. Have requested resource id and other details on private messages to reach product group.

Could you help with that.

Thank you.

Manas Mohanty 8,150 Microsoft External Staff Moderator

Hi Dimitri

We got some updates from product group.

They have found below error in backend. The number of shared access authorization rules cannot exceed 12.

Inner Exception: Azure.RequestFailedException: SubCode=40000. The number of shared access authorization rules cannot exceed 12. 
To know more visit https://aka.ms/sbResourceMgrExceptions.  
ExceptionDescription: The number of shared access authorization rules cannot exceed 12. To know more visit https://aka.ms/sbResourceMgrExceptions. .
TrackingId:dc45a330-a384-4a49-8abd-caba00555716_G44, SystemTracker:iothub-ns-wagenaar-c-19051327-0277905af0.servicebus.windows.net:wagenaar-connect-routing,
Timestamp:2025-07-22T10:24:58
Status: 400 (Bad Request)
ErrorCode: MessagingGatewayBadRequest

Suggestion given by PG is to reduce number of authorization rule less than 12 in Service Bus and Try again.

Reference - https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-resource-manager-exceptions

Hope it helps

Thank you

Dimitri 20 Reputation points

2025-08-03T14:20:03.83+00:00

Hi Manas,

I'm not sure where they found this error and if it is relevant for this issue. I'm not trying to add an authorization rule but a message enrichment. I've verified the number of authorization rules for the iot-hub and they are well below the limit of 12:

Am I missing something?

Best Regards,

Dimitri
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator

2025-08-06T07:11:34.5333333+00:00

Hi Dimitri.

Strange to see that.

Reviewing with product group and updating you.

Thank you
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator

2025-08-08T01:37:23.3333333+00:00

Hi Dimitri

Product group acknowledge the backend issue on control plan and suggested retrying the updates.

Could you please retry updating and let us know.

If the issue persists, please collect the HAR trace while issue is replicating and share it in email mentioned in private message.

Thank you
Dimitri 20 Reputation points

2025-08-09T15:49:46.97+00:00

Hi Manas,

I assume they fixed something in the backend because removing and adding enrichments is working now.

Thanks for the support,

Dimitri

Accepted answer

0 additional answers

Your answer

VSawhney 880 Reputation points Microsoft External Staff Moderator

2025-07-08T11:38:46.9266667+00:00

Hello Dimitri,

It seems like you're encountering a persistent issue when updating message enrichment settings in your IoT Hub. This typically indicates that the IoT Hub is locked due to a pending or stuck update operation. Even if the Azure Activity Log doesn’t show any active operations, the backend may still be holding a lock.

You may follow these steps to fix the issue:

Double-Check Activity Logs

In the Azure Portal, go to your IoT Hub → Activity Log.

Filter by “Administrative” operations and look for any “Update IoT Hub” entries that may have failed or are stuck.

Use Azure CLI to Abort the Operation Azure CLI provides a way to abort long-running or stuck operations:
az iot hub operation-abort --name <YourIoTHubName>
Replace <YourIoTHubName> with your actual IoT Hub name. This command attempts to cancel any in-progress operations that may be blocking updates.

Retry the Update After aborting, wait a few minutes and try applying the enrichment settings again via the portal or CLI.

Check for Locks or Policies

Ensure there are no resource locks applied to the IoT Hub (under Settings → Locks).

Also verify that no policies or RBAC restrictions are interfering with updates.

ref docs: https://learn.microsoft.com/en-us/rest/api/iothub/common-error-codes

Hope this helps!
Thank you!
Dimitri 20 Reputation points

2025-07-08T12:04:21.74+00:00

Hello,

Thanks for the prompt reply, I can see some failed operations, but none that are stuck. I tried the operation-abort command, but this is unknown and I cannot find it in the documentation, are you sure it exists?

https://learn.microsoft.com/en-us/cli/azure/iot/hub?view=azure-cli-latest

There are no locks in place.

I've tried removing an enrichment via the command line and that gives me a different error:

az iot hub message-enrichment delete --key connectorType -n <name_of_iot_hub>

(412001) Invalid ETag supplied. If you contact a support representative please include this correlation identifier: 217932d1-2ee9-433e-a2c4-285b9ece6fb9, timestamp: 2025-07-08 11:57:35Z, errorcode: IH412001.

Any more ideas?
VSawhney 880 Reputation points Microsoft External Staff Moderator

2025-07-14T15:11:52.9766667+00:00

Hello Dimitri,

Sorry for the delay in response from our end.
You may use the following code for listing and deleting the keys:

#to find keys az iot hub message-enrichment list -n <iothubname> #to delete the enrichment with keys az iot hub message-enrichment delete --key <keyname> -n <iothubname>

Please let us know if it helped you in deleting the message enrichment.

Thank you!
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Dimitri 20 Reputation points

2025-07-15T07:12:30.6633333+00:00

I tried deleting the enrichment key in this way but it fails with an error.

I tried (i replaced <hubname> with our actual hubname ofcourse):

az iot hub message-enrichment delete --key <hubname> This returned: [{"endpointNames": ["events"], "key": "connectorType", "value": "$twin.tags.connectorType"}] az iot hub message-enrichment delete --key connectorType -n <hubname> This returned: Code: 412001 Message: Invalid ETag supplied. If you contact a support representative please include this correlation identifier: 20a88a87-fa2c-4e62-be50-3465b8a845c8, timestamp: 2025-07-15 07:01:33Z, errorcode: IH412001.

To me it seems some operation on the iot-hub has failed in the past and gut stuck. But I would assume a failing operation should abort and return to the previous state after some time. It has been days now and this is still blocking us from updating the iot-hub. There are no further issues with the operation of the hub.

Any more ideas would be really welcome.
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator

2025-07-15T09:32:18.37+00:00

Hey Dimitri

Strangely the same commands are working at my side to delete enrichment.

You can delete the previous enrichment message from UI too.

Please if the deletion from UI fails too.

Let me check with product team internally on this

Thank you.
Dimitri 20 Reputation points

2025-07-15T12:56:21.59+00:00

Hey Manas,

Using the UI does not work either, I've just tried it again:

It claims there is another update operation ongoing, but there's no recent operation, I've been getting this message for more than a week now. I assume some operation failed in the past, but this should not be blocking new operations for days afterwards.

Adding an enrichment does not work either btw.

Hope you can find a resolution for us.
VSawhney 880 Reputation points Microsoft External Staff Moderator

2025-07-16T10:12:40.6566667+00:00

Hello Dimitri,

We are trying to reach PG group internally; we will let you know once we hear back from them.

Thank you!
Dimitri 20 Reputation points

2025-07-17T15:28:42.2166667+00:00

Hello V, thank you, I hope they can come up with a solution.
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator

2025-07-18T09:03:19.5533333+00:00

Hey Dimitri

Good day.

Need to collect a HAR trace while the issue is replicating from you. Have requested resource id and other details on private messages to reach product group.

Could you help with that.

Thank you.
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator

2025-08-01T02:02:33.2766667+00:00

Hi Dimitri

We got some updates from product group.

They have found below error in backend. The number of shared access authorization rules cannot exceed 12.

Inner Exception: Azure.RequestFailedException: SubCode=40000. The number of shared access authorization rules cannot exceed 12. To know more visit https://aka.ms/sbResourceMgrExceptions. ExceptionDescription: The number of shared access authorization rules cannot exceed 12. To know more visit https://aka.ms/sbResourceMgrExceptions. . TrackingId:dc45a330-a384-4a49-8abd-caba00555716_G44, SystemTracker:iothub-ns-wagenaar-c-19051327-0277905af0.servicebus.windows.net:wagenaar-connect-routing, Timestamp:2025-07-22T10:24:58 Status: 400 (Bad Request) ErrorCode: MessagingGatewayBadRequest

Suggestion given by PG is to reduce number of authorization rule less than 12 in Service Bus and Try again.

Reference - https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-resource-manager-exceptions

Hope it helps

Thank you
Dimitri 20 Reputation points

2025-08-03T14:20:03.83+00:00

Hi Manas,

I'm not sure where they found this error and if it is relevant for this issue. I'm not trying to add an authorization rule but a message enrichment. I've verified the number of authorization rules for the iot-hub and they are well below the limit of 12:

Am I missing something?

Best Regards,

Dimitri
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator

2025-08-06T07:11:34.5333333+00:00

Hi Dimitri.

Strange to see that.

Reviewing with product group and updating you.

Thank you
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator

2025-08-08T01:37:23.3333333+00:00

Hi Dimitri

Product group acknowledge the backend issue on control plan and suggested retrying the updates.

Could you please retry updating and let us know.

If the issue persists, please collect the HAR trace while issue is replicating and share it in email mentioned in private message.

Thank you
Dimitri 20 Reputation points

2025-08-09T15:49:46.97+00:00

Hi Manas,

I assume they fixed something in the backend because removing and adding enrichments is working now.

Thanks for the support,

Dimitri

Answer 1

Hi Dimitri

Thank you for confirming Dimitri that it is working post PG fixes from backend.

Attached case summary for reference

Issue: Not able to delete message enrichment

(412001) Invalid ETag supplied. If you contact a support representative please include this correlation identifier: 217932d1-2ee9-433e-a2c4-285b9ece6fb9, timestamp: 2025-07-08 11:57:35Z, errorcode: IH412001.

Recommendation shared from Support

Confirm presence of resource locks - none found.

Shared CLI commands to delete and add the message enrichment - did not work

Observation - Backend issue

Suggestion from PG

Aug 1:

Found from backend error that it was throwing authorization rules > 12, but custom confirmed there was not more than 12 ( < 7 only)

Aug 6

Product group acknowledge the backend issue on control plan and suggested retrying the updates.

Status on Aug 9 - Customer is able to add and remove message post product group fixed the issue from backend.

Thank you for staying patience and collaborative so far.

Please take a minute to accept this answer if you appreciate the inputs.

Share via

iot-hub update operations shows error that another operation is in progress, waited a few days but the problem persists.

0 additional answers

Your answer