Permissions in Azure Sentinel

Azure Sentinel uses Azure role-based access control (Azure RBAC) to provide built-in roles that can be assigned to users, groups, and services in Azure.

Use Azure RBAC to create and assign roles within your security operations team to grant appropriate access to Azure Sentinel. The different roles give you fine-grained control over what users of Azure Sentinel can see and do. Azure roles can be assigned in the Azure Sentinel workspace directly (see note below), or in a subscription or resource group that the workspace belongs to, which Azure Sentinel will inherit.

Roles for working in Azure Sentinel

Azure Sentinel-specific roles

All Azure Sentinel built-in roles grant read access to the data in your Azure Sentinel workspace.

Note

  • For best results, these roles should be assigned on the resource group that contains the Azure Sentinel workspace. This way, the roles will apply to all the resources that are deployed to support Azure Sentinel, as those resources should also be placed in that same resource group.

  • Another option is to assign the roles directly on the Azure Sentinel workspace itself. If you do this, you must also assign the same roles on the SecurityInsights solution resource in that workspace. You may need to assign them on other resources as well, and you will need to be constantly managing role assignments on resources.

Additional roles and permissions

Users with particular job requirements may need to be assigned additional roles or specific permissions in order to accomplish their tasks.

  • Working with playbooks to automate responses to threats

    Azure Sentinel uses playbooks for automated threat response. Playbooks are built on Azure Logic Apps, and are a separate Azure resource. You might want to assign to specific members of your security operations team the ability to use Logic Apps for Security Orchestration, Automation, and Response (SOAR) operations. You can use the Logic App Contributor role to assign explicit permission for using playbooks.

  • Connecting data sources to Azure Sentinel

    For a user to add data connectors, you must assign the user write permissions on the Azure Sentinel workspace. Also, note the required additional permissions for each connector, as listed on the relevant connector page.

  • Guest users assigning incidents

    If a guest user needs to be able to assign incidents, then in addition to the Azure Sentinel Responder role, the user will also need to be assigned the role of Directory Reader. Note that this role is not an Azure role but an Azure Active Directory role, and that regular (non-guest) users have this role assigned by default.

  • Creating and deleting workbooks

    For a user to create and delete an Azure Sentinel workbook, the user will also need to be assigned with the Azure Monitor role of Monitoring Contributor. This role is not necessary for using workbooks, but only for creating and deleting.

Other roles you might see assigned

In assigning Azure Sentinel-specific Azure roles, you may come across other Azure and Log Analytics Azure roles that may have been assigned to users for other purposes. You should be aware that these roles grant a wider set of permissions that includes access to your Azure Sentinel workspace and other resources:

For example, a user who is assigned the Azure Sentinel Reader role, but not the Azure Sentinel Contributor role, will still be able to edit items in Azure Sentinel if assigned the Azure-level Contributor role. Therefore, if you want to grant permissions to a user only in Azure Sentinel, you should carefully remove this user’s prior permissions, making sure you do not break any needed access to another resource.

Azure Sentinel roles and allowed actions

The following table summarizes the Azure Sentinel roles and their allowed actions in Azure Sentinel.

Role Create and run playbooks Create and edit analytic rules and other Azure Sentinel resources * Manage incidents (dismiss, assign, etc.) View data, incidents, workbooks, and other Azure Sentinel resources
Azure Sentinel Reader -- -- --
Azure Sentinel Responder -- --
Azure Sentinel Contributor --
Azure Sentinel Contributor + Logic App Contributor

* Creating and deleting workbooks requires the additional Monitoring Contributor role. For more information, see Additional roles and permissions.

Custom roles and advanced Azure RBAC

Role recommendations

After understanding how roles and permissions work in Azure Sentinel, you may want to use the following best practice guidance for applying roles to your users:

User type Role Resource group Description
Security analysts Azure Sentinel Responder Azure Sentinel's resource group View data, incidents, workbooks, and other Azure Sentinel resources.

Manage incidents, such as assigning or dismissing incidents.
Logic Apps Contributor Azure Sentinel's resource group, or the resource group where your playbooks are stored Attach playbooks to analytics and automation rules and run playbooks.

Note: This role also allows users to modify playbooks.
Security engineers Azure Sentinel Contributor Azure Sentinel's resource group View data, incidents, workbooks, and other Azure Sentinel resources.

Manage incidents, such as assigning or dismissing incidents.

Create and edit workbooks, analytics rules, and other Azure Sentinel resources.
Logic Apps Contributor Azure Sentinel's resource group, or the resource group where your playbooks are stored Attach playbooks to analytics and automation rules and run playbooks.

Note: This role also allows users to modify playbooks.
Service Principal Azure Sentinel Contributor Azure Sentinel's resource group Automated configuration for management tasks

Tip

Additional roles may be required depending on the data you are ingesting or monitoring. For example, Azure AD roles may be required, such as the global admin or security admin roles, to set up data connectors for services in other Microsoft portals.

Next steps

In this document, you learned how to work with roles for Azure Sentinel users and what each role enables users to do.

Find blog posts about Azure security and compliance at the Azure Sentinel Blog.