Snapshots
Return to synchronized estate state for the chosen point in time.
Azure infrastructure intelligence
See the Azure estate as a connected history.
Lineage turns change into reviewable evidence.
Bring resource state, activity, cost, identity, risk, ownership, and reporting into one operating view.
- Snapshot history
- Cost and risk context
- Owned follow-up
- Source-aware AI
Lineage is a review workspace for Azure teams. It preserves infrastructure context across syncs, helps investigators explain movement, and routes findings into owned work without replacing the Microsoft systems that remain authoritative.
Platform view
Implemented capabilityStart with the estate, then follow the evidence.
The dashboard brings current inventory and operational signals into a common review surface. Teams can move from a broad estate question to the resource, activity, cost, identity, or recommendation context that supports a decision.
- Tenant and subscription context remains visible
- Sync state helps qualify the freshness of a finding
- Resource and review surfaces link the investigation together
Time Machine
Implemented capabilityCompare the state that was with the state that is.
Time Machine preserves synchronized snapshots and presents timelines and diffs for a selected review window. That gives operators a durable place to examine additions, removals, and configuration movement.
Diffs
Review changed properties and resource movement between snapshots.
Timeline
Place resource history beside activity and related operating signals.
Cross-domain review
Implemented capabilityExplain movement with more than one signal.
A resource change rarely tells the whole story. Lineage places cost, identity, recommendations, activity, and security context within reach of the same investigation so reviewers can build a supported explanation.
Cost
Inspect cost movement in the context of services, resources, and review periods.
Identity
Review identities, permissions, and activity where source data is available.
Risk
Prioritize findings with asset and recommendation context, not severity alone.
Ownership
Carry a finding into assigned follow-up and a recorded decision.
From finding to outcome
Implemented capabilityKeep the investigation attached to the next step.
Action Center and reports turn review output into visible operating work. Owners, status, comments, report sections, and schedules help teams preserve the decision trail after the initial analysis.
- Assign and prioritize findings
- Record status and review notes
- Build and schedule stakeholder reports
Investigation first
Implemented capabilityAsk across the evidence without hiding its boundaries.
Atlas AI assists with investigation, synthesis, and drafted next steps across available Lineage context. It does not turn an answer into an Azure change by itself; write-class operations use separate controls and are available only where configured.
Investigate
Frame questions across synchronized resource, cost, risk, and activity context.
Summarize
Draft review notes and follow-up material for an operator to assess.
Control
Keep action paths distinct from conversational analysis and subject to approval.
Service and advisory
Service and advisoryEvaluate the product against a real operating question.
Swaves can help scope an evaluation around a recent change, cost movement, access concern, risk review, or recurring report. Source access, retention, deployment architecture, and advanced action paths are reviewed for the customer environment; they are not implied by the public product experience.
- Choose a bounded tenant, subscription, or workload
- Confirm sources, permissions, and freshness expectations
- Define a decision or report output before measuring the evaluation
Evaluate Lineage
Bring one Azure question into focus.
Start with the review window, the source systems available, and the decision the team needs to make.