AZ Lineage – Regulatory Data Lineage
Global Research Forum · Operations & Productivity
Certification per Microsoft Marketplace.
Evidence tier Source Confirmed · 9 captures on record
What the publisher says
As described on Microsoft Marketplace.
AZ Lineage Managed Application is an Azure-deployed, AI-assisted technical data-lineage solution for organizations that need traceable source-to-target evidence from technical source artefacts.
The solution is deployed inside the customer’s own Azure subscription as an Azure Managed Application. Customer source files, generated lineage outputs, run metadata and audit evidence remain in customer-controlled Azure resources rather than being transferred to a centrally hosted Global Research Forum SaaS environment.
Show the rest of the publisher’s description (36 more lines)
AZ Lineage is designed to support technical lineage, regulatory reporting, audit, data governance, migration, impact analysis and legacy-modernization workflows. Depending on the enabled product version, supported text-based inputs may include SAS programs, SQL scripts, stored procedures, ETL or mapping logic, metadata files and similar technical source artefacts. The exact enabled formats and upload limits are shown in the deployed product and documentation. PDF, scanned-image and OCR processing are not included in the standard offer.
Key capabilities include:
- AI-assisted source-to-target lineage extraction
- Column-level lineage where supported by the source evidence
- Transformation logic and source-code evidence
- File and line-level traceability
- Validation status, warnings, exceptions and suppression reasons
- Duplicate and unsafe-record controls
- Generic JSON lineage outputs
- Run summaries, chunk summaries, audit logs and exception logs
- Customer-controlled Azure deployment and storage
- Downloadable output files for customer review and downstream use
REGULATORY AND GOVERNANCE USE CASES
AZ Lineage can help customers assemble technical lineage evidence for programmes associated with:
- BCBS 239 principles for effective risk data aggregation and risk reporting
- European Central Bank expectations for effective risk data aggregation and risk reporting (ECB RDARR)
- EU Digital Operational Resilience Act (DORA) ICT governance and control-evidence workflows
- APRA CPG 235 Managing Data Risk practices in Australia
- UK PRA, Canadian OSFI and similar national data-governance, model-risk and supervisory reporting expectations
These references describe potential customer use cases only. AZ Lineage does not certify compliance with BCBS 239, ECB expectations, DORA, APRA guidance, UK PRA requirements, OSFI guidance or any other law, regulation or supervisory framework. Customers remain responsible for determining applicable obligations and obtaining appropriate legal, regulatory, audit and compliance advice.
AZURE DEPLOYMENT AND AI PREREQUISITE
The application uses customer-controlled Azure compute, storage, orchestration and metadata services together with managed identity for Azure resource access.
Real lineage processing requires a customer-owned Azure OpenAI or Microsoft Foundry endpoint and one or more compatible deployment names. The application’s managed identity must have the required role assignment on the customer’s AI resource. If the AI endpoint or deployment configuration is missing or inaccessible, the Azure resources may deploy successfully, but lineage processing will not complete.
TYPICAL USER FLOW
- Deploy AZ Lineage Managed Application from Microsoft Marketplace.
- Configure the customer-owned Azure OpenAI or Microsoft Foundry endpoint and deployment names.
- Upload supported technical source files using the available product workflow.
- Start a lineage run.
- Review run status, warnings, exceptions and generated evidence.
- Download the lineage output and supporting audit files.
Generated outputs may include lineage JSON, run summaries, chunk summaries, exception logs, audit logs, suppression records and runtime metadata.
AZ Lineage output is AI-assisted and must be reviewed by qualified customer personnel before it is used for regulatory, audit, legal, compliance, production or business decisions. The product provides technical lineage acceleration and evidence generation; it does not provide legal, regulatory, audit, financial or compliance advice.
Product information and support:
https://lineage.globalresearchforum.in/az-lineage/
Privacy policy:
https://lineage.globalresearchforum.in/az-lineage-privacy-policy/
Preview
2 images
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Sources
Publisher resources
1 linkLinked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.