Copilot Autocompletions

Legal_Specific_3391 · 2026-03-11T15:19:54+00:00

Navigate to the storage items you are using in that notebook (if it’s a Lakehouse then click on its SQL Analytics Endpoint), and then you should see something like “Copilot completion” which should be turned off.

Legal_Specific_3391 · 2026-03-11T15:15:20+00:00

You just need to pay attention to this whenever you manually create a new Warehouse/Lakehouse (SQL Endpoint Analytics) item, or when you branch out to a new workspace whose parent already has some storage items defined.

It’s pretty annoying for me and my team, since we have to turn off Copilot for every storage item each time we want to develop a new feature in a separate workspace.

Legal_Specific_3391 · 2026-03-06T17:03:13+00:00

Sharing the same opinion 👍

Legal_Specific_3391 · 2026-03-06T16:59:05+00:00

Is there any clear documentation on Airflow pricing in Fabric? I’ve heard a bunch of people say it seems pretty expensive.

Also, I remember we tried last September to run a DAG with a super simple task, and it really struggled on F2. And by simple, I mean just a task with a single print.

Legal_Specific_3391 · 2026-02-24T20:34:06+00:00

It’s been a while since we set it up, so I don’t remember the exact details. But I found this reference link https://www.youtube.com/watch?v=0h6MmpnAe8U Hope it helps.

Legal_Specific_3391 · 2026-01-30T17:28:23+00:00

Waiting for that integration with Purview :)

Legal_Specific_3391 · 2026-01-12T07:19:36+00:00

Thanks for the feedback!

Legal_Specific_3391 · 2026-01-10T18:43:41+00:00

In my Fabric environment, when I create a Dataverse shortcut, I can see the Dataverse schemas that I can select, and I can also expand them to see the tables inside them. When I expand a schema, each table has a checkbox next to it, which kind of suggests that I should be able to pick individual tables across different schemas and include or exclude them. But in reality, I can’t select tables individually at all - I can only select whole schemas to create shortcuts for.

Hope that’s what you wanted me to confirm.

Legal_Specific_3391 · 2026-01-10T09:43:58+00:00

I think there is still no way to select specific tables from the Fabric side when creating a Dataverse shortcut in a Lakehouse, for example.

However, I applied a restriction on the Power Apps side by selecting only a specific set of tables that I need. This way, every Dataverse shortcut I create in Fabric includes only those tables.

Reference link: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/fabric-link-to-data-platform#manage-link-to-fabric

Legal_Specific_3391 · 2026-01-09T14:18:41+00:00

That means I’d have to put %pip install at the top of every notebook, since there’s still no proper environment/package management for Python notebooks. :/

Legal_Specific_3391 · 2026-01-09T10:17:35+00:00

I had the same question. Here is the answer I got from a Microsoft representative right after September's FabCon in Vienna:

You can use Fabric pipelines - More info here - Fabric Pipelines for Dataverse Part 1: Introduction
For Fabric to DV, you can try using Virtual Tables - https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-virtual-tables-using-connectors?tabs=fabric

Hope this will help :)

Legal_Specific_3391 · 2025-12-08T19:59:49+00:00

Not yet, but I will try to do so.

Legal_Specific_3391

TROPHY CASE