Power Platform Community Forum Thread Details

{
"status": 403,
"message": "AuthorizationFailure\r\nclientRequestId: 9551d7b9-7f1b-4596-9556-a37b0d991f3f",
"error": {
"message": "AuthorizationFailure"
},
"source": "azureblob-ne.azconn-ne-002.p.azurewebsites.net"
}

Categories:

Using flows

Using connectors

Hi @CU25031014-0,

A 403 AuthorizationFailure occurs when Azure blocks your request due to either:

Network restrictions (firewall, private endpoints), or
Identity restrictions (Access Keys disabled or insufficient permissions).

Solutions
Option 1 The “Identity” Fix (Highly Recommended)
Modern Azure environments often disable Access Keys for security. If that is the case, any connection using Access Key authentication will always fail, regardless of correct values.

Action: Use Microsoft Entra ID Integrated authentication in Power Automate.
Requirement: Assign yourself (or the flow’s identity) the Storage Blob Data Contributor role in Azure IAM.
Benefit:

More secure
No Access Keys needed
Works even when Shared Key access is disabled

Option 2 The “Configuration” Fix
If you must keep using Access Keys, ensure Azure allows them.

Action: Azure Portal --> Storage Account --> Configuration

Set Allow storage account key access = Enabled

Check:

Use the storage account name, not the full URL
Regenerate and use a fresh Access Key if needed

Option 3 The “Network” Fix
If the storage account is behind a firewall or VNET, Power Automate cloud cannot access it, this is a known product limitation.

Test: Azure Portal --> Storage Account --> Networking

Temporarily set Public network access = Enabled from all networks
If this works, the firewall was blocking the connection.

Permanent Fix (when private access is required):
Use a secure middle tier:

Azure Function with Managed Identity, or
Logic App Standard with VNET integration

These can access the storage privately and your Power Automate flow calls them via HTTPS.

Step	Action	Why?
1	Switch to Entra ID	Avoids the "Disabled Access Key" policy entirely.
2	Verify IAM Role	You need "Storage Blob Data Contributor" for Entra ID to work.
3	Check Firewall	Power Automate Cloud cannot punch through private endpoints.

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.