Thanks for posting this. I don't like the default semantic model either. We never use it. We create a new one every time from the lakehouse. I wish they would remove the L shape grouping with the default semantic model and SQL Analytics endpoint as well. It takes up too much real-estate and dirties up an otherwise beautiful organization of items. There are other ways to get to the SQL analytics endpoint. I say get rid of the L shape grouping and access the SQL analytics endpoint through the ... "more options". Or it isn't unreasonable to just access the SQL analytics endpoint using the toggle dropdown in the upper right corner of the lakehouse. Many of us are using SSMS anyway.
Or allow users to configure the L grouping option on or off. To us it is very annoying to have many lakehouses in a workspace and it take up this much space.
Recent ideas
Allow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels2 hours agoAdvocate IIINew178Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen3 hours agoAdvocate INew293Views47likes2CommentsSupport Encrypted Sensitivity-Labeled Excel Files in Power Query
Description Currently, Power Query Online and Power Query in Excel are unable to access encrypted Excel files. Excel files with sensitivity types other than Public or Non-Business can be encrypted a...ewarstdhyjugkhi4 hours agoMicrosoft EmployeeNew17Views6likes0Comments