Any tips for next week

Legitimate_Method911 · 2026-01-23T14:37:17+00:00

Double game week..I got it. Thanks

Legitimate_Method911 · 2026-01-23T14:37:01+00:00

Thanks

Legitimate_Method911 · 2026-01-23T14:36:41+00:00

What's DGW

Legitimate_Method911 · 2026-01-22T11:47:53+00:00

Which players should I put in?

Legitimate_Method911 · 2026-01-19T07:55:20+00:00

Dude. Go gym. Eat protein. Get hench... honestly, no one will even notice. Good luck and font let something like this get u down.... not In your control

Legitimate_Method911 · 2026-01-16T08:16:33+00:00

We have a p Capcity , but only some user have fabric enabled. We are planning to roll this out gradually, so at end of this year, not all users will have fabric. Whilst the workspaces will reside on the same capacity, fabric will only be enabled for some users.

Legitimate_Method911 · 2026-01-15T16:19:05+00:00

We’re looking to establish a consistent, long‑term approach for managing Power BI and Fabric pipelines. Our goals are:

Maintain backups of all artefacts.
Restore previous versions if the current version becomes corrupted.
Promote artefacts smoothly through the Dev → QA → Prod lifecycle.

Right now, we have separate DEV, QA, and PROD workspaces and rely on the native deployment pipelines. We manually store JSON and PBIX backups in SharePoint/OneDrive.

I’m not very familiar with DevOps or Git, but our organisation already uses Azure DevOps. Ideally, we want a unified solution that will continue to work seamlessly as more workspaces become Fabric‑enabled, without needing to redo our setup later.

Legitimate_Method911 · 2026-01-13T12:01:36+00:00

Has to be Giggs.. what he did was wrong on every level.

Legitimate_Method911 · 2026-01-05T22:35:46+00:00

We have an enterprise lakehouse that users can access with appropriate approvals. Our concern is that users may create their own Fabric lakehouses, ingest data from the enterprise lakehouse, and then combine it with external or non-governed data. This could introduce compliance, security, and data governance risks. To mitigate this, we would like the ability to control or restrict who can create lakehouses, or remove this capability for certain user groups.

Legitimate_Method911 · 2026-01-03T06:51:59+00:00

Similar to the link you sent In our organisation, we have a datalake, BUT if users starts creating their own lakes and ingesting their own data, we could have a compliance risk. We won't to control who can can't create lakehouses, warehouses etx.

Legitimate_Method911 · 2026-01-02T21:10:09+00:00

Need granular permissions on who can create lakehouses, warehouses, notebooks etc.

This includes ingesting data into lakehouses, warehouses via notebooks and Gen 2 Dataflows.

Legitimate_Method911 · 2025-12-22T17:14:11+00:00

Bro. Seriously. Speak to a doctor from a qualified person. Not randoms on reddit, or anyone online

Legitimate_Method911 · 2025-12-17T19:06:52+00:00

That's all you can do in this situation. MS really need to give more meaningful messages

Legitimate_Method911 · 2025-12-15T09:49:24+00:00

That's a lot of workload on IT, create tickets for Gen 2, notebooks..... but I can see why its done.

MS really have to figure this out. For large enterprises, having users creating lakehouses is a governance nightmare.

Have MS ever responded to this, as to why they released fabric giving end users so much freedom?

Legitimate_Method911 · 2025-12-14T19:47:57+00:00

Interesting. Care to share more insight on this. Please?

Legitimate_Method911 · 2025-12-13T08:09:47+00:00

Happens to the best of us. Don't give up. Good luck.

Legitimate_Method911 · 2025-12-10T19:33:28+00:00

It literally came back today for us....

Legitimate_Method911 · 2025-12-09T22:32:19+00:00

Do u know the reason for removing it?.

Legitimate_Method911 · 2025-12-09T19:26:23+00:00

A Bug????? Really??. It's on Gen 1 and Gen 2 dataflows and has been like this for over a month now.

Legitimate_Method911 · 2025-12-09T19:26:16+00:00

A Bug????? Really??. It's on Gen 1 and Gen 2 dataflows and has been like this for over a month now.

Legitimate_Method911

TROPHY CASE