How to access attachment in PowerApp that are stored in Blobstoragecontainer,using SAS token or ACL

(1) Share

Report

Posted on by RamKan2021

102

We have developed a PowerApp and set up a Blob storage container to store attachments.
We can successfully save data (files or images) in the Blob storage container.
However, when trying to view the saved attachments in PowerApps, we encounter the error message: 'Public access is not permitted on this storage account.'
(Note: We have set the access level of the containers to 'Private'.)
We understand that to access the storage with 'Private' settings, we need to generate a SAS token or set up ACL policies.

Could you please guide us on how to configure the SAS token in PowerApps or how to create ACL policies?

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Michael E. Gernaey 53,335 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

So you have 2 options

1) do this in Power Automate and pass back the data

How to create SAS URI to access file from Azure Blob Storage using Microsoft Power Automate (Flow)? - Nebulaa IT Solutions | Nebulaa IT Solutions

Lol i had to laugh... because CoPilot Now generates the correct steps /cry harder.

2) Use the HTTP(s) Connector or the HTTP Azure AD Connector in your app

Just an FYI those are all premium connectors so they cost money.

Was this reply helpful? Yes No
Suggested answer

Ammar Zaied 97 on at

Like (0)

Report
Access to azure portal, your Azure Blob Storage account:

Select Containers and choose the container where your files are stored.

Click on Shared access signature from the left panel.

Define the permissions you need (like Read if you only want to view the files).

Set the start and expiry times for the token.

Click Generate SAS token and URL.

In PowerApps:

You will use the generated Blob SAS URL to access files.

In PowerApps, modify the URL used to display or fetch the file by appending the SAS token at the end of the Blob URL

One of the main constraints of using a SAS token is that you need to regenerate the URL periodically because the SAS token has an expiration time. This means that each time the token expires, you'll have to generate a new SAS URL to continue accessing the files.

To avoid this manual process, you can create an API or Power Apps Custom Connector or power automate that dynamically generates a SAS token for your files on demand.

Was this reply helpful? Yes No