About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
"Managed hosting" does not describe one fixed service. It describes a split of work between you and the provider, and the split can sit at different layers. The right choice depends less on the technology than on three practical questions: how many skilled hours your business really has each month, whether anyone outside the provider needs administrator access, and what evidence you must be able to show afterwards.
This article sets out three arrangements, as its own illustration, how to choose between them, and what you give up with each.
Why it matters
If you take a fully self-managed server without the staff to run it, updates slip and nobody notices a full disk until the application stops. If you take a fully managed server but your software vendor needs administrator rights every week, every vendor visit becomes a support ticket and a delay. Both are expensive mistakes that are easy to avoid by choosing deliberately.
How it works
The starting point: who controls what in infrastructure hosting
The US National Institute of Standards and Technology defines infrastructure as a service as a model in which the customer can run arbitrary software, and the customer "does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, and deployed applications". That is the self-managed baseline: the provider runs the buildings, hardware and virtualisation; you run everything inside the server.
Managed services move some of the in-server layers back to the provider. Microsoft's shared responsibility page, written for its own cloud, also lists duties a customer keeps whatever the model: data, the devices people connect from, user accounts and access management. It states that "regardless of the type of deployment, you always retain the following responsibilities". The same principle applies to any hosting arrangement: a provider can operate your server, but it cannot decide who in your business should see the payroll file.
Three arrangements this article uses
| Layer | Self-managed | Co-managed | Fully managed |
|---|---|---|---|
| Facility, hardware, virtualisation | Provider | Provider | Provider |
| Operating system updates and configuration | You | Provider, on an agreed schedule | Provider |
| Operating system monitoring and response | You | Provider alerts, both act | Provider |
| Application installation and upgrades | You | You or your vendor | Agreed between you, often provider-assisted |
| Users, permissions, data decisions | You | You | You |
| Administrator access inside the server | You | Both, with agreed rules | Provider; yours by exception |
The table is this article's own illustration of how responsibility can be split, not any provider's terms or a standard model; providers use their own labels and splits. What matters is that each layer has one named owner and the agreement says so.
What to choose and why
Count the hours honestly
Running a Windows server well means monthly updates, a restart window, checking that services came back, watching disk space and certificates, and reviewing security alerts. If nobody in your business can reliably give this time, including after hours, self-management is a false saving.
Decide who needs administrator access
Some line-of-business vendors install upgrades themselves. If your vendor needs administrator rights, a fully managed arrangement either has to grant that access by exception or route every upgrade through the provider. Co-managed arrangements are designed for this case, but they need explicit rules: who may install software, who may restart the server, and who is told when either happens.
Decide what evidence you need
If an insurer, auditor or client asks how your servers are patched and who can sign in, you need records. The Australian Signals Directorate's guidance on managed service providers says: "Ensure that your organisation clearly identifies which systems each MSP can access and how, and keep the record up to date". It also says many of its recommendations apply to any outsourced ICT service provider, not just managed service providers. Whichever arrangement you choose, ask how that record is kept and how you will see it.
A hypothetical example
A 25-person accounting practice has an office manager who handles IT part-time and an accounting-software vendor who performs two upgrades a year. Its server runs the practice application, a database and file shares.
- Self-managed would leave monthly patching and after-hours checks to the office manager. That is the risk the business is trying to remove.
- Fully managed would cover patching and monitoring, but the vendor's twice-yearly upgrades would need administrator access by arrangement.
- Co-managed fits: the provider owns operating system updates, monitoring and restarts; the vendor receives time-limited administrator access for upgrades, booked through the provider; the practice keeps users and data decisions.
The example is illustrative, not a recommendation for every practice of that size.
Questions to ask before signing
- For each layer in the table above, who is the named owner?
- Who holds administrator credentials inside the server, and how is a vendor's access granted and removed?
- Who restarts the server after updates, and who checks the application afterwards?
- What happens when your change and the provider's change conflict?
- Which records will you receive, and how often?
Read next
Related articles you may want next.
- HostingYou, your IT partner and the hosting provider: making a three-party arrangement workHow a business that uses both an outside IT partner and a separate hosting provider decides who acts first when something breaks, what access each party needs, and how to write it down so nothing falls between them.Read article
- HostingColocation, managed private cloud or virtual servers: who carries the hardware riskWhen a business replaces ageing office servers, the hosting model decides who buys the next hardware, who replaces a failed part at 2 am and who keeps firmware patched. A side-by-side guide.Read article
- HostingOutside IT partners and application vendors in your hosting portal: time-limited access and reviewControl outside IT partner and application vendor access to hosted systems. Use named accounts, limited permissions, agreed end dates and an access register.Read article
Risks and limits
- Words without layers. "Fully managed" may exclude your application entirely. Insist on the layer-by-layer answer.
- Two administrators, no rules. Co-managed servers fail when both parties change the same thing. Agree the change rules before the first change.
- Access that never ends. Vendor or former-staff accounts left active keep a door open that nobody is watching; ASD's guidance says provider access should be treated as untrusted for anything outside the provider's responsibility.
- The application gap. Operating system management does not guarantee the application works. Agree who confirms the application after maintenance.
- This article describes illustrative arrangements, not any provider's terms. Read the actual service description and contract.
Sources
Opened 15 November 2026.
- NIST: The NIST Definition of Cloud Computing, SP 800-145, September 2011.
- Australian Signals Directorate: How to Manage Your Security When Engaging a Managed Service Provider, last updated October 2021.
- Microsoft Learn: Shared responsibility in the cloud, updated 24 August 2026.
Related service: Managed support.
Learning notes
- Managed hosting is a split of layers, not a single product.
- In infrastructure hosting the customer controls the operating system and applications unless the provider takes them on.
- Data, accounts and access decisions stay with you in every model.
- Choose by honest staff hours, who needs administrator access, and the evidence you must produce.
- Co-managed arrangements need written change rules before the first change.
This article was originally published on .