Skills azure-resource-visualizer

📦

azure-resource-visualizer

Name: azure-resource-visualizer
Author: microsoft

v0.0.0-placeholder Content revision r2 Safe 🌐 Network access⚙️ External commands

Visualize Azure Resource Group Architectures

Azure resource relationships can be difficult to review across complex groups. This skill inventories resources and creates structured Mermaid architecture documentation.

Supports: Claude Codex Code(CC)

🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "azure-resource-visualizer" from https://skillstore.io/skills/microsoft-azure-resource-visualizer.md and its manifest at https://skillstore.io/api/skills/microsoft-azure-resource-visualizer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/microsoft-azure-resource-visualizer.md Signed manifest GET /api/skills/microsoft-azure-resource-visualizer/manifest Signed lockfile GET /api/skills/microsoft-azure-resource-visualizer/lockfile

Test it

Using "azure-resource-visualizer". Diagram resource group rg-commerce-prod.

Expected outcome:

Architecture document for rg-commerce-prod.
Inventory grouped by resource type, region, and SKU.
Layered Mermaid diagram with labeled network, identity, application, and data relationships.
Notes identifying verified dependencies and visibility gaps.

Using "azure-resource-visualizer". Review network and identity paths in rg-payments.

Expected outcome:

A focused architecture document showing subnets, private endpoints, managed identities, RBAC relationships, Key Vault access, and supporting resource details.

Using "azure-resource-visualizer". Inventory application resources across two subscriptions.

Expected outcome:

A Resource Graph inventory with subscription context, separate readable diagrams, confirmed cross-group dependencies, and notes for relationships requiring further verification.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

All 39 static findings are false positives caused by private example addresses, Markdown code formatting, Mermaid syntax, and legitimate read-only Azure discovery guidance. No executable Ruby code, malicious reconnaissance, prompt injection, secret exposure, or unsafe command construction was found.

Files scanned

377

Lines analyzed

Review items

False positives ignored

Risk Factors

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/microsoft-azure-resource-visualizer/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/microsoft-azure-resource-visualizer/security.svg)](https://skillstore.io/skills/microsoft-azure-resource-visualizer?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/microsoft-azure-resource-visualizer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/microsoft-azure-resource-visualizer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/microsoft-azure-resource-visualizer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

microsoft. (2026). azure-resource-visualizer security audit report (audit version 5) [Author version 0.0.0-placeholder]. Skillstore. https://skillstore.io/skills/microsoft-azure-resource-visualizer/audits/5

BibTeX citation

@techreport{microsoft-microsoft-azure-resource-visualizer-2026,
  author = {microsoft},
  title = {azure-resource-visualizer security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/microsoft-azure-resource-visualizer/audits/5},
  note = {Author version 0.0.0-placeholder}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "azure-resource-visualizer security audit report (audit version 5)"
version: "0.0.0-placeholder"
type: report
authors:
  - name: "microsoft"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/microsoft-azure-resource-visualizer/audits/5"
identifiers:
  - type: other
    value: "skillstore:microsoft-azure-resource-visualizer:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Create Architecture Documentation

Generate a current inventory and layered diagram for design reviews, handovers, or system documentation.

Review Deployment Topology

Map deployed services, network boundaries, and dependencies before operational changes or incident analysis.

Inspect Identity and Network Paths

Document managed identities, RBAC relationships, private endpoints, subnets, and Key Vault access paths.

Try These Prompts

Choose a Resource Group

List my available Azure resource groups with locations, then wait for me to select one before creating its architecture diagram.

Document One Resource Group

Analyze [resource-group]. Create a Markdown document with an inventory, verified relationships, a layered Mermaid diagram, and concise architecture notes.

Focus on Security Relationships

Analyze [resource-group] with emphasis on VNets, subnets, private endpoints, managed identities, RBAC, and Key Vault dependencies. Mark unverified relationships clearly.

Map Cross-Group Dependencies

Use Azure Resource Graph across [subscriptions] to inventory [resource-groups]. Create separate layered diagrams and document verified cross-group dependencies and visibility gaps.

Best Practices

Confirm the Azure subscription and resource group scope before discovery.
Use placeholders for keys, secrets, connection strings, and other sensitive values.
Verify each relationship from resource properties before adding it to the diagram.

Avoid

Do not include secret values in diagrams, inventories, or notes.
Do not infer dependencies from naming conventions without supporting Azure configuration.
Do not run commands that modify or delete Azure resources.