---
# source: src/content/services/en/managed-service.md
# route:  /en/services/managed-service/
title: Managed Service
group: support
audience: [enterprise, provider]
order: 2
tags: [managed-services, monitoring]
summary: Hand over operational tasks so your own IT can concentrate on its core work. For solutions we built, across the whole lifecycle.
photoNeed: "The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working"
stub: false
draft: false
---

## What this is about

Your own IT department should be able to concentrate on its core work. For certain
operational tasks it is therefore worth handing responsibility to us, rather than letting
them run alongside everything else.

## Where it helps most

On solutions we implemented ourselves. There we can commit to keeping the estate in a
supported state across its whole lifecycle, aligned with every surrounding system.

That is more than a form of words. A version that is supported on its own can still fall
outside the compatibility matrix in combination with the storage underneath it or the
backup beside it. Keeping that combination in view is the actual work, and it is exactly
what stops happening when something more urgent turns up in the day job.

## What is included

- Patching of the Microsoft servers
- System and firmware updates
- Daily checks of the backups and regular restore tests
- Capacity, log and performance monitoring
- Individual tasks on site or remote, as agreed

Your team gains time for development and projects, and demanding configurations are done by
someone who does them regularly. That saves training cost and closes knowledge gaps that
would otherwise show up internally only with the next incident.

## How this differs from the Service Desk

The service desk is where you go when something is not working. The managed service is the
responsibility for keeping the state maintained, including when nobody is calling.
