Error Code 403 Authorization Permission Mismatch on power automate

The error code 403 with the message "Authorization Permission Mismatch" indicates that there are insufficient permissions for the operation you're trying to perform in Azure Blob Storage. Even though the account initiating the request in Power Automate has Blob Storage owner level access, there are a few potential causes for this error:

1. Missing Permissions in SAS Token: If you are using a Shared Access Signature (SAS) token, ensure that it includes the necessary permissions (e.g., write permission) for uploading files.
2. Operation Requirements: Some operations may require multiple permissions. For example, overwriting a blob requires both write and delete permissions. Verify that the SAS token or role assignment includes all required permissions for the operation.
3. Role Assignment Scope: Ensure that the roles are assigned at the appropriate scope (subscription, resource group, storage account, or container). If the role is assigned at a higher level, it may not propagate correctly to the specific container.
4. Public Network Access: If the storage account has public network access disabled, ensure that the request is coming from an allowed IP address or virtual network.
5. Firewall Rules: Check if there are any firewall rules that might be blocking the request.

By reviewing these aspects, you should be able to identify and resolve the cause of the 403 error in your Power Automate integration with Azure Blob Storage.

Hi Dr. Saeid Chavoshi,

Thanks for posting question in Microsoft Q&A,

We receive error 403 Authorization Permission mismatch despite the account which is initiating the request in Power Automate having Blob Storage owner level access.

The above error occurs when you do not have the proper permissions to access the storage account, or when you are using an incorrect SAS token.

• The Owner role grants resource management but not blob data operations like upload. Assign Storage Blob Data Contributor role to the user/service principal at the storage account or container scope via, Azure Portal > Storage Account > Access control (IAM) > Add role assignment. Verify effective permissions using the portal's "Check access" tool, as group/inherited roles may conflict.
• Power Automate and Power Apps do not reliably support connecting to Azure Storage accounts that have firewalls enabled. Even if the connection appears to work now, it may stop working at any time. The only stable solution today is: Do not enable firewalls on the storage account if you need to access it from Power Platform.

Reference:

1. Azure Blob Storage - Connectors | Microsoft Learn

You can follow this below link to upload files to azure blob storage using power automate.

• Upload Files to Azure Blob Storage using Power Automate Desktop

Kindly let us know if the above helps or you need further assistance on this issue.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.