azure-defaults

Provide standardized Azure infrastructure defaults for regions, tags, CAF naming, and security baselines.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/pazdedav/my-infraops-project --skill azure-defaults-pazdedav
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-defaults
Source: https://github.com/pazdedav/my-infraops-project/tree/main/.github/skills/azure-defaults
Command: npx skills add https://github.com/pazdedav/my-infraops-project --skill azure-defaults-pazdedav

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a single source of truth for Azure infrastructure configuration, ensuring consistency in regions, tags, naming, security, and module usage across deployments.

Core Features & Use Cases

  • Standardized Defaults: Defines default regions, required tags, naming conventions (CAF), and security baselines.
  • AVM Guidance: Promotes the use of Azure Verified Modules (AVM) for resource deployment.
  • Use Case: When an agent needs to plan or generate Azure resources, it consults this Skill for the correct naming patterns, mandatory tags, and recommended regions to ensure compliance and consistency.

Quick Start

Use the azure-defaults skill to get the default region for all Azure resources.

Frequently Asked Questions about azure-defaults

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

FAQPage Schema
How do I enforce CAF naming conventions for Azure infrastructure deployments?

CAF naming conventions for Azure infrastructure require standardized patterns for resources, tags, and regions. This Skill provides a single source of truth for these defaults, ensuring agents generate compliant configurations during deployment planning.

What are the required tags and default regions when generating Azure resources?

Required tags and default regions for Azure resources are defined within this Skill's standardized baseline. It supplies mandatory tags and recommended regions, acting as a single source of truth for consistent infrastructure planning and deployment.

How do I apply Azure Verified Modules (AVM) for secure resource planning?

Applying Azure Verified Modules (AVM) for secure resource planning requires an AVM-first policy that promotes using verified modules for deployment. This Skill enforces that policy alongside security baselines and naming conventions for consistent Azure infrastructure.

Does this approach provide a security baseline for Azure governance?

Yes, this approach provides a security baseline for Azure governance by enforcing standardized configuration parameters. It integrates security baseline settings with CAF naming and AVM usage policies to maintain consistency and compliance across deployments.

Why do I need standardized defaults for Azure infrastructure?

You need standardized defaults for Azure infrastructure to ensure consistency across regions, tags, naming, and security. Without a single source of truth, deployments risk non-compliance and configuration drift, which this Skill prevents by providing baseline settings.