Collect
Synchronize approved source categories on the configured cadence.
Lineage platform
A review layer across the Azure operating estate.
Current state, historical state, and owned action stay connected.
Understand how Lineage collects context, preserves history, and supports review workflows across product surfaces.
- Synchronized context
- Historical snapshots
- Cross-domain views
- Administrative visibility
The platform organizes synchronized Azure evidence into navigable operational views. Its job is to connect domain signals and decision records while Azure, Entra, Defender, billing, and other source systems remain authoritative.
Review layer
Implemented capabilityConnect systems of record without pretending to replace them.
Lineage reads approved Azure context into tenant-aware review surfaces. Inventory, activity, cost, identity, recommendations, and risk signals remain traceable to their source category while the platform supplies the connective review model.
Organize
Normalize evidence into estate, history, and investigation views.
Review
Move from a signal to related context and an owned outcome.
Estate model
Implemented capabilityNavigate from topology to resource detail.
Resource Map provides a relationship-oriented view of the synchronized estate. It helps reviewers understand placement and neighboring resources before opening a focused change, cost, or risk investigation.
- Resource inventory and relationships
- Subscription and grouping context
- Direct paths into detailed review surfaces
Time Machine
Implemented capabilityPreserve reviewable state across synchronization runs.
Snapshots support point-in-time review and comparison. Timelines and property diffs expose how the synchronized representation moved, including resources no longer present in the current view.
Point in time
Select a retained synchronized state for review.
State comparison
Compare snapshots and inspect changed properties.
Removed resources
Keep historical context for resources absent from current inventory.
Connected work
Implemented capabilityUse specialized views without losing the investigation thread.
Cost Intelligence, Identity, Threat Intelligence, Advisor, Activity Feed, Action Center, reports, and Atlas AI each serve a specific review job. Shared tenant and time context lets operators move between them deliberately.
- 01
Observe
Dashboard, map, activity, sync, and historical state.
- 02
Explain
Cost, identity, recommendation, and risk context.
- 03
Act and report
Assigned work, report building, and governed paths where enabled.
Operational control
Implemented capabilityMake access and freshness part of the review.
Administrative surfaces expose identity and access configuration, active product sessions, audit context, sync status, and related operating settings. Available controls depend on the account role and configured environment.
- Role and access administration
- Sync status and execution visibility
- Audit and session review surfaces
Service and advisory
Service and advisoryFit sources and controls to the customer environment.
Swaves can support source mapping, permission scoping, sync planning, role design, and operating handover. Network placement, data handling, retention, model routing, and action enablement require environment-specific review and are not universal product claims.
- Map approved sources and least-privilege access
- Define owners, review cadence, and freshness expectations
- Document architecture and advanced-capability boundaries
Evaluate Lineage
Review the platform against your source landscape.
Map the Azure evidence you have, the controls you require, and the operating review Lineage should support.