Solution Atlas
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.
The Azure foundation everything else runs on — how people sign in, how the network connects, how spending is controlled, how the cloud links back to the data centre. Most cost surprises, security findings on a cloud build-out, and "we need to leave VMware" conversations sit here.
The data platform decisions — which engine to bet on, Microsoft Fabric, Databricks, or Snowflake — and the storage and governance underneath. Conversations here are usually about consolidating data sprawl, retiring an old data warehouse, or making the numbers trustworthy.
How business teams get answers from data without queuing for the data team. Self-service reporting, board packs, customer dashboards, and the governance that keeps the numbers trustworthy.
From Microsoft 365 Copilot to custom AI built on Azure AI Foundry — and the governance that makes any of it defensible to regulators, auditors, and customers.
The modern security stack — a single alerting system, identity protection, device protection — that holds together when something goes wrong, and gives the security team fewer-and-better alerts rather than more.
Keeping cloud spending visible, predictable, and accountable. Tagging discipline, forecasting, reservations, and the monthly cadence with the business that turns "how much is this costing?" from a fight into a routine conversation.
How a customer protects sensitive content, governs their data across the platforms it lives on, maps their architecture to the regulations that apply, and proves to an auditor that it all holds together.
Step 1
Pick one of seven technology domains — Infrastructure, Data, Analytics, AI, Security, FinOps, Governance.
Step 2
Narrow to a sub-domain, tagged as a standard everyday need or a specialised adaptation.
Step 3
Choose the customer user story closest to the conversation in front of you. Each is a recognisable scenario.
Step 4
The story resolves to the recommended SKUs and capabilities. Build the storyline. Download as Markdown.