
End-to-End Azure SQL Automation with Bicep and DevOps Pipelines
Learn how to fully automate the creation of an Azure SQL Server, database, and BACPAC deployment using Bicep and YAML pipelines—plus how to work around real-world issues
Learn how to fully automate the creation of an Azure SQL Server, database, and BACPAC deployment using Bicep and YAML pipelines—plus how to work around real-world issues
Last Friday, I had the pleasure of presenting a live session as part of the Microsoft Zero to Hero series, focused on a topic close to my heart: modernizing SQL workloads in Microsoft Fabric without starting from scratch.
Learn how to monitor your Dataverse-to-Fabric integration—whether via Synapse Link or Direct Link. From system table tracking to custom alerting, this article helps you ensure your data pipeline stays healthy and up-to-date.
Discover how to seamlessly connect Dataverse to Microsoft Fabric using the native Link to Fabric option. No infrastructure needed—just a few clicks to get your data flowing into a Fabric Lakehouse, ready for analytics and Power BI integration.
Learn how to integrate Dataverse with Microsoft Fabric using Azure Synapse Link. This step-by-step guide walks you through the setup using Bicep, YAML pipelines, and best practices for a scalable, Azure-native data pipeline.
Compare the two official ways to sync Dataverse data with Microsoft Fabric—Link to Fabric (Direct) and Link via Azure Synapse. Understand the pros, cons, use cases, and cost differences to choose the right path for your BI architecture.
Introduction I'm currently working with a visionary Swedish company that wants to move forward with Microsoft Fabric... it’s this innovative spirit that has led them to adopt Fabric as their core data platform. As part of their digital ecosystem, they Dynamics 365 to run business operations. Naturally,
Discover why Microsoft Fabric is a strategic upgrade for organizations using Dynamics 365. From tighter integration to simplified architecture, we break down the business case for moving from other data platforms
A while ago, I wrote “Why Microsoft, WHY!!!!?” about Fabric’s shift from TMSL (JSON) to TMDL (YAML-like). That sparked debate—some said both are API-supported, and reports stay JSON. So, I did my homework! This follow-up confirms what’s true, what’s not, and what I uncovered.
Struggling to find the elusive artifactId in Fabric Data Pipelines? You’re not alone! This critical identifier isn’t the lakehouseId, and worse—it’s hidden from the API. Discover where it actually resides, why it’s breaking CI/CD automation, and why Microsoft must make it accessible.
Introduction For those of us automating Microsoft Fabric, life was good. TMSL (Tabular Model Scripting Language) used JSON, which made programmatic manipulation easy. Need to apply CI/CD? No problem! JSON’s structured format, clear syntax, and robust tooling made it a natural fit. Then came TMDL (Tabular Model Definition
Navigating the Shift from Synapse explores the challenges enterprises face when evaluating their next data platform. From cost predictability vs. pay-as-you-go to performance; I share insights from a Fabric Data Analyst in a Day, where the debate between Fabric and Databricks took center stage