if you are uncomfortable with the responsibility of running on prem gear, deferring that responsibility to a cloud vendor doesnt "make it better".
@Viss Not sure I get this. I'm not comfortable with running on prem exchange anymore, and cloud made that better.
@jackscerebellum how did it 'get better'?
@Viss Labor budget.
Non labor G&A.
Training and Travel.
Time (can do X now that I don't have to do Y)
Business Continuity (also has aspects of above savings, but there's more to it)
Stress and QOL. (On prem exchange takes years off your life)
@jackscerebellum @Viss This. I'm confused by the on-prem responsibility idea because running a cloud, it's never been *my* responsibility to drive around in a pickup truck with good suspension looking for where some yahoo took a shotgun to a fiber-optics box for fun and brought a physlink down.
On-prem requires so many more different responsibilities---different in kind---from cloud. You still need to design robustly and account for the failure of the cloud itself, but you rarely worry about maintaining good working relationships with the professional electricians in town or whether it's time to stop trying to cool with a standard office HVAC and switch out to industrial HVAC or liquid cooling.
@mtomczak @Viss That's a huge part the many don't think about. MS has a 99.9% uptime, no way could I afford to do that on prem.
I've brought in portable AC units and extension cords too many times and payed overtime and lost sleep over squirrels.
That's just the building and environmental controls (what I lumped into G&A costs). Now add a couple transport relays, fw, circuit diversity, security appliances, it very quickly gets very expensive to run email on prem.