This is a pretty big one. No official announcement yet, perhaps they will announce formally at next week's conference... But if you take a look at some of the REST API endpoint documentation (e.g. this Create Lakehouse endpoint), you will notice a small, but impactful change (see image). You will see that you can now create items from a Service Principal account (which was previously not supported). What does this mean, you might be asking? Well, traditionally, when you create things like a Lakehouse in Fabric, you become the owner. A Service Principal (which can be created and managed in Azure Entra ID) is a generic user account, that can be now used to create these items. This makes it easier to automate creation of new items at different stages in a CI/CD pipeline. And means the 'Owner' is the Service Principal, not an individual. Is this something that you've been waiting for? Let me know how you'll be using it below 👇

My 60-day free trial is coming to an end... after 383 days (thanks Microsoft) 😂 Yours probably is too. The question is, are you prepared? What are your options? 1. You can purchase a F-SKU capacity from the Azure Portal, and reassign your existing workspaces to that new capacity. Or, 2. If you're still not ready to buy an F-SKU yet, the documentation states you can create a new trial capacity with a new user, and reassign your workspaces to that new trial capacity. 3. Any others? Let me know! Important things to note: - If you don't upgrade to a paid Fabric capacity before the end of the trial period, non-Power BI Fabric items are removed according to the retention policy upon removal (I believe this is 7 days soft delete, but double check, and also don't let it get to this!)

I’m at a crossroads with report creation in Fabric in a medallion architecture, weighing two approaches: - Unified Approach: Developing a single extensive semantic model that encompasses all data and measures, supplemented by light reports for ease of use and maintenance. - Diversified Approach: Crafting individual reports tailored to each specific use case. I’m mindful that a comprehensive model might strain performance, whereas separate reports may lead to complex maintenance routines. I’m seeking insights from the community on strategies or features within Fabric that facilitate an optimal balance between performance and report maintenance management. Thanks!

PART 1 There are some things that must be done in Snowflake before you can set up Microsoft Fabric Snowflake Mirroring. This Tutorial: Configure a Microsoft Fabric mirrored database from Snowflake (Preview) calls out what needs to be done in Snowflake, but not how to do it. If you are missing something in Snowflake, the connection setup will Fail, or you will see something like the attached image where the database you want mirror is greyed out. I'm no expert at Snowflake, but I'm going to share what I'm doing to get this working: 1) Log into Snowflake and create a User in Snowflake Called FABRIC_MIRROR: CREATE USER FABRIC_MIRROR PASSWORD = 'YourSecurePassword' 2) Then, l created a POWERBI_ROLE: CREATE ROLE POWERBI_ROLE; 3) I granted some privileges to the new POWERBI_ROLE: GRANT USAGE ON DATABASE_NAME TO ROLE POWERBI_ROLE; GRANT USAGE ON FUTURE SCHEMAS IN DATABASE DATABASE_NAME TO ROLE POWERBI_ROLE; GRANT SELECT ON FUTURE TABLES IN DATABASE DATABASE_NAME TO ROLE POWERBI_ROLE; 4) Then, I granted the POWERBI_ROLE to the FABRIC_MIRROR user: GRANT ROLE POWERBI_ROLE TO USER FABRIC_MIRROR; Next, I've got to work out how to add these Required Access Priviledges to Snowflake.

I wanted to monitor my Fabric Capacity. I've just got the trial, but plan on buying an F2 because it's the least amount to spend. However, I've read the terms "bursting," "smoothing" and "throttling" within the context of Fabric Capacities. So, I read these articles a couple times: Understand your Fabric capacity throttling - Microsoft Fabric | Microsoft Learn, and this: Fabric Capacities – Everything you need to know about what’s new and what’s coming | Microsoft Fabric Blog | Microsoft Fabric Then I Installed the Microsoft Fabric capacity metrics app - Microsoft Fabric | Microsoft Learn Now I can see the throttling (there's been none) and you know what I know about setting it up. I don't think I'll ever "see" bursting or smoothing" in the Fabric Capacity Monitor as those terms seem to just describe how Fabric "works" behind the scenes.