Make 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. When I close the browser and later return to Fabric, those items are restored automatically.
I would like an option to completely disable this behavior.
When I close my browser, I consider that session finished. The next time I open Fabric, I want to start with a clean session with no previously opened workspaces or items restored.
This would also make it easier to use separate browser tabs or windows for different tasks. For example one tab for notebooks, pipelines, and lakehouses related to specific data source and another tab for resources related to another source. Persisting and restoring the previous Fabric session makes it harder to compartmentalize work this way.
I understand that session persistence can be useful for users who want to continue exactly where they left off, so I am not suggesting that the functionality should be removed.
Instead, please provide a user preference such as:
Restore previous Fabric session
- On – Restore previously open workspaces and items
- Off – Start with a clean Fabric session
When this setting is disabled, closing the browser should effectively end the Fabric UI session. Opening Fabric again should start fresh without restoring previously opened workspaces, items, or tabs.
Why this matters
The current behavior can make Fabric slower and more cumbersome for users who frequently multitask across workspaces and different Fabric experiences.
A persistent session is useful when you intentionally want to continue working later. For users who prefer a clean workspace after closing the browser, however, it should be opt-in rather than mandatory.
Recent ideas
Allow External OneLake Data Shares to Be Accepted into Multiple Fabric Item Types
Fabric External Data Sharing provides an excellent zero-copy mechanism for sharing OneLake data across tenants. However, the receiving tenant currently has to accept the share into a Lakehouse. I w...Mourak18 hours agoNew MemberNew5Views0likes0CommentsAllow OneLake Shortcut Authentication Mode to Be Changed In Place
OneLake shortcuts support passthrough and delegated authentication, but changing the authentication model currently requires deleting and recreating the shortcut. I would like shortcut authenticatio...Mourak18 hours agoNew MemberNew7Views0likes0CommentsTenant-Wide OneLake Shortcut Lineage and Impact Analysis
This is grounded in a documented limitation: shortcut lineage is currently workspace-scoped, and Microsoft specifically says lineage for shortcuts to warehouses and semantic models isn't currently av...Mourak18 hours agoNew MemberNew15Views0likes1CommentAdd an End-to-End Production Reference Architecture for Microsoft Fabric Real-Time Intelligence
I would like to see a complete end-to-end Microsoft Fabric Real-Time Intelligence reference architecture that demonstrates how the individual RTI capabilities work together in a production-oriented s...Mourak19 hours agoNew MemberNew5Views0likes0CommentsImprove CI/CD consistency for Microsoft Fabric Real-Time Intelligence Eventstreams
Microsoft Fabric Real-Time Intelligence has made strong progress with Git integration and deployment pipelines, but lifecycle management can still be inconsistent across Eventstream sources, destinat...Mourak19 hours agoNew MemberNew3Views0likes0Comments