What are managed network services? Scope, models and how to choose a provider

How does a managed network service work day to day?

The provider connects your devices to its monitoring platform, takes over the configurations and runs the network against agreed SLAs. Your team raises changes and incidents through a service desk instead of logging into devices.

1. Assessment and onboarding. Inventory of devices, circuits, licences and configurations; documentation of the current design; fixes for urgent risks.
2. Monitoring. Devices send SNMP data, flow records and logs to the NOC. In the cloud, sources such as VPC Flow Logs are added. Alerts are tuned to cut noise.
3. Incident handling. The NOC detects a fault, opens a ticket, fixes it remotely or dispatches a field engineer, and contacts the carrier when a circuit fails.
4. Change management. Firewall rules, new sites and VLAN changes go through an agreed change process with testing and rollback plans.
5. Maintenance. Firmware and security patches in agreed maintenance windows; lifecycle tracking for end-of-support hardware.
6. Reporting and reviews. Monthly SLA and capacity reports, and a quarterly review of risks and improvements.

If you only want the monitoring part, see our note on managed network monitoring services, which covers that narrower scope.

Why do companies outsource network management?

Mostly for availability, skills and predictable cost. A network that spans offices, data centres, cloud platforms and remote staff needs round-the-clock attention that a small internal team struggles to provide.

• Downtime cost. According to ITIC's 2024 Hourly Cost of Downtime survey, an hour of downtime costs more than USD 300,000 for over 90% of mid-size and large enterprises, and 41% put it between USD 1 million and over USD 5 million. Faster detection and repair has a direct business value.
• 24/7 coverage. Staffing your own night and weekend shifts needs several engineers per role. A provider spreads that cost across many customers.
• Specialist skills. SD-WAN, firewall platforms, BGP, cloud routing and zero trust each need trained people. Few mid-size companies have all of them in-house.
• Security and compliance. In the EU, the NIS2 Directive requires in-scope organisations to manage cybersecurity risk in their network and information systems and report significant incidents. A managed provider can supply the controls, logs and evidence, but legal accountability stays with you.
• Predictable spend. A monthly fee replaces unplanned overtime, emergency call-outs and ad-hoc consultancy.

In-house vs managed vs co-managed networking

There is no single right answer. The choice depends on how many sites you run, how critical uptime is and which skills you already have.

Co-managed models are common in the Nordics and India where companies keep one or two network specialists and buy NOC cover, firewall management or SD-WAN operations around them. Our article on building a NOC team vs NOC as a service compares the staffing side in more detail.

SD-WAN, SASE and zero trust: where they fit

These are architectures a provider may deploy and run for you. They are not separate services you must buy all at once.

SD-WAN

Software-defined WAN steers traffic between sites over several links (fibre, broadband, mobile) based on application and link quality, managed from a central console. It often replaces or reduces MPLS circuits and gives branch offices direct, policy-controlled access to cloud services.

SASE

Secure access service edge combines networking (SD-WAN) with cloud-delivered security such as secure web gateway, cloud access security broker and zero trust network access. Users connect to the nearest point of presence instead of backhauling through a head office firewall.

Zero trust

Zero trust is a security model, not a product. NIST SP 800-207 describes it as moving defences from static network perimeters to users, assets and resources, with no implicit trust based on network location. In practice that means strong identity, device checks and segmented access instead of a flat internal network.

How is managed networking priced?

Most providers use one of four models. We do not quote market price ranges here, because they vary widely with scope, SLA level and whether hardware is included.

Ask every provider for the same breakdown: one-off onboarding, recurring management fee, hardware or licences, carrier costs, and hourly rates for out-of-scope work. Only then are quotes comparable.

What should the SLA say?

A useful SLA defines measurable targets and what happens when they are missed. Check for:

• Availability target per site or service, how it is measured and what is excluded (carrier faults, planned maintenance).
• Response and restore times by priority level, with clear priority definitions.
• Change lead times for standard and emergency changes.
• Service credits when targets are missed.
• Reporting: monthly SLA reports with raw incident data, not only percentages.
• Exit terms: handover of configurations, documentation and credentials when the contract ends.

How to choose a managed network provider: 10 questions

1. Which of our sites, devices and cloud networks are in scope, and what is explicitly excluded?
2. Where is your NOC, is it staffed 24/7, and who answers at 3 a.m.?
3. Which vendor platforms (firewalls, switches, SD-WAN) do your engineers support today?
4. How do you connect on-premises networks to AWS, Azure or Google Cloud?
5. What are the response and restore times per priority, and the service credits?
6. How does the change process work, and how fast are standard changes?
7. Who owns the configurations and documentation, and how do we get them on exit?
8. How do you handle security events: do you forward logs to a SOC, and who responds?
9. What evidence can you provide for NIS2, ISO 27001 or customer audits?
10. Where is our monitoring data stored, and does it stay in the EU (or in India) if we require it?

How Opsio helps

Opsio's network services focus on the connection between on-premises sites and the cloud: VPC and VNet design with AWS Transit Gateway or Azure Virtual WAN, AWS Direct Connect and Azure ExpressRoute, site-to-site VPN, firewall management, SD-WAN and 24/7 monitoring. Security events can go straight to our SOC services, and we work from offices in Karlstad, Sweden and Bangalore, India.

For Opus Bilprovning, which runs around 100 inspection stations across Sweden and inspects more than two million vehicles a year, Opsio provides 24/7 managed operations of the AWS environment that the stations depend on. That engagement is cloud operations rather than a pure network contract, but it shows the multi-site, always-on context where managed operations pay off.

Frequently asked questions

What is the difference between managed network services and managed IT services?

Managed IT services usually cover the wider IT estate: end-user devices, servers, applications and the service desk. Managed network services are narrower and deeper, focusing on connectivity, network security and network performance. Many providers sell both, and contracts often combine them.

Is a managed network service the same as a NOC?

A NOC (network operations centre) is the team and tooling that monitors networks around the clock. It is one part of a managed network service, which also includes design, configuration management, changes, security and reporting.

Can we keep our own network engineers?

Yes. A co-managed model lets your engineers keep design authority or specific platforms while the provider covers monitoring, out-of-hours incidents and routine changes. Write down who does what, so tickets do not fall between teams.

Do managed network services help with NIS2 compliance?

They can supply many of the technical measures and the evidence: logging, monitoring, patching, access control and incident records. NIS2 accountability still sits with your management body, so you need your own risk management and reporting process.

How long does onboarding take?

It depends on the number of sites and how well the current network is documented. A single office can be onboarded quickly, while a multi-country estate is usually brought in site by site. Ask the provider for a written onboarding plan with milestones.

Related reading: Claude Partner Network.