Validated fixes

Each finding lands with evidence and an approve or reject decision. Where the written scope covers it, an architect prepares each approved change.

Your team or your MSP reviews and merges the change through your own pipeline. Nothing writes to your 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, with a document glyph and tagged evidence attached; step 3, an architect plans the fix, tagged done by a person; and step 5, the saving is verified, 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.

From finding to decision

Steps 1 and 2 of figure 1 happen in the app. People at Infralign do steps 3 and 5, where the written scope covers them.

Step	Actor	Observable outcome
1. Finding lands	Infralign	The finding carries impact, evidence, owner, effort, risk, and next action.
2. Approve or reject	Your team	The app records the decision.
3. Plan the fix	Senior Azure architect	The plan addresses your architecture and policy constraints.
4. Review and merge	Your team	The approved change passes through your pipeline.
5. Verify savings	Infralign and the architect	Billing data shows the realised change against the baseline.

See reading your Decision Pack for the six decision fields.

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

A finding from NovaPulse, an illustrative demo estate.

Approve or reject each finding in the app’s Recommendations workflow. Every finding there carries an estimated saving, a confidence level, a risk level and a decision status. The tabs separate what is still pending from what your team has already approved or rejected.

On the NovaPulse demo estate the page opens on a banner of 263 pending recommendations, worth €29.8K a month and €357.0K a year, above a sortable table with a column each for title, resource, detection type, estimated saving, confidence, risk and status.

Read that €29.8K as candidates, not savings: it is Azure Advisor’s raw list at retail rates. An audit of the same estate from the cost record alone, with no tenant access, sized it at €226 a month. Expert review is what moves a line from the first number to the second.

Done when the finding shows the selected decision.

How approved changes are delivered

Where the written scope covers it, a senior Azure architect designs each approved change plan. The plan can include infrastructure as code.

The architect validates the plan against your policy and architecture constraints. Your team then reviews and merges it through your pipeline.

The scope and the fee are quoted in writing first. See price and terms. Infralign-generated pull requests are roadmap, not built, as figure 1 shows.

Where Teams fits

If you asked Infralign to wire up a Teams channel in your own Microsoft 365 tenant, it receives the monthly summary and cost alerts. Nothing is posted unless you ask.

Teams carries operational notifications only. Make approve and reject decisions in the app.

The cadence

Infralign verifies savings against the billing data used by your dashboards.

Done when the realised cost change reconciles with the agreed baseline.

Your team’s merge is the last of three gates. The safety model covers the two that run before a change plan ever reaches them.