Azure Monitor RBAC: Why Workbook Reader Role Isn't Enough to View Your Charts
Part 3 of building and locking down an Azure Monitor lab from scratch I gave a test user read-only access to a single Azure Monitor Workbook. They could open it, enter edit mode, and even change its title on screen. But they couldn't save the change. Worse, the charts couldn't display the Log Analytics data behind them. I initially thought I had a Workbook permissions problem. I was actually…
In the latest part of a series on building and securing an Azure Monitor lab, a test user encountered limitations when attempting to view an Azure Monitor Workbook. Despite being granted read-only access, the user could open the workbook, enter edit mode, and even modify its title, but they were unable to save the changes or view the underlying Log Analytics data in the charts.
The investigation revealed that there were actually two separate permission boundaries to consider: access to the Workbook itself and access to the data it queries. The Workbook Reader role, which allows viewing workbooks, does not include the permission to save changes. This discrepancy between viewing and editing capabilities under a read-only role became evident when trying to save the edited workbook title.
Additionally, the user was unable to load the charts inside the Workbook, indicating that the read-only role did not grant sufficient access to the data being queried. The findings were consistent across both the Azure Portal and Azure CLI interfaces, confirming that the Workbook Reader role alone was insufficient to allow the user to view the charts in the workbook.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.