azure-search-nav

Name: azure-search-nav
Author: microsoft

github.com/microsoftCloud & DevOps1.6k95 installsUpdated today

About azure-search-nav

A skill that builds Azure Portal navigation links from a resource URL or ARM resource ID and a search query. It uses PowerShell with Az.Accounts authentication to find matching portal blades for supported resource types.

Key features

01Accept portal URLs or ARM resource IDs
02Search Azure Portal navigation items
03Authenticate with browser or device code
04Return portal deep links
05Support configured resource types

Use cases

01Find a blade for a supported Azure resource
02Locate a portal menu for an operation
03Create a deep link from an ARM resource ID

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/microsoft/azure-skills --skill azure-search-nav

After installing, type/azure-search-navin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/

Invoke-PortalSearchNav.ps1

README.md

resource-types.json

Details

From the project README

Azure Portal Search Link Builder

Quick Reference

Item	Value
Script	`references/Invoke-PortalSearchNav.ps1`
Resource map	`references/resource-types.json`
Prerequisite	`Az.Accounts` PowerShell module
Auth	Interactive Microsoft sign-in (`Connect-AzAccount`), or device-code with `-UseDeviceAuthentication`

When to Use This Skill

User asks to find where in the Azure portal to perform an operation on a supported Container Service, Arc-enabled Kubernetes, or Compute resource.
User wants a portal deep link for a specific blade/menu item.
User provides a resource URL or ARM resource ID and a natural-language search query.

Workflow

Collect resource link (portal URL or bare ARM resource ID) and search query from the user.
Run references/Invoke-PortalSearchNav.ps1 -ResourceUrl '<link>' -Query '<query>'.
The script signs in (browser by default; pass -UseDeviceAuthentication in headless/CLI environments), calls the search API, and prints portal deep links always rooted at https://portal.azure.com.

See references/README.md for full parameter reference and API details.

Error Handling

Error	Cause	Fix
Resource type not enabled	`armProvider` not in `references/resource-types.json`	Confirm the type is in the enabled-provider list
401 from API	Invalid token, or wrong tenant selected	Re-run and select the account with access to the target subscription's tenant
Empty results	No matching navigation item for the query	Try a different search term
`Az.Accounts` not found	Module not installed	`Install-Module Az.Accounts -Scope CurrentUser`
Browser sign-in fails (no window handle)	Headless/CLI environment	Re-run with `-UseDeviceAuthentication`

Comments

Markdown supported

Details

Author: microsoft
Repository: microsoft/azure-skills
Category: Cloud & DevOps
Installs: 95
GitHub stars: 1,603

Report

More skills

All skills

lark-apps

open.feishu.cn

732.0k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

azure-prepare

github.com/microsoft

571.7k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

wizard

github.com/mattpocock

571.5k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-ai

github.com/microsoft

571.2k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.