deleteIfExists blob API not working as expected with OneLake endpoint

Question

deleteIfExists blob API not working as expected with OneLake endpoint

azureuser 0

I have Java code that uses azure-storage-blob version 12.31.3. When calling CloudBlob.deleteIfExists on a regular Azure Blob with the endpoint **`

1 answer

Your answer

Answer 1

Hi azureuser
Thanks for reaching out!

The issue you’re seeing is expected because OneLake endpoints do not fully support all Azure Blob Storage SDK operations, especially older methods like CloudBlob.deleteIfExists. OneLake is built on top of Microsoft Fabric / ADLS Gen2, and it has different API behavior compared to a standard Azure Blob endpoint.

Why this happens

deleteIfExists works normally on Azure Blob Storage, but OneLake is not a traditional Blob service, so the Blob SDK may not behave consistently or may fail silently.

What you should use instead

To work with OneLake, Microsoft recommends using:

DFS (Data Lake Gen2) REST API, or

Azure Storage Blob SDK (latest versions) with DFS endpoints, not classic Blob endpoints.

If you want to delete a file reliably, use:

DataLakeFileClient fileClient = dataLakeServiceClient
    .getFileSystemClient("filesystem")
    .getDirectoryClient("path")
    .getFileClient("file");

fileClient.deleteIfExists();

Recommendation:

Please check the endpoint you are using. If it looks like:

https://<workspace>.onelake.fabric.microsoft.com/...

then Blob APIs may not work as expected.

Switching to DataLake SDK or DFS endpoint should resolve the issue.

Hope this help. Please let me know if you have any questions.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

azureuser 0 Reputation points

2025-12-11T19:15:29.27+00:00

Hi Smaran, thanks for the response. I still have a question though. The code that I have written works perfectly fine with both original blob storage as well as ADLS Gen 2 (HNS enabled), but only has issues when using OneLake. Considering that OneLake is built upon ADLS Gen2, it seems to me that this API should still work. Using the DFS endpoint is not really an ideal solution for me as I am trying to write cross-compatible code, and I don't understand why the endpoint works fine for ADLS Gen 2 when treating it as blob storage, but has issues for OneLake. Considering that the blob endpoint is provided and described as having parity: https://dori-uw-1.kuma-moon.com/en-us/fabric/onelake/onelake-api-parity, I would expect to see a similar result to what I see with a non-OneLake data lake.

Share via

deleteIfExists blob API not working as expected with OneLake endpoint

1 answer

Your answer