azure-bicep-patterns

Generate Azure Bicep patterns for hub-spoke networking and private endpoints.

Updated Mar 9, 2026

Search Tags:#azure #networking #patterns #infrastructure #iac #bicep

Ready to run

npx skills add https://github.com/pazdedav/my-infraops-project --skill azure-bicep-patterns

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: azure-bicep-patterns
Source: https://github.com/pazdedav/my-infraops-project/tree/main/.github/skills/azure-bicep-patterns
Command: npx skills add https://github.com/pazdedav/my-infraops-project --skill azure-bicep-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides pre-built, reusable Azure Bicep code patterns to accelerate the development of robust and standardized Azure infrastructure deployments, reducing boilerplate and ensuring best practices.

Core Features & Use Cases

Networking: Implement secure and scalable Hub-Spoke network topologies.
Connectivity: Easily integrate PaaS services using Private Endpoints and DNS.
Standardization: Enforce consistent diagnostic settings, module composition, and identity management.
Use Case: When designing a new Azure environment, use this Skill to quickly scaffold a Hub-Spoke network and then add Private Endpoints for critical PaaS services like Azure SQL Database and Azure Key Vault, ensuring secure and private communication.

Quick Start

Use the azure-bicep-patterns skill to generate Bicep code for a hub-spoke network.

Frequently Asked Questions about azure-bicep-patterns

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

FAQPage Schema

How do I deploy a hub-spoke network topology in Azure using Bicep?▼

To deploy a hub-spoke network topology in Azure Bicep, use pre-built modular patterns that define the hub virtual network, spoke peering, and routing. This approach ensures secure, scalable infrastructure as code without manual configuration.

How do I configure diagnostic settings for Azure resources using Bicep?▼

Configuring diagnostic settings in Bicep involves applying standardized templates that define logging and metrics targets. These reusable patterns enforce consistent observability across Azure resources without writing repetitive boilerplate code.

Do I need Azure CLI to deploy Bicep infrastructure patterns?▼

Yes, deploying Bicep infrastructure patterns requires Azure CLI with the Bicep extension installed. This setup compiles Bicep templates into standard ARM JSON for deployment and manages authentication to your Azure environment.

What is the best way to standardize Azure infrastructure as code across multiple projects?▼

The best way to standardize Azure infrastructure as code is using modular Bicep patterns for networking, identity, and diagnostics. This enforces best practices and reduces boilerplate across multiple project deployments.

When should I not use modular Bicep patterns for Azure deployments?▼

Avoid modular Bicep patterns for highly customized, one-off Azure deployments where standardized networking or diagnostic configurations do not apply. Bespoke infrastructure with unique requirements may require writing custom Bicep code instead.