Enterprise customers adopting Microsoft Fabric want to standardize on OneLake as the unified storage layer for both structured data (Lakehouse tables, Warehouse data) and unstructured data (files stored in OneLake). This data may originate from external systems (ADLS, S3, databases, SaaS) or be created natively within Fabric workloads. A growing number of regulated customers have Infosec and compliance requirements to enforce retention policies consistently across all data in OneLake, regardless of source or workload. Today, customers are explicitly asking for a OneLake‑scoped retention capability that they can reason about as a storage‑level control, similar in intent to ADLS lifecycle policies.
A native, Purview‑governed OneLake retention model would materially reduce this adoption barrier and strengthen the OneLake governance story.
on:
Customers should ereceive notifications for all th...
miguel
on:
Recent Data and Recent Connections
on:
Need more details on Average utilization% in Capac...
lbendlin
on:
Increase the 1,000 Item Limit per Fabric Workspace
NaamaTsafrir
on:
Rename "Domain Admin" to "Domain Owner" to match P...