Hi Team, Does anybody know if it possible to group workspace in de workspace overview in de fabric portal ? (I know you can pin workspace but I want to group all those workspaces for a better overview ) We are large organisatie so we have a lot of workspaces.

Hi gents, question about Fabric storage size. according to MS, if you have F64, you get total 64TB storage. I wanna know if this 64TB shared by synapse data, lake house data (Parquet file) , PBI module, and all files(structure / unstructured) on data lake? and, if I suspend the Fabric capacity during the night time, is this objects stored in Fabric still accessible? Let say a csv file, etc. thank for answering.

I know most of you will be aware of the limitations of Pipelines inside Fabric - in that not all items are currently supported, specifically Dataflow Gen2 unfortunately. I wanted to share some feedback I have form the MS Development team on where they are with this and the timelines around anything changing. I asked from them to allow me to decide on where my Data Engineers should invest their time - you can draw your own conclusions on priorities based on the same information :_ "" Dataflow Gen 2 is not currently supported in deployment pipelines. You cannot use the standard Git integration either at present. The Git integration is likely to arrive in Q4 CY25. In the meantime, it is recommended to do something like the following 1. Export the Dataflow as a Template: 2. Open the Dataflow Gen2 you want to move. 3. Use the Export template option in the toolbar to save the dataflow as a PQT file (Power Query Template) to your local machine. 4. Check this into version control. 5. Prepare the Target Workspace: Open the target workspace where you want to deploy the dataflow. Create a new Dataflow Gen2 in this workspace. 6. Import the Template: In the new Dataflow Gen2, select the option to Import from Power Query template. Upload the PQT file you exported earlier. 7. Adjust Connections and Settings: Update any data source connections if necessary. This might involve changing workspace IDs or other identifiers to match the new environment. Ensure that all steps in the dataflow are correctly configured to point to the appropriate resources in the new workspace. 8. Publish the Dataflow: Once all adjustments are made, publish the dataflow in the new workspace. I appreciate this is a not ideal, but we are making efforts to bring DFGen2 in line with the rest of the deployment pipeline capability. ""

Hi everyone, I know a lot of you are facing the requirement to move from Power BI Premium capacities, to Fabric Capacities, because of the sunsetting of the Premium capacity licensing. This blog post by David Mitchell (Microsoft) - walks you through a few different options for you, including a manual switch, and the use of semantic-link-labs. Let me know your thoughts, is this something you're planning?

Hi falks, I am planing to create a capacity for dev/qa environemnts and a second one for production where we plan to locate the gold zone for semantic model and powerbi consumption. The question is, should be booth capacities of the same size? Should be the reporting capacity bigger than the capacity for data engineers?