Cloudockit allows you to automatically generate your Azure Architecture diagrams in editable formats with Visio, diagrams.net (draw.io), and Lucidchart. Stop wasting time and effort manually creating and updating your diagrams. Cloudockit will do the work for you!
Once you connect your Microsoft Azure environment with our software, Cloudockit can scan your whole cloud architecture and outline it automatically into a complete and editable Azure diagram.
The steps are simple: You log into your Azure Subscription and Cloudockit will leverage the Azure native API to retrieve all your resources and the links between them.
Here are some benefits of gaining a general perspective of your Azure environment:
Based on your valued feedback, Cloudockit has been fine-tuning its diagramming software since 2013. Our team understands your needs better than ever.
We know that diagrams need to be tailored to specific audiences: no single diagram will answer everyone’s needs. Therefore, instead of creating a single generic diagram, Cloudockit builds different types of diagrams targeted at different reader profiles.
Below, you will find our 5 most popular Azure architecture diagrams.
This Azure network diagram is handy for developers working with App Services. They can see the dependencies with components like SQL Databases, Storages, Event Hubs, Service Bus, Cosmos DB, etc.
Compared to the previous Azure architecture diagrams, which are organized per type of Workload, this one uses the logical grouping provided by Resource Groups. You simply generate a tab per resource group.
Cloudockit also generates global diagrams that contain everything in your Azure subscription. The global Azure network diagram shows an overview of all the resources in your Azure subscription. It is also a good starting point if you have a messy environment you want to clean up. Cloudockit automatically generates two types of global diagrams: one with all the details and the other with a high-level overview.
Cloudockit is compatible with diagrams.net, Lucidchart, and Visio, the three most popular diagramming tools on the market. We leverage plenty of their built-in features as we firmly believe you should not waste time learning to use new diagramming tools.
We also give you the option of generating your diagrams as PDF files which can be easily shared with team members or management.
Cloudockit automatically embeds data into the Shapes it generates. You can use this data to see each component’s details and generate rules in Visio.
A good example would be to create a rule where you show a Red icon for virtual machines in the stopped state, and a green icon for virtual machines in the running state.
Cloudockit lets you choose the information you want to display: you can group elements and select the layers you would like to show. For example, if you find the architecture diagrams are too challenging to read because of the NSG icons, you can hide the layer and improve your workflow.
You probably do not want to manually start a diagram generation every single time you change something in your Azure environment.
That is where Cloudockit’s built-in Scheduling feature comes in handy! Simply create a new Automation Profile. Choose when you want to schedule the generation of your architecture diagrams, and you are all set!
Cloudockit allows you to choose a tag to represent your business Application. It will automatically create Visio Azure diagrams, using a Tab for each Azure Application, without the need for a script.
Cloudockit also lets you extract the Business Application based on Regex, the resource names, or resource group names.
A diagram is an excellent way to visualize your Azure components. However, you can also greatly benefit from solid technical reports to better understand and monitor your cloud infrastructure—especially if they include diagrams.
As you can see, technical documentation no longer has to be a tedious, rigid and time-consuming manual process. Let your staff focus on what provides the most value.
Here’s a sample of a technical report containing cloud architecture diagrams: