Update Azure Application Permissions
Even after you have completed onboarding, you have the option to add or remove Prisma Cloud Security Capabilities. Learn how you can add additional capabilities and the required associated permissions in your Azure subscriptions or tenants after onboarding. To verify if you have missing permissions authenticate into Prisma Cloud and select Settings > Cloud Accounts, and view the Status column.
Update Azure Custom Role Permissions
Before you add new new Security Capabilities, you must first update the permissions granted to the existing custom role created during the onboarding process. This workflow is only available for Azure Tenant and Subscription onboarding. Additionally, Azure China does not support the use of Terraform templates.
Using Terraform Script (Recommended)
Follow the steps below to update your custom role permissions and add or modify existing Prisma Cloud Security Capabilities.
Authenticate using Azure CLI.
Navigate to the directory you created during the onboarding process to store the Terraform file. Sample directory names include onboard-tenant-<tenant-name> or onboard–subscription-<subscription-name>. Ensure that the directory contains the terraform.tfstate file created during the terraform apply step.
Select the required features under Security Capabilities and Permissions section in the Get Started dialog.
Download the Terraform again by clicking on Edit Cloud Account > Configure Account > Download Terraform Script button. The newly downloaded Terraform file contains the updated permissions.
Run the command terraform init > terraform apply and click Confirm.
The existing custom role is now updated with new permissions, once the Terraform execution is completed.
If the terraform.tfstate file is not present in the directory, when the Terraform script is executed, a new app is registered and a new custom role is created.
Manually update Custom Roles
If your organization restricts the use of Terraform scripts, you can choose to manually add the new permissions to the existing custom roles.
Authenticate into Azure portal.
For Tenant onboarding: Navigate to All Services > Management Groups. Click on Tenant Root Group For Subscription onboarding: Navigate to All Services > Subscriptions.
Select Access Control (IAM) > Roles.
Search for the custom role created during onboarding in the Search box and click on the Edit button.
Update the custom role page, click on JSON. You can view your existing custom role JSON with the permissions under the actions list.
Click on the Edit button, append the comma separated new permissions in the actions list. Click on Save > Review + update.
Verify your Role name and Permissions. Click on Update. Wait for few minutes for the custom role to update.
Add Microsoft Graph API Permissions
Follow the steps below to assign graph API permissions at the tenant level.
Add the required permissions.
Navigate to the app you previously registered. Select Azure > Active > Directory > App registrations, and select your app.
Navigate to Microsoft Graph. Select API > permissions > Add a permission > Microsoft Graph > Application permissions.
Add the permissions. Enter the permission name in Select permissions, and select the name from Permission. Add the following permissions:
User.Read.All
Policy.Read.All
Group.Read.All
GroupMember.Read.All
Reports.Read.All
Directory.Read.All
Domain.Read.All
Application.Read.All
If you have enabled additional functions like Agentless Scanning or Workload Protection additional permissions will be required. Review the Roles and Permissions list for the required permissions.
Grant admin consent for Default Directory.
Select Grant admin consent for Default Directory > Yes.
Verify that the permissions are granted.
Confirm that you can see green check marks under the Status column.
Last updated
Was this helpful?

