Azure Monitor Health Model is broken when an entity is deleted

Question

Azure Monitor Health Model is broken when an entity is deleted

Staffan Wärnberg 25

This has happened twice for me now in two different Health models. In some circumstances, when an entity is deleted in a Health model, the whole model breaks and it's not possible to use or recover it anymore. This is a critical bug since it's not possible to restore it in any way.

Steps to reproduce:

Create a Health model.
Design it with multiple entities, multiple levels of dependencies and different signals.
Do changes in the design and model.
Delete an entity from the model.
If you're unlucky, suddenly the model is broken with an error like the following.

Unable to load health model entities. Failed to create HTTP response as per the API specification with one or more errors. Please see details for more information. Consider to retry operation with api-versions ''. Missing required property: authenticationSetting. Paths in payload: '$.value[27].properties.signals.azureResource.authenticationSetting'

Quite annoying if you've worked with a Health model for a long time.

Bharath Y P 10,610 Reputation points Microsoft External Staff Moderator

2026-01-20T14:47:48.88+00:00
Hello Staffan Wärnberg,

Thank you for posting your question on the Microsoft Q&A platform.

We are looking into your issue and will keep you posted investigation updates.

Could you please help us with the below details

Is the authenticationSetting field expected to be auto‑populated by the service, or is it derived from another linked entity or signal configuration?

Does deleting an entity leave behind orphaned signal references that are not fully cleaned up by the backend?

Is this issue specific to azureResource signal types, or has it been observed with other signal providers as well?

Thanks,
Bharath Y P 10,610 Reputation points Microsoft External Staff Moderator

2026-01-21T18:25:01.5466667+00:00

Hello Staffan Wärnberg, could you please help us with the above details, thanks
Staffan Wärnberg 25 Reputation points

2026-01-26T12:32:01.3566667+00:00

Hello.

Since I can't load the design, nor export the template, it's impossible to answer your questions.
Staffan Wärnberg 25 Reputation points

2026-01-26T12:35:27.54+00:00

Update: After a week of absence, I opened the Health model again and now it was loaded...

Something (or a service update) has made it work again. However, I can see several entities in the model again, which I recently deleted.

The health model / designer is extremely buggy. I can spend hours in trying to delete an entity, which then comes back after a refresh.

Your answer

Bharath Y P 10,610 Reputation points Microsoft External Staff Moderator

2026-01-20T14:47:48.88+00:00

Hello Staffan Wärnberg,

Thank you for posting your question on the Microsoft Q&A platform.

We are looking into your issue and will keep you posted investigation updates.

Could you please help us with the below details

Is the authenticationSetting field expected to be auto‑populated by the service, or is it derived from another linked entity or signal configuration?

Does deleting an entity leave behind orphaned signal references that are not fully cleaned up by the backend?

Is this issue specific to azureResource signal types, or has it been observed with other signal providers as well?

Thanks,
Bharath Y P 10,610 Reputation points Microsoft External Staff Moderator

2026-01-21T18:25:01.5466667+00:00

Hello Staffan Wärnberg, could you please help us with the above details, thanks
Staffan Wärnberg 25 Reputation points

2026-01-26T12:32:01.3566667+00:00

Hello.

Since I can't load the design, nor export the template, it's impossible to answer your questions.
Staffan Wärnberg 25 Reputation points

2026-01-26T12:35:27.54+00:00

Update: After a week of absence, I opened the Health model again and now it was loaded...

Something (or a service update) has made it work again. However, I can see several entities in the model again, which I recently deleted.

The health model / designer is extremely buggy. I can spend hours in trying to delete an entity, which then comes back after a refresh.