5 Ways Microsoft Fabric Is Embracing Simplicity
The last couple of weeks have been exciting to watch in the Microsoft Fabric space. These are a few of the announcements that I think help us move closer to a core DataOps principle of simplicity:
Simplicity:
We believe that continuous attention to technical excellence and good design enhances agility; likewise simplicity, the art of maximizing the amount of work not done, is essential.— DataOps Manifesto
Mirroring for SharePoint Lists
In the past, I have written about pulling data from SharePoint, and this has the potential to eliminate the need to learn that pesky OData syntax or deal with the slow V1 or V2 SharePoint list connectors. The ability to surface SharePoint list data into Power BI just got simpler.
Excel Shortcuts
You cannot take the Finance team away from Excel, but you can now mirror the Excel data they manage. This should make handling version history and schema much easier, and it helps us avoid the slow SharePoint.Files connector.
Compare Code Changes
This is the question I kept getting in presentations on Git integration: ‘Can I see what changed in the service without going to Azure DevOps or GitHub?’ Now I can say yes, and life is a little simpler.
Fabric Notebook Auto Binding for Lakehouses
Ever move a notebook to another workspace and wonder why it is not behaving correctly, only to realize it is pointing to the wrong lakehouse? Yep, been there. This feature makes deployments across workspaces much simpler.
Workspace Tags
Workspace sprawl got you struggling to find where you need to go? Workspace tags help make managing and locating workspaces simpler. This is especially helpful when you have multiple workspaces for the same project, like dev, test, and prod.
I know I spend a lot of time writing about how Microsoft can make things harder for DataOps practitioners, but this time they are clearly moving in the right direction and making things simpler.
Which of these five Fabric features do you think will have the biggest impact on simplifying your data workflows? Are there other areas where you’d like to see Microsoft continue embracing the DataOps principle of simplicity? Share your thoughts on LinkedIn or Twitter/X.