IT Management

How to Choose a Managed Service Provider: Questions, Red Flags and Contract Terms

How to choose a managed service provider: questions to ask, red flags, contract terms to check, how to vet the MSP's own security, and what onboarding covers.

By Boston IT Services Group · Published November 14, 2026 · Updated November 14, 2026 · 8 min read

In short

Choosing a managed service provider means checking four things: whether its services match your needs, whether its contract protects you, whether it secures its own systems and access to yours, and whether it has a real onboarding plan. This guide gives a practical checklist, the questions to ask, red flags to watch for, contract terms to review and the security practices that CISA and its partner agencies recommend MSP customers require.

How to choose a managed service provider comes down to four checks: does the service match what your firm needs, does the contract protect you, does the provider secure its own systems and its access to yours, and does it have a real plan for the first 90 days. Price matters, but it is the easiest part to compare and the least likely to tell you whether the relationship will work.

This guide gives you the checklist we would use if we were hiring an MSP for our own office: questions to ask, red flags, contract terms and the security practices that U.S. and allied cybersecurity agencies tell MSP customers to require.

Start with what you need, not with the provider

Before you talk to anyone, write one page that describes your firm:

  • Number of users, devices, servers and locations
  • Main software (practice management, accounting, EHR, CAD, document management)
  • Where your data lives today (on-premises server, Microsoft 365, other cloud apps)
  • Compliance obligations: 201 CMR 17.00 if you hold Massachusetts residents' personal information, HIPAA, the FTC Safeguards Rule, CMMC, or client contract requirements
  • Cyber insurance requirements
  • Support hours you actually need and how much onsite presence matters
  • Known projects for the next 12 to 24 months
  • Whether you have internal IT staff who will stay (if so, read what is co-managed IT)

Send the same page to every provider you talk to. You will get quotes you can actually compare, and you will learn a lot from which providers ask good follow-up questions.

Questions to ask a managed service provider

Service and scope

  1. What is included in the monthly fee, and what is billed separately?
  2. How do you count users and devices? What about part-time staff, shared mailboxes and servers?
  3. What are your support hours, and how does after-hours emergency support work?
  4. What response and resolution commitments will you put in the contract?
  5. Are onsite visits included? How are they scheduled and billed?
  6. Who will be our main point of contact, and will we have a named engineer who knows our environment?
  7. How do you handle projects, and what are your rates?
  8. How do you handle line-of-business software vendors? Will you call them on our behalf?
  9. What reporting will we get, and how often will we meet to review it?

Security and backup

  1. What security tools are included (EDR, email filtering, MFA management, DNS filtering, training)?
  2. Who watches security alerts, and during what hours?
  3. How are backups done, where are they stored, and how often do you test restores?
  4. What happens in the first hour if we get hit by ransomware?

Fit and references

  1. What size and type of firms do you mostly support?
  2. Can we speak with two or three current clients similar to us?
  3. What does your onboarding process look like, week by week?

How a provider answers matters as much as what it says. Specific answers with documents and examples are a good sign. "We take care of everything" is not an answer.

MSP security requirements: vet the provider's own security

An MSP holds the keys to every client it supports. That makes MSPs attractive targets, because one compromise can reach many businesses. In May 2022, CISA, NSA, the FBI and cybersecurity agencies from the UK, Australia, Canada and New Zealand published a joint advisory, Protecting Against Cyber Threats to Managed Service Providers and their Customers. It is the best single reference we know for what to ask.

Based on that advisory, your MSP security requirements should cover:

What to require Why it matters
MFA on every MSP account that can access your environment Stolen technician passwords are a direct path into your network
Named accounts for each technician, no shared logins, no reuse of admin credentials across customers You can see who did what, and one client's breach does not open the door to yours
Least privilege: MSP accounts reach only the systems the MSP manages Limits damage if an account is misused
Access over a dedicated, secured connection, with MSP accounts kept out of your internal admin groups Keeps provider access visible and controlled
Disabling MSP accounts that are not in active use, including when the contract ends Removes standing access nobody is watching
Logging of MSP activity, with important logs kept for at least six months, and visibility for you You need the logs to investigate an incident
Backups of your critical data and configurations kept somewhere retrievable or air-gapped Ransomware targets backups first
Tested incident response and recovery plans You want to know the plan works before you need it
Clear notice to you of suspected or confirmed incidents on the MSP's own systems Their breach may be your breach
A contract that says who owns hardening, detection and incident response Removes the gray areas attackers exploit

CISA's Risk Considerations for Managed Service Provider Customers and its earlier piece, Going Beyond: Assessing Security Practices of IT Service Providers, add questions about who is responsible for security when IT is outsourced and what a provider should show you before a contract is awarded.

Ask for these in writing. A provider that gets defensive about its own security is telling you something.

MSP red flags

  • No written scope. If it is not in the agreement, assume it is not included.
  • Response commitments promised in the sales meeting but missing from the contract.
  • Long terms that auto-renew, with large termination fees and short notice windows.
  • Vague answers about the provider's own MFA, remote access tools or logging.
  • A single shared admin account for "the tech team."
  • No onboarding plan, or an onboarding plan that is just "install our agent."
  • No references, or references only from firms nothing like yours.
  • Pressure to replace all of your hardware immediately, before any assessment.
  • Any hint that your passwords, documentation or data will be held back if you leave.
  • No mention of compliance when you have told them you are a medical practice, law firm or accounting firm.

One red flag is not always a dealbreaker. Two or three together usually are.

MSP contract terms to read before you sign

Have your attorney review the agreement. Here are the MSP contract terms we would look at first.

Term What to check
Length and renewal Initial term, auto-renewal, notice period to cancel
Termination Termination for convenience, termination for cause if commitments are missed, fees
Scope and exclusions Line-item list of included services, devices and users; what is excluded
Service levels Response times by priority, support hours, what happens when they are missed
Pricing changes How and when fees can increase; how adding users is billed
Data ownership and return You own your data, documentation, configurations and credentials; format and timeline for handover
Offboarding assistance What help you get transitioning to another provider, and at what cost
Security obligations MFA, access controls, logging, incident notification timelines
Regulatory addenda Business associate agreement for HIPAA; security language for 201 CMR 17.00
Liability and insurance Limits of liability, the provider's own cyber and errors and omissions coverage
Subcontractors Whether they use subcontractors or offshore staff, and how those are vetted

On regulatory addenda: under 201 CMR 17.00, you must take reasonable steps to select service providers capable of protecting personal information and require them by contract to maintain appropriate security measures. Under HIPAA, HHS says a business associate agreement must be in place before a vendor creates, receives, maintains or transmits electronic protected health information for you. HHS's cloud computing guidance makes the point that even a provider storing only encrypted data without the key is still a business associate. If your MSP manages systems that hold patient data, it needs a BAA.

What a good onboarding plan looks like

The first 30 to 90 days set the tone for the whole relationship. A solid onboarding plan includes:

  1. Discovery: interviews with leadership and staff, and a review of current pain points.
  2. Inventory: every user, device, license, application, vendor and network component documented.
  3. Access: admin credentials collected and secured, old accounts removed, MFA turned on.
  4. Agents and tools: monitoring, patching, EDR and backup deployed and verified on every device.
  5. Quick fixes: urgent security gaps (unpatched systems, missing backups, no MFA on email) closed first.
  6. Documentation: network diagram, procedures and vendor contacts written up in a system you can access.
  7. Roadmap: a prioritized list of risks and recommended projects, with rough budgets.
  8. Communication: how staff submit tickets, who to call in an emergency, and a first review meeting date.

Ask each provider to show you a sample onboarding plan and a sample report. You will learn more from those two documents than from a sales deck.

Check references the right way

When you call references, ask questions they have to answer specifically:

  • What went wrong during onboarding, and how did the provider handle it?
  • How fast do they respond to an urgent issue in practice?
  • Has your main contact changed, and how was the handover?
  • Have you had a security incident, and how did they help?
  • Have you ever disputed an invoice? What happened?
  • Would you sign with them again?

How to choose a managed service provider from your shortlist

Score each finalist on scope, contract, security, onboarding and references, and treat the monthly cost as one more line in that scorecard. Our guide to managed IT services pricing shows how to line up quotes so the price comparison is fair.

If you are evaluating providers now, put every question on this page to us as well, and ask for the answers in writing. Our managed IT services for Boston businesses page describes how we work, our cybersecurity services page covers how we handle security, and firms elsewhere in the state can start from managed IT services Massachusetts.

Frequently asked questions

What questions should I ask a managed service provider?

Ask what exactly is included and excluded, how users and devices are counted, what response commitments are in the contract, who will be your main contact, how they secure their own remote access tools, whether they require MFA on every account that touches your systems, how they handle backups and restore tests, what onboarding looks like, and how you get your data, passwords and documentation back if you leave.

What are red flags when choosing an MSP?

Warning signs include a quote with no written scope, refusal to put response commitments in the contract, long auto-renewing terms with steep termination fees, vague answers about their own security, shared admin accounts across clients, no onboarding plan, unwillingness to provide references, and any suggestion that they will hold your passwords or documentation if you leave.

How long should a managed IT contract be?

Terms vary. Many providers ask for one to three years because onboarding takes real effort up front. Whatever the length, check renewal terms, notice periods, termination for cause if the provider misses its commitments, and what offboarding help you get. A shorter first term or a clear exit clause is a reasonable request for a new relationship.

How do I check an MSP's own cybersecurity?

Ask how they protect the remote management tools they use on your systems, whether every technician uses MFA and named accounts, whether they separate client environments and avoid reusing admin credentials, how long they keep logs, how they back up their own systems, and how fast they will notify you of an incident on their side. CISA's May 2022 joint advisory on MSPs lists these practices.

Should my MSP sign a business associate agreement or security addendum?

If you are a HIPAA covered entity and the MSP will create, receive, maintain or transmit electronic protected health information, HHS rules require a business associate agreement. If you hold Massachusetts residents' personal information, 201 CMR 17.00 requires contracts that obligate service providers to maintain appropriate security measures. Your attorney should review the language.

Sources and references

  1. CISA, NSA, FBI and international partners: Protecting Against Cyber Threats to Managed Service Providers and their Customers (AA22-131A, May 11, 2022)
  2. CISA Insights: Risk Considerations for Managed Service Provider Customers
  3. CISA: Going Beyond, Assessing Security Practices of IT Service Providers (September 2, 2021)
  4. Mass.gov (OCABR): 201 CMR 17.00, Standards for the Protection of Personal Information of MA Residents
  5. HHS: Summary of the HIPAA Security Rule
  6. HHS: Guidance on HIPAA and Cloud Computing

Talk to a Boston IT engineer

Tell us what is slowing your team down. We will review your current setup and send back a plain-English plan with priorities, at no cost.