Cost profile
Platform footprint (fixed, small)
Section titled “Platform footprint (fixed, small)”| Resource | Plan | Typical monthly |
|---|---|---|
| Function App | Linux consumption | ≈ $0 at pilot volumes (per-execution) |
| Storage account | Standard LRS tables | < $1 |
| App Insights / Log Analytics | Pay-as-you-go | Single-digit $ at pilot volumes |
Per published app
Section titled “Per published app”| Resource | Plan | Monthly |
|---|---|---|
| Azure Static Web App | Standard (required for custom Entra auth) | ≈ $9 |
The dominant cost is simply apps kept alive. Lifecycle policy (auto-reap abandoned apps) is on the roadmap; until then, an occasional sweep of sprig-managed tagged resources per builder keeps the estate tidy.
Data-side costs
Section titled “Data-side costs”Viewer queries hit your Microsoft Fabric capacity like any other workload. Two recommendations:
- Back builder workspaces with an appropriately sized capacity, and enable workspace-level surge protection so a runaway query loop cannot starve production.
- Watch the Fabric capacity metrics app during the pilot’s first weeks to size expectations.
Guardrails
Section titled “Guardrails”The installer creates a subscription budget with alert thresholds. Note Azure budgets notify — they do not stop spend; enforcement automation is a roadmap item, stated honestly.