Fabric Quality of Life Update: No More Default Semantic Models!

Another quick post, because today is an important day for everyone working with Fabric and Power BI!

Last month, Microsoft announced they are Sunsetting Default Semantic Models: Yaay! 😀
Today marks that day: No more automatic child semantic models!

The info message also states only a SQL endpoint is created

So now whenever you create a warehouse, lakehouse, SQL database, or mirrored database, you only will get that item, and the SQL analytics endpoint connected to it.

No more default semantic models!

This means from now on you always have to manage the semantic model yourself, whenever you create one of the above items.

What about my existing default semantic models?

To be clear: existing (default) semantic models are not affected (yet!). But by the end of December (2025) they will be decoupled from their connected item, and you will have to manage that model manually.

Conclusion

Now that Fabric is getting more widely used, the demand for stronger governance and greater control over semantic models was growing. This change takes away the auto/generated models and gives you more control in the creation of your semantic models.

To read more about this:

• Take a look at the documentation of semantic models
• Or at the blog post announcing the deprecation

There's more information in those links about the exact changes and menu-items going away, the timeline and future updates/blog posts.

Changes to Fabric Tenant Settings for API's

If you are a Fabric Administrator, either for your own tenant / company or for customers, you might get the weekly emails from Microsoft 365 Message center. I've mentioned this briefly in an earlier post about Changes to default values for a tenant setting for SQL Database.

I advice you to at least have a look through that weekly email and check for any Fabric or Power BI updates. An example update you can get is like the below. This screenshot is actually from the Message Center itself, not from the email.

The problem with the M365 Message Center is that only people with privileged roles can access it. And not all updates shown there are communicated in other ways by Microsoft. Sometimes they write a blog post, like this one: Cognitive services and Azure ML will be fully retired, sometimes there's a specific info message in Fabric, or there might be a new tag in the tenant settings, but more often you don't see any other communications around the topic.

So if you are not a Fabric Admin, you probably haven't seen the message I want to inform you about today, so that's why I'm writing this post!

Call To Action

TL;DR

Two new admin toggles are live in the Fabric Tenant Settings, under Developer settings. Check your Tenant Settings and see how they relate to your policies and governance!

Action Required on API Access Setting Split

Microsoft Fabric is changing how service principal access to public APIs is controlled. The existing all-or-nothing tenant setting was split into two separate settings — giving us admins more granular control, but also introducing a change you might need to act on after August 1, 2025.

The previous setting

What Has Changed?

From mid-May to early June 2025, the previous admin setting for public API access via service principals was replaced with:

1. Service principals can create workspaces, connections, and deployment pipelines
   → Governs “global” APIs not tied to specific Fabric permissions (e.g., workspace creation).
   → Disabled by default.

2. Service principals can call Fabric public APIs
   → Governs APIs protected by the Fabric permission model (CRUD access to workspaces, folders, etc).
   → Enabled by default.

The new settings

Why This Matters

This split is a long-needed improvement: previously, disabling API access to protect core resources also blocked developers from using safe, permission-based APIs.

Now, you can lock down the high-risk parts (like workspace creation) without blocking everything else.

But: Microsoft may have enabled the second setting (permission-based API access) by default in your tenant unless you opted out.

Why should I care? You might have service principals running scripts to create workspaces, deploy certain items or manage workspace objects for example.

What You Should Do Now

• Check your Fabric admin portal for the two new settings under Developer Settings

• Before August 1, 2025, you could've shown a checkbox labeled "Accept Microsoft’s change to enable...", and you want to keep permission-based API access disabled, uncheck the box and hit Apply

• Check the values of both settings

Timeline Recap

• May–June 2025: Settings split rolls out

• July 31, 2025: Last day to opt out of automatic enablement

• August 1, 2025: Microsoft finalizes the transition

Conclusion

In case you are running a monitoring solution that keeps a history of Tenant Settings, for example FUAM, you can check the Tenant Settings history and see when the change became active in your tenant. If you don't have such a monitoring solution, I highly recommend checking FUAM out. You can get started with setup and deployment of the solution with a few hours of work.

I spotted this setting shift on telemetry around June 1 in my tenant:

There were some changes in how tenant settings can control access for Service Principals to API's. Make sure to check your settings and adjust them accordingly.

If you want to read more info on the exact workings of the tenant settings, have a look at the Tenant Settings documentation.

Did you already notice these changes and take action?

Let me know in the comments.

My session at Fabric Week by ESPC - Q&A

On Tuesday, May 27th, I had the honor of presenting a session for the Fabric Week at ESPC:

A Day In The Life Of A(n Accidental) Fabric Administrator.

The session was recorded and is already available on YouTube, but unfortunately we ran out of time before I could answer all the questions during the session.

Thanks to ESPC and Seán Colleran I got hold of all the questions asked during the session, and I will provide answers in this blog post where I can.

Q&A

Without further ado, let's go to the questions:

1. How do you enable Fabric mirroring from the tenant settings?
   You don't have to enable mirroring specifically, but you do need to enable the creation of Fabric items in general: Enable Microsoft Fabric for your organization. You also need a workspace with an active Fabric capacity (trial or any F-SKU).

2. Can we mirror PostgreSQL with that option?
   Yes, you can mirror PostgreSQL, but only Azure Database for PostgreSQL flexible server. Keep in mind that currently mirroring doesn't support Azure Database for PostgreSQL flexible server behind an Azure Virtual Network or private networking.

3. As a Fabric admin, can I scale Fabric Capacity from F64 to F128, for example?
   For scaling only, being a Capacity admin should be enough, as explained in scale capacity.
   

4. What’s the best way to implement stop/start on Fabric Capacity?
   You might be able to, depending on the rights you have in the Azure Portal.
   To be specific, you need to have at least contributor rights on the Azure subscription. Specific permissions (to create a capacity) for an RBAC role are explained here.
   You can use the Fabric Capacities REST API's to Pause/Resume the capacity. You can call these API's with PowerShell, but also with Azure Data Factory, a Logic App, or from within a Fabric notebook. For the latter, you need a different capacity then the one you want to pause/resume though.

5. I want to manage capacity units. How can we manage the autoscaling function?
   If you mean Autoscale Billing for Spark, that is currently in preview and only controls the spark compute. There is no other option for autoscaling the SKU-size in Fabric. 

6. We have multiple customers on one tenant. Each wants to monitor their own Fabric capacity. What’s the best practice for setting up the Capacity Metrics App?
   In the Capacity Metrics workspace, you can create multiple copies of the report and put a report filter on a specific capacity. Then give a user specific permissions to only view that report.

7. Is there a way to reset tenant settings to “default” or Microsoft-recommended settings?
   Unfortunately not. You can check the documentation for the Tenant settings index, some settings mention a default value.
   If you are able to set up a totally new (test) tenant in Azure you could check the default values for the Tenant settings in that tenant.

8. On the permissions level, how do you differentiate between non-production and production environments?
   Usually this is done by using workspaces for dev-test-prod. On a workspace level you can easily manage permissions. Within Fabric you can use Deployment Pipelines to transfer items between the dev-test-prod stages.

9. I’m a user. Our new admin has set up Fabric Capacity (F2 pay-as-you-go). I have permission to create workspaces, but the Fabric Capacity option is greyed out.
   To be able to assign workspaces to a capacity you need at least Contributor permissions. The admin of a capacity can assign users on the Capacity settings page in the Admin portal:
   

   

10. Who can we scale up Spark clusters? How can we ensure only admins can do this?
    So go from a small Spark pool to a medium Spark pool.
    A workspace Admin can change the settings for Spark workloads in the workspace settings:
    

    
    
    They can adjust the current pools and create new ones. You can't limit it further, so every workspace Admin can do this.
    If you uncheck the last option, Members or lower can't change the settings on a session-level.

11. What’s the best way to implement a stop/start schedule for Fabric — e.g., only running during the day?
    Please see question 4.

12. For notification activities in a pipeline: I want to use Teams notifications. Do I need an Office license or a specific Teams license?
    To actually set up a working Teams activity, you need a Teams license, and a channel or chat to post it to. I was able to add the activity without a Teams license, but I can't select a channel to post to in that way.

13. Can a workspace admin restrict a tenant admin from accessing a specific workspace?
    No. A tenant (Fabric) admin can always go to the Admin portal and gain access to any workspace in the tenant.

14. What is the best alert mechanism? As a Fabric Admin, I want to know about overloads as soon as possible.
    There are a few options, I'll let you decide on the best one to use.
    On the Capacity settings page you can set up a notification for X% capacity usage.
    

    

    Somewhat similar, but more customizable, you can also set up an alert on the Capacity Metrics app with Activator (Real-Time Intelligence) and send a Teams or Outlook message.
    

    
    
    Not an alert mechanism per se, but on the capacity settings page, you can also set up Surge Protection, which lets you limit the compute consumed by background jobs. This way you can make sure the capacity doesn't overrun from background jobs.
    
    
    

15. Is there a way to kill a process in interactive operations?
    For most interactive operations you can't, like DAX or XMLA queries. Lakehouse or Warehouse queries can be stopped with the KILL command used in T-SQL.

16. If I pause a capacity with over-usage, will I see in advance how much I'll have to pay?
    No, not out-of-the-box. You could calculate the amount of overage, CU's and thus price, mainly from the Capacity Metrics app. But that's a manual calculation you'd have to do upfront.

17. Is there a way to connect that monitoring to a running Grafana?
    Apparently you can connect a Managed Grafana instance to a KQL database (eventhouse) in Fabric. It's explained in this post.

18. Do you need to be paying for Purview to use the Fabric Purview Hub reports?
    The Purview Hub reports are included as part of the Admin Monitoring workspace, so you don't need to pay extra or for a Purview license.

19. Is there a way to monitor the count of accesses per user on a report (like in PBI Report Server ExecutionLog3)?
    You can get this data from the default Usage Metrics Report, generated when clicking the below option on a report.
    

    
    
    You can also get all activity data (from all reports) out of the Activity Log, for example with the REST API - Get Activity Events. Keep in mind though, this has a data retention period of 30 days.
    
    

20. I understood the admin monitoring semantic models were locked — how did you create a custom version?
    You can indeed not edit the model itself, but as a Fabric Admin you do have Member access to the Admin Monitoring workspace, and thus Build permissions. So if you connect to the semantic model from Power BI Desktop, you can extend it (create a local model) with your own data. You would also be able to do this with Viewer access and build permissions.

21. Pro vs. Premium per-user license: What are the three most important reasons to choose Premium per-user over Pro on a Fabric capacity?
    It depends? 😉 In most cases, I would say if you already have Fabric, PPU is not necessary anymore. But of course, there are edge cases where it might benefit to have a PPU, I can think of one: Model size limits in low F-SKUs are pretty low (3 GB), in PPU it's 100 GB
    

22. Have you seen examples where the 30-day limit for admin monitoring has been extended by updating a custom Lakehouse and running reporting off that?
    Yes, you can export the Admin monitoring data to a Lakehouse. The solution I called out in my presentation is FUAM, which doesn't specifically extract the data from the Admin monitoring workspace, but it gets similar data from the rest of the tenant.

23. If I am not a Fabric admin, how can I get access to admin monitoring?
    By default, only users with the Fabric admin role (or higher) will have access. But the Fabric admin can also give other people (Viewer) access to the workspace.

24. Is there an API to extract user views on each Power BI report page?
    Yes, the Activity Events API, see question 19.

25. The 30 days... is that the same as the Dashboard Usage Metrics?
    Yes, right now, the retention is similar in all the Power metrics reports, except for the Capacity Metrics, which holds 14 days of data.

Microsoft Fabric Documentation (for Admins)

Maybe this topic is not the most sexiest of them all, but it certainly has the same (or maybe even more) amount of value for YOU!
And.. another post on my favorite topic: Governance and Administration!

With all the Fabric announcements in the last months, some of the Admin announcements might have slipped through. As you might know, the Admin part of Fabric is dear to my heart. I've posted about it earlier here, here, here, and here, to name a few 😀.

Earlier I wrote about the default domain settings, changes to the default tenant setting value for SQL database and I also covered the (rights of the) Fabric Adminsitrator role. Today I want to talk about a more meta-topic: existing documentation on Microsoft Learn, and of course specifically for Admins.

Microsoft Fabric documentation

By this point, I assume you've read this far (and perhaps a few other posts as well), I guess you've heard of Microsoft Learn. 😁 

If not, go there now: Microsoft Fabric documentation!

It is full of so much good content, to name a few:

• Overview 
• What is Fabric: The B.A.S.I.C.S.
• Security in Fabric: You might not be aware, but there's so many things you can do to tweak and adjust security for your organization!
• Concepts 
• Choose a Fabric data store: Choose between a Lakehouse, Warehouse, Eventhouse, or SQL Database
• Copilot in Fabric: In what workloads can you use Copilot and what are the prereqs?
• Capacity and license types: This explains concepts like a tenant, capacity, workspace, SKU's, Power BI licenses, etc.
• Tutorials
• Use taskflows to build solutions: I'm curious, who really uses these in their environment?
• End-to-end tutorials: Those tutorials where the corner-stone of getting started with Fabric after it was announced. They still provide enourmous value, although sometimes the steps can be very basic.

And there's so much more:

Ok, I know... Sometimes the documentation is, let's say, a bit behind the latest features in Fabric, right?

It may be outdated, there might be typo's, it might even be wrong in some points.

Instead of (only) complaining, you should do something about it! 😏

Did you know you can edit those pages (make sure you're logged in to your MS Learn account):

After clicking that pencil on a doc page, you end up at GitHub where you can make changes to the document. You do need a GitHub account, know how to fork the repo and create a Pull Request when you're done (if you don't know how to, read this tutorial on GitHub 101).

Microsoft Fabric documentation for admins

Now on to my favorite part: the Admin stuff! 😁

Go to Microsoft Fabric documentation for admins to learn all about admin settings, tools, the admin portal, admin roles, and monitoring and management to name a few.

What is the admin monitoring workspace

The admin monitoring workspace is a specialized environment designed for Fabric administrators to monitor and manage workloads, usage, and governance within their tenant. Using the resources available within the workspace, admins can perform tasks such as security audits, performance monitoring, capacity management, and more.

It recently got a revamp on the design side and now looks way better.

The information contained in the report is on a fairly basic level, but you can still get some good insights out of it.

Next to that, you can also connect to the semantic model and extend it.

Closing

As you see there is a lot of information available on Microsoft Learn.`

Do you think the documentation on Microsoft Learn is valuable? Have you used it?

Does it need improvement? If yes, on what points?

Let me know in the comments!

Governance & Administration - Default Domain settings

I'm picking up my favorite topic again: Governance and Administration!

With all the Fabric announcements in the last months, some of the Admin announcements might have slipped through. As you might know, the Admin part of Fabric is dear to my heart. I've posted about it earlier here, here, here, and here, to name a few 😀.

So in the next weeks I am going to highlight a few things with short, informative posts.

Last week I wrote about the rights of the Fabric Administrator.

Today I want to make you aware of a default value of the domain settings inside Fabric.

This default value might not be the best value for you.. 😉

Domains in Fabric

A short introduction to Domains: they are essentially a way of managing and structuring your data across the organization. You can logically group together data in workspaces. A logical grouping can be business units, areas, fields, solutions or actually whatever works for you. It shouldn't be something a Fabric Admin decides on his own. Ideally business and / or enterprise architects with the data owners (if any 😐) should implement the design of domains, subdomains and owners. People from you Center of Excellence (again: if available..) would be a good fit to include in this discussion.

In case you need some help or guidance on how to set up your domains, there's a nice article that can help you get started: Best practices for planning and creating domains.

Default Domain Settings

Check your defaults! I've said it multiple times, always check default settings in your tenant, be it in the tenant settings or the domain settings.

When you create a domain (either with or without adding a domain admin explicitly), you end up with the default settings applied to that domain. Let's check what that involves.

After creating your domain and navigating to the settings you can SHOULD set the Contributors of the domain.

By default, it is set to The entire organization. I would limit it to either of the other options. Preferably tenant and domain admins, but if you have a group of people from Finance that you want to allow to add workspaces to the Finance domain, I'm happy with that too. Just don't use the default setting 😀

Luckily there's one more caveat to this that restricts it to hopefully a sligthly smaller group: the documentation points out you also have to be a workspace admin to be able to use this feature, so that limits it to people that have an admin role in the workspace.

One more reason to not give everyone the admin role in your workspace by default!

Next to that, you can also audit for these changes by checking the audit log for Fabric, specifically the UpdateDataDomainFoldersRelationsAsAdmin operation, which gives you the activities when someone assigns (or unassigns) a workspace to/from a domain.

Conclusion

Domains give you a good option to manage and group the content in your organization.

Just be aware of the default settings when you create one. Set the contributors to the tenant and domain admins, or a security group, just don't use the default!

Let me know what you think, have you seen this default setting and more importantly, did you change it in any of your domains?

Governance & Administration - Fabric Administrator Role

It's been a while since I've written on a regular cadance, so I'm picking up my favorite topic again: Governance and Administration!

With all the Fabric announcements in the last months, some of the Admin announcements might have slipped through. As you might know, the Admin part of Fabric is dear to my heart. I've posted about it earlier here, here, here, and here, to name a few 😀.

So in the next weeks I am going to highlight a few things with short, informative posts.

Today I want to talk to you about the Fabric Administrator (role).

• What rights does an Admin have?
• Are there more people that also have these rights? (Hint: YES! 😉)

Toady, I'm not talking about the governance aspects of the Admin, the Tenant settings or the Admin portal in general. I'll leave that for a next time. Or read other posts, for example by Marc on other roles and controls in Fabric or the delicate balance of governance and collaboration.

Manage Fabric Administrators

Users with this role can manage everything in Fabric, so from the Admin portal, to workspace access, and have also read access to various other parts in the Office and Azure ecosystem.

I encourage you to check who are assigned this role, because it should only be a handful of people in my opinion. You can check this in the Azure portal, under Entra ID > Roles and administrators.

Alternatively you can also search for it in the top search bar and go there directly.

Looking at the description of the role, we can see a few interesting things:

(As an Admin,) You can go to Azure and O365 Service Health to check for potential status issues with those services. You can also check and file (Premium) support tickets, depending on the license/capacity you have.

I especially want to call out the last row in the permissions:

The link there reads: microsoft.powerApps.powerBi/....

Power Platform Administrator

Now let's take a look at the Power Platform Admnistrator role description:

You might have noticed the same path there: microsoft.powerApps.

So this means, everything "below" PowerApps is also accessible, so the Power Platform Admin can also access and manage the same things the Fabric Admin can!

I also encourage you to check the people assigned to this role 😀

Just In Time Access Roles

Depending on your organizational settings, Privileged Identity Management might be enabled.
This means that people might need to activate the Fabric Admin role (for a period of time) before it becomes active. In the below screenshot you can see that Ernst and me have the role permanently assigned for Powerdobs.

But if I'm working as a consultant it usually is on a need-to-have bases, so I can e.g. activate it for 1, 2 or 8 hours. 

Looking at the picture above, you can see that there's Active and Eligible assignments. Depending on the settings and activity, people might have the PIM-role, but not activated at the moment.

Wrap up

To complete the list of access to Fabric, the Global (tenant) Admin role also has access to everything in Fabric:

• Global Admin
• Power Platform Administrator
• Fabric Administrator

People with the above roles have the same rights as the Fabric Admin.

Did you know the Power Platform Administrator has those rights?

Do you think I missed any information in this blog?

Please let me know in the comments below.

Governance & Administration - Ownership Takeover for Fabric Items

It's been a while since I've written on a regular cadance, so I'm picking up my favorite topic again: Governance and Administration!

With all the Fabric announcements in the last months, some of the Admin announcements might have slipped through. As you might know, the Admin part of Fabric is dear to my heart. I've posted about it earlier here, here, here, and here, to name a few 😀.

So in the next weeks I am going to highlight a few things with short, informative posts.

Today I want to quickly show a new feature that was just introduced, but long awaited for!

Ownership takeover for Fabric items!

Yes, you read it right, you can now TAKE OVER OWNERSHIP in Fabric! 😁

In a workspace, go to the ellipsis of the item (the 3 dots), and go to settings.

In the settings of the item you can see the Take over button:

Clicking that will show a pop-up and will start the transfer of ownership.

After a few seconds (that was my experience for the handful items I tried) you will get the notification it succeeded.

After that the (Take over) button has disappeared and will show up for the original (and other) users.

A few things to be aware of:

• You need read and write permissions to the item you want to take over
• That means a Contributor or higher role in the workspace
• Depending on the item you transfer, you might need to set up/refresh credentials for connections, as explained here
• The old way of taking ownership of Power BI items will still remain the same
• Mirrored databases are not supported (yet)
• If you're taking over a pipeline that execute's other items (like a notebook), you have to take over ownership of that item separately

For more info check the MS Learn docs: Take ownership of Fabric items.

Wrap up

This is of course especially helpful when the creator of an item left the company or that account is locked for whatever reason.

What's next you ask? The API for takeover is not yet available, and you also can't switch to a Service Principal yet. It only switches ownership to the current user at this moment.

Have you tried this feature yet?

Let me know what you think!

Closing out on 2024

It's the holiday season again, already!

This year has been marked by significant advancements in Microsoft Fabric, and Power BI in specific, and I've had the privilege of engaging with these developments both personally and professionally.

Blogging

I can say I haven't been that active on my blog, I always have a lot of plans for the new year, but motivation is still not easy.. 😆 Let's not make plans this year, but just start blogging for myself and not for others or the views, and see what that brings.

5th Year MVP

One of the highlights of the year was being recognized once again as a Microsoft MVP. It’s a privilege to be part of this amazing program, and I’m very grateful for the opportunities it provides, to share knowledge, collaborate with brilliant minds, contribute to the data community and create new friendships.

Microsoft Ignite 2024: A Glimpse into the Future

One of the biggest events this year was Microsoft Ignite 2024, held in Chicago. The conference had some great innovations, with the number one being the introduction of Fabric SQL Database (in preview). This developer-friendly, transactional database, based on Azure SQL Database, offers seamless creation of operational (OLTP) databases within Fabric. Its integration with OneLake ensures near-real-time data replication, bridging the gap between transactional and analytical processing. 

Another noteworthy feature introduced was the Metrics Hub (also in preview), setting a new standard in how organizations define, track, and share KPIs. This centralized management system integrates effortlessly with Power BI, promoting consistency and enhanced collaboration across teams. 

Community Engagements and Speaking Opportunities

This year also provided new opportunities to connect with the data community through various speaking engagements. Events like DataGrillen in Germany and the 1st Fabric Conference in Europe were particularly memorable. Sharing insights on topics such as Administration and Governance in Fabric, and engaging in lively discussions with fellow data enthusiasts, was both fulfilling and inspiring. This extended beyond sessions, with early morning runs and social gatherings strengthening the relationships with old and new friends in the community. 

Looking Ahead

As we are moving into the new year, my agenda is already filled with promising developments. The upcoming Fabric February 2025 event in Oslo, Norway, is an occasion that promises to bring together the best minds in the industry. And in March the MVP Summit in Redmond will be another highlight!
It's an exciting time to be part of the data community, and I look forward to continuing this journey with all of you, exploring new technologies, sharing knowledge, and fostering the collaborative spirit that defines our field. 

Thank you for being a part of this year's journey. Wishing you all a great New Year's Eve and an insightful 2025 ahead!

Nicky. Out.

P.S. I should mention that I did use AI to create a summary of events of my blog and my LinkedIn posts. I used that as a basis for this post.

Microsoft Ignite 2024 - My Key Highlights

Last week was the annual Microsoft Ignite conference in Chicago. In this blog, I will take you through my most important highlights of the sessions.

Fabric SQL Database (Preview): The future of SQL in the cloud

Let's get straight to the point with the biggest announcement: Fabric SQL Database! 

SQL Database in Microsoft Fabric is a developer-friendly, transactional database, based on Azure SQL Database, with which you can easily create an operational (OLTP) database in Fabric. In addition to the Fabric Lakehouse and the Warehouse, you now also have an efficient SaaS SQL database at your disposal as a developer with the performance of a transactional database and under the hood a(n extra) storage that is optimized for analytical purposes (Delta Parquet).

SQL Database in Fabric is:

• The home of OLTP workloads in Fabric
• Easy to configure and manage
• Set up for analytics by automatically replicating data to OneLake in near-real-time
• Based on the underlying technology of Mirroring in Fabric
• Under the hood, the same as Azure SQL Database, plus you have a web-based editor in the Fabric portal

With the introduction of Fabric SQL Database, Microsoft is taking traditional database management to a new level:

• Simple and secure architecture: Automated management and scaling optimizations
• Source control integration and CI/CD support: Essential for modern DevOps processes
• Capacity billing: Pausable compute resources ensure cost efficiency
• Unique cross-platform capabilities: Perform JOINs across databases, warehouses, and lakehouses

In addition to SQL Database in Fabric, the next version of SQL Server was also announced: SQL Server 2025. It is currently in Private Preview. It also supports mirroring to Fabric.

Metrics Hub: Standardized Metric management in Fabric (Preview)

The introduction of the Metrics Hub in Fabric is a new standard in how organizations define, track, and share KPIs. This new approach integrates seamlessly with Power BI and provides centralized management for metrics, enabling consistency and better collaboration. You might be thinking, this sounds familiar? You are! 😊 First there was Metrics, then Goals, and now the Metrics Hub where you can create Metric sets.

The advantage of being able to create and share metrics centrally is that you still have that one single version of the truth. Users can then use these measures in Power BI reports. But developers and data scientists can also use them in notebooks, using Semantic Link (Labs)!

Fabric AI Capacities

There will be an option to run all AI (=Copilot) compute on a separate capacity, so that other Fabric workloads are not affected by the use of Copilot. You still need at least an F64, and it's not available in all Azure regions, so be sure to check the Copilot FAQ for all your questions.

Fabric Org Apps

Org apps is a new item in your workspace, which now allows you to create an app as you did before by publishing an App in your workspace. One of the benefits of this is that you can create multiple Org apps per workspace!

In addition, you can customize more things like the design and behavior of the app. However, you can still only add items from the current workspace.

It is important to know that there is a tenant setting for Org apps that you need to activate. You can also use Org apps with a trial capacity.

Some other important updates for org apps compared to workspace apps:

• In addition to Power BI reports, you can now also add Fabric notebooks and real-time dashboards
• The distribution of org apps has been simplified, because access to underlying items (e.g. semantic models) is also applied, even in other workspaces. Users will therefore receive read access to all items that are dependent on the items in the app. These rights will also be removed when a user is deleted. There are a few exceptions, so check this.
• The items in an Org app are no longer a copy of the item, but the original items from the workspace
• Check all the differences between workspace and Org apps here

This week, an extensive blog about Org apps was also published where you can find even more information.

Power BI

• The biggest update by far: write-back with User Data Functions: native write-back integration with reusable functions and new options to link these to buttons in Power BI, with which you can update data in a source
• In the Pipeline activity, you can now refresh a semantic model at table and partition level
• Dataflow Gen2 updates: this item will soon also be supported in CI/CD (in source control and deployment pipelines)

OneLake

At the heart of Fabric is OneLake, a single central repository for all data, regardless of format. Some new developments:

• Shortcuts with Iceberg tables: Direct integrations with Snowflake and other platforms
• Mirroring: Support for Azure SQL and Snowflake (GA)
• Cross-cloud JOINs: Analyze datasets spread across different clouds and formats: You can combine SQL Database, Lakehouses and Warehouses in one query
• Open mirroring (preview): this allows you to write change data from any application directly into a mirrored database in Fabric. Open mirroring is based on the open Delta Lake table format

Platform

• Workspace monitoring (not to be confused with the Admin Monitoring workspace, this is intended for tenant insights): a database in your workspace that records log data and metrics about all items in that workspace. All of this is recorded in a real-time intelligence Eventhouse database. There are example queries in the Fabric samples GitHub. 
• Surge protection for capacities: This capability is coming soon, and it allows you to set a cap on the background workload of a capacity. This helps to better guarantee the availability of interactive workloads (such as Power BI report usage). You can set this per capacity.
• OneLake catalog: This is the new central hub to find, search, and use all Fabric items. You can use all available filters, including new ones like domains and tags. You can explore in-place items and view details.

Conclusion

Ignite 2024 showed that Microsoft is strongly committed to an integrated and future-oriented data platform, with AI and Copilot as a common thread. Innovations such as workspace monitoring, improved security through service principal support, and the advanced capabilities of the OneLake Catalog make it easier than ever to manage data effectively.

I believe that with these developments, the Microsoft Intelligent Data Platform is ready to support organizations in an increasingly data-intensive world.

Do you have any highlights from Ignite that I missed? Then let me know in the comments!


Items that are being worked on now and in the future are often public via the Fabric roadmap. There you can find per workload the items that will be worked on in the coming 6-12 months.

Some examples:

• A new Fabric navigation experience
• Support for folders for Git integration
• Better ownership of Fabric items
• Fabric Capacity Metrics Cross-capacity insights
• Capacity Metrics Chargeback

My DataGrillen Adventure: Speaking, Connecting, and New Friendships

I just got back from an incredible trip to DataGrillen, and I can’t wait to share my experiences with you. If you haven’t heard of it, DataGrillen is this amazing community-driven conference in Germany, where data professionals from around the world gather to share knowledge, ideas, and, of course, some good BBQ and beers. This year was special for me because I had the honor of speaking again at the event.

A special thanks goes out to Ben (@bweissman) & William (@sql_williamd) for organizing the event! But let's start from the beginning.

The Journey Begins

The anticipation was building as I packed up the car, later picked up Eduard Koekkoek (@heartforarts) and set off on our road trip to Germany. Eduard, a great friend and fellow data enthusiast, was the perfect companion for the journey. We spent some time on the road discussing everything from the latest in data technologies to our expectations for the conference. The drive was quite long, but the conversation made it fly by.

Stepping onto the Stage

The highlight of my trip was undoubtedly my speaking session. I had the first session at the first day, just after the opening "ceremony". The preparation that goes into a talk is always intense, but the passion I have for the subject kept me going. The topic was close to my heart, Administration and Governance in Fabric, and I was thrilled to see a room of fellow data enthusiasts ready to dive into the discussion. 

The audience was incredibly receptive, and the interaction was great. There’s something deeply fulfilling about sharing knowledge and seeing that spark of understanding and curiosity in others. The Q&A session that followed was lively, with thoughtful questions. It’s moments like these that remind me why I really like what I do.

Reconnecting with Old Friends

One of the best parts of conferences is the chance to reconnect with friends and colleagues from the industry. DataGrillen was no exception. With the change of forgetting someone, I won't call out names here 😀
It was like a reunion of sorts, seeing familiar faces, catching up on the latest in our professional and personal lives, and talking about past conferences and projects. There’s a special bond that forms when you share experiences and challenges over the years, and DataGrillen provided the perfect backdrop for these reunions.

A smaller group of people, specifically people into running, like to get together for an early run on days of a conference. We created a very special, long-running thread on Twitter (a.k.a. X), that actually started 2 years ago at DataGrillen!

Ran a little bit more 😊🥵 pic.twitter.com/dWM8mNwwo4

— Koen Verbeeck 🇺🇦 🌈 (@Ko_Ver) May 17, 2024

Furthermore, we exchanged ideas over beers and BBQ, debated the future of data technologies, and shared a lot of laughs. These moments are invaluable, and they remind me of the strength and warmth of the data community. It's not just about the work we do, but the friendships we forge along the way.

Making New Connections

While reconnecting with old friends was wonderful, making new ones was equally exhilarating. DataGrillen attracted a diverse crowd of professionals, each bringing unique perspectives and experiences. I met so many passionate individuals, each conversation was a learning opportunity, and a chance to see the data world through a different lens.

The DataGrillen Vibe

What sets DataGrillen apart is its atmosphere. The organizers have created an environment that fosters learning and networking in the most enjoyable way possible. The BBQ element adds a fun twist, making the conference feel more like a community gathering than a formal event. It’s the perfect balance of professional development and relaxation.

Looking Ahead

As Eduard and I drove back home, I felt a great sense of satisfaction and inspiration. DataGrillen was more than just a conference: it was a reminder of the incredible community we’re all part of. I left with new knowledge, strengthened friendships, and a bunch of new connections that I’m excited to nurture.

If you ever get the chance to attend DataGrillen, don’t hesitate. It’s an experience that goes beyond the sessions and keynotes – it’s about the people, the conversations, and the community. I’m already looking forward to next year’s event!

Session materials

My slides were already shared with the conference, but in case you haven't found them, you can find them at my GitHub.
I've also uploaded the template file I used in my demo for Admin Monitoring to the above page.

First page of my demo file

You can also find slides of previous conferences there. I generally follow this pattern: https://github.com/NickyvVr/talks/tree/master/slides/YYYY/yyyymmdd [Conference name]

Until next time, keep learning, keep sharing, and keep grilling!

Governance & Administration - Tenant Settings: Searching

With all the Fabric announcements in the last months, some of the Admin announcements might have slipped through. As you might know, the Admin part of Fabric is dear to my heart. I've posted about it earlier here, here, here, and here, to name a few 😀.

So in the next weeks I am going to highlight a few things with short, informative posts.

You can find other posts in the series here:

• Fabric (Tenant Settings) API's
• Tenant settings: Visual Cues

Governance & Administration - Tenant Settings: Visual Cues

With all the Fabric announcements in the last months, some of the Admin announcements might have slipped through. As you might know, the Admin part of Fabric is dear to my heart. I've posted about it earlier here, here, here, and here, to name a few 😀.

So in the next weeks I am going to highlight a few things with short, informative posts.

You can find other posts in the series here:

• Fabric (Tenant Settings) API's
• Tenant Settings: Searching
  

Governance & Administration - Fabric (Tenant Settings) API's

With all the Fabric announcements in the last months, some of the Admin announcements might have slipped through. As you might know, the Admin part of Fabric is dear to my heart. I've posted about it earlier here, here, here, and here, to name a few 😀.

So in the next weeks I am going to highlight a few things with short, informative posts.

This first post in the series is focused on the Tenant settings API and other Fabric API's available at the time of writing.

You can find other posts in the series here:

• Tenant Settings: Visual Cues
• Tenant Settings: Searching

Get Tenant Settings API

Obviously, to use the Get Tenant Settings API you need to have at least Tenant.Read.All permissions, or have the Fabric Administrator role (or higher) in Azure.

There are a few use cases I see for getting these settings exported with this API:

• Documentation purposes when you have multiple Fabric Administrators
• Distributing tenant settings to users, and explaining why we (as a team of Administrators/within the Center of Excellence) made certain choices
• Get notified of the changes in the tenant settings, without having to use Microsoft Defender or M365 Security & Compliance center like mentioned here

Get Capacities Tenant Settings Overrides

With the introduction of Fabric, there has also been the ability to have capacity admins override certain tenant settings. 

Example of a tenant setting that can be delegated

Some settings in the Admin portal are automatically delegated to capacity admins, like shown above. 

Other Fabric API's

Next to the API's on the tenant settings, there are already a lot more API's in the Admin section for you to check out, for example to handle workspaces, users, domains, and items as a Fabric Admin.

Next to that, so not as a Fabric Admin, you can also interact with Lakehouse tables, and there's a bunch of Core API's, for example to use Git or OneLake Shortcuts.

Preview note

Please note that at the time of writing this post, most of the API's are still in preview and subject to change.

Except for the Get Tenant Settings API, all the API's are currently in preview: