MC1234653 High
Tenant Default Change – Workspace Admins Will Be Allowed to Enable Monitoring
Summary AI-generated
The Fabric tenant setting allowing Workspace Admins to turn on workspace monitoring will be enabled by default on March 23, 2026; no monitoring is enabled automatically.
Suggested actions AI-generated
- Review Fabric tenant setting for workspace monitoring
- Adjust governance as needed
- Optionally communicate guidance to Workspace Admins
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1217152 Tenant setting update: Copilot capacity designation enabled by default
- MC1238430 Workspace IP Firewall rules (Public Preview)
- MC1278715 Power Apps - Tenant-Level Microsoft 365 Copilot Settings to Enable Dataverse Data Access Announcement
- MC1215073 Power BI Report metadata defaults to Power BI Enhanced Report format (PBIR)
- MC1193456 Power Platform – Power Platform Monitor Overview page and predefined alerts
- MC1262537 Power Platform admin center – Upcoming update to the enforcement of tenant isolation
Original post from Microsoft
[Introduction]
To help organizations gain better operational visibility into Microsoft Fabric workloads while maintaining centralized governance, Microsoft is enabling the tenant setting “Workspace admins can turn on monitoring for their workspaces” by default. This change reflects customer feedback requesting easier access to workspace-level insights without automatically enabling monitoring or changing existing permissions. This update does not turn on monitoring for any workspace.
[When this will happen:]
Starting March 23, 2026
[How this affects your organization:]
Who is affected:
- Tenants using Microsoft Fabric
- Tenant admins managing Fabric tenant settings
- Workspace Admins managing Fabric workspaces
What will happen:
- The tenant setting “Workspace admins can turn on monitoring for their workspaces” will be enabled by default.
- No monitoring is automatically enabled for any existing or new workspace.
- Workspace Admins can choose whether to enable monitoring for their individual workspaces.
- If enabled by a Workspace Admin, monitoring provides access to logs, metrics, and operational insights related to Fabric items within that workspace.
- Existing tenant governance, permissions, and security controls are respected.
- There is no impact to end users unless Workspace Admins explicitly enable monitoring.
[What you can do to prepare:]
- No immediate action is required.
- Review the tenant setting in the Fabric Admin portal to understand or adjust your governance posture.
- If needed, disable the setting to prevent Workspace Admins from enabling monitoring at the workspace level.
- Consider communicating internal guidance to Workspace Admins about when and how workspace monitoring should be used.
- Learn more about Workspace Monitoring
[Compliance considerations:]
| Compliance area | Explanation |
|---|---|
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? | Yes. When enabled by a Workspace Admin, workspace monitoring provides access to logs and metrics for Fabric items, improving operational monitoring, audit readiness, and compliance reporting within that workspace. |
| Does the change include an admin control, and can it be controlled through tenant settings? | Yes. The capability is governed by a tenant-level setting that admins can enable or disable centrally to control whether Workspace Admins can turn on monitoring. |
| Does the change allow a user to enable and disable the feature themselves? | Yes. Workspace Admins can choose to enable or disable monitoring for their own workspaces when the tenant setting is enabled. |
Additional details from Microsoft
- Summary
- Starting March 23, 2026, the tenant setting allowing Workspace Admins to enable monitoring in Microsoft Fabric will be enabled by default. Monitoring is not auto-enabled; Workspace Admins decide to activate it, providing logs and metrics access while maintaining existing governance and security controls.