Forum Discussion
Sentinel RBAC not working for Workbooks
I've recently started testing the 3 built-in Azure Sentinel RBAC roles based on https://docs.microsoft.com/en-us/azure/sentinel/roles
- Azure Sentinel reader
- Azure Sentinel responder
- Azure Sentinel contributor
Based on the matrix in the documentation "Azure Sentinel contributor" should give the user access to add and view Workbooks. However testing show I was able to add and save new workbooks but not view saved workbooks. All other accesses seems fine I could run queries and everything.
ehloworldio Try also adding the Log Analytics Reader (or Contributor) role and try again.
6 Replies
Hi ehloworldio,
You can create a custom role to allow users to read Workbooks to avoid the read rights on the whole of Log Analytics.
For example, you can add the read rights on Azure Sentinel and on Workbooks.
When you create the custom role, start to use the Azure Sentinel Reader and add these permissions:
Microsoft.Insights/Components/Read
Microsoft.Insights/Components/Events/Read
Microsoft.Insights/Components/Query/ReadYour user will have access with read rights on the Azure Sentinel and on saved Workbooks.
- PrashTechTalkBrass Contributor
MS_Clouder - I am using Azure Lighthouse thus published a shared dashboard into my customer tenants workspace. I am lost on how to implement RBAC to access/limit users from accessing this dashboard which is at a customer tenant.
Appreciate any advice.
- Hi Prash,
What dashboard are you talking about? Sentinel dashboard?
Perhaps, you’ll get a better answer to your question on another topic specialized on Azure Lighthouse if it’s this one.
In my previous post, I talked about the reading rights on Azure Sentinel Workbook.
Let me know if I can help you.
Joris
- PrashTechTalkBrass Contributor
ehloworldio Inspite of assigning Azure Sentinel Reader role and Log Analytics Reader Role for my guest user of a different tenant, the user is is not able to view the workbook. Appreciate your advice.
- Rod_Trent
Microsoft
ehloworldio Try also adding the Log Analytics Reader (or Contributor) role and try again.