Metabase On Azure is a skill that generates a structured, modular Infrastructure-as-Code project using Azure Bicep, targeting deployments of Metabase on Azure Container Apps backed by a PostgreSQL Flexible Server. Rather than producing a single monolithic file, the skill outputs a directory organized into discrete modules covering PostgreSQL, Container Apps, and optionally a Container Registry, making the result suitable for professional deployment pipelines.

The skill handles several configuration details that are easy to get wrong manually. It configures required PostgreSQL extensions such as CITEXT, sets SSL transport modes correctly, and populates essential Metabase environment variables including MB_DB_TYPE. Secrets are separated from the main template through a generated .bicepparam file that uses secure placeholders, and a parameter mapping worksheet is included to guide the operator through filling in values before deployment.

Once the project directory is generated, the skill provides built-in commands for Bicep linting, what-if analysis to preview changes, and final resource creation against an Azure subscription. This gives a deployment pipeline a clear sequence of steps without requiring the developer to compose those commands from scratch.

This skill is relevant when the target environment is Azure and the desired analytics tool is Metabase. It is not a generic Bicep generator, nor does it cover other analytics platforms or other cloud providers. No environment variables are required to configure the skill itself at runtime.

Use cases

Generate a ready-to-deploy Bicep project for hosting Metabase on Azure Container Apps

Scaffold PostgreSQL Flexible Server configuration with CITEXT extension and SSL modes pre-set

Produce a .bicepparam file with secure placeholders to keep secrets out of main templates

Run what-if analysis against an Azure subscription before committing infrastructure changes

Set up a modular IaC layout separating PostgreSQL, Container Apps, and Container Registry concerns

Lint generated Bicep templates as part of a CI/CD pipeline

When to use it

Deploying Metabase to Azure and needing a structured, modular Bicep project as a starting point

When secret separation and parameter management discipline are required from the outset

When the team wants pre-configured Metabase environment variables and PostgreSQL extensions without manual research

When deployment needs to follow a lint → what-if → deploy sequence with commands already provided

When not to use it

Deploying Metabase to AWS, GCP, or any cloud provider other than Azure

Deploying analytics tools other than Metabase

When the infrastructure target is not Azure Container Apps (e.g., AKS, VMs, or on-premises)

When a Terraform or ARM-based workflow is required instead of Bicep

When a fully managed, no-IaC deployment path is preferred