Notebook Execution Context Awareness for Delta Tables in Lakehouse

[burakkaragoz]

🧠
 In Microsoft Fabric, users often encounter inconsistent behavior when accessing Delta tables from different interfaces — such as SQL Endpoints vs. Notebooks. A common issue is that a Delta table accessible via SQL Endpoint may throw a "table does not exist" error when accessed from a notebook, especially when workspace names contain special characters or when the notebook is executed in a different context (e.g., Data Engineering vs. Data Science).

Proposed Idea:
Introduce a "Context Awareness Layer" in Fabric Notebooks that:

• Automatically detects and aligns the execution context with the Lakehouse environment.
• Warns users if the current notebook context may not reflect the latest metadata or table state.
• Offers a one-click "Refresh Context" button to sync with the SQL Endpoint metadata.

This would prevent confusion, reduce support requests, and improve the developer experience — especially for teams working across multiple personas (data engineers, analysts, scientists).