The Azure Solution Architect Map


Azure is so broad that it is sometimes difficult to find your way. Although a list of services already exists, I tried to include extra decision factors helping to choose for a solution or another. For instance, if you were to design a Microservices architecture over containers and hesitate between AKS & Service Fabric Mesh, one differentiating factor is how these platforms handle service state. These factors are by no means comprehensive and are even subject to discussion but of course, since it is represented as a mental map, I have to remain high-level and there is no room for arguing.  I have articulated the map around 8 typical concerns when deploying workloads to the Cloud:

  • Monitoring
  • Security
  • Workload types (SoE, SoI, SoX, SoR)
  • Connectivity
  • Identity
  • CI/CD
  • Governance and Compliance
  • Containerization.

I haven’t segregated FaaS, PaaS and IaaS and some services belong to multiple high-level nodes but this should help you identifying some key areas and key services.


Here is a screenshot of the map:



and you can access it in the map format through the following URL:

Feel free to collapse/expand nodes as grasping it right with the image only is a bit challenging.


About Stephane Eyskens

Office 365, Azure PaaS and SharePoint platform expert
This entry was posted in Azure and tagged , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s