Qualify
Confirm affected resources and the source signal.
Lineage use cases
Start with the operating question your team already has.
A specific review is the clearest way to evaluate connected infrastructure intelligence.
Use Lineage for change reviews, cost variance, risk and access triage, recurring reporting, and governed action preparation.
- Change review
- Cost variance
- Risk and access
- Recurring reporting
These use cases describe ways to apply implemented product surfaces. Outcomes depend on approved source coverage, data quality, customer process, and accountable review; service support is called out separately.
Use case 01
Implemented capabilityReconstruct what moved around an incident window.
Select retained states, inspect resource and property diffs, compare activity records, and note related cost or risk movement. The output is a supported review trail, not a guaranteed root-cause determination.
- Bound the scope and before/after states
- Inspect diffs and available activity evidence
- Assign validation and document the conclusion
Use case 02
Implemented capabilityExplain a cost increase with estate history nearby.
Start with a subscription, service, resource group, or resource and a meaningful comparison period. Review movement against infrastructure changes, ownership context, recommendations, and license material where relevant.
- Compare periods and affected scope
- Test change and usage hypotheses
- Route validation or optimization work
Use case 03
Implemented capabilityPrioritize a finding with resource and identity context.
Review the affected estate, available identity and role information, activity, and recommendations before assigning remediation. Validate authoritative access and security conclusions in Microsoft source systems.
Contextualize
Review identity, activity, history, and ownership.
Route
Assign the next validation or remediation step.
Use case 04
Implemented capabilityReplace a manual evidence hunt with a repeatable report workflow.
Use report building and configured schedules to organize selected findings, movement, and decisions for a recurring operational review. Delivery and retention requirements must be confirmed for the account.
- Define audience and recurring questions
- Select review sections and evidence
- Review delivery status and decisions
Use case 05
Implemented capabilityPrepare an approved path without treating analysis as execution.
Where configured, teams can use Azure Write or Deployment Mode to organize intent, checks, plan or what-if material, approval, execution, and verification. Availability and permitted operations are environment-specific.
Prepare
Define intent and gather preflight or plan evidence.
Approve
Apply configured identity, permission, policy, and approval controls.
Verify
Retain execution and post-action review records.
Service and advisory
Service and advisoryTurn one use case into measurable evaluation criteria.
Swaves can help select a bounded scenario, map sources, define expected evidence, and facilitate the review. Integration work, managed operation, formal assessment, and deployment design are separately scoped when needed.
- Choose a representative but bounded scenario
- Agree evidence and success criteria
- Separate product fit from additional service requirements
Evaluate Lineage
Choose the first use case deliberately.
A bounded change, cost, risk, or reporting question gives the clearest product evaluation.