For companies that started with cloud services like Microsoft 365, is there usually a reason to add on-premises infrastructure later, or can they stay cloud-only?
Do young companies stay cloud-only, or eventually bring infrastructure on-site?
Answers
There's no automatic point where a young company needs its own servers. If the applications are cloud-based and the costs make sense for the business, staying there can be a perfectly workable choice.
That can also mean less server maintenance for the internal team. Vendor outages still affect the business, though, even when the vendor is responsible for fixing them.
Reply to this answer
Cloud-only gets fuzzy once you look around an office. You may still have network equipment, printers and scanners, or a local storage device for a team moving large files. A legacy application that isn't available as a hosted service can also push you toward a hybrid setup.
None of that necessarily means moving identity, email, and everything else back on-site. You can add local infrastructure for one specific job.
Reply to this answer
Watch the bill, especially for storage and virtual machines. Cloud can be convenient and still get expensive as usage grows. Compare the full cost of keeping a workload there with running it locally, including equipment and maintenance, before deciding a move will save money.
Also look at what you're cutting to control spend. Scaling resources down or removing development environments can have a real effect on systems and the people using them.
Reply to this answer
Email is a separate decision from other workloads. Bringing Exchange on-premises means taking server maintenance back on, and several views in the discussion were strongly against doing that. An on-site mail server also doesn't solve the problem of communicating with outside recipients if internet connectivity is down.
9v~plaidfunnel_263:
A specific compliance requirement could change the calculation, but that's different from bringing mail back just because another application needs a local server.
Reply to this answer
I'd start with the workload, not the company age. A local application or a department handling huge files might justify something on-site, while customer-facing services and most other apps remain in the cloud.
Moving one workload back doesn't have to be an all-or-nothing infrastructure strategy.
Reply to this answer
Add your answer
Answers are reviewed before publication.
6p!gobletwicket_392:
That's a useful distinction. I was thinking mainly about servers and core services rather than ordinary office network gear.