There is only one constant about Power BI. Since the release of the Power BI Service in July 2015, it has been growing and evolving into one of the most powerful analytical platforms. From my perspective, the advent of Fabric, meaning the appearance of new powerful analytical capabilities like data warehousing and data science inside the Fabric workspace (fka Power BI App workspace), marks the dawning of a new era. Still, when I’m talking to like-minded people who are facing administrative tasks regarding the Power BI Service, I often hear: “This is boring; I’m not an administrator; I’m an artist, a DAX ninja, an M princess, or a data modeling goddess - I do not care!”, or something similar.

I started my career as a Power BI/Fabric Sherpa, more or less with the advent of Microsoft Analysis Serves Tabular, and yes, I love DAXing, data modeling, and creating large data architectures, but I consider the tenant settings not boring. Quite the contrary, being a Power BI/Fabric sherpa means, I help Power BI users (Fabric users) to be successful on their data journey. This includes keeping the assets safe, making sure the capacities are properly utilized, and also making sure that the pace of the journey matches the fitness of my colleagues. One important aspect to be successful on this joint journey is the proper configuration of the Tenant settings.

If you are a Power BI Developer who must administer the Power BI Service, or you are starting your life as a Power BI Administrator by joining this session, in this session, you will learn how tenant settings help to keep your assets safe, how you can adapt tenant settings to match the growing data literacy of your colleagues. But even if you are experienced with the Admin Tenant setting, this session might reveal something new, because I will also show how to monitor and track the tenant settings, of course using Fabric.