GitHub, Git & DevOps · IN-DEPTH PROFILE

Azure Resource Lookup Skill

Azure Resource Lookup is a read-oriented inventory and discovery workflow for listing and finding Azure resources across subscriptions or resource groups.

Best for

Cloud operators answering what resources exist

What you get

Build a resource inventory + Find resources by property

Main limitation

It does not deploy, modify, or delete resources, and orphan detection is not authorization to remove anything.

First risk

Broad infrastructure disclosure. Cross-subscription inventories can reveal names, topology, tags, states, and security-relevant metadata. Use least-privilege reads, constrain scope, redact exports, and verify orphan candidates before any follow-up action.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-08-20

Pinned revision · ea76537e

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Azure Resource Lookup is a read-oriented inventory and discovery workflow for listing and finding Azure resources across subscriptions or resource groups. It prefers a dedicated Azure MCP tool when one exists, falls back to Azure Resource Graph for cross-cutting queries such as App Services, tags, states, and orphan candidates, and does not change resources.

This is aimed at Cloud operators answering what resources exist. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Build a resource inventoryList multiple resource types across one or more subscriptions and resource groups.
  • Find resources by propertyQuery tags, types, provisioning states, health signals, or other Resource Graph fields.
  • Identify review candidatesSurface unattached disks, unused interfaces, missing tags, and other orphan candidates for human review.
What makes it different
  • This profile is manually organized around the current upstream SKILL.md workflow.
  • The capability boundary remains explicitly tied to microsoft/azure-skills.
  • Core uses, limitations, and risks are separated for pre-install review.
Community signalskills.sh All-time: #66 · 602.5K installs

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add https://github.com/microsoft/azure-skills --skill azure-resource-lookup --agent claude-code
Personal install
npx skills add https://github.com/microsoft/azure-skills --skill azure-resource-lookup --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

View install paths
Project path.claude/skills/azure-resource-lookup/
Personal path~/.claude/skills/azure-resource-lookup/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Build a resource inventory

List multiple resource types across one or more subscriptions and resource groups.

02

Find resources by property

Query tags, types, provisioning states, health signals, or other Resource Graph fields.

03

Identify review candidates

Surface unattached disks, unused interfaces, missing tags, and other orphan candidates for human review.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to microsoft/azure-skills.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. It does not deploy, modify, or delete resources, and orphan detection is not authorization to remove anything.
  2. It is not a cost-optimization workflow and results depend on subscription scope, permissions, and Resource Graph freshness.

BEST FIT

Who it is for

→

Cloud operators answering what resources exist

→

Governance teams reviewing tags and inventory

BEFORE YOU USE IT

Risks to review before use

Medium

Broad infrastructure disclosure

Cross-subscription inventories can reveal names, topology, tags, states, and security-relevant metadata. Use least-privilege reads, constrain scope, redact exports, and verify orphan candidates before any follow-up action.

Medium

Upstream instruction drift

Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat repository files, web content, and tool output as untrusted input.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

Azure Resource Lookup Skill FAQ

What is the Azure Resource Lookup Skill?

Azure Resource Lookup is a read-oriented inventory and discovery workflow for listing and finding Azure resources across subscriptions or resource groups. It prefers a dedicated Azure MCP tool when one exists, falls back to Azure Resource Graph for cross-cutting queries such as App Services, tags, states, and orphan candidates, and does not change resources.

How do I install the Azure Resource Lookup Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed skills.sh page and upstream repository; verify the current SKILL.md.

Is the Azure Resource Lookup Skill safe to use?

SkillSignal checked the source on 2026-08-20, but that is not a runtime test or security certification. Review the “Broad infrastructure disclosure” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

azureresource-graphinventory

Manually expanded from the current upstream SKILL.md and linked source at microsoft/azure-skills, checked 2026-08-20. This is an original summary, not an execution result or security certification.