web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Azure Blob Storage - t...
Power Automate
Unanswered

Azure Blob Storage - this request is not authorized to perform this operation

(2) ShareShare
ReportReport
Posted on by 21

I have an azure storage account that i want to connect to.

The storage account is in the region west europe.

In the networking settings we enabled only selected virtual networks and IP addresses. I also allowed Azure services on the trusted services list to access this storage account.

 

When I try to connect from Power Automate to the azure blob storage i get the error message: Testen van verbinding is mislukt. Details: This request is not authorized to perform this operation. clientRequestId: 500c32e1-34ba-23d1-ec62-f76aa7b55688

 

It works when i set the storage account to enable from all networks. but that's not what i want for security reasons.

The region of our power platform is Europe (there is no option to select west europe)

 

Can anybody help me to get this working? 

Categories:
I have the same question (0)
  • NaelShichidaEmb Profile Picture
    5 on at

    Hey Julian

     

    I am undergoing similar issues for a flow that has been working fine for the past two years. Wonder if there was something that changed that is causing us to see this? I have the same setup as you, only allowing certain IPs, I believe power automate has certain IP address and they have to be whitelisted. That is what I have done in the past to get it working, however now is not the case.

    I have also attempted in getting an HTTP request to validate the current IP address using this walkthrough. (https://powernimbus.com/2021/04/whats-the-ip-of-my-flow/)

     

    Let me know if you resolve it somehow and will email microsoft support now to find a fix.

     

    Kind regards

     

    Nael 

  • NaelShichidaEmb Profile Picture
    5 on at

    Hey Julian

     

    I've managed to solve it, in my case the IP address' were whitelisted beforehand so it might not be the same issue as you. But I simply created another power flow with the exact same configuration however built from scratch and it is working as expected now.

     

    Also for reference, here is a useful IP address list that you ought to whitelist if you setup only certain IPs to run and communicate with your Azure. https://learn.microsoft.com/en-us/connectors/common/outbound-ip-addresses

    Regards

    Nael

  • Julian1977 Profile Picture
    21 on at

    Hi,

     

    Thanks for your reply.  I tried to whitelist the IP addresses you refered to in the link in my storage account, but that didn't help. i allowed the ip adresses below. 

    I also tried to make a new flow, but that didn't help as well.

     

     

     

    40.89.131.3
    40.115.108.29
    52.174.180.160
    52.178.150.68
    94.245.91.93
    52.174.88.118
    40.91.208.65
    137.117.161.181
    13.69.171.0
    13.93.36.78
    20.82.226.52
    20.82.224.59
    20.126.243.151
    20.126.241.238
    20.103.132.139
    20.103.131.1
    13.69.227.208/28
    13.69.231.192/27
    13.69.64.208/28
    13.69.71.192/27
    20.82.246.112/28
    52.146.138.32/27
    20.86.93.32/27
    20.86.93.64/29

     

  • HN-04060819-0 Profile Picture
    46 on at

    So what your are saying is that having the IPs whitelisted didn't work. So, what did you do to connect the Azure Blob storage? Please share for the benefit of others

  • HN-04060819-0 Profile Picture
    46 on at

    There is many IPs which needs to be allowed. Out of curiosity checking if there is an easy way to allow these IPs or allow the DNS name for that case

  • Verified answer
    Julian1977 Profile Picture
    21 on at

    I have it working now.. In the networking properties I had to add Microsoft.Logic/workflows to the resource instances. 

  • sandeep853085 Profile Picture
    4 on at

    Hi,

     

    We are facing same issue. We tried providing access to resource type Microsoft.Logic/workflows for instance name as 'All in current tenant'. Is this still working for you @Julian1977 ?

  • Julian1977 Profile Picture
    21 on at

    Hi,

     

    Sorry, i have built a different solution with c# code instead of power automate, because i didn't get it to work.

     

    Julian

  • Julian1977 Profile Picture
    21 on at

    And were you able to fix it? 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 522 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 364 Moderator

#3
abm abm Profile Picture

abm abm 243 Most Valuable Professional

Last 30 days Overall leaderboard