Azure Access Control Policy Creation
"contains": "Microsoft.Web/serverFarms"
},
{
"field": "type",
"contains": "Microsoft.Web/sites"
},
{
"field": "type",
"contains": "Microsoft.Web/connections"
},
{
"field": "type",
"contains": "Microsoft.ContainerRegistry/registries"
},
{
"field": "type",
"contains": "Microsoft.Logic/workflows"
},
{
"field": "type",
"contains": "Microsoft.alertsmanagement"
},
{
"field": "type",
"contains": "Microsoft.Storage/storageAccounts"
}
]
}
},
"then": {
"effect": "Deny"
}
}
}
In this case, the policy allows the creation of only 1 container that is named ci1234567 that uses 1.5 GB of memory and a single CPU. The use of any GPUs is blocked by the policy. As of this writing, the GPU feature for ACI is in preview. Consequently, the method for blocking or limiting GPUs as shown above may change. Limiting resources by SKU, family, Capacity, Tier In some cases, it may be desirable to limit a service, for example SQL databases or web apps by by SKU, family, tier, or some other property to prevent abuse. Doing so requires that you use an "allOf