azure-infra-bicep

Provision Azure infrastructure with Bicep templates for a dev environment.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/infinith4/dev-flutter-realestate --skill azure-infra-bicep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-infra-bicep
Source: https://github.com/infinith4/dev-flutter-realestate/tree/main/.codex/skills/azure-infra-bicep
Command: npx skills add https://github.com/infinith4/dev-flutter-realestate --skill azure-infra-bicep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provisioning Azure infrastructure manually is time-consuming, error-prone, and repetitive; this Skill automates the creation or update of infra using Bicep templates for the project, ensuring consistent environments.

Core Features & Use Cases

  • Generate infra/main.bicep and infra/params/dev.bicepparam to standardize deployments.
  • Create a Cosmos DB account (SQL API) with a database and multiple containers.
  • Provision a Log Analytics workspace, Container Apps environment, and a user-assigned Managed Identity.
  • Configure RBAC: assign Cosmos DB Built-in Data Contributor to the managed identity.
  • Keep the Bicep templates minimal and deployable at the resource group scope.
  • Use when asked to provision Azure infrastructure or to write Bicep templates for infra.

Quick Start

Create infra/main.bicep and infra/params/dev.bicepparam, then deploy the resources to the japaneast dev environment.

Frequently Asked Questions about azure-infra-bicep

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

FAQPage Schema
How do I automate Azure infrastructure provisioning for a dev environment using Bicep?

Automate Azure infrastructure provisioning by generating standardized Bicep templates for your dev environment. This creates a main.bicep and dev.bicepparam file to deploy Cosmos DB, Managed Identity, and Container Apps consistently.

Can I use Bicep to deploy Azure Container Apps and Cosmos DB together?

Yes, Bicep can deploy Azure Container Apps and Cosmos DB together in a single template. It provisions a Cosmos DB SQL API account, containers, a Container Apps environment, and the necessary RBAC role assignments.

How do I assign RBAC roles to a Managed Identity in Bicep?

Assign RBAC roles to a Managed Identity in Bicep by provisioning a user-assigned identity and applying role assignments at the resource group scope, such as granting the Cosmos DB Built-in Data Contributor role.

Does this Bicep template support deploying Azure resources to the japaneast region?

Yes, this Bicep template supports deploying Azure resources to the japaneast region. It targets the dev environment with a focus on the free tier and resource group scoping for lean, deployable infrastructure.

What is the best way to structure Bicep parameters for a dev environment deployment?

Structure Bicep parameters for a dev environment by separating your configuration into a dedicated params file. This approach standardizes deployments by keeping the main Bicep template minimal and parameterized.

Why do I need a Log Analytics workspace when setting up Azure Container Apps with Bicep?

A Log Analytics workspace is required when setting up Azure Container Apps with Bicep because it serves as the underlying monitoring and logging environment for the Container Apps infrastructure.