Key Takeaways
- 78% of surveyed enterprises already combine Network as a Service and managed network services.
- Observability and compliance remain major obstacles, with 75% reporting visibility barriers and 90% demanding strong audit evidence.
- Buyers are evaluating NaaS over five years, even when consumption pricing creates short-term budget volatility.
Enterprise networking strategies are moving past a simple choice between consumption-based infrastructure and fully managed operations. New research released by GTT Communications indicates that large organizations increasingly use both, but bringing the two models together can expose operational gaps that procurement decisions alone do not resolve.
The findings appear in the recently published white paper, How Enterprises Approach NaaS and MNS to Build Resilient, Future-Ready Networks. The industry survey was conducted by Hanover Research, a research and analytics firm founded in 2003. Because GTT Communications commissioned the work, technology leaders should treat it as vendor-sponsored research while still considering what the reported purchasing and operating patterns reveal.
Among respondents, 78% already use a combination of Network as a Service, or NaaS, and managed network services, or MNS. The distinction matters. In the survey, NaaS refers to an on-demand, cloud-native fabric used to provision and disconnect capabilities such as SD-WAN and SASE. MNS covers a broader provider role spanning network design, implementation and operations.
That pairing makes intuitive sense. NaaS can give IT departments flexibility as application demand, cloud usage and locations change. MNS can provide operational support where reliability, staffing and predictable service delivery take priority. However, combining the models can also create another operational boundary to manage.
Observability is the clearest example. According to the findings distributed through BusinessWire, 75% of enterprises identify a lack of observability as a barrier to NaaS adoption. Of that group, 18% say visibility problems have stopped adoption more than once.
An outage in a mixed environment may originate in the NaaS layer, within a managed service or at the handoff between them. If separate providers and monitoring systems produce different versions of events, who owns diagnosis and remediation? Without a unified operational view, incident response can slow down and audit preparation can become more labor-intensive.
Compliance adds pressure. 90% of surveyed enterprises require high or very high standards of audit evidence from network providers, while 94% consider provider-maintained immutable logs valuable or extremely valuable. Encryption-key control is similarly important: 91% want control over their keys, split between full ownership at 45% and a shared arrangement at 46%, where the customer owns the keys and the provider manages them.
Those percentages suggest that provider evaluation is expanding beyond uptime and connectivity. Enterprises increasingly need evidence showing who changed a policy, when automation acted and how network activity was recorded. In practice, observability and compliance are becoming intertwined rather than separate buying criteria.
Cost presents a different tension. Around half of respondents will tolerate budget variances of 6% to 10%, while another 39% accept swings of 11% to 15% before FinOps becomes involved. Yet 92% would accept quarterly bill fluctuations of up to 15% for a NaaS offering delivering roughly 30% lower five-year total cost of ownership.
That long view also appears in board-level justification. 61% use five-year TCO as their primary NaaS metric, compared with 19% citing three-year ROI, 11% citing the EBIT effect of moving from CapEx to OpEx and 8% prioritizing payback period.
People remain part of the equation. Talent shortages are the biggest external influence on the next network update cycle for 37% of respondents. 31% plan to automate network operations fully, while 37% prefer AI-driven automated remediation for performance incidents.
For technology leaders, the practical message is fairly direct. NaaS and MNS can complement each other, but the operating model deserves as much scrutiny as pricing and architecture. Shared telemetry, audit-ready records, clear key ownership and explicit responsibility at service boundaries can help determine whether the combination behaves like one network or several disconnected contracts.
⬇️