<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Fabric platform topics</title>
    <link>https://community.fabric.microsoft.com/t5/Fabric-platform/bd-p/ac_generaldiscussion</link>
    <description>Fabric platform topics</description>
    <pubDate>Sun, 22 Nov 2026 23:50:33 GMT</pubDate>
    <dc:creator>ac_generaldiscussion</dc:creator>
    <dc:date>2026-11-22T23:50:33Z</dc:date>
    <item>
      <title>Deployment pipeline promotes notebooks but some still point at the dev lakehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Deployment-pipeline-promotes-notebooks-but-some-still-point-at/m-p/5433060#M31906</link>
      <description>&lt;P&gt;I'm using a deployment pipeline with dev, test and prod workspaces and each one has its own lakehouse. After I promote from dev to test the notebooks come across fine, but some of them still reference the dev lakehouse as the default, so the test runs end up writing into dev. I tried setting a deployment rule for the default lakehouse and that works for most of them, but a few notebooks that attach a lakehouse through a %%configure cell in the code seem to ignore the rule completely. Is there a clean way to handle this, or is it better to stop hardcoding lakehouse ids in the notebooks and resolve them at runtime instead?&lt;/P&gt;</description>
      <pubDate>Sat, 21 Nov 2026 18:35:51 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Deployment-pipeline-promotes-notebooks-but-some-still-point-at/m-p/5433060#M31906</guid>
      <dc:creator>kumalkumar</dc:creator>
      <dc:date>2026-11-21T18:35:51Z</dc:date>
    </item>
    <item>
      <title>Stop Releasing Incomplete Features as Generally Available in Microsoft Fabric</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Stop-Releasing-Incomplete-Features-as-Generally-Available-in/m-p/5432295#M31901</link>
      <description>&lt;P&gt;Idea: Establish minimum production-readiness criteria before features can be declared Generally Available (GA).&lt;/P&gt;&lt;P&gt;Microsoft Fabric has a recurring problem: features are announced as GA while fundamental capabilities required to operate them in production are still missing, incomplete, or scheduled for future releases.&lt;/P&gt;&lt;P&gt;GA should mean production-ready, not simply that the feature is available to everyone.&lt;/P&gt;&lt;P&gt;Recent examples illustrate the problem:&lt;/P&gt;&lt;P&gt;Fabric Apps: Announced as GA while developers are still encountering limitations around CI/CD, environment-specific configuration, and deployment automation. Promoting an application from development to production shouldn't leave it connected to the development database.&lt;/P&gt;&lt;P&gt;Git integration: Source control support is not equivalent to a complete development lifecycle. Features should support reproducible deployments, configuration management, and recovery.&lt;/P&gt;&lt;P&gt;Managed identities: Announcing a preview feature with a tenant toggle but without accessible documentation or a clear provisioning workflow creates confusion rather than enabling adoption.&lt;/P&gt;&lt;P&gt;Metadata management: Introducing table and column descriptions that appear disconnected from existing Delta metadata creates another source of truth instead of improving governance.&lt;/P&gt;&lt;P&gt;Operational diagnostics: Production features should provide meaningful errors, logs, and troubleshooting capabilities without requiring custom frameworks or excessive workarounds.&lt;/P&gt;&lt;P&gt;These aren't requests for advanced functionality. They're fundamental requirements for operating software in an enterprise environment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Proposed GA acceptance criteria:&lt;/P&gt;&lt;P&gt;Before a Fabric feature is declared GA, it should meet the following requirements:&lt;/P&gt;&lt;P&gt;Source control and CI/CD: Where applicable, the feature supports version control, automated deployment, environment-specific configuration, and repeatable promotion between development, test, and production.&lt;/P&gt;&lt;P&gt;API and automation parity: Core operations available through the UI should also be available programmatically through supported APIs or tooling.&lt;/P&gt;&lt;P&gt;Operational observability: Failures produce actionable diagnostics, including meaningful error messages, execution history, and appropriate logging.&lt;/P&gt;&lt;P&gt;Complete documentation: Documentation is published, accessible, and includes deployment, security, troubleshooting, and known limitations.&lt;/P&gt;&lt;P&gt;Security and identity management: Features support appropriate non-human identities, least-privilege access, and production credential management.&lt;/P&gt;&lt;P&gt;Integration consistency: New functionality respects existing platform standards and metadata rather than introducing disconnected implementations.&lt;/P&gt;&lt;P&gt;Production validation: Features are tested against realistic enterprise deployment and operational scenarios, not merely demonstrated through successful creation and execution in a development workspace.&lt;/P&gt;&lt;P&gt;Transparent limitations: Capabilities that do not meet these criteria remain in preview, or their GA scope explicitly excludes unsupported scenarios.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why this matters:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Enterprise customers make architectural and financial commitments based on GA status.&lt;/P&gt;&lt;P&gt;Consultants and architects then have to explain why supposedly production-ready features require manual intervention, custom tooling, undocumented workarounds, or future roadmap commitments to perform basic operational tasks.&lt;/P&gt;&lt;P&gt;This increases implementation costs, creates technical debt, and damages confidence in the platform.&lt;/P&gt;&lt;P&gt;The request is simple: stop treating GA as a marketing milestone and start treating it as an engineering acceptance gate.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd rather have fewer complete features than more unfinished ones.&lt;/P&gt;&lt;P&gt;Please finish building the features before announcing that they're finished.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Nov 2026 16:26:08 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Stop-Releasing-Incomplete-Features-as-Generally-Available-in/m-p/5432295#M31901</guid>
      <dc:creator>MonkeyDData_RDP</dc:creator>
      <dc:date>2026-11-20T16:26:08Z</dc:date>
    </item>
    <item>
      <title>Oracle mirrors show “Running” but stopped reading changes from Oracle</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Oracle-mirrors-show-Running-but-stopped-reading-changes-from/m-p/5432162#M31897</link>
      <description>&lt;P&gt;On 2026-11-19 at about 6:10 AM EST, two Oracle mirrored databases on the same Fabric capacity (North Central US) stopped picking up changes within about two minutes of each other. Both still report Running, with every table Replicating and no errors.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Setup:&lt;/STRONG&gt; two mirrors of about 65 tables each, reading two different Oracle 19c databases through the same on-premises gateway cluster (version 3000.334.9).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;What I see&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The Oracle alert logs show the mirror’s LogMiner sessions, about every 3 minutes, ending normally at about 6:10 AM EST. None have run since.&lt;/LI&gt;&lt;LI&gt;Data is stale: the newest row in Oracle is about 11 hours newer than in the mirror.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Ruled out:&lt;/STRONG&gt; Oracle (no restart, no errors, grants intact, archive logs retained), the gateway (connection tests fine, other queries through it succeed), and Fabric (capacity Active, no mirror, capacity or gateway changes in the activity log). I haven’t restarted either mirror.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Questions&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Has anyone seen a mirror report Running while it silently stops reading from Oracle?&lt;/LI&gt;&lt;LI&gt;Was there an incident around 6:10 AM EST in North Central US?&lt;/LI&gt;&lt;LI&gt;Is there a way to see mirroring logs after the fact?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Archive logs are kept about 48 hours, so there’s a deadline before a full reseed (10's of millions of rows)&lt;/P&gt;</description>
      <pubDate>Fri, 20 Nov 2026 14:12:08 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Oracle-mirrors-show-Running-but-stopped-reading-changes-from/m-p/5432162#M31897</guid>
      <dc:creator>jbaz</dc:creator>
      <dc:date>2026-11-20T14:12:08Z</dc:date>
    </item>
    <item>
      <title>Fabric SQL Database with workspace-level Private Link – DNS resolution</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Fabric-SQL-Database-with-workspace-level-Private-Link-DNS/m-p/5431867#M31889</link>
      <description>&lt;P&gt;Hello Community,&lt;/P&gt;&lt;P&gt;Looking for clarification on &lt;STRONG&gt;Fabric SQL Database with workspace-level Private Link&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;We have workspace-level Private Link configured and public workspace access restricted.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Lakehouse/Warehouse endpoints resolve privately and work correctly.&lt;/LI&gt;&lt;LI&gt;The Fabric SQL Database TDS endpoint (*.database.fabric.microsoft.com) resolves via mwc-global.privatelink.pbidedicated.windows.net to a &lt;STRONG&gt;public IP&lt;/STRONG&gt;.&lt;/LI&gt;&lt;LI&gt;As public access is blocked, direct SQL Database connectivity fails.&lt;/LI&gt;&lt;LI&gt;A Warehouse-based workaround works, but direct SQL Database connectivity is preferred.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Microsoft documentation lists &lt;STRONG&gt;SQL database in Fabric (Preview)&lt;/STRONG&gt; as supported for workspace-level Private Link.&lt;/P&gt;&lt;P&gt;Can anyone confirm:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;What is the expected private DNS/CNAME path for *.database.fabric.microsoft.com?&lt;/LI&gt;&lt;LI&gt;Which Private DNS zone/records are required?&lt;/LI&gt;&lt;LI&gt;Does privatelink.pbidedicated.windows.net need to be configured for &lt;STRONG&gt;workspace-level&lt;/STRONG&gt; Private Link?&lt;/LI&gt;&lt;LI&gt;Do SQL Databases created before Private Link was enabled require any additional action?&lt;/LI&gt;&lt;LI&gt;Is the public resolution we're seeing a known Preview limitation?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Looking for the &lt;STRONG&gt;supported Microsoft configuration rather than a DNS workaround&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Nov 2026 09:08:21 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Fabric-SQL-Database-with-workspace-level-Private-Link-DNS/m-p/5431867#M31889</guid>
      <dc:creator>RashidLatif12</dc:creator>
      <dc:date>2026-11-20T09:08:21Z</dc:date>
    </item>
    <item>
      <title>Best Practices for Storing Salesforce Data in the Fabric Bronze Layer</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Best-Practices-for-Storing-Salesforce-Data-in-the-Fabric-Bronze/m-p/5431817#M31888</link>
      <description>&lt;P&gt;Hi Fabric Community,&lt;/P&gt;&lt;P&gt;We are currently building a data platform in Microsoft Fabric to integrate Salesforce and Marketo data, following the Medallion Architecture (Bronze / Silver / Gold).&lt;/P&gt;&lt;P&gt;I would like to ask about best practices for storing Salesforce data in the Bronze layer and supporting incremental Upsert operations into the Silver layer.&lt;/P&gt;&lt;H4&gt;1. Current Architecture&lt;/H4&gt;&lt;P&gt;We use Copy Activity in Fabric Pipelines to ingest Salesforce data.&lt;/P&gt;&lt;P&gt;Salesforce → Bronze: Incrementally retrieve changed records using Salesforce timestamps (such as SystemModstamp) and append them to Delta tables in the Bronze Lakehouse.&lt;/P&gt;&lt;P&gt;Bronze → Silver: Perform transformations such as data type conversions and removal of unnecessary columns, then Upsert records into Delta tables in the Silver layer using the Salesforce Id as the key.&lt;/P&gt;&lt;P&gt;Bronze layer: Store the original data retrieved from Salesforce without adding technical columns such as Run ID or ingestion timestamp.&lt;/P&gt;&lt;H4&gt;2. Challenge&lt;/H4&gt;&lt;P&gt;Since new and updated Salesforce records are continuously appended to the Bronze tables, we need a way to identify only the records ingested during the current pipeline execution when performing incremental Upserts into the Silver layer.&lt;/P&gt;&lt;P&gt;However, our current Bronze tables do not contain ingestion timestamps or Run IDs, making it difficult to accurately identify the records ingested in each execution.&lt;/P&gt;&lt;P&gt;If we process all Bronze records during every Silver Upsert, unchanged records may also be processed unnecessarily. Additionally, metadata columns such as Run ID in the Silver layer could be overwritten even when the underlying Salesforce records have not changed.&lt;/P&gt;&lt;H4&gt;3. Approaches We Are Considering&lt;/H4&gt;&lt;P&gt;&lt;STRONG&gt;Option 1: Add technical columns to Bronze Delta tables&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;When appending Salesforce records to the Bronze layer, add the following columns:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;ingestion_run_id: Identifies the pipeline execution that ingested the records.&lt;/LI&gt;&lt;LI&gt;ingestion_timestamp: Records when the data was ingested into Fabric.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;During Silver processing, use the Run ID to filter only the records ingested in the current execution before performing the Upsert.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Option 2: Store Bronze data as files instead of Delta tables&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Save the Salesforce data retrieved during each pipeline execution as separate files or in separate folders.&lt;BR /&gt;During Silver processing, read only the files associated with the current ingestion execution and perform the Upsert.&lt;/P&gt;&lt;H4&gt;4. Questions&lt;/H4&gt;&lt;P&gt;&lt;STRONG&gt;Q1. Is it appropriate to add technical columns to the Bronze layer?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;My understanding is that, according to the Medallion Architecture, the Bronze layer should generally preserve source data in its original form. However, is adding technical metadata columns such as Run ID and ingestion timestamp to Bronze tables considered a common best practice for supporting incremental processing and data traceability?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Q2. For Salesforce data, is it recommended to append records to Bronze Delta tables or store them as files?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;In a scenario where changed Salesforce records are incrementally extracted and subsequently Upserted into the Silver layer, which approach would be more appropriate? I would especially appreciate recommendations based on Microsoft Fabric best practices, along with any relevant official documentation or implementation examples.&lt;/P&gt;&lt;P&gt;Thank you in advance for your insights!&lt;/P&gt;</description>
      <pubDate>Fri, 20 Nov 2026 08:26:59 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Best-Practices-for-Storing-Salesforce-Data-in-the-Fabric-Bronze/m-p/5431817#M31888</guid>
      <dc:creator>RMori95610</dc:creator>
      <dc:date>2026-11-20T08:26:59Z</dc:date>
    </item>
    <item>
      <title>Data quality in Fabric until a native replacement arrives: what are you using?</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Data-quality-in-Fabric-until-a-native-replacement-arrives-what/m-p/5431562#M31885</link>
      <description>&lt;P&gt;With Purview Data Governance retiring (support ends 12 November 2027), Purview's data quality rules and scores go with it, and the OneLake catalog doesn't have a data quality rules or scoring feature yet.&lt;/P&gt;&lt;P&gt;For teams that need data quality now, what are you using in the meantime?&lt;/P&gt;&lt;P&gt;The options I'm weighing:&lt;/P&gt;&lt;P&gt;1) Materialized lake view constraints (CHECK ... ON MISMATCH DROP or FAIL). Neat if you already build your layers with materialized lake views.&lt;/P&gt;&lt;P&gt;2) A scheduled notebook that runs after the load, using SQL checks or a library such as Great Expectations or Soda, writing results to a table and a Power BI scorecard, with Activator alerts when a score drops.&lt;/P&gt;&lt;P&gt;3) Partner workloads from the Workload Hub (for example Informatica or Profisee). More capability, but extra licensing and setup.&lt;/P&gt;&lt;P&gt;My current preference is option 2: no new licences, it doesn't touch existing pipelines, and it's easy to switch off when a native feature arrives.&lt;/P&gt;&lt;P&gt;Keen to hear from anyone running this in production:&lt;/P&gt;&lt;P&gt;- What has worked for you, and what hasn't?&lt;/P&gt;&lt;P&gt;- How do you store your rules so they can move to a native Fabric feature later?&lt;/P&gt;&lt;P&gt;- Any experience using Activator for data quality alerts?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Nov 2026 02:05:39 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Data-quality-in-Fabric-until-a-native-replacement-arrives-what/m-p/5431562#M31885</guid>
      <dc:creator>Alinazarimehr</dc:creator>
      <dc:date>2026-11-20T02:05:39Z</dc:date>
    </item>
    <item>
      <title>Restricting specific Fabric item creation - Experiences with Fabric Policies vs. Workarounds?</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Restricting-specific-Fabric-item-creation-Experiences-with/m-p/5430846#M31870</link>
      <description>&lt;P&gt;We are running a F64 capacity POC. While testing, a small group of business users wants to try using Dataflows Gen 2, but we haven't enabled Fabric for the tenant yet.&lt;/P&gt;&lt;P&gt;Our governance goals are strict -&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;We want to enable Fabric capabilities only for this specific cohort of POC testers (via Entra ID security groups)&lt;/LI&gt;&lt;LI&gt;We want to restrict these testers to let's say creating Dataflows Gen2 only, preventing them from spinning up other Fabric artifacts (Lakehouses, Notebooks, Warehouses, Pipelines, etc.) during this phase.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;While scoping Fabric enablement via the tenant setting (&lt;STRONG&gt;Users can create Fabric Items&lt;/STRONG&gt;) to a specific security group handles item creation access at a high level, granular artifact-level restriction brings up a few questions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Has anyone implemented Fabric &lt;STRONG&gt;Policies / Policy&lt;/STRONG&gt; Sets (specifically the &lt;STRONG&gt;ItemCreation&lt;/STRONG&gt; policy type) at the capacity level to achieve this?&lt;UL&gt;&lt;LI&gt;If so, how seamless was the rollout? Did you encounter any unexpected blocking of background staging artifacts?&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;If you did not use Fabric Policies, what architectural workarounds or guardrails did you put in place instead?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Would love to hear best practices from anyone who has tackled this scenario.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Nov 2026 12:16:48 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Restricting-specific-Fabric-item-creation-Experiences-with/m-p/5430846#M31870</guid>
      <dc:creator>Bipin-Lala</dc:creator>
      <dc:date>2026-11-19T12:16:48Z</dc:date>
    </item>
    <item>
      <title>Deployment Pipeline items still say "Different from source" after deployment</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Deployment-Pipeline-items-still-say-quot-Different-from-source/m-p/5428413#M31855</link>
      <description>&lt;P&gt;We are using a simple Dev/Test/Prod deployment pipeline hooked to three Workspaces. We have a report and semantic model. After deploying the report from Dev to Test, the status of that item in the list still says, "Different from source". I thought it might be that we recently changed that report from PBIX to PBIP and added it to source control, so I deleted the report in the Test workspace and re-deployed again. Still says, "Different from source."&lt;/P&gt;
&lt;P&gt;What is going on?&lt;BR /&gt;&lt;BR /&gt;Is this a bug?&lt;/P&gt;
&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Wed, 18 Nov 2026 15:40:31 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Deployment-Pipeline-items-still-say-quot-Different-from-source/m-p/5428413#M31855</guid>
      <dc:creator>ToddChitt</dc:creator>
      <dc:date>2026-11-18T15:40:31Z</dc:date>
    </item>
    <item>
      <title>Snowflake Shared Database in Fabric</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Snowflake-Shared-Database-in-Fabric/m-p/5425611#M31846</link>
      <description>&lt;P&gt;Is it possible to copy the data from a shared database in Snowflake into Fabric, and if it is not possible is there some alternative to making the data available in Fabric?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Nov 2026 17:36:22 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Snowflake-Shared-Database-in-Fabric/m-p/5425611#M31846</guid>
      <dc:creator>amcgowan</dc:creator>
      <dc:date>2026-11-17T17:36:22Z</dc:date>
    </item>
    <item>
      <title>Purview Decom. By  Nov 2027 - Goverance Moved to Fabric</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Purview-Decom-By-Nov-2027-Goverance-Moved-to-Fabric/m-p/5425511#M31845</link>
      <description>&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is now official from Microsoft that Purview Data Governance will be retired in November 2027, with data governance moving to the OneLake catalog in Fabric. Purview itself continues for security and compliance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope Purview's governance functionality will carry over to the OneLake catalog, although that remains to be seen.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could anyone help with the following?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Will Fabric have the concepts of Data Product and Glossary Term?&lt;/P&gt;&lt;P&gt;2. Will there be a dedicated menu to create and manage data quality rules, as exists in Purview today?&lt;/P&gt;&lt;P&gt;3. Or will all of this instead be created through Fabric IQ (ontologies) and surfaced in the OneLake catalog?&lt;/P&gt;&lt;P&gt;4. Will there be a tool, in Fabric or Purview, to migrate existing Purview artefacts (governance domains, data products, glossary terms and DQ rules) into Fabric?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you in advance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Pedro&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Nov 2026 16:46:31 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Purview-Decom-By-Nov-2027-Goverance-Moved-to-Fabric/m-p/5425511#M31845</guid>
      <dc:creator>fabricpribeiro</dc:creator>
      <dc:date>2026-11-17T16:46:31Z</dc:date>
    </item>
    <item>
      <title>PII data on Fabric</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/PII-data-on-Fabric/m-p/5422863#M31828</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;We are currently modernizing our data platform and migrating workloads to Microsoft Fabric.&lt;/P&gt;&lt;P&gt;As part of this migration, we're evaluating different approaches for managing PII and sensitive customer data across the Fabric architecture.&lt;/P&gt;&lt;P&gt;I'm looking to connect with engineering teams that have already migrated to Fabric and implemented PII handling in production.&lt;/P&gt;&lt;P&gt;Specifically, would love to understand how teams are approaching tokenization, masking, access controls, data governance and secure ingestion.&lt;/P&gt;&lt;P&gt;If your team has worked on something similar, or you know someone who has, I'd appreciate an introduction.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 18:19:31 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/PII-data-on-Fabric/m-p/5422863#M31828</guid>
      <dc:creator>moboyal1</dc:creator>
      <dc:date>2026-11-16T18:19:31Z</dc:date>
    </item>
    <item>
      <title>How Do You Test Workspace Outbound Access Protection Without Breaking Existing Fabric Workloads?</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/How-Do-You-Test-Workspace-Outbound-Access-Protection-Without/m-p/5422569#M31824</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I'm exploring workspace outbound access protection in Microsoft Fabric and how teams validate connectivity before enabling stricter network security settings.&lt;/P&gt;&lt;P&gt;From what I understand, enabling outbound access protection blocks public outbound connections by default, while approved connections can be configured through managed private endpoints or data connection rules.&lt;/P&gt;&lt;P&gt;One concern is how to introduce these restrictions without unexpectedly affecting existing workloads.&lt;/P&gt;&lt;P&gt;For example, a workspace might contain notebooks, data pipelines, and connections to external data sources that currently work without additional network restrictions.&lt;/P&gt;&lt;P&gt;I'm curious how others approach testing these changes.&lt;/P&gt;&lt;P&gt;A few questions:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Do you test outbound access protection in a separate workspace before enabling it in production?&lt;/LI&gt;&lt;LI&gt;How do you identify existing connections that might be affected by the new restrictions?&lt;/LI&gt;&lt;LI&gt;What checks do you perform to confirm that approved connections still work while unauthorized connections are blocked?&lt;/LI&gt;&lt;LI&gt;Have you encountered unexpected issues with notebooks, pipelines, or cross-workspace data access after enabling these settings?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I'd be interested in hearing about practical testing approaches and lessons learned when introducing workspace-level network restrictions.&lt;/P&gt;&lt;P&gt;Thanks in advance for sharing your experiences!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 14:25:56 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/How-Do-You-Test-Workspace-Outbound-Access-Protection-Without/m-p/5422569#M31824</guid>
      <dc:creator>codeautomation</dc:creator>
      <dc:date>2026-11-16T14:25:56Z</dc:date>
    </item>
    <item>
      <title>ADO Integration with Multiple workspaces.</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/ADO-Integration-with-Multiple-workspaces/m-p/5422524#M31823</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;Right now, we are creating a product using the Fabric Platform. We almost used all components in Fabric to build the product. While moving from DEV to UAT and PROD. we are facing lot of issues. Lot of R&amp;amp;D files, we are keeping on the Dev and we can't move all the items to UAT and PROD. while using cherry pick it always showing we can't resolve the conflicts. Also, another pain point is around 15 Members in our team, whenever if we create the specific branch from dev for the developers, Warehouse related items are throwing an error mentioned that.&lt;BR /&gt;View: [Reporting].********.***** contains an unresolved reference to an object. Either the object does not exist or the reference is ambiguous because it could refer to any of the following objects: [LH_Bronze].*******.*********.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;As now all developers are working on the same workspace and we are using the fabric deployment pipeline to move the artifacts. But eventually we need individual developers should create their own workspace and branch.. going forward our team members will grow. Is it ok create an individual workspace and ADO Branch.. Please share some best practice.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 13:53:03 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/ADO-Integration-with-Multiple-workspaces/m-p/5422524#M31823</guid>
      <dc:creator>udhaya2089</dc:creator>
      <dc:date>2026-11-16T13:53:03Z</dc:date>
    </item>
    <item>
      <title>Updating many OneLake shortcuts after the storage credentials change</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Updating-many-OneLake-shortcuts-after-the-storage-credentials/m-p/5421039#M31815</link>
      <description>&lt;P&gt;We have about 30 OneLake shortcuts pointing at an ADLS Gen2 account. After the storage account key was rotated the shortcuts stopped working, and I had to open each one and update the connection by hand. Is there a way to change the connection for many shortcuts at once, or an authentication option (workspace identity, for example) that avoids this problem in the first place?&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 07:16:56 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Updating-many-OneLake-shortcuts-after-the-storage-credentials/m-p/5421039#M31815</guid>
      <dc:creator>jubinsoni</dc:creator>
      <dc:date>2026-11-16T07:16:56Z</dc:date>
    </item>
    <item>
      <title>Updating many OneLake shortcuts after the storage credentials change</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Updating-many-OneLake-shortcuts-after-the-storage-credentials/m-p/5419103#M31793</link>
      <description>&lt;P&gt;We have about 30 OneLake shortcuts pointing at an ADLS Gen2 account. After the storage account key was rotated the shortcuts stopped working, and I had to open each one and update the connection by hand. Is there a way to change the connection for many shortcuts at once, or an authentication option (workspace identity, for example) that avoids this problem in the first place?&lt;/P&gt;</description>
      <pubDate>Sun, 15 Nov 2026 02:18:44 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Updating-many-OneLake-shortcuts-after-the-storage-credentials/m-p/5419103#M31793</guid>
      <dc:creator>kumalkumar</dc:creator>
      <dc:date>2026-11-15T02:18:44Z</dc:date>
    </item>
    <item>
      <title>Best Practices for Zero-Record Handling in Fabric Pipelines</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Best-Practices-for-Zero-Record-Handling-in-Fabric-Pipelines/m-p/5415589#M31782</link>
      <description>&lt;P&gt;Hi Fabric Community,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are building a Microsoft Fabric pipeline to retrieve deleted lead records from the Adobe Marketo Deleted Leads REST API and store them in a Bronze Lakehouse.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our goal is to implement a reliable, maintainable solution using primarily no-code/low-code Fabric features.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have successfully tested the following pipeline, but would like to confirm whether this architecture follows Fabric best practices or if a simpler approach is available.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Current Pipeline Architecture&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;REST Copy Activity&lt;/P&gt;&lt;P&gt;　- Retrieve all pages using nextPageToken / moreResult&lt;/P&gt;&lt;P&gt;　- Save raw JSON files in Run ID-specific folders&lt;/P&gt;&lt;P&gt;↓&lt;/P&gt;&lt;P&gt;Dataflow Gen2&lt;/P&gt;&lt;P&gt;　- Receive the Pipeline Run ID as a parameter&lt;/P&gt;&lt;P&gt;　- Read and parse the corresponding JSON file&lt;/P&gt;&lt;P&gt;　- Expand the result arrays&lt;/P&gt;&lt;P&gt;　- Append records to a Bronze Lakehouse table&lt;/P&gt;&lt;P&gt;↓&lt;/P&gt;&lt;P&gt;Wait Activity (60 seconds)&lt;/P&gt;&lt;P&gt;↓&lt;/P&gt;&lt;P&gt;Lookup Activity&lt;/P&gt;&lt;P&gt;　- Count records for the current Pipeline Run ID&lt;/P&gt;&lt;P&gt;↓&lt;/P&gt;&lt;P&gt;If Condition&lt;/P&gt;&lt;P&gt;　├─ 0 records&lt;/P&gt;&lt;P&gt;　│ → Mark Bronze as successful (0 records)&lt;/P&gt;&lt;P&gt;　│ → Skip Silver processing&lt;/P&gt;&lt;P&gt;　│&lt;/P&gt;&lt;P&gt;　└─ 1 or more records&lt;/P&gt;&lt;P&gt;→ Mark Bronze as successful&lt;/P&gt;&lt;P&gt;→ Execute Silver processing&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Before the REST Copy Activity, we obtain an OAuth access token and a Paging Token based on the extraction start datetime.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We use a one-hour overlap to reduce the risk of missing records. Since the deleted leads have already been deleted, we retrieve all available records after the specified start datetime without applying an end datetime.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. Why We Chose This Architecture&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;① REST Copy Activity does not provide the actual deleted lead count&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Deleted Leads API returns a JSON response containing a result array and pagination metadata.&lt;/P&gt;&lt;P&gt;Although REST Copy Activity successfully retrieves and saves the paginated JSON responses, its rowsCopied value does not match the actual number of deleted lead records.&lt;/P&gt;&lt;P&gt;Therefore, we decided not to use rowsCopied for zero-record detection.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;② We use Dataflow Gen2 to parse JSON and append records to Bronze&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Dataflow Gen2 parses the JSON responses, expands the result arrays, and converts the deleted lead records into tabular data.&lt;/P&gt;&lt;P&gt;We use Append rather than Replace because we want to retain historical deletion records in the Bronze layer.&lt;/P&gt;&lt;P&gt;Each record includes a batch_id column containing the Pipeline Run ID, allowing us to identify records ingested during a specific pipeline execution.&lt;/P&gt;&lt;P&gt;Duplicates caused by overlapping extraction windows will be handled in the Silver layer.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;③ We added a Wait Activity because Lookup initially returned zero records&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When we executed Lookup immediately after Dataflow Gen2, it sometimes returned zero records even though Dataflow had successfully appended records to the Lakehouse table.&lt;/P&gt;&lt;P&gt;After adding a 60-second Wait Activity, Lookup returned the expected record count.&lt;/P&gt;&lt;P&gt;We suspect this is related to synchronization latency between Lakehouse Delta tables and the SQL analytics endpoint.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;④ We adjusted Dataflow Gen2 to handle empty results&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When no deleted leads were returned, Dataflow Gen2 initially failed because the expected attributes column was missing.&lt;/P&gt;&lt;P&gt;We modified the Power Query transformation to define the expected table schema explicitly, allowing Dataflow Gen2 to complete successfully even when there are zero records.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. Questions&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Q1. Is this pipeline architecture considered a best practice in Microsoft Fabric?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is the combination of REST Copy Activity → Dataflow Gen2 → Wait → Lookup → If Condition a recommended approach for this type of ingestion and conditional downstream processing?&lt;/P&gt;&lt;P&gt;Are there simpler or more maintainable alternatives using standard Fabric activities?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Q2. What is the recommended way to handle Lakehouse SQL analytics endpoint synchronization latency?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Adding a fixed 60-second Wait Activity resolved our immediate issue.&lt;/P&gt;&lt;P&gt;However, we are concerned that a fixed delay may not be reliable as data volumes or workloads increase.&lt;/P&gt;&lt;P&gt;Is there a recommended mechanism to detect when newly appended Lakehouse records become available through the SQL analytics endpoint, rather than relying on a fixed wait time?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Q3. Is there a better way to detect zero records without converting the JSON into a Lakehouse table first?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We initially considered using the Marketo API's moreResult property to determine whether deleted lead records were available.&lt;/P&gt;&lt;P&gt;However, we understand that moreResult indicates whether additional pages need to be retrieved, rather than whether the result contains records.&lt;/P&gt;&lt;P&gt;In some cases, the API can return an empty result array while moreResult=true, meaning subsequent pages may still need to be retrieved.&lt;/P&gt;&lt;P&gt;Therefore, checking only moreResult or the first page's record count could incorrectly classify the extraction as empty.&lt;/P&gt;&lt;P&gt;In addition, the REST Copy Activity's rowsCopied does not reflect the actual number of deleted lead records.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For these reasons, our current approach is to:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Retrieve all pages until moreResult=false.&lt;/P&gt;&lt;P&gt;Parse and expand the JSON result arrays using Dataflow Gen2.&lt;/P&gt;&lt;P&gt;Append the data to the Bronze Lakehouse table.&lt;/P&gt;&lt;P&gt;Use Lookup Activity to count records associated with the current Pipeline Run ID.&lt;/P&gt;&lt;P&gt;Skip Silver processing only when the final record count is zero.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a more efficient no-code/low-code approach to count the actual records across all paginated JSON responses and determine whether the result is empty, without first loading the data into a Lakehouse table?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We want to avoid both missed records and incorrect zero-record detection.&lt;/P&gt;&lt;P&gt;Any recommendations on best practices for this scenario would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you in advance for your insights!&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2026 10:44:26 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Best-Practices-for-Zero-Record-Handling-in-Fabric-Pipelines/m-p/5415589#M31782</guid>
      <dc:creator>RMori95610</dc:creator>
      <dc:date>2026-11-13T10:44:26Z</dc:date>
    </item>
    <item>
      <title>How do you pick the Fabric capacity size for dev, test and prod?</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/How-do-you-pick-the-Fabric-capacity-size-for-dev-test-and-prod/m-p/5414351#M31778</link>
      <description>&lt;P&gt;We run dev, test and prod on one shared capacity, and I have been using the Capacity Metrics app to look at CU usage per workspace. Prod refreshes in the morning cause most of the peaks, while dev is mostly idle. I am planning to split dev onto its own smaller capacity but am not sure how to size it. How do you decide the SKU for each environment, and is it safe to pause the dev capacity outside work hours (scheduled refreshes, pipelines, mirroring)?&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2026 00:51:21 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/How-do-you-pick-the-Fabric-capacity-size-for-dev-test-and-prod/m-p/5414351#M31778</guid>
      <dc:creator>jubinsoni</dc:creator>
      <dc:date>2026-11-13T00:51:21Z</dc:date>
    </item>
    <item>
      <title>Loading Information Protection - PBI desktop</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Loading-Information-Protection-PBI-desktop/m-p/5414271#M31776</link>
      <description>&lt;P&gt;Hi Team,&lt;BR /&gt;I am not able to open any report on my pbi app , whenver I am trying to open a report, it throws an error: "The file's sensitivity label can't be verified. Please try later". Is there a resolution for this I need to do on my side?&lt;BR /&gt;&lt;BR /&gt;I am on the Nov 2026 version of the application. Any help here is greatly appreciated.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Nov 2026 20:14:54 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Loading-Information-Protection-PBI-desktop/m-p/5414271#M31776</guid>
      <dc:creator>anikmandal</dc:creator>
      <dc:date>2026-11-12T20:14:54Z</dc:date>
    </item>
    <item>
      <title>Security Configuration Changed</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/Security-Configuration-Changed/m-p/5413856#M31767</link>
      <description>&lt;P&gt;Every time I make a change to my warehouse in OneLake, such as adding or renaming a column, the semantic models built on that warehouse show this error:&lt;/P&gt;&lt;P&gt;“Direct Lake security configuration has changed. Wait a few minutes and try again.”&lt;/P&gt;&lt;P&gt;The error can persist for several hours, preventing me from accessing the models and continuing to build reports. Has anyone experienced this issue or know how to resolve it?&lt;/P&gt;</description>
      <pubDate>Thu, 12 Nov 2026 15:10:55 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/Security-Configuration-Changed/m-p/5413856#M31767</guid>
      <dc:creator>Talha_Mughal</dc:creator>
      <dc:date>2026-11-12T15:10:55Z</dc:date>
    </item>
    <item>
      <title>dbtJob in subfolder workaround?</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-platform/dbtJob-in-subfolder-workaround/m-p/5410750#M31748</link>
      <description>&lt;P&gt;Hello!&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to run a dbt job against a dbt project that sits in a subfolder of a shared GitHub repo, not at the repo root. Since I'd like to have a single repository linked to Fabric, rather than one repository with the notebooks and a separate one for the dbt code.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;In the dbt job item in the UI by default, it says “Folder path: Root folder” prominently but I found no way to change it in the portal.&lt;/P&gt;&lt;P&gt;Through the REST API I can read the item definition (getDefinition). The &lt;A href="https://learn.microsoft.com/en-us/rest/api/fabric/articles/item-management/definitions/dbtjob-definition" target="_blank"&gt;DataBuildToolJob item definition&lt;/A&gt; lists folderPath as an optional string, “Path to the dbt project folder”.&amp;nbsp;&lt;/P&gt;&lt;P&gt;dbt-content.json has a project.folderPath field, and updateDefinition accepts a change to it. I tested three values:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;"", with the project in a subfolder and no root dbt_project.yml: error 20418, “The project yaml file was not found in the dbt project.”&lt;/LI&gt;&lt;LI&gt;warehouse/dbt/demo_project, where dbt_project.yml is in that folder: error 20418 again.&lt;/LI&gt;&lt;LI&gt;/warehouse/dbt/demo_project: error 2011, “The folder path must be a relative path, not an absolute path.”&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;So Fabric validates the field, but a relative path to the project folder did not find the yaml file.&lt;/P&gt;&lt;P&gt;Instead what does work is a dbt_project.yml at the repo root with model-paths and seed-paths pointing into the subfolder (where another dbt_project.yml file exists), and folderPath left empty.&lt;/P&gt;&lt;P&gt;Questions:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;The GitHub guide says dbt_project.yml must be at the repo root. What does the folderPath field in the item definition do?&lt;/LI&gt;&lt;LI&gt;Is this root pointer file a reasonable workaround, or other options?&lt;/LI&gt;&lt;LI&gt;Is a subfolder layout planned for the Git setup of dbt jobs?&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Sorry if the Tag is incorrect but it forces me to choose one.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Nov 2026 21:14:44 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-platform/dbtJob-in-subfolder-workaround/m-p/5410750#M31748</guid>
      <dc:creator>leppekj</dc:creator>
      <dc:date>2026-11-11T21:14:44Z</dc:date>
    </item>
  </channel>
</rss>

