Microsoft announces the public preview of Granular RBAC in Azure Monitor Logs, enabling fine-grained, row-level data access control. This feature enhances security by allowing precise user permissions within a single Log Analytics workspace, leveraging Azure ABAC for tailored access based on roles, locations, or data sensitivity. Unique :

Public Preview: Granular RBAC in Azure Monitor Logs
Microsoft just dropped a game-changing update for Azure Monitor Logs. The new Granular RBAC (Role-Based Access Control) feature is now in public preview. It lets you control data access at the row level, making your log analytics way more secure and flexible.
What’s New with Granular RBAC?
Previously, Azure RBAC allowed access control only at the workspace or table level. Now, you can set permissions down to individual rows in your logs. This means you no longer need multiple workspaces to separate data for different teams or roles.
In other words, you can keep all your data centralized in one Log Analytics workspace. Then, use granular rules to define who sees what—based on roles, locations, or data sensitivity.
“Granular RBAC in Azure Monitor Logs allows you to filter the data that each user can view or query, based on the conditions that you specify.”
Major Updates: How Granular RBAC Works
This update leverages Azure’s Attribute-Based Access Control (ABAC) to extend RBAC capabilities. You can now create or edit Azure role assignments with specific conditions. For example, under “Add condition,” you select the new DataAction called “Read workspace data.”
Then, build expressions using table names and column values to define access rules. Supported operators help you match exactly the data users should access. Once applied, users only see rows matching those conditions.
Example Use Cases
- Restricting access by organizational roles or units
- Limiting data visibility based on geographic location
- Separating sensitive data from general logs
Why This Matters for Azure Users
Centralizing data without sacrificing security is a huge win. It simplifies management, reduces overhead, and enforces least privilege access more effectively. Plus, it aligns with compliance needs by tightly controlling who can see sensitive info.
“You can control which users can access which tables and rows, based on your business or security needs and defined criteria.”
Getting started is straightforward. Just add conditions to your Azure role assignments and define your data access rules. This feature is perfect for organizations aiming to boost their observability and security posture simultaneously.
Wrap-Up
Granular RBAC in Azure Monitor Logs is a smart, flexible upgrade for anyone using Azure’s observability tools. It empowers teams to keep data centralized and secure, without juggling multiple workspaces.
Curious to try it out? Head over to Azure Monitor Logs and start defining your fine-grained access rules today. This feature is still in public preview, so your feedback can help shape its future.
From the New blog articles in Microsoft Community Hub