check before: 2025-10-28
Product:
Entra, Fabric, Power BI
Platform:
Online, World tenant
Status:
Change type:
Feature update, User impact, Admin impact
Links:
Details:
Summary:
Microsoft Fabric will introduce a tenant setting on October 28, 2025, allowing admins to control inclusion of user identifiers in OneLake diagnostic logs. By default, End User Identifiable Information is logged, but admins can opt out for privacy and compliance. This supports security, troubleshooting, and usage analytics.
Details:
[Introduction:]
To support enhanced monitoring and governance, Microsoft Fabric is introducing a new tenant setting that allows admins to control whether user identifiers are included in OneLake diagnostic logs. This change aligns with customer feedback around privacy and compliance, giving organizations more flexibility in managing diagnostic data.
[When this will happen:]
OneLake diagnostics will become generally available in mid-October 2025.
The new tenant admin setting will be available starting October 28, 2025.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2025-09-25
updated:
2025-09-25
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
Pictures
XXXXXXX ... free basic plan only
summary for non-techies**
XXXXXXX ... free basic plan only
Direct effects for Operations**
User Privacy and Compliance
If the change is implemented without preparation, user identifiable information (EUII) will be logged by default, potentially leading to privacy violations and non-compliance with data protection regulations such as GDPR.
- roles: Tenant Admins, Workspace Admins
- references: https://www.microsoft.com/en-us/microsoft-365/blog/2021/01/28/understanding-gdpr-and-microsoft-365/, https://www.eugdpr.org/
Diagnostic Monitoring and Troubleshooting
Without proper preparation, the inclusion of EUII in diagnostic logs may hinder the ability to effectively troubleshoot issues, as sensitive user data could be exposed, leading to security risks and potential misuse of data.
- roles: Workspace Admins, IT Support Staff
- references: https://www.microsoft.com/en-us/security/blog/2020/01/30/understanding-the-importance-of-logging-and-monitoring/, https://www.csoonline.com/article/3531235/the-importance-of-logging-and-monitoring-in-cybersecurity.html
Configutation Options**
XXXXXXX ... paid membership only
Data Protection**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
explanation for non-techies**
Microsoft Fabric is introducing a new feature that will allow administrators to manage how user information is included in diagnostic logs for OneLake. Imagine diagnostic logs as a security camera in a store. This camera records everything that happens, helping store managers understand customer behavior, catch any issues, and ensure everything runs smoothly. In this analogy, the store is your organization's data environment, and the security camera is the diagnostic logs.
By default, these logs will include details like who accessed the data and from where, similar to how a security camera might capture the faces of customers entering the store. This information can be crucial for security investigations, troubleshooting performance issues, and understanding how data is used within the organization. For instance, if there's a problem with data access or performance, these logs can help pinpoint what went wrong and who was involved, much like reviewing camera footage to understand an incident in the store.
However, just as some stores might choose not to record customer faces for privacy reasons, organizations can now choose to exclude user-specific information from these logs. This is done through a new setting that administrators can toggle on or off. If privacy and compliance are a concern, admins can opt out of logging user identifiers, ensuring that personal information is not included in the logs. This decision can be compared to a store choosing to blur faces in their security footage to protect customer privacy.
The introduction of this setting gives organizations the flexibility to balance the need for detailed monitoring with privacy considerations. Administrators can review their organization's policies and decide whether to keep the default setting or opt out, based on their specific needs and compliance requirements. This change is akin to a store manager deciding whether to adjust their security camera settings to align with privacy laws and customer expectations.
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
Last updated 2 months ago ago
