This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
As we continue to mature the Microsoft Fabric platform, we’re taking steps to streamline and simplify the experience for administrators and compliance teams who rely on audit logs.
Beginning July 2025, we’re consolidating a number of redundant audit operations into a unified model that reflects our broader platform architecture. This change impacts how operations for items like Datamarts, Warehouses, and SQL analytics endpoint are logged and represented.
Previously, certain operations—such as Create Datamart, Delete Warehouse, or Update Datamart Settings—were tracked as distinct entries. With this change, these actions will be captured under standardized operations like CreateArtifact, DeleteArtifact, UpdateArtifact, ReadArtifact, and ShareArtifact.
This change does not impact functionality or access. It is purely a naming alignment in audit logs to reduce noise, improve consistency, and make it easier to interpret and correlate actions across Fabric workloads.
Standardizing_Audit_Operations_for_Warehouse_DataMarts_and_SQL_Analytics_Endpoin
If you rely on audit logs for monitoring, compliance, or automation, please review and update any tools, queries, or processes that depend on the old operation names.
By transitioning to a consistent naming model, we’re making it easier for you to build scalable, workload-agnostic governance and monitoring solutions across Fabric.
For full details, refer to the updated Audit Operation List in our documentation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.