Arcentry for Microsoft Azure
Make your Microsoft Azure infrastructure easier to explain. Bring virtual networks, application services, databases, and on-premise dependencies together in an interactive architecture diagram for planning, handovers, and design reviews.
Azure deployments often sit within a larger system: an existing data center, an identity provider, a Kubernetes platform, or another cloud. A useful Azure architecture diagram shows those relationships alongside the Microsoft services, so a reader can understand the whole application.
Arcentry lets you arrange Azure components, group infrastructure into labeled areas, and draw the connections between services. Use it to explore a proposed design, explain a migration, or give a new teammate a clear starting point for understanding an environment.
Choose boundaries that match your design question. Subscriptions can communicate ownership; virtual networks and subnets can explain network placement; an application group can show logical responsibilities. Label those boundaries so readers know which meaning you intend.
For hybrid architecture, show where the on-premise environment ends and Azure begins. Label ExpressRoute or VPN connections and identify which workloads rely on them. For managed services, show access paths and private endpoints where relevant, rather than placing every service inside a network simply because it connects to it.
Use a 2D diagram in a technical document or a 3D view when you want readers to explore the relationships. Export an image for a presentation, or embed the diagram in a wiki or project page.
As the deployment changes, update the layout and annotations or use Arcentry’s REST API to maintain selected objects and metadata from your own systems. Your diagram can remain a useful reference for design decisions, onboarding, and operational discussions. Explore the free plan and pricing to get started.
Architecture ideas
Choose the view that fits the conversation: an application request path, a Kubernetes workload, or the connections between Azure and your own environment.
Show Application Gateway routing requests to an application tier, with Azure SQL Database and Blob Storage as dependencies. Identify private endpoints and network paths explicitly, rather than suggesting every managed service lives inside a subnet.
Connect Azure Container Registry, an AKS workload, ingress, and backing services. Group the cluster and its applications clearly, and label which connections carry user traffic, container images, or application data.
Map an on-premise environment connected to Azure through ExpressRoute or a VPN Gateway. Show virtual networks, shared services, and the applications that depend on the connection, so migration plans and ownership boundaries are easier to discuss.
From design to documentation
Start with an application, a virtual network, or a migration boundary. Place Azure service components alongside the people, external systems, and on-premise resources that need to appear in the same view.
Use areas for subscriptions, networks, or application groups. Add labeled connections for request paths and private connectivity, keeping identity relationships distinct from the network routes that carry traffic.
Share a 2D or 3D image, embed an interactive diagram in a wiki, or update objects through Arcentry's REST API. Keep the view aligned with the decisions and changes your team is making.
Good to know
Have a question about your workflow? Write to info@arcentry.com.
Pair your diagram with the provider's technical guidance.
Yes. Azure components, generic servers, network devices, and open-source services can share the same canvas. Use labeled areas and connections to explain ExpressRoute or VPN connectivity, migrations, and dependencies across environments.
Yes. Use Azure Kubernetes Service, container, and Azure Functions components to describe the workload. Add ingress, messaging, storage, and external dependencies, then choose the detail level that best explains your design.
Yes. Arcentry supports 2D and isometric 3D views. You can export images for documents and presentations or use an interactive embed when readers need to explore the architecture.
No cloud account connection is needed to create a diagram manually. Start with components and labels in Arcentry. If you want live state or metrics, build an integration that sends the information you choose through the REST API.
Yes. Create an Arcentry account and use the free plan without a credit card. Current diagram and item limits are listed in the pricing section.
Make the system visible
Bring the services, networks, and dependencies your team needs into one shared view.