AzureCraft is a small, focused blog about designing on Azure well. It’s for architects and engineers who want the reasoning behind a reference architecture — not just a screenshot of the portal.
Why it exists
Most Azure content explains how to click a thing. Far less explains why you’d choose one pattern over another, what the diagram should look like, and how to reuse it. AzureCraft is an attempt to write down that judgement: the decisions, the trade-offs, and the patterns that survive contact with real environments.
What we believe
- Opinionated. A clear recommendation with stated trade-offs beats a wall of “it depends.”
- Diagram-first. If it can’t be drawn clearly, it isn’t understood yet.
- Reusable. Patterns are written so you can lift them into your own designs.
- Honest. Where Azure has rough edges, we name them.
The three pillars
Landing zones, networking, identity, governance, and cost guardrails.
Landing AI workloads safely, private connectivity, and data platform patterns.
Application design that holds up under real load and real org structures.
Build something: AI Projects
Beyond the writing, AzureCraft hosts a hands-on portfolio of 12 AI projects built on Microsoft Foundry — each with a complete, step-by-step build guide. They exist to help Cloud Solution Architects sharpen real AI skills, show customers what’s possible, and kick-start co-build POCs. Working demos on your laptop, not slides.
Explore the AI Projects portfolio →
Get in touch. Want a specific topic covered, or have feedback on a post? Replace this with your email or social links — the footer and this box are ready for them.
New here? Start with Welcome to AzureCraft.