Set up and use Azure Resource Visualizer safely

This guide positions Azure Resource Visualizer as an instructional skill for a compatible assistant. It does not modify Azure resources. Before the first analysis, identify the correct tenant, subscription, and resource group. Also confirm that the selected Copilot or agent environment supports importing skills from a repository.

Workspace and permissions

Choose a protected workspace for the generated Markdown documentation. Use only the Azure and repository permissions required for analysis. Do not store tokens, passwords, or private keys in prompts, diagrams, or files. If network, identity, or application settings contain confidential values, redact them before sharing material with a connected model provider.

Analysis with a defined scope

Ask the assistant to list available resource groups first when no group has been selected. Then choose exactly one group and have its existence validated. The analysis should inventory all resources in that group and show relationships only when properties or reliable configuration support them. Unclear connections belong in the documentation as open questions, not as invented edges in the diagram.

Review the diagram

Next, review grouping across network, compute, data, security, and monitoring. Compare node labels, regions, runtimes, tiers, address spaces, and identity relationships with Azure. Ensure every important connection has an understandable label and confirm that the chosen Mermaid orientation remains readable. For very large groups, splitting the diagram by layer is appropriate.

Documentation and approval

The finished file should contain a summary, a resource inventory, a Mermaid diagram, explanations of important relationships, and open questions. A qualified person must review the output before it is used for operations, audit, or architecture decisions. The skill accelerates preparation, but it does not replace Azure expertise or a security approval.