Request a quote
Emergency SectorsCareers About us Blog Get in touch
Two colleagues in front of a large wall screen showing cloud diagrams in a darkened room

Hybrid cloud for SMEs: the seams between the office and the cloud

Most small and mid-sized organisations already run a hybrid cloud without anyone having chosen one: Microsoft 365 in the cloud, a server in the comms cupboard and an application that sits between the two. Which systems stay on site is one question. This article is about the next one: what holds the two halves together, and where it goes wrong when nobody owns that.

7 min read Written by the ITproposal team
Short answer

A hybrid cloud is an environment in which your own servers and a public cloud work as one. Two separate environments side by side are not that yet.

Decide up front whether the hybrid state is a stage or a destination. A stage has an end date per system; a destination needs investment in identity, connectivity and management.

The work sits in the seams: one account across both halves, a line that now carries every application, one master location per dataset and recovery that works across the boundary.

What hybrid cloud is, and what it is not

A hybrid cloud is an IT environment in which your own servers (on site or in a data centre) and a public cloud such as Azure or AWS work together as one: the same accounts, a permanent connection between them and one way of managing them. The term says nothing about proportions. One server on site and everything else in the cloud is just as hybrid as the reverse.

  • Multi-cloud is something else: two or more public clouds side by side, for example Microsoft 365 for office work and AWS for a web application. It can be hybrid at the same time, but it does not have to be.
  • Private cloud is an environment that runs for your organisation only, on owned or rented hardware. In a hybrid set-up it is often the on-site half.
  • “We still have a server as well” is not a hybrid cloud. Two environments running independently, with separate accounts and separate backups, are two environments. The difference is what connects them.

Which systems belong on site and why is covered in our article on own servers or the cloud. Here we assume that choice has been made and look at what comes after it.

A stage or a destination: decide up front

Almost every organisation is hybrid for a while, if only during a migration. The question that makes the biggest difference is whether that is a stage or a destination, and it is rarely asked out loud.

  • A stage has an end date per system and a reason it is still on site: an application whose vendor will only have a cloud version next year, a server that has to be replaced in eighteen months anyway. You invest the minimum in the link, because it will go again.
  • A destination means something stays on site for good, for example a production system that talks to machines in the same building. Then the link is not a temporary fix but part of your infrastructure, and it deserves the same care as the systems themselves.

The trap is the stage that becomes a destination without anyone deciding so. The temporary sync, the VPN set up “for now” and the migration partner’s admin account stay in place for years, with no owner and no monitoring. Write down for each on-site system which of the two it is, and review it every year.

One identity across both halves

The first seam is who you are. On-site servers often know users from a local Active Directory; Microsoft 365 and Azure from Microsoft Entra ID. Leave the two separate and every employee has two accounts, two passwords and two places where access has to be revoked.

So make one source authoritative. In a hybrid environment that is usually the local directory, synchronised to the cloud with Microsoft Entra Connect. Once everything that needs that directory has left the building, you reverse it and the cloud becomes the source. What does not work is two sources that each hold part of the truth.

  • Leavers affect both halves. An account disabled in the cloud that still works on site is an open door. Test it with the next person who leaves.
  • Multi-factor authentication applies everywhere. Including the VPN into the office and admin access to the local servers, not just email.
  • The sync server is itself a critical system. If it stops, accounts and passwords drift apart without anyone seeing an alert. Put it in monitoring and in the recovery plan.

The connection between the office and the cloud

In a hybrid environment the internet line sits underneath every application that uses both halves. If the line goes down, you lose not only the internet but everything on site that needs something from the cloud, and the other way round. So ask for each process: what stops if the connection between the office and the cloud is gone for an afternoon?

  • Site-to-site VPN or a dedicated link. For most SME environments an encrypted VPN between the office and the cloud is enough. A direct connection into a cloud data centre makes sense when a lot of data or time-critical traffic crosses it.
  • A second line on a different route. Two lines that enter the building through the same duct are one line. The infrastructure itself (fibre, cable, mobile network) belongs to the network operator; what you choose is the diversity.
  • Latency between the halves. A cloud application that queries a database in the office on every click becomes slow, even on a fast line. Keep components that talk to each other a lot on the same side.

One master location for each dataset

The third seam is where things live. Give each type of data one place where it is authoritative. The customer file lives in the ERP system on site and is only read in the cloud; project documents live in SharePoint and exist locally as a copy at most. As soon as the same files can be edited on both sides and sync back and forth, you get conflict copies and the question of which version is right.

Also record which data crosses the boundary, and how much. Outbound data transfer from a public cloud is usually charged separately, so a design in which a large dataset is pulled back to the office every night costs something every night. You do not see that in the design; you see it on the invoice.

And decide for each type of data whether there is a requirement about where it is stored, from legislation or from a customer contract. In a hybrid set-up you can deliberately keep that data on site, but then the backup and the sync have to follow that choice. A local file whose copy goes automatically to another country is not stored locally.

Management, patching and recovery across two environments

Two environments do not mean two ways of working. Patch on-site servers and cloud virtual machines with the same policy, keep them in one inventory and have them report into one monitoring view. Microsoft offers Azure Arc as a way to bring on-site servers into the same management as virtual machines in Azure; without that tool the principle is the same: one list, one dashboard, one owner.

Recovery is the seam that is forgotten most often. A cloud service keeps the platform available, but getting your data back after a mistake or an attack is your job, and that includes Microsoft 365. In a hybrid environment three questions are added:

  • Is the backup of the on-site half outside the building? The cloud is a logical place for it, provided the copy cannot be deleted with the same admin accounts.
  • Does recovery work when the other half is not there? A local system that needs the cloud to sign users in when it starts up will not come back during a line outage.
  • In what order does everything come back? Identity first, then the connection, then the applications. Test that as a whole, not one half at a time.

How a backup that sits outside the building and demonstrably restores is set up is described under backup as a service.

What a hybrid environment costs

A hybrid environment is rarely the cheapest option. You pay for two environments and for what connects them. What drives the bill is easy to name:

  • The on-site part. Hardware, power, cooling, maintenance and a replacement date, even if it is down to one server.
  • Cloud consumption. Compute and storage, but also outbound data transfer and services that keep running while nobody uses them.
  • Licences. Server licences for the on-site side and subscriptions for the cloud side. Some existing licences may be reused in the cloud under conditions; have that checked per licence before you build a business case.
  • The connection. The lines, a second route and the equipment at both ends.
  • Management. Two environments take more hours than one, unless they are genuinely managed with the same tools.

That is not an argument against hybrid, but it is the reason not to let the stage last longer than it needs to. Every month a temporary link stays in place, you pay for two.

Where our work stops

What we do. We map what sits on site and in the cloud, design the link between them and build it: account synchronisation, multi-factor authentication, the connection between office and cloud, monitoring and patch policy across both halves, and a backup outside the building whose restore we test. After that we manage the whole, and we also advise on and supply the internet connection.

What we do not do. We are not a cloud provider: the platform, its data centres and its availability belong to Microsoft or AWS, and your contract about that is with them. The infrastructure under the line belongs to the network operator. And whether a particular storage location meets legal or contractual requirements is a judgement for a lawyer or your data protection officer; we supply the facts about where things are, not the verdict. In the UK, the NCSC’s cloud security principles are a useful list of questions to put to the provider itself.

Frequently asked

Questions we get about this

The five that come up most often.

What is hybrid cloud?

An IT environment in which your own servers and a public cloud work together as one: the same accounts, a permanent connection between them and one way of managing them. Two environments running separately are not that yet. Most SMEs with Microsoft 365 and a server of their own are already half hybrid, just without the link.

What is the difference between hybrid cloud and multi-cloud?

Hybrid cloud combines your own servers with a public cloud. Multi-cloud means using more than one public cloud, for example Microsoft 365 and AWS. An environment can be both at once. The practical difference is that hybrid also has an on-site half, with hardware, power and a replacement date.

Is hybrid cloud meant to be temporary?

It can be either, which is why you decide up front. As a stage during a migration, each on-site system has an end date and you invest little in the link. As a destination, something stays on site for good and the link deserves the same care as the systems themselves. The risk is the stage that becomes permanent without a decision.

Is a hybrid environment more expensive than going all cloud?

Usually, because you maintain two environments and the connection between them. Cost is driven by on-site hardware, cloud consumption including outbound data transfer, licences, the lines and management time. Whether it is more expensive overall depends on what has to stay on site and why.

Do you provide the cloud yourselves?

No. The platform and its data centres belong to Microsoft or AWS, and your contract about their availability is with them. We design and manage the environment: accounts, connectivity, monitoring, patching and backup across both halves. Whether a storage location meets legal requirements is for a lawyer to judge.

Related services

Further reading

What stays on site, and which platform the rest runs on.

Shall we map the seams in your environment?

We list what sits on site and in the cloud, what connects it and where that is currently nobody’s job. After that you know whether your hybrid environment is a stage or a destination.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call