Domain Playbooks
Infrastructure
Landing zone, hybrid connectivity, sovereign cloud — the substrate everything else sits on.
8 sub-domains · 8 storiesOpen
Solution Atlas
Start with a customer conversation. Resolve into the right cloud solution.
Every dialogue starts in a technology domain. Pick the domain, narrow to a sub-domain (standard everyday need or specialised adaptation), then choose the user story closest to your customer’s situation. The right SKUs and capabilities resolve from there — ready to add, annotate, and export.
Pick a domain
7 domains · 44 storiesall with playbooksDomain Playbooks
Data
Modern data platform decisions — Fabric, Databricks, Snowflake — and the storage and governance underneath.
6 sub-domains · 6 storiesOpen
Domain Playbooks
Analytics
How business teams consume governed data without queue-based gatekeeping.
5 sub-domains · 5 storiesOpen
Domain Playbooks
AI
From Microsoft 365 Copilot to custom Azure AI Foundry workloads — and the governance that makes it defensible.
6 sub-domains · 6 storiesOpen
Domain Playbooks
Security
Modern SOC, identity protection, endpoint protection — the load-bearing security stack.
7 sub-domains · 7 storiesOpen
Domain Playbooks
FinOps
Tagged visibility, forecasting, reservations, and the cadence that keeps cloud spend governable.
5 sub-domains · 5 storiesOpen
Domain Playbooks
Governance & Compliance
Information protection, data governance, sovereignty controls, audit-defensible posture.
7 sub-domains · 7 storiesOpen
How it works
Step 1
Domain
Pick one of seven technology domains — Infrastructure, Data, Analytics, AI, Security, FinOps, Governance.
Step 2
Sub-domain
Narrow to a sub-domain, tagged as a standard everyday need or a specialised adaptation.
Step 3
Story
Choose the customer user story closest to the conversation in front of you. Each is a recognisable scenario.
Step 4
Resolve & export
The story resolves to the recommended SKUs and capabilities. Build the storyline. Download as Markdown.