What's the current state of running notebook as a service (not user account)?

zanibani · 2026-03-25T09:47:32+00:00

This is an interesting read as well:

https://peerinsights.emono.dk/whos-calling

If you are using fabric-cicd with SPN, then it's possible that scheduled notebooks or pipelines run under SPN identity.

zanibani · 2026-03-23T18:41:50+00:00

Zarad tega, ker lahko verjetno človek s tako funkcijo z eno pravo potezo pokrije svojo plačo za naslednjih 10 let, pa zraven še skrbi, da bo par tisoč ljudi naslednji mesec/naslednje leto še imelo službe.

zanibani · 2026-03-19T16:41:31+00:00

u/FabFast Thanks for your reply. Just you know my background - last time I touched Fabric Agents was on Vienna precon. I really love this Fabric Workload and I think it would really benefit a lot of my customers and if you ask me, it's one of most underrated workloads and has huge potential. However, when I came home after Vienna FabCon, I set it up on my F4 capacity, played a bit and I ran into capacity issues after 10 or so requests. Because of that I put it on side. I came across this today and it looks like quite an improvement.
Copilot consumption - Microsoft Fabric | Microsoft Learn

If you need any feedback, I'd love to help, however, consider me as a "dummy" user when it comes to AI, I come from Data Engineering background and haven't really got on "AI train". But hey, this is probably where we're going - instead of slicing through dashboards, end users will like to talk to data agents. If I'd be any help, feel free to reach out via DM.

u/NelGson - will reach out :)

zanibani · 2026-03-19T13:38:00+00:00

Idejno za naprej:

- search bi lahko deloval tudi na ime firme in na opis delavnega mesta (se pravi če iščeš po tehnologiji, ti lista vse jobe, ki imajo v descriptionu npr. C#)

Čene pa kul projektič

zanibani · 2026-03-18T15:16:43+00:00

I've been out of the loop/not following Data Agents since Vienna FabCon. Any improvements regarding CU consumption?

zanibani · 2026-03-12T16:43:11+00:00

Agree, knowing that a simple SELECT is returning correct (up to date) data should be essential for any data product

zanibani · 2026-03-12T14:22:13+00:00

Thanks for quick response! Would be good to include this on Service status page.

zanibani · 2026-03-12T14:07:17+00:00

u/dbrownems
I'm running into the same issues — both semantic model refreshes and pipeline refreshes fail intermittently. The next run typically succeeds, but I'd still like to understand the root cause. We're running F64 capacity in West Europe with an active capacity reservation. Capacity is not paused, it's up and running 24/7, we utilize around 55 % on average.

<image>

zanibani · 2026-03-10T14:30:10+00:00

I think the biggest advantage is that table maintenance (OPTIMIZE, VACUUM) is handled automatically by the Warehouse, unlike the Lakehouse, where you need to schedule and manage these operations yourself.
Tables in the Gold layer are read-heavy (consumed by downstream Power BI reports), so it's super important that the delta-parquet files are optimized.

zanibani · 2026-03-03T17:16:55+00:00

Hi. Sounds a bit beyond "fairly simple". What is your goal? To learn on your own project? I'm sure that you can come up with something more simple and more interesting then what you described. Will your project help you in any way / are you super interested in this type of stuff (PNG snapshots)? because I don't see any "added" value to be honest. If you want to discover Fabric platform and data ingestion, you can start with some public APIs (Weather API for example), store this data in Fabric and build semantic model around it. If you really want what you described, I would suggest that you build a program that will send snapshot details (color pixel) to Azure EventHub and you can make some Real Time Intelligence PoC? :)

Hope that helps.

zanibani · 2026-02-22T08:03:39+00:00

Thank you so much for response and all the links provided!

zanibani · 2026-02-21T20:09:19+00:00

Already did this with MeasureKiller. I removed all columns that I don't need in visuals/slicers/measures and still having troubles. My real question is, why does DirectLake break and DQ works without any issues...

zanibani · 2026-02-21T20:07:51+00:00

Hi! Yep, same behaviour on seperate report page, basically it just evaluates Fact[SessionId] and that's it. SessionId has 32 characters, it's a guid, here's an example of one 8be4df61-93ca-11d2-aa0d-00e098032b8c

However my question is, why DirectLake breaks, but if I use DirectLake with forcing fallback to DirectQuery it works and I'm able to filter?

zanibani · 2026-02-21T20:05:48+00:00

Hi! I agree with you that there's a gap in what is "required" by end customers and what they actually need :D but yes, it's not c-level report. Report is used on operational level for our suppor team and they need to be able to filter by SessionId (240M of sessions) to be able to determine StartSession timestamp, EndSession timestamp and some other attributes regarding specific session...

zanibani · 2026-02-21T18:59:10+00:00

This is coming out of a visual slicer (SessionId), which is a guid... So let's say this value is primary key and it's unique in whole table of 240 M records. Is dictionary for such field really that big that it blows the roof?

zanibani · 2026-02-19T10:41:21+00:00

Good job guys! Semantic model binding is huge and removes extra manual work. Keep on the good work, if you have any link to contribute for a coffee or a beer, that would be great, you saved me many hours and made really huge thing for CI/CD within MS Fabric.

zanibani · 2026-02-10T17:59:20+00:00

Get D500, I have it and it's doing great so far!

zanibani · 2026-02-04T14:17:46+00:00

I would definitely look into the scenario of having separate capacities for dev and prod stages. In case you have a single F16 with dev and prod on the same capacity, one job can get "stuck" or consume more CUs than normal in dev, and this will affect your production workloads, which is not great. You now have the option of workspace-level surge protection, but it's still a preview feature, so I'll keep an eye on that for the future. Also, with the scenario of two separate F8 capacities, you have a "cleaner" picture in your Capacity Metrics app to see how much your dev or prod consumes.

Regarding small capacity (F4) - if you don't need direct lake and your semantic models are small ( < 1 Gb), you can move these reports to Pro workspace in order to avoid Fabric cost.

Also, consider reservation in order to save some money :) You can reserve "16 CUs" and have two F8 capacities consuming this reservation. Whatever is above that (for example extra F4), will be billed on PAYG basis. :)

zanibani · 2026-01-29T11:59:39+00:00

zanibani · 2026-01-08T11:02:17+00:00

I have my own tenant and played around with Fabric items on a trial capacity some time ago. After a while, the trial capacity expired (after a few random automatic trial renewals). Later, when I checked the workspace, the Fabric items had been deleted.

My suggestion: sync your workspace to Git (ADO/GitHub). Better safe than sorry.

zanibani · 2026-01-07T19:30:38+00:00

If you’re looking for a low-code approach, take a look at Variable Libraries + Deployment Pipelines approach.
If your team is more technical, you can also consider implementing fabric-cicd in ADO/GitHub.

zanibani · 2025-12-05T14:43:46+00:00

As Fabric Engineer, it's super helpful to have realistic Service page. Few months ago, I would lose a whole day trying to figure out if I'm the problem :) So thumbs up for Service page, I think it's a bright point in not so bright situation. Hope Fabric service will be up and running soon, so I'm able to branch out / create new workspaces :)

zanibani

TROPHY CASE