IT service management (ITSM) covers the activities an organization performs to design, deliver, operate and control IT services for its customers, typically through processes such as incident, request and change management.
Title graphic: IT service management (ITSM) (Concept)
IT service management (ITSM) is the set of activities an organization performs to plan, build, deliver, run and manage IT services for its customers. It is typically organized through processes such as incident, request and change management. In contrast to technology-centred disciplines such as network or systems management, ITSM is process-oriented: it focuses on customer needs and on the services that are actually delivered, and it stresses continual improvement.
A central element of ITSM in practice is the service desk. Under ITIL, the service desk acts as the single point of contact between users and IT staff. It receives incident reports, handles service requests, and manages change requests, third-party arrangements and software licensing. ITIL distinguishes the service desk from a call center or help desk, since those cover only part of this scope. This distinction matters when an organization decides how broadly to define the function and which tasks should sit within it.
ITSM is usually guided by a framework or standard. ITIL is the most prominent one and is aimed at aligning IT with business needs. Other frameworks and standards named in the sources include COBIT, TOGAF, eTOM, FitSM, CMMI, ASL, USM, BiSL, the Microsoft Operations Framework and the certifiable standard ISO/IEC 20000. Professional bodies such as itSMF and HDI support the field, and common certifications include ITIL 4, TOGAF and COBIT. Choosing among these options is typically a question of how much structure, formal certification and process documentation an organization wants.
Routine ITSM tasks can be automated through IT process automation, which reduces manual handling of recurring requests and standard changes. ITSM tools are also often applied beyond the IT department, an approach known as enterprise service management, where the same request, workflow and service desk principles are used for other business functions.
In the Microsoft ecosystem, ITSM comes up when organizations connect service management platforms with Microsoft 365. The M365.FM episode "ServiceNow and Microsoft 365: From Intent to Business Action" (2026-01-26) addresses this in the context of integration planning. According to the episode, the starting point is an assessment of current systems and processes: identifying fragmentation and inefficiencies, evaluating current ITSM needs, and identifying pain points that an integration could address. The episode also recommends consulting the IT team to learn which features would be most beneficial, and considering how other Microsoft tools, such as Dynamics 365 or Azure DevOps, might fit into the broader strategy.
Taken together, the sources describe ITSM as both a discipline and a practical operating model. It defines how services are requested, delivered, changed and improved, which framework or standard gives the process its structure, and how tooling and automation support day-to-day work. Decisions around it typically concern the scope of the service desk, the choice of framework, the degree of automation, and whether service management practices should extend to non-IT areas of the organization.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
Type
Concept
Key points about IT service management (ITSM)
Key points about IT service management (ITSM) from the episodes, each with its source episode:
This episode of the M365.FM Podcast (titled “How to Build a High-Performance Agentic Workforce in 30 Days”) explains why most enterprise AI agent programs fail quickly, and what it really takes to build an AI-driven workforce that delivers measurable business…
How Altera Unlocks the Autonomous Microsoft Enterprise” explores why most “AI agent” initiatives in Microsoft environments stall or fail — and what it actually takes to build true autonomy at enterprise scale. The host argues that the difference between…
In this episode of the m365.fm podcast, Mirko Peters speaks with Microsoft MVP and Microsoft Certified Trainer Nathalie Leenders about building a successful career in the Microsoft Power Platform ecosystem. Nathalie shares her journey from IT service…
“Your M365 dashboards look busy—but do they move revenue, reduce cycle time, or raise CSAT? Stop counting clicks and start proving ROI: tie Teams, SharePoint, and Outlook activity directly to sales closed, cases resolved, and projects delivered with a unified…
One “small” M365 hiccup can nuke your day—Teams spins, Outlook chokes, SharePoint vanishes—and your status page still says “healthy.” The culprit? Hidden dependencies (hello, Azure AD) that turn single glitches into cross-cloud pileups. Ditch the siloed…
Timeline of episodes about IT service management (ITSM)
Articles about IT service management (ITSM) (3)
Articles in which IT service management (ITSM) is a topic:
Integrating ServiceNow with Teams: A Complete Guide · Mirko Peters Bringing ServiceNow and Microsoft Teams together isn’t just a tech project—it’s a game-changer for how your organization gets work done. This guid…
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What does IT service management (ITSM) cover? (AI)
ITSM covers the activities an organization performs to plan, build, deliver, run and manage IT services for its customers. It is typically organized through processes such as incident, request and change management.
How does ITSM differ from a help desk? (AI)
According to the sources, ITIL distinguishes the service desk from a call center or help desk, which cover only part of the scope. The service desk is the single point of contact for incidents, service requests, change requests, third-party arrangements and software licensing.
Which frameworks and standards are associated with ITSM? (AI)
ITIL is the most prominent framework. Others named in the sources include COBIT, TOGAF, eTOM, FitSM, CMMI, ASL, USM, BiSL, the Microsoft Operations Framework and the certifiable standard ISO/IEC 20000.
Microsoft 365 Usage reports via the Graph Reports API and the Unified Audit Log for activity, plus business KPIs from CRM, project tools, ITSM and CX platforms such as NPS or CSAT. · From the episode: Link Microsoft 365 Usage to Real Business Results
What hidden dependencies do teams often miss?
Power Platform flows depending on connectors, Graph-based provisioning jobs, SIEM and archiving ingest that pauses when auth breaks, and CRM or ITSM webhooks with tokens that expire mid-incident. · From the episode: Improve Microsoft 365 Resilience and Outage Response
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.