Setting old autoscale rule to disabled to not block autoscale when new autoscale profile is deployed with arm templates
When autoscaling rules exist on a service (cpu based for instance) and a new one is deployed with the help of an arm template there is no clarity in which rule is actually working, if any of them are enabled at this point.
My suggestion to fix this is to disable the old rule if the new rule arrives to autoscale with enabled equals to true. If not, keep the old one as it is.
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.