rage.fail

azure-batch-account-contributor

derived azure emits CanAdminister

match (effective permission)

{ "action": "Microsoft.Batch/batchAccounts/write", "scope_type": "resource|resourceGroup|subscription" }

where

principal effectively holds Azure Batch Account Contributor / Contributor / Owner (or a custom role granting Microsoft.Batch/batchAccounts/*) at the scope

emit

source type	`Identity`
target type	`*`
source	`<principal>`
target	`<batchAccount in scope>`
permissions	`Microsoft.Batch/batchAccounts/write`

Narrative

{principal.name} has full control of Batch account {target.name} (Microsoft.Batch/batchAccounts/*).

Raw rule rules/derived/azure/batch.yaml

id: azure-batch-account-contributor
emits: CanAdminister
match_effective_permission:
  action: Microsoft.Batch/batchAccounts/write
  scope_type: resource|resourceGroup|subscription
where:
- principal effectively holds Azure Batch Account Contributor / Contributor / Owner (or a custom role
  granting Microsoft.Batch/batchAccounts/*) at the scope
emit:
  source_type: Identity
  target_type: '*'
  source: <principal>
  target: <batchAccount in scope>
  permissions:
  - Microsoft.Batch/batchAccounts/write
  false_positive_note: batchAccounts/* grants full control of the account, pools, jobs, applications and
    keys, but NOT Microsoft.Authorization/*/write. It is still sufficient for code execution via pools/write
    + startTask and for listkeys.
  narrative: '{principal.name} has full control of Batch account {target.name} (Microsoft.Batch/batchAccounts/*).'