usage of, Create SAS URI by path (V2) , in the Logic App, to connect to the Blob Storage

Question

Hi,

I have a logic app where I want to get files from Blob storage Container. On the Azure Blob Storage there is no IP restrictions.

I am trying to make use of action Create SAS URI by path (V2) to connect with the storage from the Logic App. A connection was created using access keys as shown in the nest picture.

The connection is successful. I have tried connection in multiple ways (Entra Id, Logic App Managed Identity, Access Key)

after the connection is established, it does not allows me choose any files/Path. As shown in next picture, the error message says ,Parameter "dataset" cannot be found for this operation

Any help/idea would be great.

Thank you!

Answer 1

Hi @Sohaib Cheema Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.

I have encountered the same behavior from the Action item in the UI as you stated in the thread. Let me look into this further internally and get back to you with more findings.

In the meantime, below is a work around you can try:

I have used this Action in my Logic App linking to the Trigger When a blob is added or modified (properties only) (V2). Instead of proving a file path through the browse option from UI, I have used the bind action Enter data from previous step and used the available option List of Files Path Please refer the below image for reference.

Here is my logic app flow

When a new blob gets added, I see the file path being passed to the Create SAS URI by path action and I could access the file using the generated SAS URI.

Alternatively, if you prefer to get the file URL for a specific file and not rely on the Trigger, you can use the Action Get blob metadata V2 which has an output of file path. You can refer this in the Action Create SAS URI as follows.

Hope this helps! I will keep you posted on further findings on this thread.

---

If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.