Take a stack that already works under `flisk up` to Azure with that host's own tooling - Container Apps, AKS, App Service or Functions. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Azure. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
Installs into .claude/skills of the current project.
Are you the author of Flisk Deploy Azure?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/flisk-sh-flisk-deploy-azure)
---
name: flisk-deploy-azure
description: Take a stack that already works under `flisk up` to Azure with that host's own tooling - Container Apps, AKS, App Service or Functions. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Azure. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
license: MIT
compatibility: Requires a working local Flisk stack first. Azure CLI recommended.
metadata:
author: flisk-sh
version: "1.0"
---
# Deploy to Azure
Flisk is local-only. This skill covers taking a validated local stack to Azure.
## Workflow
1. Confirm the stack works locally: `flisk doctor && flisk up <stack>`.
2. Extract the contract from service.json.
3. Preferred targets: Azure Container Apps or AKS.
4. Push the production image to Azure Container Registry.
5. Deploy with Container Apps YAML or Bicep/Terraform, wiring secrets via Key Vault.
6. Verify health.
## Guardrails
- Keep local and production configs separate.
- Never commit local generated files or secrets.
