Merge pull request #288264 from MicrosoftDocs/main

10/11/2024 PM Publish

Author: Taojunshen

articles/azure-boost/overview.md

@@ -3,7 +3,7 @@ title: Overview of Azure Boost
 description: Learn more about how Azure Boost can Learn more about how Azure Boost can improve security and performance of your virtual machines.
 author: mattmcinnes
 ms.service: azure-virtual-machines
-ms.topic: conceptual
+ms.topic: overview
 ms.custom:
   - ignite-2023
 ms.date: 11/07/2023

articles/azure-fluid-relay/images/container-multiple-users.png

@@ -119,6 +119,7 @@ You can enable Azure NetApp Files storage with cool access during the creation o
 
     * **Enable Cool Access**: This option specifies whether the volume supports cool access.
     * **Coolness Period**: This option specifies the period (in days) after which infrequently accessed data blocks (cold data blocks) are moved to the Azure storage account. The default value is 31 days. The supported values are between 2 and 183 days.
+
     * **Cool Access Retrieval Policy**: This option specifies under which conditions data moves back to the hot tier. You can set this option to **Default**, **On-Read**, or **Never**.
 
         The following list describes the data retrieval behavior with the **Cool Access Retrieval Policy** settings:
@@ -148,6 +149,8 @@ In a capacity pool enabled for cool access, you can enable an existing volume to
 1. On the **Edit** window that appears, set the following options for the volume:
     * **Enable Cool Access**: This option specifies whether the volume supports cool access.
     * **Coolness Period**: This option specifies the period (in days) after which infrequently accessed data blocks (cold data blocks) are moved to the Azure storage account. The default value is 31 days. The supported values are between 2 and 183 days.
+    >[!NOTE]
+    > The coolness period is calculated from the time of volume creation. If any existing volumes are enabled with cool access, the coolness period is applied retroactively on those volumes. This means if certain data blocks on the volumes have been infrequently accessed for the number of days specified in the coolness period, those blocks move to the cool tier once the feature is enabled. 
     * **Cool Access Retrieval Policy**: This option specifies under which conditions data moves back to the hot tier. You can set this option to **Default**, **On-Read**, or **Never**.
 
         The following list describes the data retrieval behavior with the **Cool Access Retrieval Policy** settings:

articles/azure-fluid-relay/images/deployment-complete.png

@@ -5,7 +5,7 @@ services: virtual-machines
 author: ju-shim
 ms.service: azure-virtual-machines
 ms.subservice: azure-confidential-computing
-ms.topic: conceptual
+ms.topic: overview
 ms.date: 06/09/2023
 ms.author: jushiman #ananyagarg #sgallagher #michamcr
 ms.custom: inspire-july-2022
@@ -25,7 +25,7 @@ Microsoft is one of the founding members of the CCC and provides Trusted Executi
 
 :::image type="content" source="media/overview/three-states-and-confidential-computing-consortium-definition.png" alt-text="Diagram of three states of data protection, with confidential computing's data in use highlighted.":::
 
-Azure already encrypts data at rest and in transit. Confidential computing helps protect data in use, including cryptographic keys. Azure confidential computing helps customers prevent unauthorized access to data in use, including from the cloud operator, by processing data in a hardware-based and attested Trusted Execution Environment (TEE).  When Azure confidential computing is enabled and properly configured, Microsoft is not able to access unencrypted customer data.
+Azure already encrypts data at rest and in transit. Confidential computing helps protect data in use, including cryptographic keys. Azure confidential computing helps customers prevent unauthorized access to data in use, including from the cloud operator, by processing data in a hardware-based and attested Trusted Execution Environment (TEE).  When Azure confidential computing is enabled and properly configured, Microsoft isn't able to access unencrypted customer data.
 
 The threat model aims to reduce trust or remove the ability for a cloud provider operator or other actors in the tenant's domain accessing code and data while it's being executed. This is achieved in Azure using a hardware root of trust not controlled by the cloud provider, which is designed to ensure unauthorized access or modification of the environment.
 

articles/azure-netapp-files/manage-cool-access.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: overview
-ms.date: 05/22/2023
+ms.date: 10/09/2024
 ms.author: alkohli
 #Customer intent: As an IT admin, I need to understand what Azure Stack Edge Pro GPU is and how it works so I can use it to process and transform data before sending it to Azure.
 ---

articles/confidential-computing/overview.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: overview
-ms.date: 05/22/2023
+ms.date: 10/09/2024
 ms.author: alkohli
 #Customer intent: As an IT admin, I need to understand what Azure Stack Edge Mini R is and how it works so I can use it to process and transform data before sending to Azure.
 ---

articles/databox-online/azure-stack-edge-gpu-overview.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: overview
-ms.date: 05/22/2023
+ms.date: 10/09/2024
 ms.author: alkohli
 #Customer intent: As an IT admin, I need to understand what Azure Stack Edge Pro 2 is and how it works so I can use it to process and transform data before sending to Azure.
 ---

articles/databox-online/azure-stack-edge-mini-r-overview.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: overview
-ms.date: 05/22/2023
+ms.date: 10/09/2024
 ms.author: alkohli
 #Customer intent: As an IT admin, I need to understand what Azure Stack Edge Pro R is and how it works so I can use it to process and transform data before sending to Azure.
 ---

articles/databox-online/azure-stack-edge-pro-2-overview.md

@@ -5,7 +5,7 @@ author: RoseHJM
 ms.author: rosemalcolm
 ms.service: azure-deployment-environments
 ms.topic: concept-article
-ms.date: 02/24/2024
+ms.date: 10/11/2024
 
 # Customer intent: As a platform engineer, I want to understand ADE and `azd` work together to provision application infrastructure and deploy application code to the new infrastructure.
 
@@ -15,7 +15,7 @@ ms.date: 02/24/2024
 
 In this article, you learn about Azure Developer CLI (`azd`) and how it works with Azure Deployment Environments (ADE) to provision application infrastructure and deploy application code to the new infrastructure.
 
-The Azure Developer CLI (`azd`) is an open-source command-line tool that provides developer-friendly commands that map to key stages in your workflow. You can install `azd` locally on your machine or use it in other environments.
+`azd` is an open-source command-line tool that provides developer-friendly commands that map to key stages in your workflow. You can install `azd` locally on your machine or use it in other environments.
 
 With ADE, you can create environments from an environment definition in a catalog attached to your dev center. By adding `azd`, you can deploy your application code to the new infrastructure.
 
@@ -31,7 +31,7 @@ At scale, using ADE and `azd` together enables you to provide a way for develope
 
 The Azure Developer CLI commands are designed to work with standardized templates. Each template is a code repository that adheres to specific file and folder conventions. The templates contain the assets `azd` needs to provision an Azure Deployment Environment environment. When you run a command like `azd up`, the tool uses the template assets to execute various workflow steps, such as provisioning or deploying resources to Azure.
 
-The following is a typical template structure:
+The following diagram shows a typical template structure:
 
 ```txt
 ├── infra                                        [ Contains infrastructure as code files ]
@@ -46,7 +46,7 @@ The following is a typical template structure:
 
 All `azd` templates include the following assets:
 
-- *infra folder* - The infra folder is not used in `azd` with ADE. It contains all of the Bicep or Terraform infrastructure as code files for the azd template. ADE provides the infrastructure as code files for the `azd` template. You don't need to include these files in your `azd` template.
+- *infra folder* - The infra folder is not used in `azd` with ADE. It contains all of the Bicep or Terraform infrastructure as code files for the `azd` template. ADE provides the infrastructure as code files for the `azd` template. You don't need to include these files in your `azd` template.
 
 - *azure.yaml file* - A configuration file that defines one or more services in your project and maps them to Azure resources for deployment. For example, you might define an API service and a web front-end service, each with attributes that map them to different Azure resources for deployment.
 
@@ -56,9 +56,9 @@ All `azd` templates include the following assets:
 
 Most `azd` templates also optionally include one or more of the following folders:
 
-- *.devcontainer folder* - Allows you to set up a Dev Container environment for your application. This is a common development environment approach that isn't specific to azd.
+- *.devcontainer folder* - Allows you to set up a Dev Container environment for your application. This common development environment approach that isn't specific to `azd` .
 
-- *.github folder* - Holds the CI/CD workflow files for GitHub Actions, which is the default CI/CD provider for azd.
+- *.github folder* - Holds the CI/CD workflow files for GitHub Actions, which is the default CI/CD provider for `azd` .
 
 - *.azdo folder* - If you decide to use Azure Pipelines for CI/CD, define the workflow configuration files in this folder.
 
@@ -91,7 +91,7 @@ To learn more about how to make your ADE environment definition compatible with
 
 ## Enable `azd` support in ADE
 
-To enable `azd` support with ADE, you need to set the `platform.type` to devcenter. This configuration allows `azd` to leverage new dev center components for remote environment state and provisioning, and means that  the infra folder in your templates will effectively be ignored. Instead, `azd` will use one of the infrastructure templates defined in your dev center catalog for resource provisioning.
+To enable `azd` support with ADE, you need to set the `platform.type` to devcenter. This configuration allows `azd` to use new dev center components for remote environment state and provisioning, and means that  the infra folder in your templates is ignored. Instead, `azd` uses one of the infrastructure templates defined in your dev center catalog for resource provisioning.
 
 To enable `azd` support, run the following command:
 
@@ -100,7 +100,7 @@ To enable `azd` support, run the following command:
    ```
 ### Explore `azd` commands
 
-When the dev center feature is enabled, the default behavior of some common azd commands changes to work with these remote environments. For more information, see [Work with Azure Deployment Environments](/azure/developer/azure-developer-cli/ade-integration?branch=main#work-with-azure-deployment-evironments).
+When the dev center feature is enabled, the default behavior of some common `azd` commands changes to work with these remote environments. For more information, see [Work with Azure Deployment Environments](/azure/developer/azure-developer-cli/ade-integration?branch=main#work-with-azure-deployment-evironments).
 
 
 ## Related content