rage.fail

azure-vmss-instance-write

derived azure emits CanModifyConfiguration

match (effective permission)

{ "action": "Microsoft.Compute/virtualMachineScaleSets/virtualMachines/write", "scope_type": "resource|resourceGroup|subscription|mg" }

emit

source type	`Identity`
target type	`*`
source	`<principal>`
target	`<scale set instance>`
permissions	`Microsoft.Compute/virtualMachineScaleSets/virtualMachines/write`

Narrative

{principal.name} can modify instance {instance.name} of {vmss.name} (virtualMachineScaleSets/virtualMachines/write).

Raw rule rules/derived/azure/vmss.yaml

id: azure-vmss-instance-write
emits: CanModifyConfiguration
match_effective_permission:
  action: Microsoft.Compute/virtualMachineScaleSets/virtualMachines/write
  scope_type: resource|resourceGroup|subscription|mg
emit:
  source_type: Identity
  target_type: '*'
  source: <principal>
  target: <scale set instance>
  permissions:
  - Microsoft.Compute/virtualMachineScaleSets/virtualMachines/write
  false_positive_note: Per-instance write does not add an extension by itself; pair with extension/runCommand
    for execution. Primarily meaningful in Flexible orchestration mode; under Uniform orchestration per-instance
    model overrides are limited.
  narrative: '{principal.name} can modify instance {instance.name} of {vmss.name} (virtualMachineScaleSets/virtualMachines/write).'