The recording of 'Microsoft Fabric: What's new and what's next' from #MSBuild is now available: https://t.co/eOp5YmdvlQ. So many new #MicrosoftFabric features released!
Proud to see #AmestoSolutions mentioned as a trusted Fabric Featured Partner 🥹
@JoshCaplan1984 Love seeing these features. However, restricting feature to SKU is really unfortunate. This security feature costs «nothing» using PaaS in Azure. If we want to combine the worlds we need to comprimise security in Azure. Unfortunate for small companies and the development process.
@Datatouille @justblindbaek @GregBaldini@NickyvV Based on the total CU you are 51% above F2 capacity. My guess is that you will need to pay for this CPU burst as you will not smoothen it out over time. I bet the price is more 0.21, but still fast and cheap. Bursting will be the hardest pricing element when turning cap on/off
@kurtbuhler “what of my problems/pain points does this solve?”. 80 pct of the use cases are not solved by new feature roll outs. If you are waiting for the perfect solution you will not start to build anything. Great things about new features, you will find them when you google your problems
@Heptabase Love the rapid feature development! The mobile experience keeps getting better. Are tag views (table/kanban) for mobile browsing on the roadmap?
@s_debruyn@JustynaLucznik Fantastic blog series! Great to see a dbt example in Fabric. Any thoughts on how to run the transformations in Fabric on a schedule? ADO pipelines, import git and run in notebook, similar to dbt task in databricks workflows?
@milicevica23@CharlesWebb22@ta_rente@getdbt@msFabric Maybe it's possible to run dbt project inside a notebook? 🤔😅
A native dbt connector similar to the one in databricks workflows inside pipelines would be nice.