Azure Search Nav

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: Azure account and interactive sign in, disclosed up front: using this skill requires an Azure account with access to the target subscription, PowerShell with the Az.Accounts module (Install-Module Az.Accounts -Scope CurrentUser if it is missing), and an interactive Microsoft sign in through Connect-AzAccount (or device code authentication with -UseDeviceAuthentication in headless environments). At use time the script acquires an access token for https://management.azure.com/, reads the tenant GUID out of that token, and sends your ARM resource id and your search query, with the token as a Bearer header and the tenant GUID as the App-Tenant-Id header, in a POST to the pinned Microsoft search endpoint https://PCNX-AI-etc5bra3fscchrew.b02.azurefd.net/aks-search-direct-mid (an Azure Front Door host). That send is the service working as designed: the resource id and query go to Microsoft to find the portal blade. Nothing else is sent, no token is written to disk by the script, and nothing is sent during installation itself. Install "Azure Search Nav" for me. Builds an Azure portal deep link to a specific blade or menu item for supported resources (Microsoft.ContainerService, Microsoft.Kubernetes and Microsoft.Compute). You give a resource link (a portal URL or a bare ARM resource id) and a plain language search query describing the operation; the bundled PowerShell script signs you in interactively to Azure, calls the aks-search-direct-mid semantic search API with your query and resource id, extracts the returned menu ids, and prints portal deep links rooted at https://portal.azure.com. It ships SKILL.md, the script references/Invoke-PortalSearchNav.ps1, a README with the full parameter and API details, and references/resource-types.json, the enabled resource type map. Repository: https://github.com/microsoft/azure-skills (the skill is the whole .github/plugins/aks-skills/skills/azure-search-nav/ folder at the pinned commit: SKILL.md, references/Invoke-PortalSearchNav.ps1, references/README.md, references/resource-types.json) Pinned version: install the code at commit cf79ce8778ad063eeac19dbe8bf982d71b466ce0 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/microsoft/azure-skills into a temporary folder, check out commit cf79ce8778ad063eeac19dbe8bf982d71b466ce0, and copy the .github/plugins/aks-skills/skills/azure-search-nav/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-18: [FINGERPRINTS] - SKILL.md: SHA-256 7e869e37173d7608320554e85a444aa337c3e66cc3b7145cd33caae67b5c0abd - references/Invoke-PortalSearchNav.ps1: SHA-256 cb4ebf21ba3ecce06ba03b35694c315069a97b5806fefe725d09a1aebabb6287 - references/README.md: SHA-256 57659c285dda597bcca87d68d1a28053db9d7e79c2bb4a3bc03794567f3249b7 - references/resource-types.json: SHA-256 68d8a9666206174d75e56a02991b2c2f462238b9398a782614bbf48486ba09f3 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full (and every other file in the folder) and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 4 files: SKILL.md, references/Invoke-PortalSearchNav.ps1 (the only executable code), references/README.md and references/resource-types.json. Manual review read the PowerShell script in full. - Nothing is sent anywhere during installation itself; the only download is the skill folder from GitHub at the pinned commit. - At use time the script signs in with Connect-AzAccount, gets a token for https://management.azure.com/ with Get-AzAccessToken, derives the tenant GUID from the token claims, and POSTs your resource id and search query to the pinned endpoint https://PCNX-AI-etc5bra3fscchrew.b02.azurefd.net/aks-search-direct-mid with Bearer and App-Tenant-Id headers, exactly as disclosed in the prerequisites. The endpoint and token audience are pinned in the script and are not parameters. - The script never writes the token to disk and builds every output link against https://portal.azure.com. A 401 means an invalid token or the wrong tenant, per SKILL.md. 3. When I say "yes, install", install it as a skill: copy the whole folder into the agent's skills directory, in a folder named "azure-search-nav", keeping every file (SKILL.md, references/Invoke-PortalSearchNav.ps1, references/README.md, references/resource-types.json). 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (for example: sign in or create an account, provide any API key, or install any local tool named in the prerequisites; using the skill is a separate step that only starts when I ask for it, and every paid or authenticated use disclosed above happens only then). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.