Account does not exist.

Azure Data Studio needs to contact Azure Key Vault to access a column master key for Always Encrypted, but no linked Azure account is available. Please add a linked Azure account and retry the query.

The configured Azure account for {0} does not have sufficient permissions for Azure Key Vault to access a column master key for Always Encrypted.

({0} KB)

Downloaded {0}

Downloading {0}

Failed to start {0}

Installed {0}

Installing {0}

Installing {0} to {1}

Starting {0}

{0} Started

Notebooks

Only .ipynb Notebooks are supported

Unsupported platform

$(sync~spin) {0}...

Cancel

Cancel operation?

Search Server Names

Error notifying of node change: {0}

Root

Session for node {0} does not exist

View Known Issues

{0} component exited unexpectedly. Please restart Azure Data Studio.

% of Cluster data capacity used

Application name

Authentication type

Azure Data Explorer (Kusto)

Cluster

Connect retry count

Connect retry interval

Connect timeout

Connection Resiliency

Context

Custom name of the connection

Database

Database Name

Delay between attempts to restore connection

Failover partner

Indicates the password to be used when connecting to the data source

Indicates the user ID to be used when connecting to the data source

Initialization

KUSTO configuration

Kusto cluster name

Microsoft Entra ID - Universal with MFA support

Name

Name (optional)

New Notebook

No Authentication

Number of attempts to restore connection

Open Notebook

Password

Security

Should BIT columns be displayed as numbers (1 or 0)? If false, BIT columns will be displayed as 'true' or 'false'

Should column definitions be aligned?

Should data types be formatted as UPPERCASE, lowercase, or none (not formatted)

Should keywords be formatted as UPPERCASE, lowercase, or none (not formatted)

Size (MB)

Source

Specifies the method of authenticating with Kusto Server

Status

The length of time (in seconds) to wait for a connection to the server before terminating the attempt and generating an error

The name of the application

The name of the initial catalog or database in the data source

The name of the workstation connecting to Kusto Server

The name or network address of the instance of Kusto Server that acts as a failover partner

Total Machines in the cluster

Type

User Authentication

User name

Workstation Id

[Optional] Log debug output to the console (View -> Output) and then select appropriate output channel from the dropdown

[Optional] Log level for backend services. Azure Data Studio generates a file name every time it starts and if the file already exists the logs entries are appended to that file. For cleanup of old log files see logRetentionMinutes and logFilesRemovalLimit settings. The default tracingLevel does not log much. Changing verbosity could lead to extensive logging and disk space requirements for the logs. Error includes Critical, Warning includes Error, Information includes Warning and Verbose includes Information