skills.rest
Lynricsy
LynricsyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

azure

Manages Azure architecture, Bicep deployments, identity, and cloud services.

22|Updated Sep 10, 2026
Search Tags:#deployment#azure#rbac#cloud#infrastructure-as-code#aks#bicep
One-click install
npx skills add https://github.com/Lynricsy/HyperSkills --skill azure-lynricsy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure
Source: https://github.com/Lynricsy/HyperSkills/tree/main/skills/azure
Command: npx skills add https://github.com/Lynricsy/HyperSkills --skill azure-lynricsy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Azure work fails in ways the compiler never catches: templates that build cleanly but fail at deployment, role assignments that grant nothing, quotas discovered only mid-migration, and production incidents with no logs because diagnostics were never enabled. This Skill encodes the verified rules, workflows, and diagnostic ordering that close the gap between "compiles" and "actually works" on Azure. ## Core Features & Use Cases - Bicep authoring and review: linter severity gates via bicepconfig.json, symbolic references, secret handling, naming rules, and pinned Azure Verified Modules with ModuleStatus checks. - Safe deployments: the build/validate/what-if/deploy release gate, what-if change-symbol reading, deployment stacks versus Complete mode, and azd project conventions with federated CI identity. - Identity, hosting, and operations: Entra ID versus Azure RBAC, managed identity and workload identity federation, hosting selection across App Service, Container Apps, Functions and AKS, plus production diagnosis, quotas, cost, and Well-Architected reviews. - Use Case: Before merging a pull request that adds a storage account and a Function App, run the Bicep review workflow to catch an illegal storage name, a secret in an output, and a management-plane role where a data-plane role was needed. ## Quick Start Ask the agent to review infra/main.bicep for deployment-blocking issues and security findings using the azure skill.

Frequently Asked Questions about azure

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

FAQPage Schema
How do I review a Bicep template before deploying to Azure?▼

Check bicepconfig.json first so security linter rules are errors, not warnings, then verify resource names against per-type rules, replace resourceId() strings with symbolic references, and remove secrets from outputs. Finish with az deployment group what-if and read every delete line before deploying.

Why does bicep build succeed but the deployment still fail?▼

bicep build only checks syntax, types, and linter rules; name rules, quota, RBAC, policy, and referenced-resource existence are enforced by ARM at deployment time. Close the gap with az deployment group validate and what-if, not by rereading the template.

What is the difference between management plane and data plane roles in Azure RBAC?▼

Management-plane roles like Storage Account Contributor manage the resource itself but do not grant data access such as reading blobs or Key Vault secrets. Grant a data-plane role like Storage Blob Data Reader, and prefer managed identity over fetching account keys with listKeys.

Does the Consumption Functions plan support virtual network integration?▼

No. The Consumption (Y1) plan cannot do VNet integration at all, so reaching a private endpoint requires migrating to Flex Consumption or Premium. Flex Consumption is Linux-only with 512, 2048, or 4096 MB instances and a shared 250-core regional quota.

How do I find the right Azure quota name for a resource type?▼

There is no 1:1 mapping from an ARM resource type to a quota name, so guessing fails. Install the quota extension, run az quota list on the provider scope, and match on the localizedValue field, then use the name field with az quota show.

When should I choose AKS over Container Apps or App Service?▼

Choose AKS only for a stated reason: the Kubernetes API itself, an existing Helm estate, node-level control, or scale that justifies cluster overhead. Otherwise eliminate on networking constraints first and prefer Container Apps, App Service, or Functions based on traffic shape and operational appetite.

Related Skills

Explore More Software Engineering Skills→
microsoftmicrosoft
2.9k

azure-enterprise-infra-planner

Generate Bicep or Terraform templates for enterprise Azure infrastructure from workload descriptions.

Official
Advanced
allthingslinuxallthingslinux
1

observability-engineer

Design and implement observability across distributed systems with metrics, logs, and traces.

Official
Advanced
physics91physics91

k8s-reviewer

Review Kubernetes manifests and Helm charts for resource configuration, security, and best practices.

Community
Advanced
partme-aipartme-ai
610

terraform

Guide Terraform infrastructure as code with HCL syntax and state management.

Official
Intermediate