r/MicrosoftFabric • • 11h ago

Data Factory Browse SharePoint: the new easiest way to connect to any files or folders in SharePoint!

Post image
27 Upvotes

You start with a list of all the SharePoint sites that you have access and you can navigate through any of them like you would in a file explorer and then connect to either a file or a specific folder (with a chance to exclude subfolders).

Have you given this a try? Currently available in Dataflow Gen2 for Fabric.

Documentation article: https://learn.microsoft.com/power-query/get-data-sharepoint


r/MicrosoftFabric • • 8h ago

Community Share I always explain Fabric to customers as a building with apartments, so I built the 3D version

16 Upvotes

I always explain Fabric to customers as a building with apartments, so I built the 3D version

Whenever I explain Fabric to customers, I end up saying it's like a building with apartments: everyone has their own space, but they share the same compute and utilities. It works pretty well, people get it right away.

So I wanted to see how far I could push that idea, and turned it into an actual 3D map built on FUAM data. Domains are towns, workspaces are houses, capacities are the power plants feeding them. If a domain has failures, there's a storm over that town, and you can fly down to a house and walk inside to see what's in there and who has keys.

Honestly, I did it because it was fun and fast to build. But it turned out to be a nice way to look at a tenant too.

GIFs and details are in the Fabric Apps Gallery (all fake Contoso data).


r/MicrosoftFabric • • 8h ago

Community Share Fabric Update - November 17th, 2026

Thumbnail
youtu.be
16 Upvotes

r/MicrosoftFabric • • 10h ago

Discussion Fabric Down? Anyone else?

12 Upvotes

We are in the US. Today around 10 eastern I am just now noticing semantic models not loading and other users are saying some reports are not loading and someone else mentioned query against the warehouse is not running. Nothing is reporting on Microsoft system outage. Does not seem to be capacity issue. Anyone else experiencing problems today?


r/MicrosoftFabric • • 17h ago

Power BI Rayfin Apps in Power BI Desktop

11 Upvotes

Hi all,

First of all, exciting news in Microsoft Ignite with the announcement of GA of Fabric Apps + the ability to create them from the Power BI Desktop.

Anyone knows how the "Copilot" part will be billed that you will use in the desktop? I can't find any documentation on this. Will it be your own license, or will it be charged to the Fabric Capacity ?

Thanks !


r/MicrosoftFabric • • 13h ago

App Development Fabric Apps - Does it support "Apps-Owns-Data" embed?

8 Upvotes

We currently expose Power BI dashboards to users via a Custom Portal using App-Owns-Data method and users have no direct access to Fabric workspace.

We were eagerly waiting for the Fabric Apps GA announcement so we could start leveraging Fabric Apps for a multitude of use cases and also for some reports/dashboards given the level of flexibility it offers.

What's unclear though is whether Fabric apps can be embedded like regular power bi reports or not? If not, will it ever be supported or is it supposed to work only with Microsoft Entra always?


r/MicrosoftFabric • • 16h ago

Community Share Cross-workspaces workload: Experiment orchestrating one DAG across 50 and 500 Microsoft Fabric workspaces

10 Upvotes

Hey everyone,

I want to share an experiment I ran on cross-workspace orchestration across 50 and 500 Microsoft Fabric workspaces.

My motivation comes from my background running enterprise analytics for a large organisation. One of the distinctive strengths of Fabric, compared with other platforms, is its suitability for self-service BI across a large organisation. OneLake is pivotal to that.

This raises some common challenges I've experienced. If a central team manages shared data, while dozens of business teams independently build their own data products, how do we coordinate dependencies, understand the impact of failures and manage recovery?

So I set up an experiment with 50 workspaces, then scaled it to 500 to see whether the approach would hold.

In particular, I wanted to see whether Weaver, an open-source data engineering framework I've been building for Fabric, could handle the challenge.

The setup

I created 50 real Fabric workspaces on an FTL64 capacity:

  • 3 central workspaces covering Bronze, Silver, Gold and shared semantic models.
  • 47 business workspaces, each with its own catalogue.
  • A mixture of Lakehouses, Warehouses, semantic models and reports.
  • 53 cross-workspace connections, including a deliberate dependency cycle.

Every workspace was independently initialised, built and loaded. Together, they formed one dependency graph across the organisation.

I then deliberately broke a central Bronze customer table, BRZ.Customer.

The results

1. Enterprise-wide impact analysis

  • 161 downstream objects identified across 49 other catalogues.
  • Full assessment in 134 seconds.
  • The assessment distinguished stale objects from those still operational.

2. The central team could recover its own estate independently.

I then tested recovery from the central team's perspective, across its three workspaces.

A single load --stale identified and planned just six affected objects, in dependency order:

  • Bronze workspace: Reload the affected central Bronze data.
  • Silver/Gold workspace: Propagate the repair through the Silver Lakehouse and Gold Warehouse.
  • Semantic model workspace: Refresh the central semantic model against the repaired data.

The central team recovered its own estate without reloading any business team's data.

There was even a network interruption during the semantic model's load recording. On rerun, only the semantic model needed refreshing rather than repeating the entire recovery.

3. Business teams could see what was affected on their side.

I tested this from the perspective of business team 05.

  • Its own Health assessment identified two affected Mart tables.
  • It traced the cause back to BRZ.Customer.
  • The assessment took just 10 seconds.

No need to contact the central engineering team.

4. Business teams could decide how to recover.

After the central team repaired its estate, team 05 could see that its own tables were now behind the upstream data.

It reloaded only its two stale tables, taking 24 seconds, and returned to green.

No need to rebuild the whole workspace or wait for a central orchestrator.

5. The system tolerated dependency cycles.

I deliberately created a cycle between two business workspaces.

The cycle was identified and reported, and execution proceeded by cutting one dependency edge. The rest of the estate continued operating normally.

One object remained correctly stale afterwards because it had consumed the other team's previous load.

One final experiment

I also tried running one federated load across all 50 workspaces, with independent branches executing concurrently while respecting dependencies.

The result:

  • 81 execution nodes across 47 segments.
  • All successful under one workflow ID.
  • End-to-end time of 9 minutes 21 seconds.

This opens up another possibility: a central team could coordinate an organisation-wide refresh when required, while ordinary day-to-day execution remains decentralised.

Then I tried 500 workspaces.

I expanded the experiment to 500 workspaces: three central workspaces and 497 business teams, using the same FTL64 capacity.

The results:

  • 1,160 execution steps successfully coordinated in approximately 39 minutes.
  • 752 downstream objects traced to a single failure, spanning 450 workspaces.
  • Full Health assessment across 500 catalogues in approximately 5–7 minutes.
  • Individual team assessment still took around 13 seconds.

What I learned

OneLake is absolutely wonderful, and I think the Microsoft Fabric architecture is extremely strong for large enterprises.

With Fabric, teams can achieve two things:

  • Complete decentralised freedom when appropriate: Teams can own their workspaces, choose their tools and development processes, and use a common data hub.
  • Complete coordination when required: Dependencies, failure impacts, execution and recovery can be understood across the entire organisation.

My conclusion is that:

  • Microsoft Fabric is one of the strongest platforms for enterprise data analytics, where central information can be shared across multiple business areas without pigeonholing people into high-code development. People can choose Python, SQL, semantic models or simply reports. OneLake is a brilliant architectural foundation for this.
  • Open-source tools like Weaver can help data teams get the most out of Fabric. Not just with coordination challenges like this, but by giving teams a head start on robust data engineering across Python, Spark and T-SQL. And the more teams use it in an organisation, the better it gets.

I suspect I'm not alone in facing these challenges. Keen to hear about other people's experiences and techniques for managing multiple workspaces.

Do you have cross-workspace or cross-item dependency workloads? How do you deal with them?

Full experiment and technical details:

https://weaverstack.dev/guides/organising-microsoft-fabric-workspaces/

Happy to answer any questions!


r/MicrosoftFabric • • 12h ago

Administration & Governance New table overview pane with descriptions

8 Upvotes

When you open a table in a lakehouse, you now can see an overview with a summary and column overview just like Databricks has. What I don't get is where you can define the description of the table and columns. I tested the COMMENT in my sparksql query but that doesn't sync. Only entering a text using that new overview works.

The COMMENT data I entered in sparksql does show up in a new folder 'metadata' in the file view.

Is anyone else also testing this and did I miss something maybe?

New overview pane of a table
SparkSQL table definition using COMMENT
metadata folder with column COMMENT but no table COMMENT

r/MicrosoftFabric • • 22h ago

Administration & Governance Have semantic model refreshes become cheaper?

8 Upvotes

Maybe I'm going crazy, but it looks like semantic model refresh operations became cheaper around 13th November?

Looks like our weekend load (yellow) and weekday load (orange) both fell by ~20%.

Anyone else experienced this?

CU(s) per day for semantic model activty

r/MicrosoftFabric • • 8h ago

App Development Fabricator App Deployment - Change DB connections between environments

6 Upvotes

We have developed a simple MDM app using Fabricator that points to an existing SQL DB in a DEV workspace.

We now want to deploy this into a Production workspace and when we do it, the app should point to the SQL DB in the Production workspace.

When we publish the app to the Production workspace using Fabricator, it still points to the DEV DB.

If we publish using Deployment pipelines too, it continues to point to the DEV DB.

The only option I've found so far is to change the connection in the local Fabricator environment first to point to the Production DB and then deploy it into the PROD workspace but that seems like a risky process prone to mistakes.

Does a better process exist?


r/MicrosoftFabric • • 3h ago

Data Engineering How do you handle rows that fail a check today but will pass later (reference data not there yet)?

5 Upvotes

I have a daily batch, PySpark + Delta, medallion.

Some of my rows fail a check when I build a table, but they are not wrong. The reference data they need is just not there yet, and a couple of days later the same row would pass. So I have to keep them somewhere and retry them on every run.

How do you handle this?

- Where do the failed rows live?

- What exactly do you store for them?

- How do they get retried?

Is there a known pattern for this?


r/MicrosoftFabric • • 5h ago

Power BI Report Usage Metrics deleted by Microsoft?

Post image
5 Upvotes

Did anyone else experience that your usage metrics in the "new" usage metrics report are cut off like 3 days ago? We see only data for the last three days, while in the old usage metrics we see more realistic data for the last three months showing usage every day. Although this alone is already a strong indicator that there is a bug on #Microsoft side, I also double-checked whether someone deleted a report and created a new one with a new ID starting new usage metrics tracking, but this report ID has existed for months. For one case I even deleted the semantic model of this new usage metrics report so it was recreated on next new usage metrics report open, but it still shows only this data.
Is there any way to fix this? Or is this just yet another glitch in a long history of glitches on this toy data platform?


r/MicrosoftFabric • • 5h ago

Data Factory No failure bodies from Web.Contents in PQ?

5 Upvotes

Can anyone tell me what they do to troubleshoot API failures?

Consider a web connector operation like this:

let
    BaseUrl = "https://example.com",
    Response = Web.Contents(
        BaseUrl,
        [
            RelativePath = "/v1/items",....
        ]
    ),
    JsonData = Json.Document(Response)
in
    JsonData

... if this fails with 500 code or whatever, the reason phrase from HTTP may say nothing more than "internal failure". This is the thing that is prominently exposed in the Power BI logs and UX.

However this is a meaningless message. For most REST APIs there should also be a response body that has a full stack trace and other contextual messages.

However when I look in the gateway logs I can't find the HTTP response body for failures. I don't think it is presented even when enhanced diagnostics are enabled. What are PQ developers supposed to do for troubleshooting web connectors that fail intermittently? I have not found a good approach, either in prod or in dev. (It doesn't help matters that Fiddler recently stopped being "free forever". But even when Fiddler was free, it wasn't a great way to debug our PQ.)


r/MicrosoftFabric • • 12h ago

Administration & Governance What criteria do you use to certify items in Fabric (vs. just Promoted)?

4 Upvotes

Hi all,

We’re rolling out endorsement in our Fabric tenant and I’m trying to define a sensible certification process. Promoted feels straightforward: the owner decides it’s ready to share and flags it. But I’m struggling with what should be required for Certified.

I’d love to hear how others handle this:

  1. What are your must-have criteria before an item gets the Certified badge?
  2. Do you use different standards for different item types (semantic models vs. lakehouses vs. reports)?

r/MicrosoftFabric • • 12h ago

Security Workspace private link + Lakehouse with schemas: really not supported? Any ETA?

5 Upvotes

Hi all,

I'm designing a workspace setup with inbound public access denied (workspace private link), outbound access protection and CMK. The Security feature availability matrix lists:

Item Workspace private links CMK OAP
Lakehouse ✓ ✓ ✓
Lakehouse with Schema – ✓ ✓

So schema-enabled lakehouses don't support workspace private link. But the workspace private link support page just says "Lakehouse" and doesn't mention schemas at all.

A few questions:

  1. Is this still accurate? Has anyone run a schema-enabled lakehouse in a workspace with inbound public access denied?
  2. If it isn't supported, what happens in practice? Does it block setting inbound to Deny (InboundRestrictionNotEligible)? Can you create the lakehouse at all? Or does it work and just isn't officially supported?
  3. Is there an ETA or roadmap item for support?

This matters for us because new lakehouses default to schemas, and our engineering workspace needs to be locked down.

Thanks!


r/MicrosoftFabric • • 12h ago

Discussion New folders in Lakehouse?

3 Upvotes

Just saw 2 new folder in the lakehouse view, didn't read anything about this in the November Feature summary?