raym85
1 year agoAdvocate I
Status:
New
Dynamic Lakehouse Attachment When Merging Feature Branch to Main
As a Microsoft Fabric user, I’ve noticed an issue when merging code from a feature branch to the main branch. My notebook retains the lakehouse that was attached in my local development environment, even after publishing to main. This creates extra manual steps to reattach the correct lakehouse, which can be error-prone and disrupt workflows.
It would be great to have a way to dynamically update the lakehouse attachment when merging from a feature branch to main. This isn’t about deployment pipelines for different environments but rather about ensuring that the correct lakehouse is automatically linked when the code is merged.
This feature would help streamline collaboration and prevent issues
No CommentsBe the first to comment
Recent ideas
Programmatic point-of-failure recovery for Fabric pipelines
The Fabric monitoring UI already supports Rerun → rerun from failed activity. That capability is only reachable by a human clicking in the portal. Please make point-of-failure recovery available to a...EversonElias7 hours agoRegular VisitorNew9Views1like0CommentsEnable Managed Private Endpoints Support for Microsoft Fabric Capacities Below F64
Managed Private Endpoints in Microsoft Fabric are currently supported only on F64 and higher capacities. Customers using lower capacities, such as F8, cannot establish private connectivity to Azure s...v-tsindhu8 hours agoMicrosoft EmployeeNew9Views0likes0CommentsAccessibility bug: Notebook cell text becomes invisible under Windows 11 High Contrast mode
Any text written inside a Fabric notebook is invisible when Wndows High contrast mode is enables. This applies to cell text only (not the UI). In addition, auto-complete windows are not respecting t...abigb9 hours agoNew MemberNew4Views0likes0Comments