You still need a geek or geek adjacent person. Their stuff breaks all the time in weird and wonderful ways and someone local has to figure that out and send trouble tickets in to the vendor(s).
With Google, you pretty much can't get support, even if you are a paying customer, so you absolutely have to have your own human, if only to tell you: You can't use Google that way...
With MS you can get support, but you pay extra for it, and it's hit and miss as to how useful it is.
With Apple, you get support. It's generally pretty good, but can occasionally fail.
It’s the same with O365.
When evaluating options, I’ve learned to ask myself the question, ”how do I fix this if it breaks?” If my answer is, ”it won’t ever break”, I’ve learned it’s always a red flag that says I don’t understand enough about that solution to support it, because everything can (and will) break.
Users being stupid, using and holding it wrong, etc.
Just because you haven't had any bad experiences with Google, MS, Apple, etc doesn't mean it's a rosy world where everything works all the time.
As far as network/connectivity, how is that a Google problem if your office can’t connect to the internet?
It was fortunate that we were paying for the level where there was a separate way for discovery lawyers to suck out all your files, as that was the only way I found to get them back.
The other issue with gsuite is the file ownership model means that by default files are owned by an individual and can end up being lost after they leave. Transferring ownership is some kind of weird batch job that can fail and need to be retried.
If you have a company on O365 and don’t ever need IT support, you either have a very very small company or are living the dream surrounded by unicorns.
Something is broken at least every day or two and I’m on a full MS stack. Hopefully we manage to dump Teams in the near future and this’ll hopefully get significantly better. Teams is the bulk of the issues.
Last year we had Mac users start to report "when I attach a file, it looks like it's sent, but then recipient never sees it, and sent-emails doesn't show it either!" It got worse and worse.
This is kind of a problem in a business that sends and reviews a lot of documents. I spent two months on countless calls with MS, repeatedly capturing videos they requested, etc.
Finally, I happened to come across an advisory that hey, Outlook for Mac is broken, and will "eat" attachments. Dated a week before we started to see the problem. Firstly, it took them MONTHS to get it resolved as it required significant updates to Exchange. Secondly, in all the interactions I had to have with their support team: they had NO IDEA. Worse than useless.
What has broken about using any of o365?
Microsoft’s assumption is that businesses are using 365, and so both the number of features and the various paths to trouble tend reflect that.
To the random business owner, dropping them into anything other than Microsoft Admin Center is akin to dropping a tier one helpdesk agent into the AWS Management Console with no guidance. The trick is once you’re beyond a handful of employees you typically need to work beyond the MS Admin Center. If you want to do anything remotely sophisticated with identities, deploy SSO, etc, you need to be working from the Azure or (duplicative) Entra portals. If you want to do something like route helpdesk email, you need to be in the Exchange Admin Center. Tweaking spam filters is in yet another portal (currently Security Center, although that has changed a few times). And so on. Not to mention the more esoteric features that are only available behind Graph API calls.
I used to administer Google Workspace environments too, and while that control panel is MUCH more friendly, it’s still exceedingly easy for a non-technical person following a random walkthrough online to foul up their environment. I’ve watched that happened first hand many times.
