Fabric Administration – Tenant Settings API
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. So in the next posts around Fabric Administration 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.
List Tenant Settings 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
Romain Casteres, currently a Cloud Solution Architect at Microsoft, created a nice solution in Fabric to extract the tenant settings and report on the changes. You can check out his solution 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
