May 11 2021 11:41 AM
May 11 2021 11:41 AM
Hi @AzureSentinel Team,
I believe this is a bug unless there is any reason to do so.
At Azure Sentinel Automation (Preview) when tried to assign permission for logic app I am getting the error below.
Pls Note: Although i am the owner of subscription i am not able to assign the permission whereas only global admin with subscription ownership can do this role assignment.
Saving automation rule 'TEST 1' failed. Error: Caller is missing required playbook triggering permissions on playbook resource '/subscriptions/xxx/resourceGroups/yyy/providers/Microsoft.Logic/workflows/logicapp1', or Azure Sentinel is missing required permissions to verify the caller has permissions
May 11 2021 12:25 PM
@PrashTechTalk I think this is related to there being a requirement to allow Automation to kick off the playbook in the resource group that the playbook resides in. Got to the Azure Sentinel Settings menu option, then select Settings in header, and expand Playbook permissions. Click on the "Configure permissions" button and assign the correct permissions to your resource group if it does not already have the permissions needed.
May 12 2021 04:15 AM
May 25 2021 07:19 PM
Jun 09 2021 12:40 PM
Jun 11 2021 06:15 AM
@Javier Soriano Hi Javier, Yes it is though Azure Lighthouse setup.
Jun 14 2021 12:27 AM
Jun 14 2021 04:33 AM
Jun 14 2021 06:10 AM - edited Jun 14 2021 06:11 AM
Perfect. Very same response from your support team as well on this issue. Good to highlight this at the documentation or may have improved from the time the this issue was raised.
There are two main scenarios when managing cross-tenant automation rules:
• Automation rule created in the customer tenant is configured to run a playbook located in the service provider tenant. This approach is normally used to protect intellectual property in the playbook. Nothing special is required for this scenario to work. Just grant permissions to the relevant resource group where the playbook is located via Manage playbook permissions menu as explained here.
• Automation rule created in the customer tenant is configured to run a playbook located in the customer tenant. Used when there is no need to protect intellectual property. For this scenario to work, permissions to execute the playbook need to be granted to Azure Sentinel in both tenants. In the customer tenant, you grant them via Manage playbook permissions menu as explained here. To grant the relevant permissions to the service provider tenant, you need to include the Azure Security Insights app in your Azure Lighthouse delegation template with the Azure Sentinel Automation Contributor role. The scenario looks like this:
Jun 14 2021 07:04 AM
Jun 14 2021 08:44 AM - edited Jun 14 2021 08:47 AM
@Javier Soriano - I noticed an intresting one here.
Scenario 1: Unable to see Manage Permission Link
Although being a owner of the azure subscription and adding logic app contributor role to my user id within the customer tenant. I am not able to see the Manage Permission link at the sentinel automation rule. Why cant one edit the permission in this case ??
Do you expect the user to have Azure Sentinel Contributor role other than owner and logic app contributor. ??
Scenario 2: Able to see Manage Permission Link but cannot modify.
With Azure lighthouse after including delegation of Azure Security Insights with Azure Sentinel Contributor role from the service provider tenant I am able to check its permission but not change it, this is acceptable as I am NOT in the service provider tenant and with Azure Lighthouse a user can max have a contributor role.
Jun 14 2021 08:57 AM
Jun 14 2021 01:46 PM
Jun 14 2021 01:49 PM
Jun 15 2021 01:16 AM