Azure-docs: Can not disable front door health probe with single enabled back end host

[mjpearse]

RE
https://docs.microsoft.com/en-us/azure/frontdoor/front-door-health-probes#disabling-health-probes

The documentation states:
"Even if you have multiple backends in the backend pool but only one of them is in enabled state, you can disable health probes."

This is not the case presently when attempting to do this in the Azure portal. I can only disable them with one backend host.

If I have two backend hosts with only one of the two enabled, the health probe status switcher in the portal becomes read-only, fixed on enabled.
Documentation error or Frontdoor/Portal bug?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: f35a0b39-ab2f-ba8a-0907-e0f3a6b69135
• Version Independent ID: 0e6c8267-a911-9c6b-0522-3ec96753b3ef
• Content: Azure Front Door - backend health monitoring
• Content Source: articles/frontdoor/front-door-health-probes.md
• Service: frontdoor
• GitHub Login: @sharad4u
• Microsoft Alias: sharadag

[SubhashVasarapu-MSFT]

@mjpearse , We are looking into this query and will update you as soon as possible.

[willshi]

@SubhashVasarapu-MSFT the same issue for us, please fix ASAP.

[leniency]

I have a similar issue where I have multiple pools, each with only a single backend. I should be able to disable the probe:

If you have a single backend in your backend pool, you can choose to disable the health probes reducing the load on your application backend.

But get the error:

Error: Health probe can only disabled when there is only one enabled endpoints.

It works fine when I have only a single pool and single backend, but other configurations error, counter to what the docs say should be possible

[SubhashVasarapu-MSFT]

@mjpearse , Appreciate your patience. It looks like a bug from the portal side as I can disable the health probe using PowerShell having 2 backends with one in disabled state.

Will be back shortly with the updated status.

[SubhashVasarapu-MSFT]

@mjpearse , Team is working on fixing this portal bug. We will keep you posted!
We are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.