Skip to content

Reference

FAQ

Straight answers to the questions teams ask before connecting Azure.

How long does connecting take, and who does it?

Section titled “How long does connecting take, and who does it?”

Your Azure admin does it. Budget about 15 minutes at the keyboard and about 30 minutes elapsed at management group scope, per the onboarding checklist. The setup wizard at app.infralign.ai is about 6 minutes of that, and there is nothing to paste into it beyond your tenant ID.

The rest is the one-time admin consent, two role assignments, and up to ten minutes for Azure to propagate them. Nobody at Infralign types anything for you, and no credential is emailed. See how long this really takes.

When do the dashboards open, and how will we know?

Section titled “When do the dashboards open, and how will we know?”

Your cost data lands on the first nightly run after you connect, between 02:30 and 06:15 UTC. Once that run has landed, Infralign checks it and opens your dashboards within one business day, and [email protected] emails you when they are live. See your first day.

Your own admins, on the People page. A person can sign in as soon as they are added, with their own Microsoft work account. No invite email is sent, so tell them yourself. Admins may add addresses only at domains recorded for your account. See manage who has access.

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.

Azure-heavy SMEs with roughly €100K+ of annual spend, a lean platform team, and no dedicated FinOps function. That is enough spend for optimisation to matter, and not enough headcount to staff it as a discipline. The free offer sets out what you get.

The visibility tier includes dashboards, reports, the chatbot, and one audit at no cost. An engagement starts only after you accept a written scope and quote. See the free offer.

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.

No. It builds on it. The Azure Cost Details API is the primary data source. Infralign prioritises by € impact, attaches utilisation evidence, attributes an owner, and adds 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?”

No. Infralign writes nothing to your estate, and your team reviews and merges every change through its own pipeline. A senior Azure architect prepares change plans today; automated pull-request generation remains on the roadmap. See the safety model.

Read-only, EU-hosted, isolated per customer. Security at Infralign states residency, subprocessors, retention and the GDPR position; isolation and data handling has the mechanics.

Yes. Neither role can create, modify, or delete anything in your estate. Reader exposes control-plane metadata only and has no DataActions, so it cannot read database rows, blob contents, VM disks, or Key Vault secret values. See permissions.

The audit is targeted for week one, which starts once your first nightly run has landed and Infralign has opened your dashboards. In an engagement, the first change plans are typically reviewed in week two, and savings can often be measured in weeks three to four.

Azure data latency, change windows, and billing cycles all stretch those targets. Savings measurement methodology explains when a result becomes verified.


Get your free audit, or start the technical work at connect Azure.