This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Hi,
Today I tried setting up OneLake Diagnostic Logs in Microsoft Fabric. The setup seems to complete, but when I try to open/browse the diagnostic logs item in the Lakehouse files under Workspaces, I get an error.
What I see
Server error shown in the UI
Status: 403 – “This request is not authorized to perform this operation using this permission.”
Error code shown: AuthorizationPermissionMismatch
The UI also shows HTTP response code 500.
I am Admin in both workspaces involve
Solved! Go to Solution.
Hi @XlentVibruz ,
For additional clarity, this behavior is intentional and results from the separation between Fabric control plane permissions and Azure Storage data-plane permissions. The AuthorizationPermissionMismatch (403) error is returned by Azure Storage when Fabric tries to access the diagnostic log blobs, it is not generated by the Fabric service. Please make sure the necessary storage RBAC role is assigned at the correct scope (storage account, container, or resource group), as assigning it at the wrong level can still cause access issues. After assigning the role, allow enough time for RBAC propagation before trying to access again.
For more information, check
OneLake diagnostics – Microsoft Fabric:
https://learn.microsoft.com/en-us/fabric/onelake/onelake-diagnostics-overview
Hi @XlentVibruz ,
For additional clarity, this behavior is intentional and results from the separation between Fabric control plane permissions and Azure Storage data-plane permissions. The AuthorizationPermissionMismatch (403) error is returned by Azure Storage when Fabric tries to access the diagnostic log blobs, it is not generated by the Fabric service. Please make sure the necessary storage RBAC role is assigned at the correct scope (storage account, container, or resource group), as assigning it at the wrong level can still cause access issues. After assigning the role, allow enough time for RBAC propagation before trying to access again.
For more information, check
OneLake diagnostics – Microsoft Fabric:
https://learn.microsoft.com/en-us/fabric/onelake/onelake-diagnostics-overview
Hi @XlentVibruz ,.
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.
Hi @XlentVibruz ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you
Hi @XlentVibruz
I think you are getting this error bcz of Onelake Diagnostic Logs are stored in a system managed location that would require specific storage level permisssions ., not a Fabric work spcae admin rghts. Eventhough if you're a admin of both the workspaces, hope you may not have the access of necessary Azure storage RBAC roles to browse this Onelake Diagnostic Logs.
I would recommedn you please check with your Azure admin to grant you the access of Storage Blob Data Reader role on the diognastic logs container. Just try in this way. Hope you will browse all logs.
Please read this threads
OneLake diagnostics - Microsoft Fabric | Microsoft Learn
Thank you!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
From what I can see, OneLake diagnostics are handled through Fabric, and I don’t see any Azure Storage account or diagnostic logs container exposed where the Storage Blob Data Reader role could be assigned.
I’ve been Fabric Admin and Global Admin from the beginning and am using the same capacity.
Check out the April 2026 Fabric update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
| User | Count |
|---|---|
| 36 | |
| 19 | |
| 13 | |
| 11 | |
| 10 |