In Azure we give our resource a name using a standard naming convention. For Fabric one of our capacities is named something like xxx02prdxxxfab001 (xxx1 = our prefix, prd = production, xxx2 = solution abbrivation, fab = fabric resource, 001 = capacity number 1). We are using this naming convention, because properties of a resource can change and you don't want te get stuck with a resource name with a specific name, that might not be valid in the future.   But this name is now also the name of the capacity in Fabric, where, in Fabric, we actually want to rename it to a name more recognizable to it's properties, like "F64 production capacity". The option is already there in Fabric on the capacity settings, but you can't change the name after clicking the pencil button. We are using multiple capacities, so it would be usefull to have the ability the rename the capacities.   ... View more

It should be possible for admin to monitor and manage the personal bookmark created by end users. ... View more

Power BI - MS announcement regarding upcoming events or furute updates are great but it will be also appreciated if company announcement will be possible ... View more

Microsoft should allow users to choose whether to enable smoothing rather than making it a mandatory feature. The smoothing capability should be an option, not an imposition from Microsoft. Smoothing introduces uncertainty, making it difficult to optimize costs for a Microsoft Fabric subscription. Additionally, smoothing is causing challenges across multiple areas, as highlighted in discussions within the Microsoft Fabric Community. Search - Microsoft Fabric Community ... View more

To make it easy to filter workspaces, and also enable cost chargeback scenarios, it should be possible to apply Tags to workspaces. ... View more

Understand that this is just a repurposed forums in some fashion, but would be great to fix up this 'Idea' section a bit with some polish.   What is 'Top Kudoed Posts' - do you mean most upvoted?  (You use 'Votes' everywhere else)   Looking at the first 'Kudoed Post' with 4k upvotes it says "NEEDS VOTES" in all caps.  What?  Needs votes for what, to be considered?  How many votes does it need, is 4k not enough? Is this just a status that means it's not WIP or something?     Also, the top post shows as being posted in 2024 but all the comments are from 2020 - is 2024 when it was created or last updated?  Confusing.   There are like 30 items in the 'Categories' dropdown filter, did you use a RNG to determine ordering?  Some Fabric items are near the top, some are near the bottom, it's obviously not alphabetical.   Having a 'Top Ideas' tab is silly if you default to including Completed ideas.  Default to NON Completed ideas otherwise the first several pages by default are items that might have been completed years ago.   ... View more

If you want to change the name of a Dataflow Gen2, you go to its PROPERTIES. But for a Dataflow Gen2 (CI/CD, preview), you change the name under SETTINGS. If you want to change the name of a Lakehouse, you go to SETTINGS.   Where you go to change the NAME of an artifact depends on its TYPE. This is inconsistent and confusing to the users.   "Properties" and "Settings" are synonomous. They should be combined into ONE area, not two. ... View more

So we're trying to pull some data out of a SharePoint site. We wanted to auth via ServicePrincipal, but it doesnt work, apparently not supported. "discussed the issue internally with our team and it was identified that our Product Group has updated us that this is not a supported scenario, and the issue is by design." Can this either become supported (may be similar to https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=e5ec086c-f1ce-ee11-92bd-6045bdbce644&%3Bpage=1) Or ideally remove the feature from the pulldown menu if it doesnt work (so others dont waste hours of their time trying to get it going and/or MS support trying to figure it out) ... View more

Currently we cannot associate one workspace to multiple deployment pipelines. If We have two workspaces with different sets of code and want to deploy to one Workspace that holds all code. It is not possible to create two deployment pipelines and deploy code from two workspaces into one. Use case: We have architecture where common/orchestration code sites in one workspace and deploy the code to any team's workspaces that want to utilize our orchestration code. With current product limitation, we cannot have multiple deployment pipelines created for each team and have common code workspace assigned to each pipeline. ... View more

When using the SQL Analytic Endpoint from a Fabric Workspace to connect via SSMS, there are now FOUR (used to be TWO) databases for Staging. These should be hidden in SSMS.  I sort of assume that they are kind of like tempdb in SQL Server where the user has no business doing things in there. I should not have access to these databases. Please hide these database from the general user population in SSMS. ... View more

Have been looking into amending the Request Access messages as we use a separate Request System for managing Access Requests.   Whilst doing this I found the following - You can amend the Access Request message on an App or on a Semantic Model, but you can't amend a message for Workspace or the associated Report for a Semantic Model - both of these options would be very useful.   For example I set a message on a Semantic Model, but when sharing the associated report link to a user without access, the message displayed was the default message and not the amended one. Another useful option would be to have the Access Message request managed in the Admin Portal, where you could select to apply it to App, Workspace, Report or Semantic Model.  We have a lot of Pipelines/Workspaces and a lot of reports within them, so this would save a lot of time rather than going through individually.  If this could also allow you to add a Placeholder, so that it automatically identifies in the message which App, Workspace, Report or Semantic Model, the user is requesting access to. Also as an observation - when amending the message on the App, you can include a hyperlink which remains as a hyperlink when the message is displayed.  But when amending the message on the Semantic Model, the hyperlink is lost and is just displayed as plain text. ... View more

Addition of an Archive status for artifacts in Fabric. This feature would allow admins to mark an artifact as “archived,” making it inaccessible to users without actually deleting it. This would serve as a preliminary step in the deprecation process, giving a grace period during which users can request the artifact to be restored if needed. If no requests are made within a set period, the artifact can then be permanently deleted. This approach helps manage content more effectively and ensures that important data isn’t lost prematurely. I heard this idea on the Explicit Measures podcast's discussion of retiring and archiving content (episode 359) and I thought it made a lot of sense. ... View more

Since F64 is required for a number of features, new customers that are starting small are required to start with that sizing. This normally means that the same capacity is shared across different environments. Currently, we can only limit the amount of resources for a workspace by leveraging Spark pools, however that does not cover the Data Warehouse experience (for instance). It would be great to have an option to assign a max of X% of a capacity to a workspace so that we can prioritize the production workloads when 1 single capacity is used. ... View more

A number of our customers invite the Entra ID account from my employer into their Azure Entra to do work. This works relatively easy with the Azure Portal and PowerApps. Both portals show the option to switch directory, making it easy to work with the customer environment. The app.fabric.microsoft.com portal is missing this feature, making it hard to switch to the correct tenant. A simple switch like the other portals would be very nice. ... View more

It would be great if we could assign custom roles to limit what users can interact with in Fabric. As far as I know if we provide someone, say a Power BI developer, "Member" level access, that user now has access to other personas such as Data Engineering/Data Science. It would be ideal if we could choose what developer persona activities they have access to. ... View more

In Lakehouses and Warehouses, I can use SSMS and script out an existing table with simple SSMS right-click context menu. But for the CREATE TABLE statement that gets generated, it includes the clause "ON [PRIMARY]" and this is NOT allowed here. SSMS needs better awareness of the types of databases it is connecting to. If you do this connected to a Synapse data warehouse, you don't get this clause. ... View more

Currently, it seems there is an admin tenant level option to enable fabric items based on Azure AD groups. But being in the group also gives you access to everything within Fabric. Its either all the items or none. It would be great to specify certain items from fabric to regular Powerbi business analysts like data activator for managing alerts for their own dashboards. ... View more

It would be very beneficial to have that checkbox to enable or disable Lakehouse Schemas (Public Preview) after the initial Lakehouse creation, vs ONLY at initial creation. Sometimes we like to change our mind and Lakehouse Schemas also hasn't been available for long, so if Lakehouses were created before this option was available, we'd like the ability to turn it on and upgrade the current Lakehouse vs the current workaround of re-creating a brand new Lakehouse along with any additional dependencies or linked items like semantic models/reports after the fact. This should be a Lakehouse setting that allows a user to turn on/off Schema preview for any Fabric Lakehouse. ... View more

As Data Engineer, I would like to be able to add / extend custom properties to the monitoring hub items. So that I can extend the monitoring hub options with our own values. ... View more