What Data Does Eventhouse OneLake Availability Copy?
You have a Fabric workspace that contains a Real-Time Intelligence solution and an eventhouse. Users report that from OneLake file explorer, they cannot see the data from the eventhouse. You enable OneLake availability for the eventhouse. What will be copied to OneLake?
Community Insight
The question tests the default copy scope of Eventhouse OneLake availability, and the trap is assuming that enabling it automatically backfills existing eventhouse data.
Eventhouse OneLake availability exposes eventhouse data in OneLake so users can access it through OneLake file explorer. This page explains that the feature copies only newly ingested data by default unless existing-table backfill is explicitly selected.
The most common wrong answer is D, because candidates see that the UI offers Apply to existing tables for historic backfill and assume that option is always included when OneLake availability is enabled.
Community Discussion (51 comments)
- Existing tables aren't affected. New tables are made available in OneLake. https://learn.microsoft.com/en-us/fabric/real-time-intelligence/event-house-onelake-availability#how-it-works
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Enabling OneLake availability on an eventhouse makes eventhouse data available in OneLake for OneLake file explorer, but the default copy scope is forward-looking: newly ingested data is written to OneLake after the setting is turned on. Existing tables remain in eventhouse storage unless the administrator explicitly selects the Apply to existing tables option to perform a historic backfill. Because the stem only says you enable OneLake availability and does not mention that backfill choice, the data copied is only new data added to the eventhouse. This matches Microsoft's documented behavior that existing tables aren't affected by merely enabling the feature.Why the Other Options Are Wrong
A is wrong because OneLake availability is not limited to new databases added later; it applies to the eventhouse or database scope you enable and its new data. B is wrong because enabling the feature does not copy only existing data; without backfill it copies new data, not historic data. C is wrong because enabling OneLake availability does cause data to flow to OneLake—new records are copied. D is the tempting choice because the UI and docs mention Apply to existing tables, but that checkbox is an extra action for backfill and is not stated in the question.Community Comment Notes
The comments split along documentation versions: Tuki93 and IshtarSQL read the stem literally and note that "Existing tables aren't affected" and only new data is synced. Several other learners, including Bin_Hashim and CMDev, vote D because current docs describe the Apply to existing tables backfill option. The key distinction is that backfill must be explicitly selected; merely enabling OneLake availability does not make existing eventhouse data appear in OneLake. The question's wording therefore supports E, even though the documented option can produce D when used.Official Reference
Exam Strategy
Read for an explicit backfill instruction: if the stem only says you enable OneLake availability, do not assume existing tables are included. The Apply to existing tables checkbox is an extra action for historic backfill, so choose the new-data-only option unless the question states that backfill was selected.
Frequently Asked Questions
Does enabling OneLake availability backfill existing eventhouse tables automatically?
No. Existing tables are copied only if you select the Apply to existing tables option for historic backfill; otherwise only new data is copied.
Why do some community answers choose D instead of E?
Because current docs mention an Apply to existing tables backfill option, but the stem never says that option was selected, so default behavior remains new data only.