Generate targeted Diagrams for the appropriate audience
Leverage the tools you know
Support most popular Azure Workload
Once you have linked your environment with the tool, Cloudockit is able to scan all your cloud architecture and summarize it automatically into a complete and editable diagram.
The principle is simple: You login to your Azure Subscription and then Cloudockit is leveraging the Azure native API to retrieve all your resources and all the links between the resources.
No installation required, just easy as plug and play, Cloudockit brings your diagraming game into the next step.
Diagrams are great to have a global overview of all the dependencies in your Azure Subscription, but also to narrow down the vision sometimes.
Let’s say that you want to know the Virtual Network and the Subnet used by a very specific Virtual Machine.
If you are having storages capacity concerns, you also want to find which Storage Account is being used by this Virtual Machine.
That’s where a diagram is useful, as it is quick to read, and it immediately displays all the information you are looking for.
Imagine that you have an Azure Storage Account named “storageToDelete” that was used by a Virtual Machine named “betaServer”.
One day, you have to move the betaServer disk to another Storage Account, named “storagearm”. Quite simple, you moved your VM, now guess what.
Of course, you are about to delete “storageToDelete”, you don’t need this one anymore right?
But wait, looking at the diagram, it appears that “storageToDelete” is currently being used by one of your Function. Hold on a second!
This may sounds obvious, but this diagram make you realize that when a new employee is onboarding, the first weeks will not be really productive because he has to understand and size what’s going on in your environment.
Even if you hire the best Azure Solution Architect in town, if you don’t have a clue of what is your environment is about, he will spend a lot of time trying to reverse-engineer what you currently have.
The organization is not only wasting time there, but good chances are that you’ll be ending up with something partially wrong. That’s another reason why you should use diagrams to visualize your Azure environment, coming along a proper documentation.
At Cloudockit, we are working on building diagrams since 2013, and we have collected hundreds of feedbacks regarding diagrams, so we are learning every day, improving our understanding in the matter.
Nowadays, diagrams need to be built for specific audiences: there is no single diagram that will be perfect for everyone.
And that’s why Cloudockit does not generate a single generic diagram, but instead different types that will be used by specific people with different needs.
To illustrate that, here are the top 5 most popular diagrams, plebiscites by users of our loved tool.
In this diagram, you will be able to see all your Virtual Machines and the dependencies with Networking components (Virtual Network, Network Interface Cards…) and storages (Storage Account, Managed Disks…):
This one is really usefull for developpers that works with App Services to see the dependencies with components like SQL Databases, Storages, Event Hubs, Service Bus, Cosmo DB …
Compared to the two previous diagrams that are organized per type of Workload, this one uses the logical grouping provided by Resource Groups.
So basically, what you do is you generate a tab per resource group.
Cloudockit also generates a global diagram that contains everything in your Azure Subscription. The global diagram gives you an overview of all the resources that you have in your Azure subscription and is a good starting point if you have a messy environment that you want to clean-up for example. Cloudockit automatically generates two types of Global diagram: one with all the details and one with the high level overview. This one is particularly useful in scenario where you want to redesign your Virtual Network configuration for example.
Cloudockit support both Draw.io and Visio. We choose this path as we strongly think that you should not waste time to learn new Diagraming tools as you are probably familiar with one of these two. Existing tools like draw.io and Visio have plenty of built-in features that are leveraged by Cloudockit.
Cloudockit automatically embed data into the Shapes that it generates. You can use this data to see the details of each component and to generate rules in Visio.
A good example of that would be to create a rule where you show a Red icon for Virtual Machines that are in the Stopped state and a Green icon for Virtual Machines that are in the Running state. We are currently working to integrate those kind of rules directly in the product so that you don’t need to do that yourself.
Cloudockit gives you a lot of flexibility regarding the information you want to display: you can group elements together then select if a layer shows or not.
For example, if you find that the Diagrams are too difficult to read because of the NSGs icons, you can hide this layer only and improve your workflow.
You probably don’t want to manually start a diagram generation every single time you have changed something in your Azure environment.
That’s where Cloudockit built-in Scheduling features can help a lot! Simply create a new Automation Profile, choose when you want to schedule the generation of your Visio diagrams, and you are all set!
Cloudockit allows you choose a Tag representing your Business Application (works for other elements also) and it will automatically create Visio Diagrams, using a Tab per Application, no script needed!
Cloudockit also support the ability extract the Business Application based on Regex on the Resources Names or Resource Groups Names.
A diagram is a good way to visualize your Azure components, but it is even better to have Diagrams coming with full technical documentation.
Cloudockit provides both! With you complete and editable diagrams comes a Word document with all the information that gets automatically generated.
See what it looks like:
We are always working to add more features to give you the best Azure Diagrams.
Here are a few things we are currently working on :