fabric platform | workspaces
495 TopicsSearch for models that failed or are in progress
We'd like to be able to search a workspace for models that are currently refreshing or models that have failed to refresh. We have a workspace with a lot of models; and its difficult to identify the models that have failed or are in progress. This is needed when there is a data source outage, networking incident or other 'urgent' event that requires us to manually trigger refreshes or to see what models are actively refreshing.8Views0likes0CommentsOption to disable or bulk-clear Multitasking session tabs in the Left Navigation Pane
Currently, when working in the Fabric/Power BI Service, opening reports, dataflows, lakehouses, or semantic models automatically stacks them as active session tabs directly under the active workspace in the left navigation pane. For developers like me working in tons of reports, this forces my to manually close all reports I worked in one by one when I hit the limit. Requested Solution: Add a 'Close All Tabs' button: Allow users to clear all accumulated open session items in the left pane with a single click. OR Toggle to Disable Multitasking Tab Stacking: Provide a preference in Settings to prevent opened items from auto-stacking in the left navigation bar altogether.7Views0likes0CommentsChange the behavior of Fabric View (design experience) for clicking on Workspace in Navigation
Microsoft added or revamped the "design experience" down to two options only: Power BI and Fabric. Fine. Suggestion #1: Get it to REMEMBER the state I left it in when I closed the browser. I'm starting to drift toward the Fabric experience, but I have to SELECT it every time I open the browser. Seggestion #2: I like that I can have multiple Workspaces available in the left side navigation. But when I click on one I was hoping to have it OPEN SAID WORKSPACE, NOT give me a hierarchy view which includes ALL OPEN Workspaces. I have to now FIND the workspace I JUST CLICKED ON in that side navigation, and CLICK IT AGAIN. Just open the workspace for me! Even if there is only ONE workspace open, it is still TWO CLICKS to get to the full workspace view. In the Power BI Experience, ONE CLICK on the Workspace in the side navigation brings up that workspace.152Views2likes1Commentreset workspace environment
Hello I am having issues sometimes when, by mistake, I delete or update a certain object in my git-connected workspace environment and then I try to switch branches. That little mistake can cause me a lot of debugging time trying to find out what exactly changed ( i get a ref id ) , and finding a way to either delete it from my existing workspace or manually update something in the remote git branch that I am trying to sync to. This is just to allow fabric to sync my workspace with a remote branch. It would save me a lot of time if there would just be an option to wipe clear my existing workspace ( with the risk of losing uncommited changes, etc ) , just to be able to sync from git and make my workspace functional again. If this option is viable, in order to basically start with a clean workspace once more and sync from git, it would save me a lot of time. Please provide feedback, I'm trying to understand if sync problems can be fixed this way, with a hard reset.17Views0likes0CommentsSQL Analytics Endpoint host name - CNAME or defined alias
The host name for a SQL Analytics endpoint is ugly. They look like this: random_ugly_alphanumeric-random_ugly_alphanumeric.datawarehouse.fabric.microsoft.com The first segment looks like it is tenant-specific - if I have several workspaces that each have a lakehouse with a SQL analytics endpoint, the first segment is the same for each of them. The secong segment is specific to the workspace - if you have multiple lakehouses in the same workspace, each of the SQL Analytics endpoints have the same hostname. So it appears that there's only one SQL Analytics endpoint in the workspace and it has multple database contexts. I get it. If I have a bunch of users who have some legacy need to connect via a TSQL endpoint, I need to give them this ugly name. If I have multiple workspaces with similar names, for dev, test, and prod, it is very easy to make a mistake and copy the wrong host name because they have nothing in the host name that links them back to the workspace they are in (except the ugly random alphanumeric string). Also, I might want to switch users to a different SQL Analytics host name a some point and it means that existing connections need to have their host names updated - ODC files, DSNs, connection strings, etc. It can be a lot of changes to coordinate. I thought maybe I could use a DNS CNAME record to alias the hostname - testfabricsql.mydomain.com goes to the test workspace's SQL Analytics host name, prodfabricsql.mydomain.com goes to the Prod workspace's, etc. This would make it easy to update the host name in one place. It didn't work, unfortunately - something about the dynamic nature of the network on the Microsoft side. So, I'd like it if we could have one of these options: 1. support the CNAME option 2. create a named alias in the Fabric workspace 3. have something more recognizable in the host name that is generated. Even if it still has a bunch of random alphanumeric strings in it. (this is difficult because if it is derived from the workspace name, then if you change the workspace name, does it also change the host name? that's probably not great either.)12Views0likes0CommentsSupport semantic model creation with Workspace-level Private Link
Semantic models are a core enterprise BI artifact. Workspace‑level Private Link with blocked public access is mandatory for regulated industries (banking, financial services, public sector). Without supported Semantic Model creation, Fabric cannot be adopted as a production‑ready BI platform in these environments. This capability is critical for enterprise and regulated customers evaluating Microsoft Fabric as a strategic analytics platform. Current state documented here: Supported scenarios for workspace private links - Microsoft Fabric | Microsoft Learn The main concern with workaround: Temporary public access or item‑creation order workarounds are non-deterministic, not automatable, and violate compliance requirements.439Views9likes2CommentsWorkspace Identity support for Lakehouse.Contents() - Fabric Lakehouse connection
Please make it possible to use Workspace Identity authentication when creating a Fabric Lakehouse connection which will be used by semantic models that connect to Lakehouse data source (Lakehouse.Contents()).26Views0likes0CommentsEnhanced Workspace Management and Collaboration in Microsoft Fabric
Microsoft Fabric should enhance Workspaces with advanced collaboration, granular role-based permissions, customizable workspace organization, improved search, and better resource management. These improvements would help teams efficiently manage large-scale data, analytics, and reporting projects while reducing administrative complexity. A more flexible and intuitive Workspace experience would significantly improve productivity, governance, and collaboration.13Views0likes0CommentsAllow Multiple Audiences with the Same Name in One Workspace
This is regarding Org Apps: Currently, Org App audience names must be distinct within the same workspace. This idea is to allow multiple audiences to have the same name within the same workspace, for different Org Apps. For example: Sales & Marketing (workspace) Sales (org app) |-Admin (audience) |-Sales Team (audience) |-Marketing Team (audience) Products (org app) |-Admin (audience) |-Sales Team (audience) |-Marketing Team (audience)15Views0likes0CommentsAllow Collapse by default in Org App
We would like the ability to collapse sections in the Overview page of the new Fabric Org App by default. When there are many sections with many reports for each section, we would like the ability to collapse those report names by default, this only showing the section names to the user. If they want to go into a section, they can then expand that section.71Views1like1Comment