Mar 26 2020 11:14 AM
I've recently started testing the 3 built-in Azure Sentinel RBAC roles based on https://docs.microsoft.com/en-us/azure/sentinel/roles
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.
Mar 26 2020 11:37 AM
Solution@ehloworldio Try also adding the Log Analytics Reader (or Contributor) role and try again.
Mar 27 2020 01:24 PM
@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.
Apr 08 2020 01:59 AM
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/Read
Your user will have access with read rights on the Azure Sentinel and on saved Workbooks.
Apr 20 2020 12:26 PM
@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.
Apr 22 2020 01:54 PM
Apr 23 2020 02:12 AM
@MS_Clouder - Thanks for your reply. I am talking about the Azure Dashboards that utilize graphs pinned from workbook and some custom graph that query sentinel workspace logs. As an MSSP when you build these dashboards and push to customer tenants workspace using Azure lighthouse we dont get the control to assign RBAC permissions for the dashboard resource that resides in customer tenant.
Mar 26 2020 11:37 AM
Solution@ehloworldio Try also adding the Log Analytics Reader (or Contributor) role and try again.