azure-resource-visualizer

Generate Mermaid architecture diagrams from Azure resource group inventories.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/p-potvin/vaultwares-pipelines --skill azure-resource-visualizer-p-potvin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-resource-visualizer
Source: https://github.com/p-potvin/vaultwares-pipelines/tree/main/.github/agents/agents/azure-resource-visualizer
Command: npx skills add https://github.com/p-potvin/vaultwares-pipelines --skill azure-resource-visualizer-p-potvin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps cloud architects and engineers quickly understand and document how Azure resources within a resource group relate to one another by producing accurate, readable architecture diagrams and accompanying documentation instead of manually tracing dependencies and configurations.

Core Features & Use Cases

  • Resource discovery: Enumerates resource groups and inventories all resources in a selected group using Azure Resource Graph or Azure CLI.
  • Relationship mapping: Analyzes network, identity, configuration, and data-flow relationships and identifies dependencies across resources and groups.
  • Diagram generation & documentation: Produces detailed Mermaid diagrams grouped by layer (Network, Compute, Data, Security, Monitoring) and creates a markdown architecture file with inventory, diagram, and relationship explanations.
  • Use Case: A cloud architect can convert a complex resource group into an annotated Mermaid diagram and markdown report to onboard teams, perform audits, or plan migrations.

Quick Start

Ask the skill to analyze my resource group "rg-production-westus" and generate a [rg-production-westus]-architecture.md file with a full Mermaid diagram and resource inventory.

Frequently Asked Questions about azure-resource-visualizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Mermaid architecture diagrams from Azure resource groups?

To generate Mermaid architecture diagrams from Azure resource groups, you enumerate resources using Azure Resource Graph or CLI, extract network and identity mappings, and output valid Mermaid markdown with grouped subgraphs and labeled connections. This produces detailed diagrams of resource topology.

Can I map network connections and identity relationships across Azure subscriptions?

You can map network connections and identity relationships across Azure subscriptions by extracting resource metadata and configuration mappings. The Skill analyzes network, identity, and data-flow relationships to identify dependencies within or across your cloud networking environments.

What is the best way to document Azure resource topology for cloud networking audits?

The best way to document Azure resource topology for audits is generating a markdown architecture file containing a full Mermaid diagram and resource inventory. This annotates resources grouped by layer—Network, Compute, Data, Security, and Monitoring—with relationship explanations.

Does this approach require Azure CLI to visualize resource group topology?

Visualizing resource group topology requires discovery via Azure Resource Graph or Azure CLI. You need to run resource discovery to inventory all resources in a selected group before extracting metadata and generating the architecture visualization.

How to onboard teams to complex Azure resource configurations using diagrams?

To onboard teams to complex Azure configurations using diagrams, convert the resource group into an annotated Mermaid diagram and markdown report. This maps resource topology, network connections, and data flows, providing clear architecture documentation for team understanding.

Are there limitations when mapping data flows across multiple resource groups?

When mapping data flows across multiple resource groups, the Skill analyzes dependencies across resources and groups, but relies entirely on Azure Resource Graph or CLI discovery data. Complex or unconfigured cross-group data flows may not be captured if not explicitly defined in resource metadata.