Notifications
Announcements
Your Access Key configuration in Power Automate is correct. When this setup fails with an authentication error, the issue is almost always caused by storage account–level restrictions, not the key itself.
Based on your screenshots:
Allow trusted Microsoft services is already enabled — this alone is not sufficient
Power Automate is still being blocked by other networking or security settings
Please verify the following on the Storage Account:
Public network access
Storage Account → Networking
Must be Enabled
For testing, set network access to All networks
If set to Selected networks, Power Automate cannot connect
Private Endpoint
Storage Account → Networking → Private endpoint connections
If any private endpoint exists, Power Automate cannot connect directly using Access Key
Shared Key access
Storage Account → Configuration
Allow storage account key access must be Enabled
If disabled, Access Key authentication will always fail
Connection recreation
After any change, delete the existing Azure Blob Storage connection in Power Automate
Recreate it using:
Storage account name only (not the blob URL)
Key1 or Key2
In short: the authentication error is misleading — the root cause is networking or shared-key access restrictions on the storage account, not incorrect credentials.
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.
In our never-ending quest to improve we are simplifying the forum hierarchy…
We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Michael E. Gernaey 503 Super User 2025 Season 2
Tomac 321 Moderator
abm abm 237 Most Valuable Professional