M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Service catalog

Concept

A central record of the software services a company runs, showing for each service its owner, documentation, dependencies, status and support links.

✦ CONCEPTService catalogM365.FM
Title graphic: Service catalog (Concept)

Also discussed

The episode about Service catalog also covers Internal developer platform, Azure subscription and Platform engineering.

Description

A service catalog is a central record of the services an organization runs. In the software context described on M365.FM, it acts as a map of running software and shows, for each service, who owns it, where its documentation and source code live, what it depends on, what its operational status is, and where to find dashboards and support information. The term is also used more broadly in IT and business settings, where a service catalog is a curated collection of services kept in a digital registry that doubles as a knowledge management tool.

The main purpose is visibility. As organizations accumulate hundreds or thousands of applications and services, understanding what exists becomes increasingly difficult. A service catalog helps developers and operations teams answer basic questions quickly, such as which team owns a given service, how it connects to other services, and whom to contact when something goes wrong. In the broader IT service management sense, a catalog also centralizes services so that distributed parts of an organization use the same ones instead of duplicate local versions, and it can reveal gaps and redundancies.

A typical catalog entry carries a defined set of attributes. According to general descriptions of the concept, an entry usually has a named accountable owner, a name or identifier, a description, a category, related request types and supporting services, information on who may request or view it, any costs, how it is requested and fulfilled, and escalation points and key contacts. Services in such a catalog are typically repeatable, with controlled inputs, outputs and procedures. Some implementations also track demand metrics such as the most and least used services, approval and delivery times, and spending.

Users usually search or browse the catalog by category, review the details of a service, submit a request and follow its status. Under ITIL, an IT service catalogue is the published part of the service portfolio, and cloud service catalogues often work as self-service portals with standardized definitions. These descriptions focus on business and IT services and requests; a developer-oriented catalog of software components is a related but distinct framing, and the two should not be assumed to be identical.

The M365.FM episode "Internal Developer Platforms (IDPs) - Simply Explained" presents the service catalog as one building block of an internal developer platform. It appears alongside golden paths, where developers supply only the information that matters, such as the service name, owner, environment, runtime and approved options, while the platform handles the underlying setup. In that context the catalog provides the central map of what is running, including ownership, documentation, dependencies, source code, operational status, dashboards and support information.

The episode "High-Performance Azure Cloud Governance to Reduce Waste" uses the term in a governance sense. It lists a cloud service catalog as one governance strategy, described as a list of approved services that standardizes consumption and mitigates risks. It appears next to a cloud governance framework, cloud service management, cloud security, cloud cost management and cloud compliance. Here the catalog functions less as a map of existing software and more as a controlled set of approved offerings that guides how cloud services are consumed.

When deciding how to use a service catalog, the main considerations are which meaning applies and what the entries must contain. A catalog meant to document running software needs reliable ownership, dependency and status information, while a catalog meant to govern consumption needs a clear definition of approved services and who may request them. In both cases the value depends on entries having a named owner and staying current, since a record that is incomplete or outdated cannot answer the ownership and support questions it exists to address.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept

Key points about Service catalog

Key points about Service catalog from the episodes, each with its source episode:

Episodes about Service catalog

Episodes in which Service catalog is discussed:

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What is a service catalog? (AI)

A service catalog is a central record of the services an organization runs. For software services it shows each service's owner, documentation, dependencies, status and support links, so teams can quickly see what exists and who is responsible.

What does a service catalog entry usually contain? (AI)

Entries typically include a named accountable owner, a name or identifier, a description, a category and related services, access information, costs where relevant, how the service is requested and fulfilled, and escalation points and key contacts. In developer settings, source code, dashboards and operational status are also listed.

How does a service catalog relate to an internal developer platform? (AI)

The M365.FM episode "Internal Developer Platforms (IDPs) - Simply Explained" describes the service catalog as the central map of running software within an internal developer platform, alongside golden paths that let developers provide only key details while the platform handles the setup.

Glossary

Community wiki

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.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: