Skip to content
DT Nova

How to choose a managed service provider: an MSP evaluation checklist

How to choose a managed service provider decides who holds the keys to your company's IT: accounts, devices, backups and often security. This guide gives you the evaluation criteria, a scoring checklist, the contract and SLA terms that matter, the NIS2 and GDPR checks, the total cost logic and the questions to ask before you sign.

The NIS2 Directive defines a managed service provider as an entity that provides services related to the installation, management, operation or maintenance of ICT products, networks, infrastructure, applications or other network and information systems, on site or remotely (Article 6(39)). That is a lot of access to hand over, so choose with care.

The short version

  • Write down what you want covered before you ask for offers.
  • Choose on security practice and response times, not on the size of the tool list.
  • Keep every account, licence and domain in your company's name.
  • Read the exit clause as closely as the price.
  • Start with an assessment, then a plan, then the monthly service.

Know what you are buying

MSP offers differ more than the word suggests. Some cover user support and devices only; others include Microsoft 365 or Google Workspace administration, networks, servers, cloud, backup, security monitoring and IT planning. Decide first whether you want everything handed over or a split with your own IT person, which is co-managed IT. If you are still deciding whether to outsource at all, read MSP vs in-house IT first.

MSP evaluation checklist with scores

Score each provider from 1 to 5 per line and multiply by the weight.

CriterionWeightWhat to check
Scope in writing3A service description listing users, devices, systems and what is excluded
Response and resolution3Times per priority in the contract, with reporting against them
Security practice3Multi-factor authentication everywhere, patching schedule, endpoint protection, logged admin access
Backup and recovery3What is backed up, where, how often restores are tested
Your ownership2Accounts, licences, domains and documentation in your name
Data protection2Data processing agreement, subprocessor list, EU locations
Reporting2A monthly report with tickets, patch status, backup results and risks
Onboarding and exit2A written onboarding plan and an exit plan with handover duties
Fit1References of your size, language, working hours

NIS2 and DORA: what customers must check

If your company is an essential or important entity under NIS2, Article 21(2)(d) requires supply chain security measures, including security aspects of your relationships with direct suppliers and service providers, and Article 21(3) asks you to take into account each supplier's specific vulnerabilities and the quality of its products and cybersecurity practices. Under Article 20, your management body approves the cybersecurity risk-management measures and oversees them. An MSP you choose becomes part of that duty.

Financial entities have stricter rules. Since 17 January 2025, the DORA Regulation has required them to remain fully responsible for compliance when they use ICT third-party providers (Article 28) and to put key terms in writing, including where functions are provided and data processed, and how data is returned if the provider stops (Article 30).

GDPR: the MSP is a processor

An MSP that administers your systems can access personal data, so it acts as your processor. GDPR Article 28 requires you to use only processors that give sufficient guarantees, to sign a contract that binds the processor to your instructions, and to authorise in writing any other processor it brings in. Ask for the standard agreement and the subprocessor list early; a provider without them is telling you something.

Contract and SLA terms that matter

  • Priorities defined. What counts as critical, high, normal and low, with examples.
  • Response and resolution times per priority, and what happens when they are missed.
  • Hours covered, and how out-of-hours incidents are handled.
  • What is in the fee and what is billed as projects or extra hours.
  • Notice period, and the provider's duties during handover.
  • Documentation kept current and available to you at all times.

Total cost logic

Managed IT is usually priced per user, per device, or as a fixed monthly fee for a defined scope. Compare offers on the same scope, then add what sits outside the fee: projects, hardware, licences, out-of-hours work, onboarding, and your own coordination time. Our guide to managed IT services cost explains the pricing models in detail.

Risks and red flags

  • Admin accounts or the domain registered in the provider's name.
  • No written scope, only "unlimited support".
  • Backups that have never been test-restored.
  • Shared admin passwords instead of named, logged accounts.
  • No data processing agreement on request.
  • Long notice periods with no handover duties.

When a bigger or smaller provider is right

A larger provider suits companies that need round-the-clock coverage, many sites or a security operations centre. A smaller provider suits companies that want to talk to the same people every time and a scope shaped to them. Neither size is better in itself; the checklist decides.

Questions to ask managed service providers

  1. What exactly does the monthly fee cover, and what is billed on top?
  2. What are your response and resolution times per priority, and how do you report on them?
  3. How is admin access controlled, and is every action logged?
  4. How are backups made and restore-tested, and how often?
  5. Will all accounts, licences and domains be in our company's name?
  6. Who are your subprocessors, and where do they process data?
  7. What does onboarding look like in the first month?
  8. If we leave, what do you hand over, and how long does it take?

Our own managed IT services start with an assessment and a written plan, with accounts in the client's name. For user help only, see IT support. Every guide is in the guides library.

Questions people ask

What should we look for in a managed service provider?

A written scope of what is covered, response and resolution times in the contract, security practice you can check, such as multi-factor authentication, patching and tested backups, accounts and licences registered in your company's name, a data processing agreement, clear onboarding and offboarding, and references from companies of your size.

What questions should we ask a managed service provider?

Ask what exactly the monthly fee covers and what is billed on top, how fast they respond and resolve by priority, how backups are tested, how admin access is controlled and logged, who their subprocessors are, how they report each month, and how the handover works if you leave.

What is the difference between an MSP and an MSSP?

Under the NIS2 Directive, a managed service provider installs, manages, operates or maintains ICT products, networks, infrastructure or applications for customers. A managed security service provider is an MSP that carries out or assists with cybersecurity risk management. Many providers offer both.

Is an MSP covered by NIS2?

Managed service providers and managed security service providers are named in NIS2 as entities in the ICT service management sector, and their customers that fall under NIS2 must manage supply chain security, including their relationships with service providers. Check with the provider how it meets the rules in your country.

How do we switch managed service providers safely?

Make sure every account, licence, domain and password vault is in your company's name, ask the current provider for documentation and an exit plan under the contract, run both providers side by side for a short overlap, and change all admin credentials once the new provider has taken over.

Sources