Integrations

Azure

Azure support matters when teams need one shared reasoning model across different infrastructure providers. The goal is consistency of interpretation, not provider-specific fragmentation.

Shared operational modelCloud visibility with provenanceReplay and scene continuity

Back To Docs Hub

Page Focus

Azure integration maps cloud runtime, platform observations, and service posture into the same evidence and replay model used across CTK.

Shared operational model

Azure observations should still become evidence, contradictions, and confidence signals in the same language as other environments.

Cloud visibility with provenance

The product should retain whether a signal came from Azure-managed context or another workspace path.

Replay and scene continuity

Azure-derived intelligence should still be replayable and projectable inside Lens without losing meaning.

Questions This Page Answers

How do Azure observations stay compatible with the shared CTK model?

Why is provenance crucial for provider-specific signals?

What should operators expect from replay and Lens when Azure data is involved?

Move across the shared CTK documentation model.

Replay Reconstruction

/docs/replay/reconstruction

Lens Live State

/docs/lens/live-state

Getting Started

/docs/getting-started