Fix it now
Antivirus for a managed service provider is a platform purchase, not a protection purchase. You are buying tenancy separation, a billing model that matches how you invoice, and an integration into the tool you actually log into. Two of the three vendors here have changed their programme naming recently, so check what you are quoting.
- Buy Bitdefender GravityZone for MSPs as the default. Bitdefender publishes monthly consumption and billing through distributors and RMM partners with no minimum commitments, parent-child infrastructures for multiple client environments, and integrations for ConnectWise, Kaseya, NinjaOne, Atera and RG System.
- Note the name has changed: Bitdefender’s page is GravityZone for Managed Service Providers, also referred to as GravityZone MSP Security. If a quote says Cloud MSP Security, ask what it maps to.
- Buy into Sophos if managed detection is part of your offer. Sophos runs MSP with partner-owned licence entitlements, MSP Flex with consumption-based billing in arrears, and MSP Elevate for accelerated discounts, all from one Sophos Central dashboard.
- Check the ESET roadmap before standardising on it. ESET’s own documentation states that ESET MSP Administrator 2 is in a feature freeze and is set to be replaced by ESET PROTECT Hub.
- Look at Microsoft 365 Lighthouse if your clients are already on Business Premium. Microsoft states it requires enrolment in the CSP programme and delegated access, carries no additional cost, and surfaces Microsoft Defender XDR threat detail across tenants.
- Never run several clients inside one shared tenant to save effort. The bill for that arrives at the first offboarding.
Ask four billing questions in writing: how usage is aggregated, whether the count is a peak or an average for the period, whether non-deployed seats in a tenant are billable, and what happens in an offboarding month. No vendor publishes those.
If the billing model and the integration list settle it, you are done. Below is the tenancy test worth running in every trial, and what to check about your own console’s security.
Why it happens
You are not protecting one estate. You are buying a platform that has to keep dozens of estates apart, bill you for what you actually deployed rather than what you predicted, and let a technician move between clients without logging out and back in. Detection quality is assumed at this level; tenancy and billing are what you are choosing between.
Real separation means each client company has its own policy tree, its own reporting, its own data boundary and its own set of technicians with access. Bitdefender describes its structure as parent-child infrastructures for managing multiple client environments; ESET’s licence-management hierarchy runs through seven levels from ESET HQ down through distributor, division, MSP, MSP manager, managed MSP and MSP customer. A single console that groups endpoints by folder and calls it multi-tenant will work until a client asks for a report that must not mention anyone else.
The billing model is the other half, and it is the half that matches how you invoice. The point of an MSP programme is that you are billed in arrears for seats you actually deployed rather than committing to annual quantities. Bitdefender states monthly consumption and billing with no minimum commitments. Sophos names MSP Flex as its consumption-based-billing-in-arrears tier. Those are published positions you can hold a distributor to.
You are evaluating a platform and have two weeks
You have this one if A trial tenant, a demo call booked, and no idea what to actually test.
- Create two companies. Deploy an agent to each. Restrict a technician account to one and confirm the other is genuinely invisible rather than merely unlisted.
- Produce a client-facing report for one company and check nothing from the other appears on it.
- Then offboard that company: remove it, and confirm what happens to its data, its licences and its endpoints. Offboarding is where platforms differ most and where nobody looks until it is urgent.
Your clients are already standardised on Microsoft 365
You have this one if Most of the portfolio is on Business Premium and you are about to sell a second endpoint product on top.
- They already own Defender for Business, which Microsoft includes in Business Premium for organisations up to 300 users.
- Microsoft 365 Lighthouse is the multi-tenant view, and Microsoft states it carries no additional cost – but it requires CSP programme enrolment, either Direct-Bill or Indirect Reseller, and delegated access to the customer tenants. If you are not in CSP, that is the blocker.
- Servers still need the Defender for Business servers add-on, per server instance for up to 60 servers, which is the gap in an otherwise free multi-tenant story.
You are about to standardise on a portal that is being replaced
You have this one if A migration plan built around a vendor console you have not checked the roadmap for.
- ESET’s own online help states that ESET MSP Administrator 2 is currently in a feature freeze and is set to be replaced by ESET PROTECT Hub, using updated subscription terminology.
- That is not a reason to avoid ESET, and its DEM plug-ins for ConnectWise Automate, Datto RMM, N-able N-central, N-able N-sight RMM, NinjaOne and Kaseya VSA are a real integration list.
- It is a reason to ask which portal your onboarding process should be built against before you write the runbook.
The third consideration, and the one providers skip, is delegated access hygiene. Technicians should hold roles rather than shared credentials, multi-factor authentication should be enforced on every console account without exception, and there should be an audit trail of who changed which client’s policy. Your management console is itself a high-value target precisely because it reaches every client you have.
Full reference
The platforms, as each vendor publishes them
| Bitdefender | Sophos | ESET | Microsoft | |
|---|---|---|---|---|
| Current programme name | GravityZone for Managed Service Providers, also GravityZone MSP Security | MSP, MSP Flex, MSP Elevate | ESET MSP programme, via ESET MSP Administrator 2 | Microsoft 365 Lighthouse with Defender for Business |
| Billing | Monthly consumption and billing through distributors and RMM partners, no minimum commitments | MSP Flex: consumption-based billing in arrears; MSP: partner-owned licence entitlements | Licence management and usage reporting through EMA 2 | Through your Microsoft agreement; Lighthouse itself carries no additional cost |
| Tenancy | Parent-child infrastructures for multiple client environments | Full visibility and control across all customers from a single Sophos Central dashboard | Seven-level hierarchy from ESET HQ through distributor, division, MSP, MSP manager, managed MSP to MSP customer | Customer tenants with delegated access; CSP enrolment required |
| Named integrations | ConnectWise, Kaseya, NinjaOne, Atera, RG System | RMM/PSA integrations through the Sophos marketplace | DEM plug-ins for ConnectWise Automate, Datto RMM, N-able N-central, N-able N-sight RMM, NinjaOne, Kaseya VSA | Within the Microsoft stack |
| Managed detection | Bitdefender MDR | Sophos MDR | ESET MDR tiers | Microsoft security range |
| Roadmap note | – | – | EMA 2 in feature freeze, to be replaced by ESET PROTECT Hub | – |
| Servers | Within GravityZone licensing | Sophos Workload Protection, separate from the endpoint packages | Server Security in the PROTECT bundles | Defender for Business servers add-on, up to 60 servers |
The four billing questions to ask in writing
- How is usage aggregated across your clients – per tenant, or across the whole portfolio?
- Is the count a peak for the period or an average?
- Are seats provisioned but not deployed in a tenant billable?
- What happens to billing during a client’s offboarding month?
None of those four are published by any vendor in this comparison, which is exactly why they belong on the email rather than in your assumptions. Bitdefender’s published ‘no minimum commitments’ answers a fifth question and none of these.
Integration with the rest of the stack
The console you log into most is not the antivirus console. It is the remote monitoring and management tool, and the connector between the two decides how much manual work each new client generates. Check three things specifically: that deployment can be triggered from your management tool, that health status flows back so an agent that stops reporting raises a ticket automatically, and that seat counts can be reconciled against what you invoice without a spreadsheet.
Where a prebuilt connector does not exist, an application programming interface is the fallback and its quality varies. Ask whether you can enumerate tenants, retrieve deployment status and pull licence usage through it, because those three calls are what most providers automate first.
The Microsoft route, and its actual prerequisites
If your client base is standardised on Microsoft 365 Business Premium, you may already be managing endpoint protection you sold them. Microsoft 365 Lighthouse is the multi-tenant portal for that, and Microsoft is specific about who can use it: MSPs enrolled in the Cloud Solution Provider programme, either Direct-Bill or Indirect Reseller, with delegated access to customer tenants. It carries no additional cost and surfaces device compliance, security configuration baselines aimed at SMB tenants, multifactor authentication and self-service password reset configuration, risky sign-in detection, and threat detail from Microsoft Defender XDR.
The honest limits are the ones from the underlying plan rather than the portal: 300 users per customer tenant, and servers requiring the Defender for Business servers add-on at up to 60 servers per customer. For a portfolio of small offices those ceilings rarely bite, and where they do, the client is changing plan family anyway.
The pick, by the shape of your practice
- General small-business client base, mixed platforms, monthly billing required: Bitdefender GravityZone for MSPs, for the published no-minimum consumption billing and the breadth of named integrations.
- You sell or plan to sell managed detection: Sophos, so the escalation path lives where your technicians already work, and MSP Flex for the billing shape.
- Clients with older hardware or a preference for an on-premises console: ESET, asking first whether to build against EMA 2 or ESET PROTECT Hub.
- Client base already on Microsoft 365 Business Premium and you are in CSP: Lighthouse and Defender for Business before selling a second product.
- You are managing clients through separate small-business consoles, one login each: consolidate. That pattern is where technician time disappears.
- You want to keep a client’s platform after they leave: design for clean offboarding instead, and write it into the contract.
When a licence is the actual fix
If you are choosing a platform to build a managed endpoint service on, Bitdefender GravityZone for Managed Service Providers is the one we supply most often to providers: separate companies rather than folders, monthly consumption billing that Bitdefender publishes as carrying no minimum commitments, and named integrations for ConnectWise, Kaseya, NinjaOne, Atera and RG System. Arco supplies it through the partner programme and can walk through the parts that decide whether it fits: how tenants and technician roles are structured, how usage is aggregated and counted, and how a client offboarding is handled. Tell us how many client companies and roughly how many endpoints, and we will set the structure up correctly the first time rather than after the first offboarding.
Questions people ask about this
Is there a monthly minimum on Bitdefender’s MSP programme?
Bitdefender publishes monthly consumption and billing through its distributor and RMM partner network with no minimum commitments. That is a published position, so hold your distributor to it. The questions Bitdefender does not publish are how usage is aggregated, whether the count is a peak or an average, and how an offboarding month is treated – ask those in writing.
Can we resell a normal business SKU instead of an MSP one?
You can, and providers do it when a client insists on owning the subscription. What you lose is consumption billing, central multi-tenant management and the ability to deploy without a purchase order. It is a reasonable exception for one large client and a poor default for a portfolio.
Which ESET portal should we build our onboarding against?
Ask before you write the runbook. ESET’s own online help states that ESET MSP Administrator 2 is in a feature freeze and set to be replaced by ESET PROTECT Hub, which uses updated subscription terminology. The DEM plug-ins for ConnectWise Automate, Datto RMM, N-able N-central and N-sight, NinjaOne and Kaseya VSA are the current integration list.
Do we need to be in CSP to use Microsoft 365 Lighthouse?
Yes. Microsoft states Lighthouse is for MSPs enrolled in the Cloud Solution Provider programme, Direct-Bill or Indirect Reseller, with delegated access to customer tenants. It carries no additional cost. If you are not in CSP, the multi-tenant Microsoft route is not open to you.
What happens when a client leaves?
That depends on the platform, and it is the question to ask during evaluation rather than during the notice period. Look for a documented path that removes the company cleanly, releases the seats from your billing, and either uninstalls the agents or hands them over. Test it in the trial, not in production.
