Azure DevOps Academy · Service Catalogue

Service Definition

Describe purpose, users, boundaries, dependencies and ownership for a technical service.

Objective: Create an unambiguous catalogue entry that supports consumers and operators.

Practical guidance

Discover and define

01

Define customer outcomes and scope

Apply this point to a real Azure DevOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.

02

Identify owners and support teams

Apply this point to a real Azure DevOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.

03

Map dependencies and exclusions

Apply this point to a real Azure DevOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.

Practical guidance

Execute and improve

01

Document features and service options

Apply this point to a real Azure DevOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.

02

Define access and request processes

Apply this point to a real Azure DevOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.

03

Publish support and escalation paths

Apply this point to a real Azure DevOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.

Practical guidance

Assure and evidence

01

Review with stakeholders

Apply this point to a real Azure DevOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.

02

Set review dates

Apply this point to a real Azure DevOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.

03

Maintain version history

Apply this point to a real Azure DevOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.