Azure · DrawArc
Azure diagram tool for application architecture
Explain how an Azure application handles a request, reaches its data and recovers from failures. Explore a public Azure-context storefront diagram with Front Door, API Management and AKS, then download an editable project or sign in to customize a private copy.
Online storefront checkout — Azure environment / Identity and access. Public read-only canvas: zoom, pan, code and project download without login. Sign in to customize a saved copy. Deployment context is illustrative, not a verified routing configuration.
Draw an Azure request path your team can follow
Begin with the users and public entry boundary. The linked example combines a storefront workflow with Azure Front Door, API Management and Azure Kubernetes Service as deployment context. Its runtime-context connector is a logical relationship, not a complete network or packet-routing specification. Use the code and canvas to name the actual services, show where authentication is checked and identify which component owns each business operation. A useful review should make it possible to follow checkout, payment and order updates without guessing what an unlabeled arrow means.
Choose App Service, Functions or AKS deliberately
A container cluster is not required for every Azure web application. Compare the operating model with App Service or Functions before adopting AKS. Record workload duration, deployment needs, network access and the team's operational capacity. DrawArc supplies Azure stencils for services including App Service, Functions, Blob Storage, SQL, Cosmos DB and AKS; an icon does not configure the service. Replace a runtime only after updating its dependencies and explaining which responsibilities move to the platform or remain with your team.
Make identity and private data access explicit
Draw the distinction between an identity provider, an access decision and the data operation it protects. Document workload identity, secret ownership and permitted database connections. Evaluate private endpoints and routing for the selected services rather than treating a box labelled private as an implemented control. The identity extension in the public example is a review prompt: it does not establish tenant isolation or deploy Microsoft Entra policies. Add the authorization checks used by your application and test access across customer boundaries.
Include recovery and the cost of each decision
For each critical dependency, specify a timeout, retry limit, alert owner and recovery path. Discuss zone or region choices separately from backup restoration: a replica does not undo an incorrect write. Compare service complexity, network cost and operational ownership against the workload's needs. Start with a readable logical view and add a separate deployment view when subnet, policy and zone detail becomes too dense. Consult the Azure Architecture Center before implementation; DrawArc does not deploy resources or validate a subscription's configuration.
Turn Azure design questions into a reviewable diagram
Workflow comparison, not a performance benchmark. Sources reviewed 14 November 2026; check current provider documentation before deciding.
| Consideration | DrawArc | Implementation decision |
|---|---|---|
| Application runtime | Replace cloud icons, groups and connections in an editable project. | Choose App Service, Functions or AKS based on workload and operations. |
| Identity boundary | Label where identity and authorization decisions occur. | Configure identities, scopes, role assignments and application checks. |
| Data access | Separate public entry and data dependencies visually. | Validate network routes, endpoints, database permissions and secrets. |
| Recovery | Add failure paths and recovery notes to the design. | Provision backups and failover, then measure a restore drill. |
Provider-neutral patterns you can adapt to Azure
RAG LLM Production System Architecture
Edit a RAG system architecture showing document ingestion, chunking, embeddings, vector retrieval, an LLM gateway and evaluation.
Data EngineeringMedallion Lakehouse Data Pipeline
Customize a medallion data pipeline diagram showing ingestion, Bronze raw data, Silver validation, Gold models, orchestration and BI.
Frequently asked questions
Can I view an Azure diagram without signing in?
Yes. The public Azure example supports read-only zoom, pan, code and project download without login. Sign in to customize a saved private copy. Separate starter templates support anonymous local editing.
Does DrawArc import my Azure subscription automatically?
No. These diagrams are authored references. They do not discover Azure resources, create policies or deploy infrastructure.
Can I replace AKS with App Service?
Yes. Download the editable project or customize a private copy, replace the runtime and update the connections and operational assumptions.