Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 8%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EST%3C/text%3E%3C/svg%3E)
Hi Jona
Thanks for sharing the details - this really helps pinpoint the issue.
From the error message when running the notebook through the pipeline Notebook activity, it looks like you're hitting a permissions issue on the Blob Storage container:
StatusCode=403, ErrorCode=AuthorizationPermissionMismatch
This request is not authorized to perform this operation using this permission
This usually means that the identity executing the pipeline doesn't have sufficient permissions on the storage account, even though it works fine in debug mode.
Why it works in Debug Mode:
In debug mode, the notebook likely runs under your user identity or workspace managed identity, which already has access to the storage container via RBAC or Access Key.
Why it fails in Pipeline:
When orchestrated in a pipeline Notebook activity, the execution runs under the Synapse workspace managed identity, not your personal identity. This managed identity needs explicit permission to access the storage account.
How to Fix It
- Go to the storage account (where the blob container lives).
- Assign the Synapse workspace managed identity (you can find it under Synapse Studio > Manage > Managed identities) one of the following roles at the Storage account or container level:
-
Storage Blob Data Contributor- (for read/write access) -
Storage Blob Data Reader- (if only reading)
-
- You can do this via the Access Control (IAM) blade in the storage account.
Also check:
Make sure you're using the correct URI prefix:
- If you're using abfss:// (ADLS Gen2), it requires RBAC.
- If you're using wasbs:// (Blob URI with access key or SAS), ensure key access is allowed.
Let me know once you've applied the role, and feel free to re-trigger the pipeline. It should resolve the AuthorizationPermissionMismatch error.
I hope this information helps. Please do let us know if you have any further queries.
Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.