Private Cloud
😟 THE PROBLEM
A regulation says this system must run on hardware only your organisation uses.
😊 THE SOLUTION
Build a private cloud: cloud-style self-service on dedicated hardware.
- Data cannot share hardware with others✓ Single-tenant, dedicated infrastructure
- Teams wait weeks for each server✓ Self-service portal gives VMs in minutes
- You need full control of the setup✓ You own and configure everything
Quick answer
A private cloud is cloud computing infrastructure used exclusively by one organisation. It offers cloud-style self-service, automation and scaling, but on dedicated hardware, usually in the organisation's own datacenter or hosted for it by a third party. You get maximum control and pay the full cost of owning and running it.
Exam objective: 1.1.3 Define cloud models, including public, private, and hybrid. 1.1.4 Identify appropriate use cases for each cloud model. (Skills measured as of July 20, 2026)
Start with a question
Why would a bank or a defence company pay more to have a cloud all to itself?
Shared bus networks are cheap and convenient, yet some people still buy a private car, or even an armoured one. They want to decide exactly who gets in, where it is parked and who services it.
Some organisations feel the same about their computing. They want the convenience of cloud (click a button, get a server) without sharing hardware with anyone. That is a private cloud.
Explain it like I’m 10
The technical explanation
A private cloud is a cloud deployment model where the infrastructure is provisioned for exclusive use by a single organisation. It can be:
- On-premises: in the organisation’s own datacenter, run by its own staff, or
- Hosted: in a third-party datacenter, on hardware dedicated to that organisation.
What makes it a cloud, not just a server room, is that it offers cloud characteristics to its internal users: self-service provisioning, pooled and virtualised resources, automation and often usage metering and chargeback to departments.
| Private cloud | Public cloud | |
|---|---|---|
| Tenancy | Single organisation | Many organisations (isolated) |
| Up-front cost | High (hardware, software, facilities) | None |
| Hardware maintenance | Organisation | Provider |
| Scalability | Limited by purchased hardware | Near-unlimited |
| Control | Maximum | Configuration-level |
| Typical drivers | Strict compliance, data control, legacy integration | Agility, scale, cost |
Traditional on-premises
- Dedicated hardware
- Ticket-based requests
- Manual provisioning (days or weeks)
- No metering
Private cloud
- Dedicated hardware
- Self-service portal or API
- Automated provisioning (minutes)
- Usage metering and chargeback
Public cloud
- Shared, provider-owned hardware
- Self-service portal or API
- Automated provisioning (minutes)
- Pay-as-you-go billing
Real-world business scenario
A national healthcare provider
- The problem
- Patient records systems must stay in facilities the provider controls under a national regulation, yet internal teams were waiting weeks for each new server.
- What they used
- A private cloud built on Azure Local in its two datacenters, with a self-service catalogue for development teams, managed through the Azure portal with Azure Arc.
- Why that choice
- Data and hardware stay on-premises to satisfy regulation, while teams get cloud-style self-service and consistent Azure management.
- The result
- VM delivery went from weeks to under an hour, and non-regulated analytics moved to the public cloud in a hybrid design.
When to use it and when not to
✓ Use it when…
- Regulation or policy requires single-tenant infrastructure under your control.
- You need deep customisation of hardware or network that public cloud does not offer.
- Large, stable workloads where you can keep dedicated hardware busy.
✕ Think twice when…
- Demand is variable or unpredictable. You would need to buy for the peak.
- You lack the skills to build and run a true self-service platform.
- The main motivation is "it feels safer" without a concrete requirement. Public cloud security is very strong when configured well.
↔ Alternatives to consider
- **Public cloud with isolation options**: Dedicated Hosts, confidential computing, private endpoints.
- **Hybrid cloud**: private for what must stay, public for everything else.
- **Sovereign or government clouds** for public-sector requirements.
Interview preparation
Say your answer out loud first, then open the model answer. Interviewers care more about your reasoning than the exact words.
Beginner What is a private cloud?
Model answer
A private cloud is cloud infrastructure that only one organisation uses. Its teams get cloud features like self-service and automation, but the hardware is dedicated to that organisation, often in its own datacenter.
Interviewer follows up
So is every company server room a private cloud?
You
No. A server room where people raise tickets and wait days for a VM is just traditional on-premises IT. It becomes a private cloud when it offers on-demand self-service, pooled resources, automation and usage metering.
Intermediate Compare private and public cloud on cost and control.
Model answer
Private cloud gives maximum control over hardware, location and configuration, but the organisation pays up front (CapEx), maintains everything and has limited capacity. Public cloud has no up-front cost, near-unlimited scale and no hardware maintenance, but less physical control.
Experienced developer Many private cloud projects disappoint. Why?
Model answer
Building the cloud experience is hard. Self-service portals, APIs, metering, automation and fast provisioning take serious engineering, and many projects end up as virtualisation with a ticket system. They also keep the fixed-capacity problem and the hardware refresh cycle. That is why many organisations now prefer hybrid, using public cloud for elastic workloads and cloud-managed on-premises platforms such as Azure Local with Azure Arc for what must stay local.
Scenario A defence contractor must keep certain data in its own facility under its own staff's physical control, but wants developers to provision VMs on their own. What model fits?
Model answer
A private cloud for that sensitive workload, ideally one that is cloud-managed so developers get self-service and consistent tooling. Less sensitive workloads can still go to the public cloud, or a sovereign or government cloud, in a hybrid design.
Test yourself with exercises
4 original practice questions in the AZ-900 style. Pick your answers, then check them. You will see why each option is right or wrong. Score 75% or more and this topic is marked complete.
Quick revision
Key points
- Private cloud = cloud capabilities on infrastructure dedicated to one organisation.
- Can be on-premises or hosted by a third party, but always single-tenant.
- Maximum control, privacy and customisation.
- Requires CapEx, in-house skills and maintenance; capacity is limited.
- Not every server room is a private cloud. Self-service and automation make the difference.
Important terminology
- Private cloud
- Cloud infrastructure dedicated to a single organisation, on-premises or hosted by a third party.
- Single-tenant
- Infrastructure serving only one customer, the opposite of multi-tenant.
- Self-service portal
- A catalogue where internal teams request resources themselves, the "cloud-like" part of a private cloud.
- Azure Local
- Microsoft's solution (formerly Azure Stack HCI) for running virtualised workloads on validated hardware in your own location, managed through Azure.
Common mistakes
- Assuming private cloud must be in your own building. A third party can host it.
- Assuming private cloud scales like public cloud. It is limited by the hardware bought.
Exam tips
- "Single organisation", "complete control", "dedicated hardware" all point to private cloud.
- The organisation is responsible for hardware maintenance in a private cloud.
Five quick revision questions
-
1.How many organisations use a private cloud's infrastructure?Show
One.
-
2.Can a private cloud be hosted by a third party?Show
Yes, as long as the infrastructure is dedicated to that one organisation.
-
3.Who maintains the hardware in a private cloud?Show
The organisation (or the hosting provider it pays), not shared with other customers.
-
4.What is the main advantage of a private cloud?Show
Maximum control over infrastructure, security and location.
-
5.What is the main disadvantage?Show
High cost (CapEx and operations) and limited scalability.
Official references
Finished this lesson? Tick it off. Your progress is saved in this browser.
Next up: Hybrid and Multi-cloud