Servicing Exchange 2013 and later

You say CUs will be full product releases and may contain schema changes, which are essentially the same as a service pack today. Installing service packs is a pain comared to RUs today, not to mention unlike RUs SPs require 3rd party vendor validation like you claim CUs will. So how is a CU not like a SP???

All I hear is we get the privelage of being forced to deploy CUs (essentially SPs) every 6 months at a minimum, preferably every 3 months, because the currently installed CU won't be supported 3 months after the next CU. This is all just so you can drop the existing deployment cycle/methodology for on-premesis customers in lieu of the quarterly one you set up for Exchange online.

Thanks but no thanks when it comes to applying the equivalent of a SP every 3 months and all that goes with a major SP update.

Clearly your on-premesis customers are becoming less and less a priority compared to your online cloud solution, to the point where it seems sometime in the not too distant future we will be forced to move to your cloud solution or switch to another on-premesis solution.