Skip to content
All posts

Who's Who in a Microsoft 365 Deal: ITIL v5 Service Relationships

ITIL v5 service relationships explained with M365: providers, consumers and vendors, sponsor vs customer vs user, relationship types and service quality.

On Monday I covered products, services and value. But value is always co-created by someone with someone. This post is about the who: the organizations and roles in a service relationship, how close those relationships get, and how service quality is measured.

I'll use one scenario throughout: a company buying and running Microsoft 365.

Three kinds of organization

ITIL® v5 names three roles an organization can play:

  • Service provider: responsible for delivering and supporting services. In my scenario, that's the managed service provider running the tenant.
  • Service consumer: responsible for procuring and using services. That's the company.
  • Digital product vendor: responsible for creating and continually improving digital products and their offerings. That's Microsoft, building Teams, Exchange and Entra ID. This role is new in v5, and it reflects how much of IT today is built on someone else's product.

An organization can be a whole company, a single team or one self-employed person. And organizations form chains and networks. An internal IT team consumes Microsoft 365 and provides IT services to the rest of the business, both at once.

Inside the consumer there are three roles. They can have different, sometimes conflicting, expectations:

RoleWhat they doIn my scenario
SponsorAuthorizes the budgetThe CFO signs off the licence spend
CustomerDefines requirements and owns the outcomesThe IT manager decides on E5 with DLP and Teams Phone
UserUses the serviceStaff in Outlook and Teams every day

My shorthand: the sponsor pays, the customer decides, the user uses. The conflicts are real. The CFO wants the cheapest licence, the IT manager wants the security features, and users just want Teams to work.

How close is the relationship?

ITIL describes three types of service relationship:

BasicCooperativeCollaborative (partnership)
FocusEfficiencyImprovement and effectivenessInnovation and growth
ServicesOff-the-shelf, standardConfigured or customizedCustom, bespoke
AgreementsStandard contracts and SLAsAdvanced SLAsBespoke or outcome-based, or none
M365 exampleBuying Business Basic onlineAn MSP running your tenant under a tailored SLAA partner co-building a custom solution with you

As the relationship gets closer, it also involves more of the organization: operational for basic, up to strategic for collaborative.

Service journey and band of visibility

Two ideas describe the relationship over time:

  • Service journey: all the activities and interactions between provider and consumer. It's about what happens over time, and the steps don't always run in order. They can even happen simultaneously.
  • Band of visibility: what each side can actually see of the other. If you've ever had an MSP who can't see your business priorities, or a client who can't see your backlog, you've felt a narrow band of visibility.

Measuring service quality

Service quality is the sum of a service's characteristics that matter for meeting stated and implied needs. Service levels are the metrics that define it. v5 sorts those metrics into four categories, with none more important than the others:

  • Utility: does it do what's needed? Teams lets you meet and chat.
  • Warranty: does it do it reliably and securely? Teams is available and protected.
  • User experience: how does it feel to use? Joining a meeting is easy.
  • Sustainability: does it meet environmental, social and economic requirements?

An SLA is the documented agreement between provider and customer setting out the services and their agreed levels. For digital services, ITIL says SLAs should cover utility, warranty and sustainability, plus user experience for anything user-facing. If your SLAs only measure uptime, that's warranty alone.

What I'm taking into the exam

  • Provider = delivers and supports. Consumer = procures and uses. Digital product vendor = creates and improves the product.
  • Sponsor pays, customer decides, user uses.
  • Basic = efficiency, cooperative = improvement, collaborative = innovation.
  • Service journey = what happens. Band of visibility = what's seen.
  • Four service level categories: utility, warranty, UX, sustainability.

ITIL® is a registered trademark of PeopleCert group. This post contains my personal study notes and interpretation, not official ITIL guidance.

Back to all posts