// cairn labs · cost guard + deployment preflight · prototype

ExpenseClaims v1.0.0.5 · UNMANAGED

Generated Sun, 12 Jul 2026 19:20:32 GMT · Assumptions: 25 app users, 5 flow-only users · UK list prices 2026-07-12

connectors

1+HTTP

premium dependencies

cloud flows

preflight findings

£0.00

cheapest compliant / month

Connector licence tiers

Connector	Id	Tier
SharePoint	shared_sharepointonline	standard
SQL Server	shared_sql	premium
Office 365 Outlook	shared_office365	standard
HTTP action (in-flow)	Http	premium feature

Licence scenarios — “cheapest compliant architecture”

Scenario	Est. monthly	Basis	Notes
A — Per-user Premium (everyone licensed)	£442.50	25 app users × £15.40 (Power Apps Premium) + 5 flow-only users × £11.50	Simplest and most flexible; unlimited apps per user.
B — Per-process flows + standard app data	£76.90	1 premium flow(s) × £76.90 per-process; app itself refactored to standard connectors only	Only compliant if the APP uses no premium connectors — premium work moves into per-process flows any user can trigger.
C — Refactor to standard connectors cheapest	£0.00	Replace premium dependencies (see recommendations) — runs on existing M365 seeded licences	£0 additional licences. Viability depends on data volume/relational needs.

Architecture recommendations

SQL Server is the costliest dependency here: for <~5k rows and simple relations, SharePoint lists (standard) may suffice; for relational needs, compare Dataverse (premium but included in scenario A) vs SQL + gateway.

HTTP action is premium: if calling an internal API, an Azure Function behind a custom connector doesn't avoid premium — but reshaping the integration through standard connectors (e.g. SharePoint/Outlook events) might.

Unmanaged solution: fine for dev, do not deploy unmanaged to production (preflight finding P1).

Deployment preflight — 8 finding(s)

Sev	Code	Finding	Fix
high	PF-001	Solution is UNMANAGED — importing unmanaged to production prevents clean upgrades/removal.	Export as managed for production; keep unmanaged for dev only.
medium	PF-002	Connection reference 'SharePoint - Expenses' (SharePoint) has no bound connection — import will prompt or flows will be off.	Pre-create connections in target + bind via deployment settings file.
medium	PF-002	Connection reference 'Finance SQL (prod)' (SQL Server) has no bound connection — import will prompt or flows will be off.	Pre-create connections in target + bind via deployment settings file.
high	PF-003	Environment variable 'Finance API Base URL' has neither default nor current value — dependent components will fail at runtime.	Provide value via deployment settings file at import.
high	PF-005	Flow 'Process expense claim' contains hard-coded URL: https://finance.contoso-internal.com/api/claims	Move to an environment variable.
medium	PF-006	Flow 'Process expense claim' contains hard-coded email: [email protected]	Move to an environment variable or security-group lookup.
low	PF-007	Flow 'Process expense claim' contains 1 hard-coded GUID(s) (first: c7d1f2e3-88aa-4b1c-9f3e-2a6b5d4c3f21) — likely environment-specific IDs.	Replace with environment variables (data source type where applicable).
medium	PF-004	Flow 'Weekly expense digest' state is 'Draft' — it will be OFF after import.	Turn on post-import (pipeline step) or fix state before export.

Flows

Flow	State	Trigger	Connectors	Premium?
Process expense claim	Activated	When_a_claim_is_submitted	shared_sql, shared_office365	yes
Weekly expense digest	Draft	Recurrence_weekly	shared_sharepointonline	no

Cairn Labs · labs.cairnautomation.co.uk · Planning guidance with recorded assumptions — not legal or licensing advice. Prices are UK list (ex-VAT, annual billing) and change; verify against the Microsoft Power Platform Licensing Guide before quoting.