<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>FinOps on Rework-Space</title><link>https://rework-space.com/blog_tags/finops/</link><description>Recent content in FinOps on Rework-Space</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 12 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rework-space.com/blog_tags/finops/index.xml" rel="self" type="application/rss+xml"/><item><title>Beyond Separated Billing: Merging Azure Infrastructure and Databricks DBUs with FOCUS</title><link>https://rework-space.com/blog/2026-08-12-merging-azure-databricks-costs-with-focus/</link><pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate><guid>https://rework-space.com/blog/2026-08-12-merging-azure-databricks-costs-with-focus/</guid><description>The problem Every month, your Databricks platform produces two bills. Azure invoices the virtual machines, local SSDs, premium storage, and network egress your clusters run on, while Databricks meters DBU consumption in its own system tables. The number everyone actually wants, the true cost of a single workload, exists in neither.
So teams do what teams always do: they export both datasets to Excel and reconcile them by hand. It is slow, it is error-prone, and it has to be redone every month because hyperscalers restate billing data retroactively.</description></item></channel></rss>