Merge pull request #264663 from hhunter-ms/hh-198770

[Dapr/ACA] Remessage overview

Author: denrea

articles/container-apps/dapr-authentication-token.md

@@ -5,7 +5,7 @@ ms.author: hannahhunter
 author: hhunter-ms
 ms.service: azure-container-apps
 ms.topic: how-to 
-ms.date: 05/16/2023
+ms.date: 08/02/2024
 ---
 
 # Enable token authentication for Dapr requests

articles/container-apps/dapr-component-connection.md

@@ -6,7 +6,7 @@ ms.author: hannahhunter
 ms.reviewer: nickgreenf
 ms.service: azure-container-apps
 ms.topic: how-to 
-ms.date: 12/20/2023
+ms.date: 08/02/2024
 ms.custom: template-tutorial, service-connector, build-2023, engagement
 ---
 

articles/container-apps/dapr-component-resiliency.md

@@ -6,7 +6,7 @@ services: container-apps
 author: hhunter-ms
 ms.service: azure-container-apps
 ms.topic: conceptual
-ms.date: 02/22/2024
+ms.date: 08/02/2024
 ms.author: hannahhunter
 ms.custom: ignite-fall-2023, ignite-2023, devx-track-azurecli
 # Customer Intent: As a developer, I'd like to learn how to make my container apps resilient using Azure Container Apps.
@@ -91,7 +91,7 @@ resource myPolicyDoc 'Microsoft.App/managedEnvironments/daprComponents/resilienc
 
 ### Before you begin
 
-Log-in to the Azure CLI:
+Log in to the Azure CLI:
 
 ```azurecli
 az login

articles/container-apps/dapr-components.md

@@ -6,7 +6,7 @@ author: hhunter-ms
 ms.service: azure-container-apps
 ms.custom: build-2023
 ms.topic: conceptual
-ms.date: 04/29/2024
+ms.date: 08/02/2024
 ---
 
 # Dapr components in Azure Container Apps

articles/container-apps/dapr-functions-extension.md

@@ -7,7 +7,7 @@ ms.author: hannahhunter
 ms.reviewer: paulyuk
 ms.service: azure-container-apps
 ms.topic: how-to
-ms.date: 10/30/2023
+ms.date: 08/05/2024
 ms.custom: references_regions
 # Customer Intent: I'm a developer who wants to use the Dapr extension for Azure Functions in my Dapr-enabled container app
 ---
@@ -30,7 +30,7 @@ The [Dapr extension for Azure Functions](../azure-functions/functions-bindings-d
 
 ## Set up the environment
 
-1. In the terminal, log into your Azure subscription.
+1. In the terminal, log in to your Azure subscription.
 
    ```azurecli
    az login

articles/container-apps/dapr-overview.md

@@ -1,21 +1,21 @@
 ---
-title: Dapr integration with Azure Container Apps
+title: Microservice APIs powered by Dapr
 description: Learn more about using Dapr on your Azure Container App service to develop applications.
 ms.author: hannahhunter
 author: hhunter-ms
 ms.service: azure-container-apps
 ms.custom: build-2023
 ms.topic: conceptual
-ms.date: 04/22/2024
+ms.date: 08/05/2024
 ---
 
-# Dapr integration with Azure Container Apps
+# Microservice APIs powered by Dapr
 
-[Distributed Application Runtime (Dapr)][dapr-concepts] provides APIs that run as a sidecar process that helps you write and implement simple, portable, resilient, and secured microservices. Dapr works together with Azure Container Apps as an abstraction layer to provide a low-maintenance, serverless, and scalable platform. [Enabling Dapr on your container app][dapr-enable] creates a secondary process alongside your application code that simplifies application intercommunication with Dapr via HTTP or gRPC.
+Azure Container Apps provides APIs powered by [Distributed Application Runtime (Dapr)][dapr-concepts] that help you write and implement simple, portable, resilient, and secured microservices. Dapr works together with Azure Container Apps as an abstraction layer to provide a low-maintenance and scalable platform. Azure Container Apps offers a selection of fully managed Dapr APIs, components, and features, catered specifically to microservice scenarios. Simply [enable and configure Dapr][dapr-enable] as usual in your container app environment.
 
-## Dapr in Azure Container Apps
+## How the microservices APIs work with your container app
 
-Configure Dapr for your container apps environment with a [Dapr-enabled container app][dapr-enable], a [Dapr component configured for your solution][dapr-components], and a Dapr sidecar invoking communication between them. The following diagram demonstrates these core concepts related to Dapr in Azure Container Apps.
+Configure microservices APIs for your container apps environment with a [Dapr-enabled container app][dapr-enable], a [Dapr component configured for your solution][dapr-components], and a Dapr sidecar invoking communication between them. The following diagram demonstrates these core concepts, using the pub/sub API as an example.
 
 :::image type="content" source="media/dapr-overview/dapr-in-aca.png" alt-text="Diagram demonstrating Dapr pub/sub and how it works in Container Apps.":::
 
@@ -60,7 +60,7 @@ Azure Container Apps ensures compatibility with Dapr open source tooling, such a
 - **Actor reminders**: Require a minReplicas of 1+ to ensure reminders is always active and fires correctly.
 - **Jobs**: Dapr isn't supported for jobs.
 
-## Next Steps
+## Next steps
 
 - [Enable Dapr in your container app.][dapr-enable]
 - [Learn how Dapr components work in Azure Container Apps.][dapr-components]

articles/container-apps/faq.yml

@@ -65,7 +65,7 @@ sections:
 
           - **Business reasoning for scaling**: You might be eligible for a quota increase request if the platform limits are blocking your workload demands. Scale limits overrides are evaluated on a per-case basis.
 
-  - name: Dapr
+  - name: Microservice APIs powered by Dapr
     questions:
       - question: |
           What Dapr features and APIs are available in Azure Container Apps?
@@ -82,12 +82,12 @@ sections:
       - question: |
           What is the Dapr version release cadence in Azure Container Apps?
         answer: |
-          Dapr's typical release timeline is up to six weeks after [the Dapr OSS release](https://docs.dapr.io/operations/support/support-release-policy/). The latest Dapr version is made available in Azure Container Apps after rigorous testing. Rolling out to all regions can take roughly up to two weeks.
+          Dapr's typical release timeline is up to six weeks after [the Dapr OSS release](https://docs.dapr.io/operations/support/support-release-policy/). The latest Dapr version is made available in Azure Container Apps after rigorous testing. Rolling out to all regions can take roughly up to two weeks. 
 
       - question: |
           How can I request a Dapr feature enhancement for Azure Container Apps?
         answer:
-          You can submit a feature request via the [Azure Container Apps GitHub repository](https://github.com/microsoft/azure-container-apps/issues/new/choose). Make sure to include "Dapr" in the feature request title.
+
           You can submit a feature request via the [Azure Container Apps GitHub repository](https://github.com/microsoft/azure-container-apps/issues/new/choose). Make sure to include "Dapr" in the feature request title.
   
   - name: Dockerless deployments

articles/container-apps/microservices-dapr-bindings.md

@@ -1,13 +1,13 @@
 ---
 title: "Tutorial: Event-driven work using Dapr Bindings"
 titleSuffix: "Azure Container Apps"
-description: Deploy a sample Dapr Bindings application to Azure Container Apps.
+description: Deploy a sample application to Azure Container Apps that leverages the Dapr Bindings API.
 author: hhunter-ms
 ms.author: hannahhunter
 ms.service: azure-container-apps
 ms.custom: devx-track-dotnet, devx-track-js, devx-track-python
 ms.topic: how-to
-ms.date: 12/20/2023
+ms.date: 08/02/2024
 zone_pivot_group_filename: container-apps/dapr-zone-pivot-groups.json
 zone_pivot_groups: dapr-languages-set
 ---
@@ -16,12 +16,12 @@ zone_pivot_groups: dapr-languages-set
 
 In this tutorial, you create a microservice to demonstrate [Dapr's Bindings API](https://docs.dapr.io/developing-applications/building-blocks/bindings/bindings-overview/) to work with external systems as inputs and outputs. You'll:
 > [!div class="checklist"]
-> * Run the application locally. 
+> * Run the application locally with the Dapr CLI. 
 > * Deploy the application to Azure Container Apps via the Azure Developer CLI with the provided Bicep. 
 
 The service listens to input binding events from a system CRON and then outputs the contents of local data to a PostreSql output binding.
 
-:::image type="content" source="media/microservices-dapr-azd/bindings-quickstart.png" alt-text="Diagram of the Dapr binding application.":::
+:::image type="content" source="media/microservices-dapr-azd/bindings-quickstart.png" alt-text="Diagram of the binding application.":::
 
 ## Prerequisites
 
@@ -38,7 +38,7 @@ Before deploying the application to Azure Container Apps, start by running the P
 
 ### Prepare the project
 
-1. Clone the [sample Dapr application](https://github.com/Azure-Samples/bindings-dapr-nodejs-cron-postgres) to your local machine.
+1. Clone the [sample application](https://github.com/Azure-Samples/bindings-dapr-nodejs-cron-postgres) to your local machine.
 
    ```bash
    git clone https://github.com/Azure-Samples/bindings-dapr-nodejs-cron-postgres.git
@@ -50,7 +50,7 @@ Before deploying the application to Azure Container Apps, start by running the P
    cd bindings-dapr-nodejs-cron-postgres
    ```
 
-### Run the Dapr application using the Dapr CLI
+### Run the application using the Dapr CLI
 
 1. From the sample's root directory, change directories to `db`.
 
@@ -75,13 +75,13 @@ Before deploying the application to Azure Container Apps, start by running the P
    npm install
    ```
 
-1. Run the JavaScript service application with Dapr.
+1. Run the JavaScript service application.
 
    ```bash
    dapr run --app-id batch-sdk --app-port 5002 --dapr-http-port 3500 --resources-path ../components -- node index.js
    ```
 
-   The `dapr run` command runs the Dapr binding application locally. Once the application is running successfully, the terminal window shows the output binding data.
+   The `dapr run` command runs the binding application locally. Once the application is running successfully, the terminal window shows the output binding data.
 
    #### Expected output
 
@@ -108,9 +108,9 @@ Before deploying the application to Azure Container Apps, start by running the P
    docker compose stop
    ```
 
-## Deploy the Dapr application template using Azure Developer CLI
+## Deploy the application template using Azure Developer CLI
 
-Now that you've run the application locally, let's deploy the Dapr bindings application to Azure Container Apps using [`azd`](/azure/developer/azure-developer-cli/overview). During deployment, we will swap the local containerized PostgreSQL for an Azure PostgreSQL component.
+Now that you've run the application locally, let's deploy the bindings application to Azure Container Apps using [`azd`](/azure/developer/azure-developer-cli/overview). During deployment, we will swap the local containerized PostgreSQL for an Azure PostgreSQL component.
 
 ### Prepare the project
 
@@ -136,7 +136,7 @@ cd bindings-dapr-nodejs-cron-postgres
    | Azure Location  | The Azure location for your resources. [Make sure you select a location available for Azure PostgreSQL](../postgresql/flexible-server/overview.md#azure-regions). |
    | Azure Subscription | The Azure subscription for your resources. |
 
-1. Run `azd up` to provision the infrastructure and deploy the Dapr application to Azure Container Apps in a single command.
+1. Run `azd up` to provision the infrastructure and deploy the application to Azure Container Apps in a single command.
 
    ```azdeveloper
    azd up
@@ -215,7 +215,7 @@ Upon successful completion of the `azd up` command:
 
 ### Prepare the project
 
-1. Clone the [sample Dapr application](https://github.com/Azure-Samples/bindings-dapr-python-cron-postgres) to your local machine.
+1. Clone the [sample application](https://github.com/Azure-Samples/bindings-dapr-python-cron-postgres) to your local machine.
 
    ```bash
    git clone https://github.com/Azure-Samples/bindings-dapr-python-cron-postgres.git
@@ -227,7 +227,7 @@ Upon successful completion of the `azd up` command:
    cd bindings-dapr-python-cron-postgres
    ```
 
-### Run the Dapr application using the Dapr CLI
+### Run the application using the Dapr CLI
 
 Before deploying the application to Azure Container Apps, start by running the PostgreSQL container and Python service locally with [Docker Compose](https://docs.docker.com/compose/) and Dapr.
 
@@ -254,13 +254,13 @@ Before deploying the application to Azure Container Apps, start by running the P
    pip install -r requirements.txt
    ```
 
-1. Run the Python service application with Dapr.
+1. Run the Python service application.
 
    ```bash
    dapr run --app-id batch-sdk --app-port 5001 --dapr-http-port 3500 --resources-path ../components -- python3 app.py
    ```
 
-   The `dapr run` command runs the Dapr binding application locally. Once the application is running successfully, the terminal window shows the output binding data.
+   The `dapr run` command runs the binding application locally. Once the application is running successfully, the terminal window shows the output binding data.
 
    #### Expected output
 
@@ -287,9 +287,9 @@ Before deploying the application to Azure Container Apps, start by running the P
    docker compose stop
    ```
 
-## Deploy the Dapr application template using Azure Developer CLI
+## Deploy the application template using Azure Developer CLI
 
-Now that you've run the application locally, let's deploy the Dapr bindings application to Azure Container Apps using [`azd`](/azure/developer/azure-developer-cli/overview). During deployment, we will swap the local containerized PostgreSQL for an Azure PostgreSQL component.
+Now that you've run the application locally, let's deploy the bindings application to Azure Container Apps using [`azd`](/azure/developer/azure-developer-cli/overview). During deployment, we will swap the local containerized PostgreSQL for an Azure PostgreSQL component.
 
 ### Prepare the project
 
@@ -315,7 +315,7 @@ cd bindings-dapr-python-cron-postgres
    | Azure Location  | The Azure location for your resources. [Make sure you select a location available for Azure PostgreSQL](../postgresql/flexible-server/overview.md#azure-regions). |
    | Azure Subscription | The Azure subscription for your resources. |
 
-1. Run `azd up` to provision the infrastructure and deploy the Dapr application to Azure Container Apps in a single command.
+1. Run `azd up` to provision the infrastructure and deploy the application to Azure Container Apps in a single command.
 
    ```azdeveloper
    azd up
@@ -392,7 +392,7 @@ Upon successful completion of the `azd up` command:
 
 ### Prepare the project
 
-1. Clone the [sample Dapr application](https://github.com/Azure-Samples/bindings-dapr-csharp-cron-postgres) to your local machine.
+1. Clone the [sample application](https://github.com/Azure-Samples/bindings-dapr-csharp-cron-postgres) to your local machine.
 
    ```bash
    git clone https://github.com/Azure-Samples/bindings-dapr-csharp-cron-postgres.git
@@ -404,7 +404,7 @@ Upon successful completion of the `azd up` command:
    cd bindings-dapr-csharp-cron-postgres
    ```
 
-### Run the Dapr application using the Dapr CLI
+### Run the application using the Dapr CLI
 
 Before deploying the application to Azure Container Apps, start by running the PostgreSQL container and .NET service locally with [Docker Compose](https://docs.docker.com/compose/) and Dapr.
 
@@ -431,13 +431,13 @@ Before deploying the application to Azure Container Apps, start by running the P
    dotnet build
    ```
 
-1. Run the .NET service application with Dapr.
+1. Run the .NET service application.
 
    ```bash
    dapr run --app-id batch-sdk --app-port 7002 --resources-path ../components -- dotnet run
    ```
 
-   The `dapr run` command runs the Dapr binding application locally. Once the application is running successfully, the terminal window shows the output binding data.
+   The `dapr run` command runs the binding application locally. Once the application is running successfully, the terminal window shows the output binding data.
 
    #### Expected output
 
@@ -464,9 +464,9 @@ Before deploying the application to Azure Container Apps, start by running the P
    docker compose stop
    ```
 
-## Deploy the Dapr application template using Azure Developer CLI
+## Deploy the application template using Azure Developer CLI
 
-Now that you've run the application locally, let's deploy the Dapr bindings application to Azure Container Apps using [`azd`](/azure/developer/azure-developer-cli/overview). During deployment, we will swap the local containerized PostgreSQL for an Azure PostgreSQL component.
+Now that you've run the application locally, let's deploy the bindings application to Azure Container Apps using [`azd`](/azure/developer/azure-developer-cli/overview). During deployment, we will swap the local containerized PostgreSQL for an Azure PostgreSQL component.
 
 ### Prepare the project
 
@@ -492,7 +492,7 @@ cd bindings-dapr-csharp-cron-postgres
    | Azure Location  | The Azure location for your resources. [Make sure you select a location available for Azure PostgreSQL](../postgresql/flexible-server/overview.md#azure-regions). |
    | Azure Subscription | The Azure subscription for your resources. |
 
-1. Run `azd up` to provision the infrastructure and deploy the Dapr application to Azure Container Apps in a single command.
+1. Run `azd up` to provision the infrastructure and deploy the application to Azure Container Apps in a single command.
 
    ```azdeveloper
    azd up
@@ -576,7 +576,7 @@ azd down
 
 ## Next steps
 
-- Learn more about [deploying Dapr applications to Azure Container Apps](./microservices-dapr.md).
+- Learn more about [deploying microservices using Dapr to Azure Container Apps](./microservices-dapr.md).
 - [Enable token authentication for Dapr requests.](./dapr-authentication-token.md)
 - Learn more about [Azure Developer CLI](/azure/developer/azure-developer-cli/overview) and [making your applications compatible with `azd`](/azure/developer/azure-developer-cli/make-azd-compatible).
-- [Scale your Dapr applications using KEDA scalers](./dapr-keda-scaling.md)
+- [Scale your applications using KEDA scalers](./dapr-keda-scaling.md)