<?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>rss.livelink.threads-in-node</title>
    <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/ct-p/fbc_ideas</link>
    <description>rss.livelink.threads-in-node</description>
    <pubDate>Mon, 16 Nov 2026 22:11:20 GMT</pubDate>
    <dc:creator>fbc_ideas</dc:creator>
    <dc:date>2026-11-16T22:11:20Z</dc:date>
    <item>
      <title>Advanced Per-Column and Cell-Level Formatting Options for Power BI Tables and Matrices</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Advanced-Per-Column-and-Cell-Level-Formatting-Options-for-Power/idi-p/5422877</link>
      <description>&lt;P&gt;I would like to suggest expanding the formatting capabilities of native Power BI Table and Matrix visuals by introducing more flexible, independent column-level and cell-level formatting options.&lt;/P&gt;&lt;P&gt;Currently, native tables have limitations when customizing individual columns and cells. It would be extremely useful to have greater control over the appearance of each column without affecting the entire visual.&lt;/P&gt;&lt;P&gt;The proposed enhancements include:&lt;/P&gt;&lt;P&gt;1. Font formatting: Allow bold and italic styles to be applied independently to each column.&lt;/P&gt;&lt;P&gt;2. Background and font colors: Allow individual customization of cell background colors and text colors, including conditional formatting based on cell values.&lt;/P&gt;&lt;P&gt;3. Rounded labels and badges: Allow values to be displayed inside colored containers with rounded corners, similar to status indicators or badges.&lt;/P&gt;&lt;P&gt;4. Individual cell formatting: Allow different styles to be applied to specific values within the same column.&lt;/P&gt;&lt;P&gt;5. Column alignment: Allow independent left, center, and right text alignment for each column.&lt;/P&gt;&lt;P&gt;6. Combined formatting: Allow all these formatting options to work together without affecting other columns or cells.&lt;/P&gt;&lt;P&gt;For example, in financial or operational reports, status values such as DEV, ING, DEP, and INT could be displayed as colored rounded badges, while other columns could have independent font styles, colors, and formatting rules.&lt;/P&gt;&lt;P&gt;These improvements would significantly enhance report readability, visual presentation, and customization capabilities, while reducing the need for third-party custom visuals such as Deneb.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 18:35:06 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Advanced-Per-Column-and-Cell-Level-Formatting-Options-for-Power/idi-p/5422877</guid>
      <dc:creator>alexis_apg</dc:creator>
      <dc:date>2026-11-16T18:35:06Z</dc:date>
    </item>
    <item>
      <title>Repair broken semantic model references directly in Fabric Plan</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Repair-broken-semantic-model-references-directly-in-Fabric-Plan/idi-p/5422726</link>
      <description>&lt;P&gt;Renaming tables or columns in a connected semantic model can leave a Fabric Plan unusable. In our Silver-to-Gold migration, we had to manually edit Plan definition files to repair references. Afterwards, previously entered budget values were no longer visible.&lt;/P&gt;&lt;P&gt;Please add a &lt;STRONG&gt;“Repair references”&lt;/STRONG&gt; option that identifies missing fields, lets users select their replacements, and updates dependent calculations directly within Plan.&lt;/P&gt;&lt;P&gt;Users should be able to fix these references through the interface, preserving the existing layout, planning inputs and allocations, without rebuilding the Plan or re-entering data.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 16:19:53 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Repair-broken-semantic-model-references-directly-in-Fabric-Plan/idi-p/5422726</guid>
      <dc:creator>PedroSergey10</dc:creator>
      <dc:date>2026-11-16T16:19:53Z</dc:date>
    </item>
    <item>
      <title>Enable manual data entry directly from a Power BI visual</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Enable-manual-data-entry-directly-from-a-Power-BI-visual/idi-p/5422716</link>
      <description>&lt;P&gt;I suggest adding a simple option in Power BI that allows report users to add or edit records in tables created with “Enter data,” directly from a report visual, with permissions defined by the report author.&lt;/P&gt;&lt;P&gt;A practical use case is recording comments for each product code and displaying them in a table or tooltip, preserving the comment, author, and date without having to edit the file in Power BI Desktop and republish it.&lt;/P&gt;&lt;P&gt;Although Translytical task flows supports write-back scenarios, it requires configuring additional Fabric components and a database. For a straightforward need such as saving a comment, a simpler native option would be valuable.&lt;/P&gt;&lt;P&gt;This feature would make it easier to track observations and collaborate on data within the report itself.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Permitir el ingreso manual de datos desde un visual de Power BI&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Sugiero incorporar en Power BI una opción sencilla para que los usuarios puedan agregar o editar datos en tablas creadas con «Introducir datos», directamente desde un visual del reporte, con permisos definidos por el autor.&lt;/P&gt;&lt;P&gt;Un caso práctico es registrar observaciones por código de producto y mostrarlas en una tabla o tooltip, conservando el comentario, el usuario y la fecha, sin tener que editar el archivo en Desktop y volver a publicarlo.&lt;/P&gt;&lt;P&gt;Aunque Translytical task flows permite implementar escenarios de escritura, requiere configurar componentes adicionales de Fabric y una base de datos. Para una necesidad puntual como guardar una observación, sería útil contar con una alternativa nativa más simple.&lt;/P&gt;&lt;P&gt;Esta funcionalidad facilitaría el seguimiento y la colaboración sobre los datos desde el propio reporte.&lt;/P&gt;&lt;P&gt;Gracias por considerar esta sugerencia.&lt;/P&gt;&lt;P&gt;Saludos cordiales.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;David Gudino&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 16:11:13 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Enable-manual-data-entry-directly-from-a-Power-BI-visual/idi-p/5422716</guid>
      <dc:creator>David_Gud</dc:creator>
      <dc:date>2026-11-16T16:11:13Z</dc:date>
    </item>
    <item>
      <title>Expose Background Metadata Synchronization Status and Health Metrics in Microsoft Fabric</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Expose-Background-Metadata-Synchronization-Status-and-Health/idi-p/5422679</link>
      <description>&lt;P&gt;Microsoft Fabric currently performs background metadata synchronization between Lakehouse storage and SQL Analytics Endpoints. While this process is critical for data availability and queryability, customers have no direct visibility into its status, progress, health, failures, or latency.&lt;/P&gt;&lt;P&gt;This lack of observability creates operational challenges for data engineering, platform, and support teams when troubleshooting scenarios where:&lt;/P&gt;&lt;P&gt;Newly created Lakehouse tables are not visible in SQL Analytics Endpoints&lt;/P&gt;&lt;P&gt;Schema changes are not reflected in SQL metadata&lt;/P&gt;&lt;P&gt;Delta table registrations are delayed&lt;/P&gt;&lt;P&gt;Metadata synchronization is stalled or failed&lt;/P&gt;&lt;P&gt;Business users perceive data availability issues&lt;/P&gt;&lt;P&gt;Today, customers must infer synchronization status indirectly through manual validation of sys.tables, INFORMATION_SCHEMA.TABLES, or endpoint behavior. There is currently no authoritative source indicating whether metadata synchronization is:&lt;/P&gt;&lt;P&gt;Running&lt;/P&gt;&lt;P&gt;Queued&lt;/P&gt;&lt;P&gt;Completed&lt;/P&gt;&lt;P&gt;Delayed&lt;/P&gt;&lt;P&gt;Failed&lt;/P&gt;&lt;P&gt;Retrying&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 15:39:20 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Expose-Background-Metadata-Synchronization-Status-and-Health/idi-p/5422679</guid>
      <dc:creator>ravigopalv</dc:creator>
      <dc:date>2026-11-16T15:39:20Z</dc:date>
    </item>
    <item>
      <title>Custom instructions for Copilot report analysis</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Custom-instructions-for-Copilot-report-analysis/idi-p/5422575</link>
      <description>&lt;P&gt;I believe it would be very useful to have an&amp;nbsp;&lt;STRONG&gt;Instructions&lt;/STRONG&gt; field where users can provide additional context to Copilot before it analyzes a report. Currently, there is no option to define this context, which may result in Copilot generating analyses that include unnecessary or irrelevant information.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;img /&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 14:30:43 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Custom-instructions-for-Copilot-report-analysis/idi-p/5422575</guid>
      <dc:creator>CrisMarRey</dc:creator>
      <dc:date>2026-11-16T14:30:43Z</dc:date>
    </item>
    <item>
      <title>Support GitHub App authentication in Microsoft Fabric Git integration</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Support-GitHub-App-authentication-in-Microsoft-Fabric-Git/idi-p/5422460</link>
      <description>&lt;P&gt;Description&lt;/P&gt;&lt;P&gt;Currently, Microsoft Fabric Git integration requires a Personal Access Token (PAT) to establish a connection with GitHub.&lt;/P&gt;&lt;P&gt;This creates challenges for enterprise organizations, particularly regarding credential lifecycle management, security governance and dependency on individual user accounts.&lt;/P&gt;&lt;P&gt;GitHub Apps provide a more secure and scalable authentication mechanism, allowing organizations to use dedicated application identities with fine-grained repository permissions.&lt;/P&gt;&lt;H3&gt;Feature Request&lt;/H3&gt;&lt;P&gt;Introduce support for GitHub App authentication as an alternative to Personal Access Tokens when configuring Microsoft Fabric Git integration.&lt;/P&gt;&lt;P&gt;Organizations should be able to authenticate Fabric using a GitHub App, with permissions scoped to the required repositories and operations.&lt;/P&gt;&lt;P&gt;Ideally, the integration should support:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;GitHub App authentication using an App ID and private key.&lt;/LI&gt;&lt;LI&gt;Fine-grained repository-level permissions.&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;Business Value&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;Eliminates dependency on individual user accounts and PATs.&lt;/LI&gt;&lt;LI&gt;Improves credential security and lifecycle management.&lt;/LI&gt;&lt;LI&gt;Enables centralized governance of technical identities.&lt;/LI&gt;&lt;LI&gt;Supports the principle of least privilege through fine-grained permissions.&lt;/LI&gt;&lt;LI&gt;Makes Fabric Git integration more suitable for enterprise environments.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Mon, 16 Nov 2026 13:12:44 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Support-GitHub-App-authentication-in-Microsoft-Fabric-Git/idi-p/5422460</guid>
      <dc:creator>andreviana</dc:creator>
      <dc:date>2026-11-16T13:12:44Z</dc:date>
    </item>
    <item>
      <title>Support signed commits in Microsoft Fabric Git integration</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Support-signed-commits-in-Microsoft-Fabric-Git-integration/idi-p/5422457</link>
      <description>&lt;H3&gt;Description&lt;/H3&gt;&lt;P&gt;Currently, when Microsoft Fabric synchronizes changes with a GitHub repository, commits generated by Fabric are not cryptographically signed.&lt;/P&gt;&lt;P&gt;This creates a challenge for organizations with security and compliance policies that require all commits to be signed and verified.&lt;/P&gt;&lt;P&gt;As a result, organizations enforcing GitHub signed commit policies cannot fully adopt the Fabric Git integration, despite its significant value for version control, collaboration and CI/CD workflows.&lt;/P&gt;&lt;H3&gt;Feature Request&lt;/H3&gt;&lt;P&gt;Introduce support for cryptographically signed commits when Microsoft Fabric creates commits in GitHub repositories.&lt;/P&gt;&lt;H3&gt;Business Value&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;Enables adoption of Fabric Git integration in organizations enforcing signed commit policies.&lt;/LI&gt;&lt;LI&gt;Improves security, integrity and traceability of changes.&lt;/LI&gt;&lt;LI&gt;Ensures compliance with enterprise software development and governance standards.&lt;/LI&gt;&lt;LI&gt;Reduces the need for alternative synchronization workflows or manual workarounds.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Mon, 16 Nov 2026 13:10:01 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Support-signed-commits-in-Microsoft-Fabric-Git-integration/idi-p/5422457</guid>
      <dc:creator>andreviana</dc:creator>
      <dc:date>2026-11-16T13:10:01Z</dc:date>
    </item>
    <item>
      <title>Undo / “Step back” button for filter and slicer changes in Power BI reports</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Undo-Step-back-button-for-filter-and-slicer-changes-in-Power-BI/idi-p/5422214</link>
      <description>&lt;P&gt;You know that moment when you’re clicking through slicers, exploring the data, and then you click one thing too many and lose the view you liked? Right now there’s no way back. You can clear the slicer, hit “Reset to default” and start from scratch, or try to remember what you had selected.&lt;/P&gt;&lt;P&gt;It would be great to have a simple &lt;STRONG&gt;Undo / Step back&lt;/STRONG&gt; for filter and slicer changes in reports:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Go back one step at a time (and maybe redo too)&lt;/LI&gt;&lt;LI&gt;Ctrl+Z works, just like everywhere else&lt;/LI&gt;&lt;LI&gt;Authors can add an “Undo” button to the report page&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Everyone is used to undo from Excel, browsers and basically every other tool, so users are surprised it doesn’t exist here. Personal bookmarks help a bit, but nobody remembers to save one &lt;EM&gt;before&lt;/EM&gt; clicking around.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 11:49:08 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Undo-Step-back-button-for-filter-and-slicer-changes-in-Power-BI/idi-p/5422214</guid>
      <dc:creator>m4t3j4</dc:creator>
      <dc:date>2026-11-16T11:49:08Z</dc:date>
    </item>
    <item>
      <title>Parquet Safe import check for a Lakehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Parquet-Safe-import-check-for-a-Lakehouse/idi-p/5422018</link>
      <description>&lt;P&gt;If you import a file containing column headers the import may fail on the destination. If the destination is a lakehouse the created table will parquet. Business uses often create columns with unsupported characters in a column name. In the GUI an error is created stating: unknown error. This is not clear. I request a parquet compliant check hen selecting a destination lakehouse.&lt;/P&gt;&lt;P&gt;Note:Parquet itself can technically store many unusual characters, but Spark/Fabric commonly causes problems when column names contain characters such as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Spaces&lt;/LI&gt;&lt;LI&gt;; ,&lt;/LI&gt;&lt;LI&gt;{ }&lt;/LI&gt;&lt;LI&gt;( )&lt;/LI&gt;&lt;LI&gt;Newlines/tabs&lt;/LI&gt;&lt;LI&gt;=&lt;/LI&gt;&lt;LI&gt;Special characters such as /, #, ?, %&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Mon, 16 Nov 2026 11:11:33 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Parquet-Safe-import-check-for-a-Lakehouse/idi-p/5422018</guid>
      <dc:creator>Juriaandataai</dc:creator>
      <dc:date>2026-11-16T11:11:33Z</dc:date>
    </item>
    <item>
      <title>Display Unit for Thousands should be lowercase k</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Display-Unit-for-Thousands-should-be-lowercase-k/idi-p/5421869</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;The Display Unit for Thousands in Power BI is currently uppercase K.&lt;/P&gt;&lt;P&gt;According to the International System of Units (SI) the display unit for thousand should be lowercase k (kilo). The uppercase K is reserved for Kelvin.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 10:38:02 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Display-Unit-for-Thousands-should-be-lowercase-k/idi-p/5421869</guid>
      <dc:creator>TWIE</dc:creator>
      <dc:date>2026-11-16T10:38:02Z</dc:date>
    </item>
    <item>
      <title>hi</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/hi/idi-p/5421765</link>
      <description>&lt;P&gt;test&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 10:15:21 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/hi/idi-p/5421765</guid>
      <dc:creator>mad123</dc:creator>
      <dc:date>2026-11-16T10:15:21Z</dc:date>
    </item>
    <item>
      <title>Test</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Test/idi-p/5421762</link>
      <description>&lt;P&gt;Test&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 10:14:26 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Test/idi-p/5421762</guid>
      <dc:creator>Ajayjena</dc:creator>
      <dc:date>2026-11-16T10:14:26Z</dc:date>
    </item>
    <item>
      <title>Let Planning writeback capture a non-row/column dimension (e.g. cost center)</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Let-Planning-writeback-capture-a-non-row-column-dimension-e-g/idi-p/5421110</link>
      <description>&lt;P&gt;Right now, Planning writeback only captures values that are literal row or column dimensions on the sheet. Filter Context, page-level filters, and the Writeback “Filter Type” setting all quietly do nothing to the destination table — nothing shows up in Mapping, no new Writeback Logs entry, the SQL table doesn’t change. The only documented way to split planning data by something like a cost center or region is to duplicate the entire sheet once per value, each with its own separate writeback table, and then reassemble the company total outside Planning.&lt;/P&gt;&lt;P&gt;For two cost centers, that’s already an N-table maintenance exercise. For a real deployment with a dozen or a hundred, it stops being a workaround and starts being a wall.&lt;/P&gt;&lt;P&gt;Could we get a supported way to tag a writeback row with a dimension value that isn’t itself a row or column — e.g. Filter Context actually reaching the writeback payload, or a documented guarantee that writeback for an RLS-restricted user only writes the rows that role can see (so one shared table + RLS could cover this cleanly)?&lt;/P&gt;&lt;P&gt;This feels like a fairly central capability for anyone planning by cost center, region, business unit, or any dimension with more than a handful of members — which is most real planning models. Right now the only sustainable pattern is “one physical table per dimension member,” which doesn’t feel like where this product is supposed to end up.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 07:30:20 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Let-Planning-writeback-capture-a-non-row-column-dimension-e-g/idi-p/5421110</guid>
      <dc:creator>Harri_Juhani</dc:creator>
      <dc:date>2026-11-16T07:30:20Z</dc:date>
    </item>
    <item>
      <title>Support Folder-Level Selection in Selective Branching</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Support-Folder-Level-Selection-in-Selective-Branching/idi-p/5420294</link>
      <description>&lt;P&gt;Currently, when branching out to a new workspace in Microsoft Fabric, users can either include all items in the current workspace or enable the option to select specific items individually.&lt;/P&gt;&lt;P&gt;While selecting individual items is useful, it can become cumbersome when a workspace contains a large number of items organized into folders.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Suggested Improvement&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;It would be great if users could select entire folders when using the selective branching option, rather than having to select each item individually.&lt;/P&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Selecting a folder should automatically select all items within that folder.&lt;/LI&gt;&lt;LI&gt;Users should be able to select multiple folders at once.&lt;/LI&gt;&lt;LI&gt;Users should still be able to select individual items when needed.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Benefits&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Reduces the effort required to select items when branching out from large workspaces.&lt;/LI&gt;&lt;LI&gt;Makes it easier to branch out items based on logical or functional groupings.&lt;/LI&gt;&lt;LI&gt;Leverages the existing folder structure in Fabric workspaces to make selective branching more intuitive.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;As workspaces grow and contain more items, folder-level selection would make the branching process much more efficient.&lt;/P&gt;&lt;P&gt;Thanks for considering this idea!&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 04:25:19 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Support-Folder-Level-Selection-in-Selective-Branching/idi-p/5420294</guid>
      <dc:creator>reireirejinjin</dc:creator>
      <dc:date>2026-11-16T04:25:19Z</dc:date>
    </item>
    <item>
      <title>OneLake shortcut lets a QA user with no production access append into the production lakehouse table</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/OneLake-shortcut-lets-a-QA-user-with-no-production-access-append/idi-p/5418030</link>
      <description>&lt;P&gt;We use a OneLake shortcut so a QA lakehouse can read a production lakehouse table without copying the data.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The shortcut is in the QA lakehouse, under Tables. It points at one Delta table in the production lakehouse. The QA user is not a member of the production workspace and has no write access on the production lakehouse. The user can work in QA only.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That user appended rows through the QA shortcut. Those rows were written to the production lakehouse table. Production data changed even though the user has no access to production.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A shortcut is a pointer, not a copy. An append through the shortcut writes the target table. In our case the target is the production table, so the QA append became a production data change.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Documented behavior is that a write through a shortcut is allowed only when the user has write permission on both paths: the shortcut path in QA, and the target path in production. The stricter permission is the one that applies. A user with no write access on the production target must not be able to append, update, or delete through the shortcut.&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;Steps to reproduce&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the production workspace, use lakehouse [production lakehouse name] and Delta table [table name].&lt;/P&gt;&lt;P&gt;Create a QA workspace and lakehouse [QA lakehouse name]. The QA user is a member of this workspace only.&lt;/P&gt;&lt;P&gt;In the QA lakehouse, under Tables, create an internal OneLake shortcut to [production workspace] / [production lakehouse] / [table name].&lt;/P&gt;&lt;P&gt;Confirm the QA user is not in the production workspace and has no direct permission on the production lakehouse or table.&lt;/P&gt;&lt;P&gt;As that QA user, append rows to the shortcut table from QA, using [notebook / pipeline / dataflow / Lakehouse explorer].&lt;/P&gt;&lt;P&gt;Open the same table in the production lakehouse.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Expected result&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The append fails. The production table is unchanged. QA can read the production table through the shortcut. QA cannot insert, update, or delete production rows unless that user is explicitly granted write access on the production target.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Actual result&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The append succeeds. The new rows appear in the production lakehouse table. The user still has no access to the production workspace.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Impact&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;QA and production are separate on purpose. Production is the system of record. A QA user must not be able to change it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This bypasses workspace separation. Any QA user who can write to the shortcut can add rows to production. The same path can update or delete production files, because a shortcut does not keep a separate copy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Requested change&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Enforce the documented rule on every write path, including Spark, pipelines, dataflows, and the Lakehouse explorer.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A write through an internal OneLake shortcut requires write permission on the shortcut path and write permission on the target path.&lt;/P&gt;&lt;P&gt;If the user has no access, or only read access, on the production lakehouse, the write is denied and the production Delta table is not modified.&lt;/P&gt;&lt;P&gt;Return a clear permission error that names the target lakehouse and table.&lt;/P&gt;&lt;P&gt;Apply the same check to append, overwrite, update, delete, and schema change.&lt;/P&gt;&lt;P&gt;Do not use the shortcut creator’s identity, or the QA item owner’s identity, to authorize a QA user’s write to production.&lt;/P&gt;</description>
      <pubDate>Sat, 14 Nov 2026 10:09:32 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/OneLake-shortcut-lets-a-QA-user-with-no-production-access-append/idi-p/5418030</guid>
      <dc:creator>Shyam90090</dc:creator>
      <dc:date>2026-11-14T10:09:32Z</dc:date>
    </item>
    <item>
      <title>Enable Viewing and Saving DAX Queries in Fabric Web Semantic Model Editing</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Enable-Viewing-and-Saving-DAX-Queries-in-Fabric-Web-Semantic/idi-p/5416719</link>
      <description>&lt;P&gt;# Enable Viewing and Saving DAX Queries in Fabric Web Semantic Model Editing&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**Problem**&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Power BI Desktop supports creating, saving, and reopening DAX queries in DAX Query View. However, the web-based semantic model editing experience in Microsoft Fabric does not provide the same functionality.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently, when editing a semantic model directly in a Fabric workspace:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. **Existing saved queries are not displayed.** DAX queries previously saved with the semantic model in Power BI Desktop are not visible in the web experience.&lt;/P&gt;&lt;P&gt;2. **New queries cannot be saved.** DAX queries created in the web experience are not persisted with the semantic model and are lost when the browser session ends.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;These limitations make it difficult to use the Fabric web experience as a complete semantic model development environment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**Expected Behavior**&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Provide feature parity between Power BI Desktop and Fabric web semantic model editing by supporting:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- **View saved queries:** Display existing DAX queries stored with the semantic model, including their query tab names and contents.&lt;/P&gt;&lt;P&gt;- **Save queries:** Allow users to save newly created or modified DAX queries to the semantic model.&lt;/P&gt;&lt;P&gt;- **Cross-environment consistency:** Ensure saved DAX queries are accessible and editable from both Power BI Desktop and the Fabric web experience.&lt;/P&gt;&lt;P&gt;- **Query persistence:** Preserve saved queries across browser sessions, including their names and contents.&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;Microsoft Fabric increasingly supports developing and managing semantic models directly in the browser. DAX Query View is an important tool for developing, testing, debugging, and validating DAX expressions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Without the ability to view or save queries, developers must switch to Power BI Desktop to maintain reusable DAX queries, even when the semantic model itself is managed in Fabric.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Adding this functionality would eliminate an unnecessary dependency on Power BI Desktop and improve the consistency of the semantic modeling experience across development environments.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**Microsoft Documentation**&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Microsoft explicitly documents this limitation under *DAX Query View in the web*:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://learn.microsoft.com/en-us/power-bi/transform-model/dax-query-view#dax-query-view-in-web&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**Related Existing Idea**&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DAX Query View – Save queries:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://community.fabric.microsoft.com/idea/fbc_ideas/dax-query-view---save-queries/4882354&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The existing idea addresses saving queries but does not explicitly identify the current feature disparity between Power BI Desktop and Fabric web semantic modeling, including the inability to access queries already saved with the semantic model.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This request specifically seeks feature parity between the two development experiences.&lt;/P&gt;</description>
      <pubDate>Sat, 14 Nov 2026 02:05:07 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Enable-Viewing-and-Saving-DAX-Queries-in-Fabric-Web-Semantic/idi-p/5416719</guid>
      <dc:creator>jasonhorner</dc:creator>
      <dc:date>2026-11-14T02:05:07Z</dc:date>
    </item>
    <item>
      <title>DAX Query View – Allow Selecting and Copying Query Tab Names</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/DAX-Query-View-Allow-Selecting-and-Copying-Query-Tab-Names/idi-p/5416711</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Problem&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;In Power BI Desktop's DAX Query View, query tab names cannot be selected or copied as text. This limitation exists in two places:&lt;/P&gt;&lt;P&gt;Query tab label: Users cannot highlight or select the text displayed on a query tab to copy its name to the clipboard.&lt;/P&gt;&lt;P&gt;Rename tab: When renaming a query tab, users cannot select part or all of the existing tab name for copying or editing using standard text-selection interactions.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Expected behavior&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Allow users to select and copy the text of a query tab name.&lt;/P&gt;&lt;P&gt;Support standard text editing and selection when renaming tabs.&lt;/P&gt;&lt;P&gt;Support keyboard shortcuts such as Ctrl+A, Ctrl+C, Ctrl+X, and Ctrl+V in the rename field.&lt;/P&gt;&lt;P&gt;Allow selection of individual words or portions of tab names using the mouse or keyboard.&lt;/P&gt;&lt;P&gt;Preserve existing tab navigation and drag-and-drop behavior.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Why this matters&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;DAX Query View is a developer-oriented experience. Developers frequently use descriptive query names and need to reuse those names when creating related queries, documentation, or troubleshooting notes.&lt;/P&gt;&lt;P&gt;Requiring users to manually retype query names is unnecessary friction and inconsistent with standard text-editing experiences in modern development tools.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Suggested improvement&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Make the query tab rename field behave like a standard editable text input and provide an easy way to copy a query tab's name, such as a "Copy tab name" context-menu command.&lt;/P&gt;</description>
      <pubDate>Sat, 14 Nov 2026 02:00:32 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/DAX-Query-View-Allow-Selecting-and-Copying-Query-Tab-Names/idi-p/5416711</guid>
      <dc:creator>jasonhorner</dc:creator>
      <dc:date>2026-11-14T02:00:32Z</dc:date>
    </item>
    <item>
      <title>Add specific security groups to the following tenant setting</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Add-specific-security-groups-to-the-following-tenant-setting/idi-p/5416565</link>
      <description>&lt;P&gt;It would be nice to have the ability to control this tenant setting on a more granular level:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Block republish and disable package refresh&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Currently the tenant setting above is set to either be allowed or disabled for the entire tenant. I'd like to have the ability to set up specific security groups or exclude specific security groups so that I can manage my tenant more granularly.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2026 20:16:36 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Add-specific-security-groups-to-the-following-tenant-setting/idi-p/5416565</guid>
      <dc:creator>Steven_1</dc:creator>
      <dc:date>2026-11-13T20:16:36Z</dc:date>
    </item>
    <item>
      <title>Feature Parity Between Power BI Service and Power BI Desktop Web Connector (Service Principal Auth)</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Feature-Parity-Between-Power-BI-Service-and-Power-BI-Desktop-Web/idi-p/5416545</link>
      <description>&lt;P&gt;The Web connector in Power BI Desktop does not have the same capabilities as the Web connector in Power BI Service—specifically, Service Principal authentication is not available in Power BI Desktop. Please add Service Principal authentication support to the Web connector in Power BI Desktop to achieve feature parity with Power BI service and enable secure, automated refreshes without relying on individual user credentials.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2026 19:37:04 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Feature-Parity-Between-Power-BI-Service-and-Power-BI-Desktop-Web/idi-p/5416545</guid>
      <dc:creator>Raja-Ford</dc:creator>
      <dc:date>2026-11-13T19:37:04Z</dc:date>
    </item>
    <item>
      <title>Support Service Principal Authentication for Lakehouse Destination in Dataflow Gen2</title>
      <link>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Support-Service-Principal-Authentication-for-Lakehouse/idi-p/5416285</link>
      <description>&lt;H2&gt;Problem Statement&lt;/H2&gt;&lt;P&gt;Currently, Service Principal authentication is not available when configuring a Fabric Lakehouse as a destination in Dataflow Gen2.&lt;/P&gt;&lt;P&gt;This creates a limitation for customers who want to use a non-user identity for their automated data integration processes.&lt;/P&gt;&lt;H2&gt;Customer Scenario&lt;/H2&gt;&lt;P&gt;The customer is using Dataflow Gen2 to load data into a Fabric Lakehouse and wants to authenticate using a Service Principal rather than an Organizational Account.&lt;/P&gt;&lt;P&gt;The Service Principal has the necessary access to the Fabric workspace/Lakehouse; however, Service Principal authentication is not available for configuring the Lakehouse destination.&lt;/P&gt;&lt;H2&gt;Business Impact&lt;/H2&gt;&lt;P&gt;Customers implementing automated or enterprise data integration solutions may prefer Service Principals to avoid dependencies on individual user identities.&lt;/P&gt;&lt;P&gt;Without Service Principal authentication for the Lakehouse destination, customers must rely on the currently supported authentication mechanism, which may not align with their identity and automation requirements.&lt;/P&gt;&lt;H2&gt;Requested Feature&lt;/H2&gt;&lt;P&gt;Please add Service Principal authentication support for Fabric Lakehouse destinations in Dataflow Gen2.&lt;/P&gt;&lt;P&gt;Ideally, customers should be able to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Select Service Principal as the authentication method when configuring a Lakehouse destination.&lt;/LI&gt;&lt;LI&gt;Provide the required Service Principal credentials.&lt;/LI&gt;&lt;LI&gt;Authorize the Service Principal to write to the destination based on its Fabric permissions.&lt;/LI&gt;&lt;LI&gt;Refresh/run the Dataflow Gen2 without depending on an individual user's Organizational Account.&lt;/LI&gt;&lt;/UL&gt;&lt;H2&gt;Expected Outcome&lt;/H2&gt;&lt;P&gt;Dataflow Gen2 should support Service Principal authentication when writing data to a Fabric Lakehouse destination, allowing customers to implement identity-based automated data integration without relying on an individual user account.&lt;/P&gt;&lt;H2&gt;Current Workaround&lt;/H2&gt;&lt;P&gt;Use the currently supported authentication option for the Lakehouse destination.&lt;/P&gt;&lt;H2&gt;Customer Ask&lt;/H2&gt;&lt;P&gt;Enable Service Principal authentication for Lakehouse destinations in Dataflow Gen2 to support enterprise automation and non-user identity scenarios.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2026 16:12:03 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Fabric-Ideas/Support-Service-Principal-Authentication-for-Lakehouse/idi-p/5416285</guid>
      <dc:creator>ewarstdhyjugkhi</dc:creator>
      <dc:date>2026-11-13T16:12:03Z</dc:date>
    </item>
  </channel>
</rss>

