Resources — The Handbook
The architecture diagrams from the Handbook — yours to download and edit
Every architecture diagram in the Microsoft Power Platform Solutions Architect’s Handbook is available here as an editable file — a starting point for your own As-Is and To-Be models, fit-gap structures and integration designs, rather than a blank canvas.

What’s included
Every diagram from the second edition
The download covers the full set of diagrams used across the book’s end-to-end transformation walkthrough — from discovery and the existing-landscape assessment, through requirements, fit-gap analysis and solution design, to integration, security, ALM and go-live.
- The nine-pillars framework for solution architecture
- Current-landscape and As-Is architecture models
- Requirements and fit-gap analysis structures
- Solution-design topology and data-model diagrams
- Integration, gateway and proxy patterns
- Security, business-unit and DLP models
- ALM, environment and go-live flows
They are deliberately generic. The book builds them around a fictional financial-services organisation, so nothing here is client-specific — which makes them safe to lift, rename and reshape for your own programmes.
Downloads
Two formats, one click
Editable Visio source
The full diagram set as a Microsoft Visio file (.vsdx), supplied zipped for download. Open it in Visio, pull out the diagrams you need, and adapt them for your own architecture work.
~2 MB · .zip containing a .vsdx file
Diagrams PDF
Every diagram as a single PDF — for reading, printing or sharing when you just need to see them and don’t have Visio to hand.
~840 KB · .pdf
Files are hosted in the site media library. If a download link does not resolve, the diagram files may still need to be uploaded to Media.
Using the diagrams
Free to adapt for your own work
These are my own diagrams from my published book, shared here so practitioners can build on them rather than start from a blank canvas. You are welcome to download them, edit them and reuse them in your own architecture documents and proposals. A credit back to the Handbook is appreciated but not required.
The diagrams stand on their own, but the book is where the reasoning behind each one lives — why a model is shaped the way it is, and the decisions that sit underneath it.
Want the thinking behind the diagrams?
The Handbook works through each of these diagrams in context. If you would like to talk through how the same approach applies to a programme of your own, that is an easy conversation to start.



