Reference
FAQ
Straight answers to the questions teams ask before connecting Azure.
Getting started
Section titled “Getting started”Do we need clean Azure tags before we start?
Section titled “Do we need clean Azure tags before we start?”No. Billing data and resource metadata are enough to begin, so dashboards and the audit work from day one on estates with poor tags. Ownership and allocation are attributed progressively — see data sources.
Who is Infralign best suited to?
Section titled “Who is Infralign best suited to?”Azure-heavy SMEs with roughly €100K+ of annual spend, a lean platform team, and no dedicated FinOps function — enough spend for optimisation to matter, and not enough headcount to staff it as a discipline. The free offer sets out what you get.
What does the free tier cost?
Section titled “What does the free tier cost?”Nothing. Dashboards, reports, the chatbot, and the audit — working session and findings report included — are free and stay free. A paid engagement starts only if you choose to proceed to fixes, priced per estate after the audit. See the free offer.
What is the FOCUS lane?
Section titled “What is the FOCUS lane?”An optional second cost lane for subscriptions where the daily Cost Details export becomes too slow to complete overnight, built from native FOCUS 1.2 exports on a monthly cadence. It trails the daily Cost API lane on freshness and adds one storage grant, so reach for it only when scale makes it worthwhile. Setup is in FOCUS exports and storage setup.
How it works
Section titled “How it works”Does this replace Azure Cost Management?
Section titled “Does this replace Azure Cost Management?”No — it builds on it. The Azure Cost Details API is the primary data source; Infralign adds prioritisation with € impact, utilisation evidence, ownership attribution, and an approve/reject path from finding to delivered fix. Every source is listed in data sources.
Will Infralign make changes automatically?
Section titled “Will Infralign make changes automatically?”Never. Discovery is read-only, and no change touches production without your team’s approval and merge. Automating this so approved fixes ship as merge-ready pull requests is on the roadmap — the full model is in safety model.
How is our data handled?
Section titled “How is our data handled?”Access is read-only, scoped per subscription, and revocable at any time. The platform reads billing data and resource metadata, never data inside your resources. Roles and scopes are in permissions; hosting, isolation, and retention are in security and data handling.
Results
Section titled “Results”What results has this method produced?
Section titled “What results has this method produced?”The method behind the platform saved €750K per year, recurring, at an Irish enterprise, including a 62% cost reduction across the SQL estate, with zero production outages from approved refactors. Your numbers depend on your estate, which is what the free audit establishes. See what the audit covers.
How quickly should we expect savings?
Section titled “How quickly should we expect savings?”Dashboards populate after the first nightly run, within a day of connecting, and the audit findings land in week one. In an engagement, the first change plans are typically reviewed in week two, and savings verified in weeks three to four. How a saving becomes verified is in savings measurement methodology.
Next: Get your free audit — bring us your Azure bill and leave with a number. Or start at connect Azure.