Skip to content
Infralign Infralign Infralign docs

The agent

Validated fixes

How approved audit findings become verified savings — evidence-backed recommendations, an approve/reject workflow, and expert-led change delivery.

Click any image to enlarge.

Each finding lands in the app with its evidence attached and an approve or reject decision in your hands. Approved findings are delivered through an expert-led engagement: a senior Azure architect prepares the change plan, and your team reviews and merges it through your own pipeline. Nothing writes to your production estate automatically.

From finding to verified saving, with a key noting that dashed means roadmap, not built. A week axis runs week one, week two, weeks 3 to 4 across two bands. The cyan Infralign band, marked read-only, holds step 1, the finding lands, tagged evidence attached; step 3, an architect plans the fix, carrying a person icon and tagged done by a person; and step 5, the saving is verified, also carrying a person icon and tagged done by a person. The amber band below — labelled your team, your pipeline, and marked every write to your estate happens here — holds step 2, you approve or reject, tagged in the app; step 4, you review and merge, tagged your pipeline; and a dashed slate card, automated pull requests, tagged roadmap, not built. Arrows run from the Infralign band down into your band in week one and in week two. From finding to verified saving, with a key noting that dashed means roadmap, not built. A week axis runs week one, week two, weeks 3 to 4 across two bands. The cyan Infralign band, marked read-only, holds step 1, the finding lands, tagged evidence attached; step 3, an architect plans the fix, carrying a person icon and tagged done by a person; and step 5, the saving is verified, also carrying a person icon and tagged done by a person. The amber band below — labelled your team, your pipeline, and marked every write to your estate happens here — holds step 2, you approve or reject, tagged in the app; step 4, you review and merge, tagged your pipeline; and a dashed slate card, automated pull requests, tagged roadmap, not built. Arrows run from the Infralign band down into your band in week one and in week two.
Figure 1 — Every write to your estate happens in your own pipeline; the two steps marked done by a person are delivered by an architect, not by the platform.

From finding to decision

Section titled “From finding to decision”

Steps 1 and 2 of figure 1 happen in the app. Steps 3 to 5 are the engagement.

Every finding surfaced in the audit arrives with the six fields needed to judge it — € impact, evidence, owner, effort, risk, and next action. Reading your audit report sets out what each one carries.

A finding as it lands in the app, with severity, confidence, effort and basis chips above the estimated monthly saving.

From the NovaPulse demo estate — the format of a finding, not a customer result.

You approve or reject each finding in the app’s Recommendations workflow. Findings are written to be reviewable in minutes, so real review stays cheap.

How approved changes are delivered

Section titled “How approved changes are delivered”

Today, approved changes ship through the expert-led engagement — the method described in the FAQ’s results answer: a senior Azure architect designs the change plan, including any infrastructure-as-code, and hand-validates it against your policy and architecture constraints before your team reviews and merges it through your own pipeline. Merge-ready pull requests raised by the platform itself are roadmap, not built — the dashed panel in figure 1 says so.

Where Teams fits

Section titled “Where Teams fits”

If you’ve connected Microsoft Teams, a pipeline summary card lands in your channel after each nightly run, plus failure-alert cards if a source didn’t land. Teams carries operational notifications only — approve and reject decisions happen in the app.

The cadence

Section titled “The cadence”

Savings are verified against the same billing data your dashboards read, so claimed and actual savings reconcile in one place.

Next: Safety model — the three gates between the platform and your production estate.