Skip to content

Commit 5fc83d0

Browse files
authored
Update resource-context-rbac.md
1 parent 16b4d1d commit 5fc83d0

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

articles/sentinel/resource-context-rbac.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.author: cwatson
1212

1313
# Manage access to Microsoft Sentinel data by resource
1414

15-
Typically, users who have access to a Log Analytics workspace enabled for Microsoft Sentinel also have access to all the workspace data, including security content. Administrators can use [Azure roles](roles.md) to configure access to specific features in Microsoft Sentinel, depending on the access requirements in their team.
15+
Access to a workspace is managed by using Azure RBAC. Typically, users who have access to a Log Analytics workspace enabled for Microsoft Sentinel also have access to all the workspace data, including security content. Administrators can use [Azure roles](roles.md) to configure access to specific features in Microsoft Sentinel, depending on the access requirements in their team.
1616

1717
However, you may have some users who need to access only specific data in your workspace, but shouldn't have access to the entire Microsoft Sentinel environment. For example, you may want to provide a non-security operations (non-SOC) team with access to the Windows event data for the servers they own.
1818

@@ -154,6 +154,10 @@ The following list describes scenarios where other solutions for data access may
154154

155155

156156

157-
## Next steps
157+
## Related content
158158

159-
For more information, see [Permissions in Microsoft Sentinel](roles.md).
159+
For more information, see:
160+
161+
- [Permissions in Microsoft Sentinel](roles.md)
162+
- [Manage access to Log Analytics workspaces](/azure/azure-monitor/logs/manage-access)
163+
- [What is Azure role-based access control (Azure RBAC)?](/azure/role-based-access-control/overview)

0 commit comments

Comments
 (0)