Front Doors - Health and Loadbalancer settings when deploying Arm

Question

We have a production environment which hosts multiple sites; These were all done in the in the portal, and as a consquences it has created a new Load Balancer and Health probe for each site that has been added.
This translates into a very messy Arm template, in my testing i have been able to use one setting for multiple sites.
My question is, does this in anyway impact performance doing this, and would switching 20 frontends/backend/routing rules to one setting from 20 have any adverse impact on any of these sites?

FYI, the reason for doing this is to avoid technicians making changes via portal and breaking something, but rather have to do a Pull requests before running a pipeline.
(as this was done recently which impacted a couple of sites)

Answer 1

Hello @HUMPHREY Adam (1IT/CLD) ,

There should be no impact if the configuration is correct & accepted by all the backend pools. What I mean here is all the 20 sites should be able to accept the same healthprobe settings such as protocol, path etc. If they require different protocols & paths, then it could cause an issue.

Also, any updates to backend pools are seamless and will cause zero downtime (if the new configuration is correct).
Please refer : https://learn.microsoft.com/en-us/azure/frontdoor/front-door-faq#how-long-does-it-take-to-deploy-an-azure-front-door-does-my-front-door-still-work-when-being-updated

Kindly let us know if the above helps or you need further assistance on this issue.

----------------------------------------------------------------------------------------------------------------

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.