Skip to content

Commit 3aeac35

Browse files
authored
Merge pull request #111665 from lp-code/lp-code-patch-1
Clarify the meaning of the attestation report
2 parents 66238e9 + 826b3a0 commit 3aeac35

File tree

2 files changed

+8
-2
lines changed

2 files changed

+8
-2
lines changed

articles/container-instances/container-instances-tutorial-deploy-confidential-container-default-portal.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,10 @@ Open the overview for the container group by navigating to **Resource Groups** >
6565

6666
2. Once its status is *Running*, navigate to the IP address in your browser.
6767

68-
:::image type="content" source="media/container-instances-confidential-containers-tutorials/confidential-containers-aci-hello-world.png" alt-text="Screenshot of the hello world application running, PNG.":::
68+
:::image type="content" source="media/container-instances-confidential-containers-tutorials/confidential-containers-aci-hello-world.png" alt-text="Screenshot of the hello world application running, PNG.":::
69+
70+
The presence of the attestation report below the Azure Container Instances logo confirms that the container is running on hardware that supports a hardware-based and attested trusted execution environment (TEE).
71+
If you deploy to hardware that does not support a TEE, for example by choosing a region where the [ACI Confidential SKU is not available](./container-instances-region-availability.md#linux-container-groups), no attestation report will be shown.
6972

7073
Congratulations! You have deployed a confidential container on Azure Container Instances which is displaying a hardware attestation report in your browser.
7174

articles/container-instances/container-instances-tutorial-deploy-confidential-containers-cce-arm.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -194,7 +194,7 @@ With the ARM template that you've crafted and the Azure CLI confcom extension, y
194194

195195
* **Subscription**: select an Azure subscription.
196196
* **Resource group**: select **Create new**, enter a unique name for the resource group, and then select **OK**.
197-
* **Location**: select a location for the resource group. Example: **North Europe**.
197+
* **Location**: select a location for the resource group. Choose a region where the [Confidential SKU is supported](./container-instances-region-availability.md#linux-container-groups). Example: **North Europe**.
198198
* **Name**: accept the generated name for the instance, or enter a name.
199199
* **Image**: accept the default image name. This sample Linux image displays a hardware attestation.
200200

@@ -224,6 +224,9 @@ Use the Azure portal or a tool such as the [Azure CLI](container-instances-quick
224224

225225
![Screenshot of browser view of app deployed using Azure Container Instances, PNG.](media/container-instances-confidential-containers-tutorials/confidential-containers-aci-hello-world.png)
226226

227+
The presence of the attestation report below the Azure Container Instances logo confirms that the container is running on hardware that supports a TEE.
228+
If you deploy to hardware that does not support a TEE, for example by choosing a region where the ACI Confidential SKU is not available, no attestation report will be shown.
229+
227230
## Next Steps
228231

229232
Now that you have deployed a confidential container group on ACI, you can learn more about how policies are enforced.

0 commit comments

Comments
 (0)