Microsoft Fabric Updates Blog

Announcement: Eventhouse Standard Storage Billing

As part of the consumption model for Eventhouse, we are enabling Standard Storage consumption. This change is scheduled to start rolling out the week of September 16th. This means that you will start seeing billable consumption of the OneLake Storage Data Stored meter from the Eventhouse and KQL Database artifacts. For details on all things KQL Database and Eventhouse consumption check out this article.

OneLake Standard Storage used to persist and store all queryable data. When you set the retention policy, you affect this storage tier. For instance, if you need to maintain 365 days of queryable data you can set the retention to 365 days. This storage tier is comparable to the Azure ADLS (Azure Data Lake Storage) hot tier.

The amount of standard storage is controlled via your retention policy. To understand how to configure you retention policy check out this article

You can monitor how much OneLake Standard storage you are utilizing via the Microsoft Fabric Capacity Metrics App under the storage tab. Usage from KQL Database and Eventhouse will be reported via the KustoStandardStorage Operation Name. The “Billing Type” will change from “Non-billable” to “Billable”.

Fabric Capacity Metric App

Useful Links

Eventhouse/KQL Consumption

Fabric Capacities

Fabric Pricing

Fabric Capacity App

Caching Policy

Eventhouse Minimum Consumption

Related blog posts

Announcement: Eventhouse Standard Storage Billing

September 26, 2024 by Ye Xu

Fast Copy in Dataflow Gen2 is now General Available! This powerful feature enables rapid and efficient ingestion of large data volumes, leveraging the same robust backend as the Copy Activity in Data pipelines. With Fast Copy, you can experience significantly shorter data processing times and improved cost efficiency for your Dataflow Gen2. Additionally, it boosts … Continue reading “Announcing the General Availability of Fast Copy in Dataflows Gen2”

September 26, 2024 by Guy Reginiano

Now you can set up Data Activator alerts directly on your KQL queries in KQL querysets.