Managed services
Take responsibility where it can sensibly be delegated.
Managed services do not mean a blanket promise to operate everything. We define which platform, application or integration layer belongs to us and where another team remains responsible.
Typical operating models
Microsoft 365 with infrastructure around it
Support for a selected Microsoft 365 environment while DNS, connectivity, telephony or other components remain under our operational responsibility. The Microsoft-specific service is described under Microsoft 365 Support.
Server operations with a clear boundary
Taking responsibility for defined parts of a Linux or Windows server environment while internal IT or an application provider operates another layer.
Networks and communications
Operating or troubleshooting Internet access, site networks and SIP services. SBC-based Teams Telephony is treated as a separate integration project under Teams Telephony with SBC.
Clear responsibility before the incident
Scope, dependencies and escalation paths are documented before we take responsibility. This avoids discovering during an incident that two providers each assumed the other one was responsible.