How to create an Azure architecture diagram

The short version: Open a diagram tool with official Azure icons (Calma Studio is free and needs no signup), drag the resources you need onto the canvas, group them by resource group and virtual network, connect them to show how traffic flows, and export the result — as an image, an isometric 3D view, or deployable Bicep, Terraform or ARM. The whole thing takes minutes. Open Studio →

What you'll need

Nothing to install — a browser and a rough idea of the resources in your architecture: an app, a database, some networking, and the supporting pieces (secrets, storage, telemetry). Documenting something that already exists? Have its resource list handy. Designing something new? A napkin sketch is enough to start.

Step 1 · Pick a tool with official Azure icons

Use a tool that speaks Azure, not a generic shape library. Calma Studio is free, runs in your browser and ships the official Azure icon set, so a reviewer instantly recognises a Storage account, a Key Vault or an AKS cluster. No signup to start.

Step 2 · Add your Azure resources

Drag resources onto the canvas from the palette — compute (VMs, App Service, Functions, AKS, Container Apps), networking (VNets, subnets, NSGs, Front Door), data (SQL, Cosmos DB, Storage) and the platform pieces (Key Vault, Log Analytics). Name each one as it is — or will be — in Azure.

Step 3 · Group by resource group, VNet and subnet

This is what separates an Azure diagram from clip-art. Put resources inside the containers they really live in: resource groups, virtual networks and subnets. In Calma Studio the containers are first-class — move a resource and its box follows — so the nesting mirrors how Azure is actually organised.

Step 4 · Connect the resources

Draw the relationships that matter: which service talks to which, what sits behind the gateway, where the private endpoints land. Connections make the diagram read as an architecture, not just an inventory.

Step 5 · Set region and tags (optional)

Heading towards deployment? Set the region and tags — per resource or as project defaults. They carry through to the exported code, so you're not re-typing them later.

Step 6 · Export — image, 3D or infrastructure-as-code

Export a PNG for a doc, switch to the isometric 3D view for a presentation, or — the step most tools can't do — turn the diagram into Bicep, Terraform or ARM you can actually deploy.

Tips for a diagram that reads well

• Group before you connect — nesting first makes the connections far cleaner.
• Name things like Azure does — real resource names beat "Database 1".
• Start from a template — the gallery has landing zone, hub-and-spoke, AKS and more; open one and adapt it.
• One diagram per concern — a network view and a data-flow view read clearer than one crowded canvas.

Open Calma Studio — free, no signup →

FAQ

• What's the easiest way to make an Azure architecture diagram? Start from a template in a tool with official Azure icons, then adapt it — far faster than a blank canvas. Calma Studio is free and needs no signup.
• Do I need a Visio or Lucidchart licence? No. Calma Studio is free and browser-based; see the Lucidchart alternative.
• Can I turn the diagram into code? Yes — export to Bicep, Terraform or ARM from the same canvas.
• How long does it take? A simple architecture is minutes, especially starting from a template.
• Are the icons the official Azure ones? Yes — by resource type, with shape and colour by category.