Announcing: Table discovery in OneLake Catalog search
Analysis / inference: Microsoft Fabric search will include individual tables from semantic models, lakehouses, and mirrored databases, inheriting parent item permissions rather than data-level permissions.
- Published
- 05 Oct 2026, 11:25 PM IST
- Updated
- 05 Oct 2026, 11:25 PM IST
- Source
- Azure updates · Limited verification
- Classification
- Microsoft Security
Section 01 · Summary analysis
Global search, OneLake Catalog UI, Search API, MCP servers, and the Fabric CLI will return individual table assets based on parent item permissions, excluding object-level security protected semantic models.
AI summary / analysis; claims are not independently verified. Check the primary source before acting.
Section 02 · Analysis
SecOps Signal analysisChanges table visibility across Microsoft Fabric search surfaces and catalogs, potentially surfacing datasets to users who have parent item read permissions but lack granular data access.
Users may discover table names, descriptions, and column names for items where they hold read access even if direct data querying is restricted, requiring administrative review of tenant discovery settings.
Section 03 · Recommended actions
- Review the tenant setting 'Users can find objects in search' in the Fabric admin portal
- Evaluate whether organizational data governance requires disabling table discovery in search
- Audit parent item permissions across lakehouses, semantic models, and mirrored databases
- Review the "Users can find objects in search" setting in the Microsoft Fabric admin portal under Tenant settings
- Verify semantic models protected by object-level security are properly excluded from search results
- Check user permissions on parent lakehouses, semantic models, and mirrored databases