Hosted vs OnPremise - 14/05/2018
Microsoft Exchange has undoubtedly been the messaging service of choice for enterprises around the world. Though Exchange On-Premises has received plenty of attention throughout the years, especially regarding how to build, operate, and maintain its environment, the gradual transition to the cloud has recently prompted dialogue around Exchange Online.
Considering that organizations largely depend on IT to determine whether their email services should be kept on-premises or in the cloud, it’s essential to begin addressing the future of your mail and calendaring server. In this blog post, we’ll distinguish features unique to Exchange Online vs. Exchange On-Premises and deliver the most prominent differences between the two. Asking the Right Questions
Before we break down the distinctions between Exchange Online and Exchange On-Premises, we need to first confront the pain points that many organizations have about their email ecosystem.
Here are the most pressing questions that organizations are concerned with:
If you can relate to any of the questions listed above, then it’s safe to presume that your organization needs to address whether it should rely on Exchange Online or Exchange On-Premises. Even if these common pain points don’t necessarily align with your organization’s interests, examining the top differences between Exchange Online and Exchange On-Premises will help narrow down which version you should commit to.
2. Economies of Scale
Exchange On-Premises struggles to replicate the sheer size and scale of Exchange Online’s mailbox. Though Exchange On-Premises takes advantage of mid-sized servers and JBOD disks within the Exchange Preferred Architecture, it requires a tremendous amount of scalability to achieve what Exchange Online permits, which is $4 for a 50GB mailbox. Exchange On-Premises also requires components like load balancers, redundant data centers, and mailbox dispersion to lower risk. Though Exchange On-Premises can be as reliable as Exchange Online, the analysis between cost and risk can be a difficult balancing act—the less risk on-premises, the higher the cost per mailbox.
Not only is Exchange Online impossible to compete against when considering the time it takes to provision user inboxes, it also updates its firmware at a speed that simply cannot be rivaled by Exchange On-Premises. In comparison to Microsoft’s on-premises update release schedule being four times a year, Exchange Online is capable of servicing updates daily. Exchange On-Premises introduces features via service packs and Cumulative Updates, which vary depending on the version of Exchange. Additionally, both service packs and Cumulative Updates may also mandate other dependencies, such as .NET, to be updated. On the other hand, Exchange Online absorbs these dependencies and introduces features at groundbreaking speeds. What Exchange Online may achieve in a matter of minutes or hours, Exchange On-Premises may take months or years to perform a wholesale update for enterprise versions of Exchange.
4. Operational Efficiency
With Exchange Online, admins are not required to check backups, monitor application logs, or even rebalance Database Availability Groups after patching the server farm. With Exchange On-Premises, admins are required to perform status checks on all of the aforementioned tasks, in addition to building and maintaining a reliable service. Exchange On-Premises also requires an operational staff, which is an extra weight that does not equate to a more optimal performance.
Though Exchange Online is generous in terms of how it provides mailboxes with up to 100GB of storage and unlimited archiving, it is far from flexible. Users can consume what is presented in the Exchange Online service description, but are not capable of expanding their options outside of building the features on their own.
However, Exchange On-Premises provides the ultimate flexibility of deployment, especially since IT can provision them within their budgetary constraints. These may include a multi-tenant deployment for hosted Exchange, customizing Outlook Web Access (OWA), or even a requirement to run code within the transport stack. With Exchange On-Premises, the ability to customize and deploy features is limited only by the organization’s resources and budget.
While there are plenty of differences between Exchange Online and Exchange On-Premises, deciding whether to deploy on-premises or in the cloud should always be determined by the organization’s need for requirements or features. Since it’s difficult for organizations to sign off against must-have features, the final arbiter of how to deploy organization-wide mailboxes tend to point back to if mandatory requirements are met.