界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
部署与运维 · SKILL.md

azure-search-nav

azure-search-nav

【部署与运维】Builds an Azure portal deep link to a specific blade/menu item for supported Microsoft.ContainerService, Microsoft.Kubernetes, and Microsoft.Compute resources using the aks-search-direct-mid semantic search API. WHEN: 'find where in the Azure portal to do something', 'search the portal for an operation', 'construct a portal link from a search query a…

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: azure-search-nav description: "Builds an Azure portal deep link to a specific blade/menu item for supported Microsoft.ContainerService, Microsoft.Kubernetes, and Microsoft.Compute resources using the aks-search-direct-mid semantic search API. WHEN: 'find where in the Azure portal to do something', 'search the portal for an operation', 'construct a portal link from a search query and a resource'." license: MIT metadata: author: Microsoft version: "1.0.1"

Azure Portal Search Link Builder

Quick Reference

ItemValue
Scriptreferences/Invoke-PortalSearchNav.ps1
Resource mapreferences/resource-types.json
PrerequisiteAz.Accounts PowerShell module
AuthInteractive 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

  1. Collect resource link (portal URL or bare ARM resource ID) and search query from the user.
  2. Run references/Invoke-PortalSearchNav.ps1 -ResourceUrl '<link>' -Query '<query>'.
  3. 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

ErrorCauseFix
Resource type not enabledarmProvider not in references/resource-types.jsonConfirm the type is in the enabled-provider list
401 from APIInvalid token, or wrong tenant selectedRe-run and select the account with access to the target subscription's tenant
Empty resultsNo matching navigation item for the queryTry a different search term
Az.Accounts not foundModule not installedInstall-Module Az.Accounts -Scope CurrentUser
Browser sign-in fails (no window handle)Headless/CLI environmentRe-run with -UseDeviceAuthentication
我的收藏