Microsoft.Kusto clusters 2019-01-21

Bicep resource definition

The clusters resource type can be deployed with operations that target:

For a list of changed properties in each API version, see change log.

Resource format

To create a Microsoft.Kusto/clusters resource, add the following Bicep to your template.

resource symbolicname 'Microsoft.Kusto/clusters@2019-01-21' = {
  name: 'string'
  location: 'string'
  tags: {
    tagName1: 'tagValue1'
    tagName2: 'tagValue2'
  }
  sku: {
    capacity: int
    name: 'string'
    tier: 'string'
  }
  properties: {
    trustedExternalTenants: [
      {
        value: 'string'
      }
    ]
  }
}

Property values

clusters

Name Description Value
name The resource name string (required)

Character limit: 4-22

Valid characters:
Lowercase letters and numbers.

Start with letter.

Resource name must be unique across Azure.
location The geo-location where the resource lives string (required)
tags Resource tags. Dictionary of tag names and values. See Tags in templates
sku The SKU of the cluster. AzureSku (required)
properties The cluster properties. ClusterProperties

ClusterProperties

Name Description Value
trustedExternalTenants The cluster's external tenants. TrustedExternalTenant[]

TrustedExternalTenant

Name Description Value
value GUID representing an external tenant. string

AzureSku

Name Description Value
capacity The number of instances of the cluster. int
name SKU name. 'Dev(No SLA)_Standard_D11_v2'
'Standard_D11_v2'
'Standard_D12_v2'
'Standard_D13_v2'
'Standard_D14_v2'
'Standard_DS13_v2+1TB_PS'
'Standard_DS13_v2+2TB_PS'
'Standard_DS14_v2+3TB_PS'
'Standard_DS14_v2+4TB_PS'
'Standard_L16s'
'Standard_L4s'
'Standard_L8s' (required)
tier SKU tier. 'Basic'
'Standard' (required)

Quickstart templates

The following quickstart templates deploy this resource type.

Template Description
Create a database watcher

Deploy to Azure
This sample creates a database watcher for Azure SQL and configures its data store, SQL targets, and managed private endpoints
Azure Digital Twins with Time Data History Connection

Deploy to Azure
This template creates an Azure Digital Twins instance configured with a time series data history connection. In order to create a connection, other resources must be created such as an Event Hubs namespace, an event hub, Azure Data Explorer cluster, and a database. Data is sent to an event hub which eventually forwards the data to the Azure Data Explorer cluster. Data is stored in a database table in the cluster
Create a cluster a database

Deploy to Azure
This template allows you to create a cluster and a database.
Deploy Azure Data Explorer DB with Cosmos DB connection

Deploy to Azure
Deploy Azure Data Explorer DB with Cosmos DB connection.
Deploy Azure Data Explorer db with Event Grid connection

Deploy to Azure
Deploy Azure Data Explorer db with Event Grid connection.
Deploy Azure Data Explorer db with Event Hub connection

Deploy to Azure
Deploy Azure Data Explorer db with Event Hub connection.
Deploy Azure Data Explorer cluster into your VNet

Deploy to Azure
This template allows you deploy a cluster into your VNet.

ARM template resource definition

The clusters resource type can be deployed with operations that target:

For a list of changed properties in each API version, see change log.

Resource format

To create a Microsoft.Kusto/clusters resource, add the following JSON to your template.

{
  "type": "Microsoft.Kusto/clusters",
  "apiVersion": "2019-01-21",
  "name": "string",
  "location": "string",
  "tags": {
    "tagName1": "tagValue1",
    "tagName2": "tagValue2"
  },
  "sku": {
    "capacity": "int",
    "name": "string",
    "tier": "string"
  },
  "properties": {
    "trustedExternalTenants": [
      {
        "value": "string"
      }
    ]
  }
}

Property values

clusters

Name Description Value
type The resource type 'Microsoft.Kusto/clusters'
apiVersion The resource api version '2019-01-21'
name The resource name string (required)

Character limit: 4-22

Valid characters:
Lowercase letters and numbers.

Start with letter.

Resource name must be unique across Azure.
location The geo-location where the resource lives string (required)
tags Resource tags. Dictionary of tag names and values. See Tags in templates
sku The SKU of the cluster. AzureSku (required)
properties The cluster properties. ClusterProperties

ClusterProperties

Name Description Value
trustedExternalTenants The cluster's external tenants. TrustedExternalTenant[]

TrustedExternalTenant

Name Description Value
value GUID representing an external tenant. string

AzureSku

Name Description Value
capacity The number of instances of the cluster. int
name SKU name. 'Dev(No SLA)_Standard_D11_v2'
'Standard_D11_v2'
'Standard_D12_v2'
'Standard_D13_v2'
'Standard_D14_v2'
'Standard_DS13_v2+1TB_PS'
'Standard_DS13_v2+2TB_PS'
'Standard_DS14_v2+3TB_PS'
'Standard_DS14_v2+4TB_PS'
'Standard_L16s'
'Standard_L4s'
'Standard_L8s' (required)
tier SKU tier. 'Basic'
'Standard' (required)

Quickstart templates

The following quickstart templates deploy this resource type.

Template Description
Create a database watcher

Deploy to Azure
This sample creates a database watcher for Azure SQL and configures its data store, SQL targets, and managed private endpoints
Azure Digital Twins with Time Data History Connection

Deploy to Azure
This template creates an Azure Digital Twins instance configured with a time series data history connection. In order to create a connection, other resources must be created such as an Event Hubs namespace, an event hub, Azure Data Explorer cluster, and a database. Data is sent to an event hub which eventually forwards the data to the Azure Data Explorer cluster. Data is stored in a database table in the cluster
Create a cluster a database

Deploy to Azure
This template allows you to create a cluster and a database.
Deploy Azure Data Explorer DB with Cosmos DB connection

Deploy to Azure
Deploy Azure Data Explorer DB with Cosmos DB connection.
Deploy Azure Data Explorer db with Event Grid connection

Deploy to Azure
Deploy Azure Data Explorer db with Event Grid connection.
Deploy Azure Data Explorer db with Event Hub connection

Deploy to Azure
Deploy Azure Data Explorer db with Event Hub connection.
Deploy Azure Data Explorer cluster into your VNet

Deploy to Azure
This template allows you deploy a cluster into your VNet.

Terraform (AzAPI provider) resource definition

The clusters resource type can be deployed with operations that target:

  • Resource groups

For a list of changed properties in each API version, see change log.

Resource format

To create a Microsoft.Kusto/clusters resource, add the following Terraform to your template.

resource "azapi_resource" "symbolicname" {
  type = "Microsoft.Kusto/clusters@2019-01-21"
  name = "string"
  location = "string"
  parent_id = "string"
  tags = {
    tagName1 = "tagValue1"
    tagName2 = "tagValue2"
  }
  body = jsonencode({
    properties = {
      trustedExternalTenants = [
        {
          value = "string"
        }
      ]
    }
    sku = {
      capacity = int
      name = "string"
      tier = "string"
    }
  })
}

Property values

clusters

Name Description Value
type The resource type "Microsoft.Kusto/clusters@2019-01-21"
name The resource name string (required)

Character limit: 4-22

Valid characters:
Lowercase letters and numbers.

Start with letter.

Resource name must be unique across Azure.
location The geo-location where the resource lives string (required)
parent_id To deploy to a resource group, use the ID of that resource group. string (required)
tags Resource tags. Dictionary of tag names and values.
sku The SKU of the cluster. AzureSku (required)
properties The cluster properties. ClusterProperties

ClusterProperties

Name Description Value
trustedExternalTenants The cluster's external tenants. TrustedExternalTenant[]

TrustedExternalTenant

Name Description Value
value GUID representing an external tenant. string

AzureSku

Name Description Value
capacity The number of instances of the cluster. int
name SKU name. "Dev(No SLA)_Standard_D11_v2"
"Standard_D11_v2"
"Standard_D12_v2"
"Standard_D13_v2"
"Standard_D14_v2"
"Standard_DS13_v2+1TB_PS"
"Standard_DS13_v2+2TB_PS"
"Standard_DS14_v2+3TB_PS"
"Standard_DS14_v2+4TB_PS"
"Standard_L16s"
"Standard_L4s"
"Standard_L8s" (required)
tier SKU tier. "Basic"
"Standard" (required)