Struggling to monitor capacity, assets, and usage in Microsoft Fabric? Limited data and scattered tools make governance tough. The open-source Fabric Unified Admin Monitoring (FUAM) tool brings everything into one place. It gives admins clear insights and better control.
In this guide, you’ll learn what FUAM is and why it’s useful, how to deploy and configure it, and key features and reporting capabilities. You’ll also learn the common challenges and how to troubleshoot them.
Table of Contents
An Introduction to Fabric Unified Admin Monitoring
When monitoring your Fabric setup, there are numerous tasks to keep track of. Fabric Unified Admin Monitoring is an open-source monitoring solution built for Microsoft Fabric administrators. This tool simplifies the process, bringing together several tracking tasks into a cohesive framework. Additionally, it provides actionable insights for both daily operations and long-term governance.
It allows you to track and analyze critical aspects of your environment, such as:
- Inventory of Fabric assets and workspaces
- User activity and report usage
- Capacity units and resource consumption
- Best practice checks across multiple semantic models
Unlike the standard Microsoft Fabric Capacity Metrics app (which retains only 14 days of usage data), the Unified Admin Monitoring tool’s longer monitoring window and deeper analysis provide a much broader picture of your system’s performance.
Benefits of Using Fabric Unified Admin Monitoring
- Comprehensive Visibility – Monitor assets, users, reports, pipelines, and semantic models in one place.
- Capacity Planning – Track capacity usage and identify optimization opportunities.
- Custom Reporting – Generate dashboards that highlight system health, performance trends, and activity history.
- Scalability – Designed for both small tenants and enterprise-scale environments.
- Community-Driven – With its open-source nature, it allows contributions and improvements from the Microsoft Fabric community.
How to Install Fabric Unified Admin Monitoring
To deploy Fabric Unified Admin Monitoring, follow the recommended steps:
1. Access the GitHub Repository
The official GitHub repository provides the installation files, notebooks, and documentation. Download the required notebook to your local environment.
2. Import the Notebook into Fabric
- Create a new Fabric workspace with capacity enabled.
- Import the monitoring notebook.
- Run the notebook to automatically create the necessary connections, pipelines, lakehouses, and reports.
3. Configure Service Principal
To enable data refresh, you’ll need to:
- Register an application in Azure Entra ID.
- Generate a client secret and capture the Application ID and Directory ID.
- Assign the service principal to a security group with access to Fabric REST APIs.
4. Update Connections
Replace placeholder connections with the service principal credentials to ensure secure access to Fabric endpoints.
5. Execute Pipelines
Run the orchestrator pipeline to start pulling data from endpoints into your Fabric lakehouse, where the data is then transformed and made available for semantic models and reports.
Key Features of Fabric Unified Admin Monitoring
After installation, the tool automatically sets up a few key components in your workspace to get things running smoothly, including:
- Notebooks – Automate data ingestion and transformation.
- Lakehouses – Store raw, silver, and gold-layer monitoring data.
- Pipelines – Orchestrate data refresh and transformations.
- Reports – Visualize capacity usage, user activity, and inventory insights.
You can customize parameters such as:
- Activity Scope – Define how many days of history to load (e.g., 30 days).
- Refresh Frequency – Schedule weekly refreshes to balance cost and performance.
- Workspace Sources – Choose which Fabric workspaces to monitor.
Challenges and Troubleshooting Fabric Unified Admin Monitoring
As with any open-source project, you may encounter challenges. Some common issues include:
- Notebook Failures – Failure occurs when a Fabric notebook cannot execute properly, often due to missing libraries, incorrect configurations, or kernel issues.
Restarting the notebook kernel often resolves library import errors.
- Pipeline Errors – Errors happen when a Fabric data pipeline fails to run successfully. Usually, misconfigured parameters, missing data sources, or permission issues cause this.
Verify parameter settings and ensure that required tables exist in the lakehouse.
- Permission Problems – These arise when users or service principals lack the required access rights to Fabric resources or APIs.
Confirm that your service principal has the correct API permissions via Azure Entra ID and the Fabric Admin portal.
- Data Gaps – Occur when expected monitoring or activity data isn’t readily available in Fabric because the API hasn’t collected it. This may be due to limited API history, infrequent refresh schedules, or data that simply hasn’t made it into the system.
Remember that some endpoints only allow queries up to 30 days, so plan refresh frequency accordingly.
If errors persist, consult the GitHub Issues section for reported bugs and community fixes.
Best Practices for Using the Monitoring Tool
Follow these best practices to ensure efficiency, accuracy, and sustainability while avoiding common pitfalls.
- Run Weekly Refreshes. Avoid daily refreshes unless you require real-time monitoring, as this can consume excess Fabric capacity units.
- Leverage Fabric Metrics App. Use it alongside the Unified Admin Monitoring tool for the most up-to-date capacity insights.
- Review Documentation. Always check prerequisites before deploying in corporate environments.
- Contribute to the Community. Submit improvements or bug fixes back to the GitHub repository.
Conclusion
The Fabric Unified Admin Monitoring tool is a powerful way to gain visibility into your Microsoft Fabric environment. While it requires some setup and configuration, the benefits far outweigh the effort. By following best practices, you can enjoy centralized monitoring, extended data history, and actionable insights.
For Fabric administrators looking to optimize performance, this open-source solution is an excellent starting point.
Ready to take your Microsoft Fabric skills to the next level? Check out expert-led training and consulting services at Level Up Your Data and start building smarter data solutions today.
Frequently Asked Questions
Question: What should I do if notebooks fail due to missing metadata while deploying Fabric Unified Admin Monitoring?
Answer: First, restart the notebook kernel to clear temporary issues and rerun the process. If the problem persists, verify that the required metadata tables exist in the lakehouse and rerun the pipeline to regenerate them. Second, check the GitHub documentation for known issues and fixes.
Question: How to manage permissions for other admins?
Answer: Assign them to the appropriate groups in Azure Entra ID and grant access to the necessary Fabric APIs and workspaces. This ensures they have the correct roles without overexposing sensitive resources.
Question: How does Fabric Unified Admin Monitoring differ from the Fabric Capacity Metrics app?
Answer: The Metrics app provides only 14 days of data, while Fabric Unified Admin Monitoring extends history and offers more detailed reporting.
