Use an SLA for Azure Data Explorer clusters

March 21, 2025 ยท View on GitHub

SYNOPSIS

Use SKUs that include an SLA when configuring Azure Data Explorer (ADX) clusters.

DESCRIPTION

When choosing a SKU for an ADX cluster you should consider the SLA that is included in the SKU. ADX clusters offer a range of offerings. Development SKUs are designed for early non-production use and do not include any SLA.

RECOMMENDATION

Consider using a production ready SKU that includes a SLA.

EXAMPLES

Configure with Azure template

To deploy clusters that pass this rule:

  • Set the sku.tier property to Standard.
  • Set the sku.name property to non-development SKU such as Standard_D11_v2.

For example:

{
  "type": "Microsoft.Kusto/clusters",
  "apiVersion": "2023-08-15",
  "name": "[parameters('name')]",
  "location": "[parameters('location')]",
  "sku": {
    "name": "Standard_D11_v2",
    "tier": "Standard"
  },
  "identity": {
    "type": "SystemAssigned"
  },
  "properties": {
    "enableDiskEncryption": true
  }
}

Configure with Bicep

To deploy clusters that pass this rule:

  • Set the sku.tier property to Standard.
  • Set the sku.name property to non-development SKU such as Standard_D11_v2.

For example:

resource adx 'Microsoft.Kusto/clusters@2023-08-15' = {
  name: name
  location: location
  sku: {
    name: 'Standard_D11_v2'
    tier: 'Standard'
  }
  identity: {
    type: 'SystemAssigned'
  }
  properties: {
    enableDiskEncryption: true
  }
}