Still using Azure Scheduler? Schedule in 30 September 2019 'cos it's being euthanised

Another benefit of having a strategy and an architecture

Is that you are less likely to need to change direction completely and for no apparent benefit to the customer.

If the new fangled way is better, why can’t they migrate the existing configuration automatically so that it doesn’t impact customers ?

We used to call this backwards compatibility, it wins big brownie points with management when we need to change things

"long-in-the-tooth Azure service"

Five years old. Long in the tooth? I offer you cron: goes back at least to V7 Unix (1979) in my experience.

More replace simple with fancy, fancy, bells, and whistles

Not at all surprised. The scheduler must have been to simple and reliable and dull. These days everything must have every feature under the sun and then some.

The further expand on the cron analogy. It too may see a similar push to the wayside by the systemd crowd. This is not isolated to Azure or Microsoft.

Why can't we follow the "if it ain't broke, don't fix it" mantra? Sure it may have a few issues, but they have been worked around. A simple modular system tends to work much better than a single complex gargantuan system.

No, we need to reinvent the wheel, and axle, and bearing, and drive linkage, and differential, and braking, and engine, and steering, and lighting, and chassis, and cab, ad nauseum just because we want to create a new car radio, then do it all again to add mp3 playing into the new, new car radio.