@scottalanmiller said in On prem Exchange hardware questions.:
@PhlipElder said in On prem Exchange hardware questions.:
EDIT: Which was great because we weren't being hit by a bus load of calls when O365/M365 went down.
Sure, but that's like driving without a seatbelt in one car, and having someone in another car with a seatbelt. Then saying "ha, by being in the car without a seatbelt, we weren't hurt when the other car had an accident." It sounds like you are doing something safer, but you aren't, it's just presented in an emotionally misleading way.
The real advantage to lost of on-prem hosted systems is that outages tend to be temporally isolated - each outage has no connection to another. So you don't get swamped with outage calls all at once, even though your overall downtime is likely many, many times higher and requires way more engineering effort.
Supporting both, I know the difference is huge. On prem outages means we have to dedicate engineering time, generally billable, and do all kinds of customer management. O365 outages our service center can just point customers to the DownDetector page and explain that the service is down until MS corrects it. Even with loads of O365 customers calling in at once, it's less effort to deal with 100 customers on O365 during an outage than one on prem that we have to actually fix.
Again, on prem makes lots of sense at the right times. Just saying that presenting the recent outage as if it would affect the decision of any logical IT shop doing its evaluation properly is misleading. It's an emotional plea, but someone using proper risk assessment would understand that it's just part of any system and the fact that it was recent is not relevant and doesn't affect future risk assessment.
Not going down this road with you again Scott.
TTFN