What does IntelliconOps retain for a provisioning job?

The job record connects submitted parameters and effective policy with the requester, approver, blueprint version, workflow checksum, timestamped events, workflow-step results, provider resources and final outcome.

Can an operator see the automation used for an earlier job?

Yes. A request snapshot retains the blueprint version, workflow definition and checksum used by the job so authorised operators can inspect the exact executed source.

Are failed cloud operations recorded?

Yes. Failed jobs retain their timeline, workflow-step status, error context and provider resource records so operators can investigate and decide what to do next.

What evidence is retained for an OpenTofu change?

IntelliconOps records the deployment, provider, module version, configuration fingerprint, plan identity and summary, expiry, approval or rejection, apply run and synchronised managed-resource result. Sensitive plan and state artifacts remain encrypted and are not exposed as raw browser output.

Can an applied OpenTofu change be traced to its approved plan?

Yes. The apply run references its source plan and retains matching plan and configuration identities, showing that the approved saved plan—not a regenerated plan—was used.

Auditable cloud operations

Keep the request, decision, execution and outcome connected.

IntelliconOps connects each operation across AWS, Microsoft Azure and Google Cloud to the intent, reviewed definition, human decision, timestamped execution and resulting managed resources.

Book a demonstration

Job #1042Completed

Requested by: Platform engineer
Approved by: VM group owner
Blueprint: Linux VM v1.1.0
Provider: Microsoft Azure
Outcome: Virtual machine ready

Request snapshot and workflow checksum retained

Traceable by design

Follow the evidence from intent to cloud outcome.

The operational record connects human intent and governance decisions to the provider-aware workflow and resources that followed.

Identify the submitted values and effective policy
Resolve the exact blueprint version and workflow checksum
Review the job timeline, step results and provider resource ledger

IntelliconOps evidence chain connecting an infrastructure prompt, Blueprint Studio, Python and Ansible automation, and an Azure outcome

Operational timeline

One job. One connected evidence chain.

Job #7 shows an Azure day-two operation from queue to completion. The same job model connects provider-aware operations to their decision context and workflow result.

Requester, approver, start and finish times
Queue, worker and completion events
Workflow-step status and provider output
Cost context and Azure reconciliation controls

IntelliconOps Job 7 log with queue, worker and completion events, requester, approver, timestamps and workflow output

OpenTofu evidence chain

Show that the infrastructure change matches the plan that was approved.

OpenTofu adds plan and state evidence to the familiar request, decision and execution timeline. IntelliconOps connects the records without exposing raw sensitive artifacts in the browser.

Deployment

Cloud account, provider, approved module version, typed inputs and configuration fingerprint.

Saved plan

Plan hash, expiry, risk level and parsed additions, changes, replacements or removals.

Decision

Approval or rejection status, responsible user and timestamp. Destructive authority is checked separately.

Apply run

A run linked to the source plan records queue, start, completion or failure and OpenTofu diagnostics.

Managed result

Sanitised state projection, provider resource identifiers and synchronised IntelliconOps inventory links.

Plan dce1fcb117fe…Approved

Configuration: 00db313db0f…
Proposed change: 2 add · 0 change · 0 destroy
Decision: Approved by authorised operator
Apply source: This exact saved plan

Protected evidence

Useful to operators. Restricted by design.

Plan summaries explain actions without returning the raw artifact
Saved plan and state artifacts remain encrypted
Sanitised managed resources support inventory and investigation
Failure diagnostics remain attached to the relevant run

Useful operational evidence

Answer the questions that appear after the change.

Who requested and approved it?

Connect the job to its requester, approver and approval timestamp.

What definition was reviewed?

Inspect the Blueprint version and workflow checksum, or the OpenTofu module, configuration and saved-plan identity.

What happened and when?

Read timestamped phases, progress, warnings, failures and completion events.

What exists now?

Review provider resources across AWS, Azure or Google Cloud and the synchronised managed-resource result.

See IntelliconOps in action

Give every cloud request a clear, controlled path.

Tell us how your teams manage infrastructure today. We will show you how IntelliconOps can simplify the work.