Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedFabric Ideas just got better! New features, better search, and direct team engagement. Learn more
Hi, we recently tried to call fabric storage with a third party integration tool (BQ Omni) and got blocked because the tool only supports Blob storage urls, it will not take the slightly different fabric url format.
BQ omni will only take this url format: https://<account>.blob.core.windows.net/<path>/<fileName
Fabric url format does not work: https://onelake.dfs.fabric.microsoft.com/<workspace>/<item>.<itemtype>/<path>/<fileName>
It appears this is a well known issue, documented at How do I connect to OneLake? - Microsoft Fabric | Microsoft Learn under Common Issues.
We've submitted a feature request to google already (BigQuery Omni OneLake External Table Support [413157431] - Issue Tracker)
However my question for Microsoft is: rather than making every customer who hits it this send requests to fix in each individual third-party tool, could Microsoft not simply offer an alias for fabric urls that complies with the blob storage format and accepted by third party tools?
E.g. could you provide an alias so for fabric path https://onelake.dfs.fabric.microsoft.com/<workspace>/<item>.<itemtype>/<path>/<fileName> the blob storage path https://fabric.blob.core.windows.net/<workspace>/<item> also works. Or maybe https://fabric-workspace.blob.core.windows.net/<item>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.