azure-infra-expert

Provides read-only Azure infrastructure guidance covering Entra ID, Key Vault, SignalR, Storage, private networking, and Log Analytics.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/psmfd/pi-config --skill azure-infra-expert-psmfd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure-infra-expert
Source: https://github.com/psmfd/pi-config/tree/main/agent/skills/azure-infra-expert
Command: npx skills add https://github.com/psmfd/pi-config --skill azure-infra-expert-psmfd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Designing Azure infrastructure correctly requires navigating scattered Microsoft documentation on identity, networking, and monitoring, and mistakes like misconfigured private DNS zones or RBAC propagation gaps cause hard-to-diagnose outages. This Skill gives an agent a curated, source-ranked reference for Azure hosted services so recommendations are grounded in first-party Microsoft guidance. ## Core Features & Use Cases - Service reference library: Covers Microsoft Entra ID, Key Vault, Managed SignalR, Storage Accounts, Private Endpoints, ExpressRoute, and Log Analytics via on-demand reference files. - Source authority hierarchy: Prioritizes Microsoft Learn, CLI/SDK docs, and Architecture Center over community sources, with a defined process for documenting conflicts between first-party sources. - Pitfall detection: Flags immutable settings (ADLS Gen2 hierarchical namespace, Key Vault purge protection), retired components (classic App Insights, MMA agent), and common DNS/RBAC misconfigurations. - Use Case: When planning a hub-and-spoke network with private endpoints for Key Vault and Storage, the Skill produces a recommendation with the correct privatelink DNS zones, RBAC role assignments, and Bicep/Terraform/az CLI snippets. ## Quick Start Ask the agent to recommend an Azure architecture for securing a Storage account with private endpoints and managed identity access, including DNS and RBAC requirements.

Frequently Asked Questions about azure-infra-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure private endpoints for Azure Key Vault?▼

Key Vault private endpoints require disabling public network access, creating the endpoint in your VNet, and linking the privatelink.vaultcore.azure.net private DNS zone so clients resolve the vault FQDN to the private IP. The trusted services bypass must be explicitly enabled for supported first-party services.

What is the difference between Key Vault RBAC and access policies?▼

Azure RBAC uses built-in roles like Key Vault Secrets User, while access policies grant per-principal operation lists. Enabling RBAC immediately disables all access policies, so role assignments must exist before switching modes.

Why does my private endpoint work from the hub VNet but not spokes?▼

This is almost always a private DNS zone linking gap. The privatelink zone must be linked to every VNet that resolves the name, or spokes must forward DNS through a hub Private DNS Resolver.

Can ADLS Gen2 hierarchical namespace be disabled after enabling it?▼

No, hierarchical namespace is a one-way setting on a StorageV2 account. Once enabled at creation it cannot be disabled, and the account must be recreated to reverse the choice.

Does this Skill modify Azure resources or files?▼

No, it is strictly read-only. It never uses write or edit tools and returns all ARM, Bicep, Terraform, or az CLI snippets inline for the caller to implement.