This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Simplified, workspace-governed ingestion without external dependencies
COPY INTO and OPENROWSET from OneLake are now available in Preview for Microsoft Fabric Data Warehouse.
With this release, you can load and query files directly from Lakehouse File folders, without relying on external staging storage, SAS tokens, or complex IAM configurations. This improvement reinforces Fabric’s vision of a fully SaaS-native platform, where data movement, access control, and analytics all live within the same governed environment.
You can now use both COPY INTO and OPENROWSET directly with OneLake paths, enabling SQL-based read and write access to files stored in Lakehouse folders—without Spark, pipelines, or external staging.
This update removes the need for external services and manual setup, delivering a true SaaS-native experience secured by Entra ID, and ready for scale.
With OneLake as a source for COPY INTO and OPENROWSET, you can now:
COPY INTO directly on files stored in Lakehouse folders (CSV, Parquet, JSON).Copy Into
COPY INTO dbo.Sales FROM 'https://onelake.dfs.fabric.microsoft.com/<workspace>/<lakehouse>/Files/Sales.csv' WITH ( FILE_TYPE = 'CSV', FIRSTROW = 2, FIELDTERMINATOR = ',', ERRORFILE = 'https://onelake.dfs.fabric.microsoft.com/<workspace>/<lakehouse>/Files/Sales_Errors.csv' );
OPENROWSET
SELECT *
FROM OPENROWSET(
'https://onelake.dfs.fabric.microsoft.com/<workspace>/<lakehouse>/Files/Sales.csv'
);
This preview is available to all Microsoft Fabric users. Simply upload files into any Lakehouse’s Files folder and use COPY INTO or OPENROWSET from your Data Warehouse—with no external storage required.
We’re working on simplifying the authoring experience even further. In upcoming updates, users will be able to reference workspace and Lakehouse names using friendly names rather than full path URLs—making scripts more readable, maintainable, and collaboration friendly.
Explore our documentation for a more in-depth look.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.