Others

How to Hide Intermediate Tables in Microsoft Purview Data Lineage

Tauseeq Magsi Sep 27, 2026 869 views

Question details

The user wants to know if they can hide an intermediate table in a data lineage flow (e.g., showing only source A to destination C) without the intermediate table B appearing in the graph.

Hiding Intermediate Tables in Microsoft Purview Data Lineage

Product: Microsoft Purview
Device & OS: not provided
Scenario: Configuring lineage visibility and restricting user access to specific intermediate data assets within Microsoft Purview.
Observed behavior: While Microsoft Purview collections and permissions can successfully restrict a user's access to view the details of an intermediate asset, the table itself continues to be displayed as a node in the end-to-end lineage graph.

Before you start

Ensure you have Data Curator or Data Reader permissions in Microsoft Purview to view the current lineage maps and verify how collection permissions are currently applied to your intermediate assets.

Solution 1Recommended

Manage Lineage Visibility using Curated Models and Custom Visualizations

Since Microsoft Purview does not natively remove restricted assets from the lineage graph, you must use curated data products or external visualization tools to achieve a direct source-to-destination view.

Microsoft Purview is designed to provide full transparency in its lineage graphs for compliance and auditing purposes. Consequently, restricting permissions on an intermediate table prevents users from opening the asset's schema and details, but it does not remove the node from the lineage visual.

To present a cleaner, A-to-C-only view to specific business users without exposing the intermediate steps, you will need to implement workarounds using custom curated models, published data products, or third-party reporting tools.

Verify existing permission impacts

Check your Purview collections to ensure that the intermediate table's access is restricted. Verify that users without access can see the node in the lineage map but cannot click into it to view sensitive properties or schemas.

Create a curated lineage model

Design and publish a logical data product that explicitly defines the relationship directly from source A to destination C. This logical view bypasses the physical intermediate table B, providing business users with a simplified lineage.

Build a custom visualization

Export your lineage metadata programmatically using the Microsoft Purview Apache Atlas REST API. Import this data into a visualization tool like Power BI, where you can apply filters to hide intermediate nodes based on your business rules.

Consult the Microsoft Purview community

Visit the Microsoft Purview Q&A community forums to seek advice on customized lineage models or to submit a feature request for native A-to-C lineage views in future Purview updates.

Manage Lineage Visibility using Curated Models and Custom Visualizations

Lineage Transparency Principle: Purview prioritizes structural transparency. Even when asset-level data access is denied via collection permissions, the lineage mapping remains intact to show the complete operational data flow.

Free Microsoft Office alternative

Manage Data Governance Documentation with WPS Office

While Microsoft Purview handles automated enterprise data governance, you still need reliable tools to draft governance policies, document data mappings, and outline lineage requirements. WPS Office is a highly compatible, free alternative to Microsoft Office that helps you efficiently create and share these critical documents.

1. Download and install WPS Office: Visit the official WPS Office website to download the free suite and follow the installation instructions.
2. Document lineage rules in WPS Spreadsheet: Open WPS Spreadsheet to create clear, organized tables tracking your source-to-destination mappings and intermediate table restrictions.
3. Share with stakeholders: Save your documentation in the standard .xlsx format and securely share it with data engineers and governance teams.

Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx) for seamless collaboration.Lightweight and fast, making it ideal for drafting complex data governance policies and lineage mapping requirements.Built-in PDF editing tools for reviewing, annotating, and securely sharing data product definitions.Free to use with an intuitive, tabbed interface that increases productivity across all your documentation tasks.

microsoft office alternative - wps office

Frequently Asked Questions

Why does an intermediate table still show in Microsoft Purview lineage when I restricted its permissions?

Microsoft Purview separates structural lineage visibility from data access permissions. Restricting permissions successfully prevents unauthorized users from viewing the table's schema or underlying data, but the node itself remains in the graph to ensure an accurate, transparent representation of the system's data flow.

Can I use Microsoft Purview collections to completely hide specific lineage nodes from certain users?

No. Placing an intermediate asset in a highly restricted collection will only hide the detailed properties and data of that asset. The lineage graph will still map the relationship connecting the source, the restricted intermediate asset, and the destination.

How can I export lineage data to create custom views without showing intermediate tables?

You can programmatically extract lineage metadata by utilizing the Apache Atlas REST API supported by Microsoft Purview. Once extracted, you can load the metadata into reporting tools like Power BI and apply custom filters to exclude intermediate tables, visualizing only the direct source-to-destination relationships.

Office Quick Solutions