Skip to content

Commit bd2da85

Browse files
Merge pull request #2758 from MicrosoftDocs/main638957126015727695sync_temp
For protected branch, push strategy should use PR and merge to target branch method to work around git push error
2 parents 9fca3e9 + 4a3b08e commit bd2da85

File tree

2 files changed

+47
-0
lines changed

2 files changed

+47
-0
lines changed
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
title: Enable confidential compute on your Azure Data Explorer cluster
3+
description: Learn how to deploy Azure Data Explorer clusters with confidential compute SKUs for hardware-based security and sensitive workload protection.
4+
ms.reviewer: bwatts
5+
ms.topic: how-to
6+
ms.date: 09/30/2025
7+
ms.custom: references_regions
8+
9+
#Customer intent: I want to deploy Azure Data Explorer cluster in an confidential compute SKU.
10+
---
11+
12+
# Enable confidential compute on your Azure Data Explorer cluster (preview)
13+
14+
Confidential compute virtual machines (VMs) provide strong security and confidentiality for tenants. They establish a hardware-enforced boundary between your application and the virtualization stack. Clusters deployed with confidential compute VMs ensure hardware-based security and data confidentiality for sensitive workloads by establishing a trusted execution environment (TEE). For more information, see [confidential compute](/azure/confidential-computing/confidential-vm-overview) and [Azure guidance for isolated compute](/azure/confidential-computing/confidential-vm-faq).
15+
16+
Azure Data Explorer supports confidential compute using the SKU [**ECasv5 and ECadsv5 Series Virtual Machines**](https://learn.microsoft.com/azure/virtual-machines/ecasv5-ecadsv5-series). This SKU can scale up and down automatically to meet the needs of your application or enterprise.
17+
18+
Confidential compute VMs are ideal for running sensitive workloads that require a trusted execution environment (TEE). For more information about supported SKUs for Azure Data Explorer, see [Select the correct VM SKU for your Azure Data Explorer cluster](manage-cluster-choose-sku.md).
19+
20+
## Enable confidential compute on Azure Data Explorer cluster
21+
22+
To enable confidential compute in Azure Data Explorer, follow one of these steps:
23+
24+
* [Create a cluster with confidential compute SKU](#create-a-cluster-with-confidential-compute-sku)
25+
* [Select the confidential compute SKU on an existing cluster](#select-the-confidential-compute-sku-on-an-existing-cluster)
26+
27+
## Create a cluster with confidential compute SKU
28+
29+
1. Follow the instructions in [create an Azure Data Explorer cluster and database in the Azure portal](create-cluster-and-database.md).
30+
2. In [create a cluster](create-cluster-and-database.md#create-a-cluster) within the **Basics** tab, select one of the **ECasv5 and ECadsv5 Series Virtual Machine** SKUs from the **Compute specifications** dropdown.
31+
32+
## Select the confidential compute SKU on an existing cluster
33+
34+
1. On your Azure Data Explorer cluster **Overview** screen, select **Scale up**.
35+
1. In the **Compute optimized** section, select one of the **ECasv5 and ECadsv5 Series Virtual Machine** SKUs.
36+
1. Select **Apply** to update the SKU.
37+
38+
> [!TIP]
39+
> The scale-up process might take a few minutes.
40+
41+
## Related content
42+
43+
* [Manage cluster vertical scaling (scale up) in Azure Data Explorer to accommodate changing demand](manage-cluster-vertical-scaling.md)
44+
* [Select the correct VM SKU for your Azure Data Explorer cluster](manage-cluster-choose-sku.md)
45+

data-explorer/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,6 +79,8 @@ items:
7979
href: cross-tenant-query-and-commands.md
8080
- name: Isolated compute
8181
href: isolated-compute.md
82+
- name: Confidential compute
83+
href: confidential-compute.md
8284
- name: Network security
8385
items:
8486
- name: Network security overview

0 commit comments

Comments
 (0)