Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions data-explorer/kusto/api/connection-strings/kusto.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: Kusto connection strings
description: This article describes Kusto connection strings.
ms.reviewer: orspodek
ms.topic: reference
ms.date: 11/18/2024
ms.date: 01/08/2025
---
# Kusto connection strings

Expand Down Expand Up @@ -130,12 +130,14 @@ For application authentication, specify `AAD Federated Security` as `true`. Then
| Uncompressed | Uncompressed | A boolean value that instructs the client to avoid requesting transport-level compression. |

> [!NOTE]
> When the `Streaming` flag is enabled (default), the SDK doesn't buffer all response data in memory; instead, it "pulls" the data from the service when the caller requests it. Therefore, it is essential that in this case the caller properly disposes of the data, such as `IDataReader`.
> once it is done reading the data, as the network connection
> When the `Streaming` flag is enabled (default), the SDK doesn't buffer all response data in memory; instead, it "pulls" the data from the service when the caller requests it. In this case, the caller must properly dispose of the data, such as `IDataReader`,
> once it's done reading the data, as the network connection
> to the service is held open unnecessarily.

## Examples

The following examples show how to set up connections using C#. For examples in other languages, see [App authentication methods](../get-started/app-authentication-methods.md).

:::moniker range="azure-data-explorer"

### Microsoft Entra ID federated authentication with current user identity
Expand Down Expand Up @@ -358,3 +360,9 @@ var kustoConnectionStringBuilder = new KustoConnectionStringBuilder(kustoUri)
```

::: moniker-end

## Related content

* [Connection strings overview](index.md)
* [Kusto API](../index.md)
* [Kusto Query Language (KQL)](../../query/index.md)
17 changes: 12 additions & 5 deletions data-explorer/kusto/query/logical-operators.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: Logical (binary) operators
description: Learn how to use Logical (binary) operators to return a Boolean result.
ms.reviewer: alexans
ms.topic: reference
ms.date: 08/11/2024
ms.date: 01/08/2025
---
# Logical (binary) operators

Expand All @@ -15,7 +15,7 @@ The following logical operators can be used to perform comparisons and evaluatio
|-------------|------|-------|
|Equality |`==` |Returns `true` if both operands are non-null and equal to each other. Otherwise, returns `false`.|
|Inequality |`!=` |Returns `true` if any of the operands are null or if the operands aren't equal to each other. Otherwise, returns `false`.|
|Logical and |`and` |Returns `true` only if both operands are `true`.|
|Logical and |`and` |Returns `true` only if both operands are `true`. The logical `and` has higher precedence than the logical `or`.|
|Logical or |`or` |Returns `true` if either of the operands is `true`, regardless of the other operand.|

> [!NOTE]
Expand Down Expand Up @@ -125,15 +125,22 @@ The following query shows that null values are treated as false.

:::moniker range="azure-data-explorer"
> [!div class="nextstepaction"]
> <a href="https://dataexplorer.azure.com/clusters/help/databases/Samples?query=H4sIAAAAAAAAAysoyswrUchMS9NIys/P0cgrzcnRVEjMS1EoKSpN1YGSaYk5xamaALhLkpUrAAAA" target="_blank">Run the query</a>
> <a href="https://dataexplorer.azure.com/clusters/help/databases/Samples?query=H4sIAAAAAAAAAysoyswrUSgAkbaZaWkaSfn5ORp5pTk5mgqJeSkKJUWlqTpQMi0xpzhVEwDMXGssMQAAAA%3D%3D" target="_blank">Run the query</a>
::: moniker-end

```kusto
print iff(bool(null) and true, true, false)
print print=iff(bool(null) and true, true, false)
```

**Output**

|print_0|
|print|
|--|
|false|

## Related content

* [case()](case-function.md)
* [has operator](has-operator.md)
* [in operator](in-cs-operator.md)
* [startswith operator](startswith-operator.md)
2 changes: 1 addition & 1 deletion data-explorer/kusto/query/scalar-data-types/datetime.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ and the [todatetime()](../todatetime-function.md) function.
|%Y-%m-%d %H:%M|2014-11-08 15:55|
|%Y-%m-%d|2014-11-08|

### [RFC 822](https://www.ietf.org/rfc/rfc0822.txt)
### [RFC 822](https://www.w3.org/Protocols/rfc822/)

|Format|Example|
|------|-------|
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ To prepare your cluster for migration:
> Failure of your cluster to connect to essential services for ingestion and external tables poses a risk of data loss. Additionally, queries calling out to other network-protected services may cease to function.

> [!WARNING]
> The migration step must be performed within a few hours of completing the preparation steps. Delaying the migration might cause the service to malfunction. ```
> The migration step must be performed within a few hours of completing the preparation steps. Delaying the migration might cause the service to malfunction.

## Migrate your cluster

Expand Down Expand Up @@ -152,6 +152,36 @@ After migrating to private endpoints, perform the following checks to verify the

1. Check that ingestion is working properly with the [.show ingestion failures command](/kusto/management/ingestion-failures?view=azure-data-explorer&preserve-view=true) or refer to the guidance in [Monitor queued ingestion with metrics](monitor-queued-ingestion.md). This verification is especially relevant if you need to connect to network secured services for ingestion with services like [Azure Event Hubs](ingest-data-event-hub.md).

## Rollback

To roll back your migration to the previous Virtual Network injected configuration by modifying the ARM template:

1. Locate the [**VirtualNetworkConfiguration**](/azure/templates/microsoft.kusto/clusters?pivots=deployment-language-arm-template#virtualnetworkconfiguration-1) in the ARM template of your cluster.

```json
"virtualNetworkConfiguration": {
"state": "Disabled",
"subnetId": "[concat(parameters('virtualNetworks_Test_vnet_externalid'), '/subnets/newsubnet')]",
"enginePublicIpId": "[parameters('publicIPAddresses_vnetclusterwestus3engine_externalid')]",
"dataManagementPublicIpId": "[parameters('publicIPAddresses_vnetclusterwestus3dm_externalid')]"
},
```

1. Replace **"state": "Disabled"** with **"state": "Enabled"**. Verify that the other properties remain unchanged.

```json
"virtualNetworkConfiguration": {
"state": "Enabled",
"subnetId": "[concat(parameters('virtualNetworks_Test_vnet_externalid'), '/subnets/newsubnet')]",
"enginePublicIpId": "[parameters('publicIPAddresses_vnetclusterwestus3engine_externalid')]",
"dataManagementPublicIpId": "[parameters('publicIPAddresses_vnetclusterwestus3dm_externalid')]"
},
```

1. [**Deploy**](/azure/azure-resource-manager/templates/deployment-tutorial-local-template?tabs=azure-powershell) the ARM template to apply the changes.

This restores your cluster to the previous Virtual Network injected configuration.

## Related content

- [Create a Private Endpoints for Azure Data Explorer](security-network-private-endpoint-create.md)
Expand Down
Loading