Josh Caplett’s Post

The Lakehouse is meant to be OPEN, meaning no single, proprietary engine should have preferred read/write access to that data at a cheaper rate. Once your data is in the lake, you should be able to choose the best tool for the task at hand without being locked into a proprietary solution. This is how you truly democratize data throughout the organization.

Fabric OneLake is NOT open format as Microsoft claimed. If you access data in OneLake from non-Fabric compute, you pay up to 3X! for reading and writing compared to Fabric compute. 

Confused by the Microsoft Fabric OneLake Pricing?   In our latest blog post, Dylan Ford explores Microsoft Fabric OneLake's dual pricing models. He will guide you through the intricacies of accessing your data and reveal the true cost implications.   🔍 He covers: Understanding OneLake: A look at Microsoft Fabric's integrated data services and the unique features of OneLake. Dual Pricing Models: An explanation of the "Redirection" and "Proxy" methods and how they impact your costs. Accessing Data Inside vs. Outside Fabric: Real-world analogies to illustrate the cost differences and potential pitfalls. 👉 Read the blog post: https://lnkd.in/g6sb9AS6

👀 Now more than ever, enterprises often have their eyes on security, cost, and lock-in as they consider how to store and govern their data. If you are thinking about Fabric’s OneLake for storing enterprise data, make sure you thoroughly understand the implications across these 3 key areas (especially if you think you might use that data now-or-in-the-future with other tools in addition to Fabric)

PSA: If you or someone you know is considering Fabric for your data platform or to build GenAI applications make sure you read the fine print or you may find yourself paying 3X for some workloads. Imagine burning your budget at 3X speeds when you're running in production at scale. 🤯 Read #aimpoint's assessment below 👇

This is very important to read. It describes Microsoft's pricing model for OneLake, which at surface value, isn't obvious. You really don't want to pay 3x more by putting data in OneLake.

This is a worthy read by Dylan Ford highlighting the cost implications of accessing data both inside and outside of Microsoft Fabric OneLake. The analogy of a credit card company's fee structure perfectly illustrates the complexities and potential pitfalls of these pricing models. Read how these pricing approaches can have a significant cost implication on your overall data strategy in the link below. #DataAnalytics #MicrosoftFabric #OneLake #CostManagement #AzureDatabricks https://lnkd.in/gMdXMv9M

At #MSBuild , Microsoft has a ton of new announcements regarding Microsoft Fabric. Here is Arun Ulag's blog post summarising these https://lnkd.in/eUbs3yXC #MicrosoftFabric

Microsoft #fabric external data sharing is now available! As a heads up, here are a few things to keep in mind: - The sharer cannot control who has access to the data in the consumer's tenant. - The consumer can grant access to the data to anyone, even guest users from outside the consumer's organization. - Data may be transferred across geographic boundaries when it's accessed within the consumer's tenant. Learn more about external data sharing in Microsoft #fabric here: https://lnkd.in/gMgExTUZ

Here's what new is in the Fabric world Announcing the public preview of task flows in Microsoft Fabric https://lnkd.in/danGVGeE #ThatTechieGirl #TechnologyAdvisor #Fabric #MSFTAdvocate #Microsoft #Data