Forum Discussion

jeremycolson1's avatar
jeremycolson1
Advocate I
2 years ago

Access Lakehouse from Logic App

Has anyone had any luck connecting a logic app to a lakehouse in Microsoft Fabric?

 

Some additional background...

We have a data pipeline that is ultimately generating a summary of some actions taken within the pipeline. This summary is stored as an Excel spreadsheet on our lakehouse/Files. Within our Data Factory pipeline, one of the lasts tasks is to email this report. Unfortunately, while Data Factory has an email activity, it does not support attachments. So our workaround was to create a logic app whereby we could post a request from Data Factory, parse the JSON, retrieve the file from the Fabric lakehouse, and then email that file to the appropriate group.

 

This approach unfortunately fails when utilizing Get Blob Content (V2). The error generated is:

Provided storage account endpoint doesn't follow the naming convention. Storage Account name should be between 3 and 24 characters (lowercase letters and numbers). If providing the Storage Account endpoint, make sure to enter the full URI (for example https://accountname.blob.storage.net)

 

We tried the abfs path Fabric utilizes:

abfss://<workspace>@onelake.dfs.fabric.microsoft.com/<lakehouse_name>.Lakehouse/Files

 

And then we tried the BLOB URL:

https://onelake.blob.fabric.microsoft.com/<workspace>/<lakehouse_name>.Lakehouse/Files

 

And then the DFS URL (because why not):

https://onelake.dfs.fabric.microsoft.com/<workspace>/<lakehouse_name>.Lakehouse/Files

 

Nothing works... And the odd thing, Azure Storage Explorer has no problem accessing the underlying ADLS Gen2 storage account (the lakehouse). So I'm assuming this is a problem with the way this particular action works within Logic Apps. Looks like it's attempting to validate the URI, but Fabric uses a slightly different endpoint naming convention (even though it's just ADLS Gen2) and Logic Apps just has not caught up?

 

This is our first time utilizing Logic Apps, so this might be a dense question. We did not find any other actions specifically for Fabric, so we are a bit stuck at this point.

 

Thanks for any help/guidance you can provide!

-JC

 

P.S. I also posted this over in the other forums under Logic Apps, but not sure how much experience that community has working with Fabric.

data pipeline
lakehouse

3 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    HI jeremycolson1,

    So you mean to use azure logic app to access to the underlying data that fabric Lakehouse hosts, right?
    If that is the case, I'd like to suggest you use pipeline to output the file destination to the azure storage instead of direct invoke it from external.
    Then you can use the logic app to trace above file and invoke azure contents to send email.

    Regards,

    Xiaoxin Sheng

    • jeremycolson1's avatar
      jeremycolson1
      Advocate I
      2 years ago

      Thanks Anonymous ... This was in our back pocket as a workaround, but we really wanted to avoid the overhead of provisioning additional infrastructure unless it was absolutely necessary. It's starting to sound like this might be the case if Logic Apps cannot connect to Fabric.