Merge pull request #313797 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-27 17:00 UTC

Author: learn-build-service-prod[bot]

articles/container-apps/authentication-github.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: how-to
-ms.date: 10/28/2024
+ms.date: 03/23/2026
 ms.author: cshoe
 ---
 
@@ -15,7 +15,7 @@ This article shows how to configure Azure Container Apps to use GitHub as an aut
 
 To complete the procedure in this article, you need a GitHub account. To create a new GitHub account, go to [GitHub](https://github.com/).
 
-## <a name="github-register"> </a>Register your application with GitHub
+## Register your application with GitHub
 
 1. Sign in to the [Azure portal] and go to your application. Copy your **URL**. You use it to configure your GitHub app.
 1. Follow the instructions for [creating an OAuth app on GitHub](https://docs.github.com/developers/apps/building-oauth-apps/creating-an-oauth-app). In the **Authorization callback URL** section, enter the HTTPS URL of your app and append the path `/.auth/login/github/callback`. For example, `https://<hostname>.azurecontainerapps.io/.auth/login/github/callback`.
@@ -24,19 +24,19 @@ To complete the procedure in this article, you need a GitHub account. To create
 1. Make note of the client secret value, which you need later.
 
    > [!IMPORTANT]
-   > The client secret is an important security credential. Do not share this secret with anyone or distribute it with your app.
+   > The client secret is an important security credential. Don't share this secret with anyone or distribute it with your app.
 
-## <a name="github-secrets"> </a>Add GitHub information to your application
+## Add GitHub information to your application
 
 1. Sign in to the [Azure portal] and navigate to your app.
 1. Select **Authentication** in the menu on the left. Select **Add identity provider**.
 1. Select **GitHub** in the identity provider dropdown. Paste in the `Client ID` and `Client secret` values that you obtained previously.
 
-    The secret is stored as a secret in your container app.
+   The secret is stored as a secret in your container app.
 
 1. If you're configuring the first identity provider for this application, you also see a **Container Apps authentication settings** section. Otherwise, you can move on to the next step.
 
-    These options determine how your application responds to unauthenticated requests. The default selections redirect all requests to sign in with this new provider. You can change customize this behavior now or adjust these settings later from the main **Authentication** screen by choosing **Edit** next to **Authentication settings**. To learn more about these options, see [Authentication flow](./authentication.md#authentication-flow).
+   These options determine how your application responds to unauthenticated requests. The default selections redirect all requests to sign in with this new provider. You can change customize this behavior now or adjust these settings later from the main **Authentication** screen by choosing **Edit** next to **Authentication settings**. To learn more about these options, see [Authentication flow](./authentication.md#authentication-flow).
 
 1. Select **Add**.
 
@@ -46,8 +46,8 @@ You're now ready to use GitHub for authentication in your app. The provider is l
 
 Use the following guides for details on working with authenticated users.
 
-* [Customize sign-in and sign-out](authentication.md#customize-sign-in-and-sign-out)
-* [Access user claims in application code](authentication.md#access-user-claims-in-application-code)
+- [Customize sign-in and sign out](authentication.md#customize-sign-in-and-sign-out)
+- [Access user claims in application code](authentication.md#access-user-claims-in-application-code)
 
 ## Next steps
 

articles/container-apps/authentication-google.yml

@@ -5,7 +5,7 @@ metadata:
   description: Learn to use the built-in Google authentication provider in Azure Container Apps.
   author: craigshoemaker
   ms.author: cshoe
-  ms.date: 11/18/2024
+  ms.date: 03/23/2026
   ms.service: azure-container-apps
   ms.topic: how-to
   ms.custom:
@@ -46,9 +46,9 @@ procedureSection:
 
           The secret will be stored as a [secret](manage-secrets.md) in your container app.
       - |
-        If you're configuring the first identity provider for this application, you'll also be prompted with a **Container Apps authentication settings** section. Otherwise, you may move on to the next step.
+        If you're configuring the first identity provider for this application, you're prompted with a **Container Apps authentication settings** section. Otherwise, you may move on to the next step.
 
-          These options determine how your application responds to unauthenticated requests. The default selections redirect all requests to sign in with this new provider. You can change customize this behavior now or adjust these settings later from the main **Authentication** screen by choosing **Edit** next to **Authentication settings**. To learn more about these options, see [Authentication flow](authentication.md#authentication-flow).
+          These options determine how your application responds to unauthenticated requests. The default selections redirect all requests to sign in with this new provider. You can change or customize this behavior now or adjust these settings later from the main **Authentication** screen by choosing **Edit** next to **Authentication settings**. To learn more about these options, see [Authentication flow](authentication.md#authentication-flow).
       - |
         Select **Add**.
 

articles/container-apps/authentication-twitter.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: how-to
-ms.date: 11/18/2024
+ms.date: 03/23/2026
 ms.author: cshoe
 ---
 
@@ -15,7 +15,7 @@ This article shows how to configure Azure Container Apps to use X as an authenti
 
 To complete the procedure in this article, you need an X account that has a verified email address and phone number. To create a new X account, go to [x.com](https://x.com).
 
-## <a name="twitter-register"> </a>Register your application with X
+## Register your application with X
 
 1. Sign in to the [Azure portal] and go to your application. Copy your **URL**, later you use it to configure your X app.
 1. Go to the [X Developers] website, sign in with your X account credentials, and select **Create an app**.
@@ -24,23 +24,24 @@ To complete the procedure in this article, you need an X account that has a veri
 1. Select the **Keys and Access Tokens** tab.
 
    Make a note of these values:
+
    - API key
    - API secret key
 
    > [!IMPORTANT]
-   > The API secret key is an important security credential. Do not share this secret with anyone or distribute it with your app.
+   > The API secret key is an important security credential. Don't share this secret with anyone or distribute it with your app.
 
-## <a name="twitter-secrets"> </a>Add X information to your application
+## Add X information to your application
 
 1. Sign in to the [Azure portal] and navigate to your app.
 1. Select **Authentication** in the menu on the left. Select **Add identity provider**.
 1. Select **Twitter** in the identity provider dropdown. Paste in the `API key` and `API secret key` values that you obtained previously.
 
-    The secret is stored as [secret](manage-secrets.md) in your container app.
+   The secret is stored as [secret](manage-secrets.md) in your container app.
 
 1. If you're configuring the first identity provider for this application, you're prompted with a **Container Apps authentication settings** section. Otherwise, you move on to the next step.
 
-    These options determine how your application responds to unauthenticated requests. The default selections redirect all requests to sign in with this new provider. You can change customize this behavior now or adjust these settings later from the main **Authentication** screen by choosing **Edit** next to **Authentication settings**. To learn more about these options, see [Authentication flow](authentication.md#authentication-flow).
+   These options determine how your application responds to unauthenticated requests. The default selections redirect all requests to sign in with this new provider. You can change customize this behavior now or adjust these settings later from the main **Authentication** screen by choosing **Edit** next to **Authentication settings**. To learn more about these options, see [Authentication flow](authentication.md#authentication-flow).
 
 1. Select **Add**.
 
@@ -50,8 +51,8 @@ You're now ready to use X for authentication in your app. The provider is listed
 
 Use the following guides for details on working with authenticated users.
 
-* [Customize sign-in and sign-out](authentication.md#customize-sign-in-and-sign-out)
-* [Access user claims in application code](authentication.md#access-user-claims-in-application-code)
+- [Customize sign-in and sign out](authentication.md#customize-sign-in-and-sign-out)
+- [Access user claims in application code](authentication.md#access-user-claims-in-application-code)
 
 ## Next steps
 

articles/container-apps/java-metrics-scale-with-keda.md

@@ -6,7 +6,7 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-extended-java
 ms.topic: tutorial
-ms.date: 12/23/2024
+ms.date: 03/25/2026
 ms.author: cshoe
 #customer intent: As a developer, I want to set up auto scale using Java metrics exposed from Azure Container Apps
 ---
@@ -19,9 +19,9 @@ In this tutorial, you add a custom scale rule to scale your container app with J
 
 ## Prerequisites
 
-* An Azure account with an active subscription. If you don't already have one, you can [create one for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
-* [Azure CLI](/cli/azure/install-azure-cli).
-* [A Java application deployed in Azure Container Apps](java-get-started.md).
+- An Azure account with an active subscription. If you don't already have one, you can [create one for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
+- [Azure CLI](/cli/azure/install-azure-cli).
+- [A Java application deployed in Azure Container Apps](java-get-started.md).
 
 ## Set up the environment
 
@@ -42,7 +42,7 @@ Use the following steps to define environment variables and set up the environme
    |-------------------------|------------------------------------------------------------------------------------|
    | `LOCATION`              | The Azure region location where you create your Azure Container Apps.              |
    | `TENANT_ID`             | Your tenant's ID.                                                                  |
-   | `SUBSCRIPTION_ID`       | The subscription ID which you use to create your Azure Container Apps.             |
+   | `SUBSCRIPTION_ID`       | The subscription ID, which you use to create your Azure Container Apps.             |
    | `RESOURCE_GROUP`        | The Azure resource group name for your Azure Container Apps.                       |
    | `APP_NAME`              | The app name for your Azure Container Apps.                                        |
    | `IDENTITY_NAME`         | The name for your managed identity, which is assigned to your Azure Container Apps.|
@@ -54,25 +54,27 @@ Use the following steps to define environment variables and set up the environme
    ```
 
 ## Set up a managed identity for your Azure Container Apps
+
 To scale with Azure Container Apps platform metrics, you need a managed identity to access metrics from Azure Monitor.
 
 1. Create a user-assigned identity and assign it to your Azure Container Apps. You can follow the doc [add a user-assigned identity](./managed-identity.md#add-a-user-assigned-identity). After you create the identity, run the CLI command to set the identity ID.
 
-    ```azurecli
-    USER_ASSIGNED_IDENTITY_ID=$(az identity show --resource-group $RESOURCE_GROUP --name $IDENTITY_NAME --query "id" --output tsv)
-    ```
+   ```azurecli
+   USER_ASSIGNED_IDENTITY_ID=$(az identity show --resource-group $RESOURCE_GROUP --name $IDENTITY_NAME --query "id" --output tsv)
+   ```
 
 2. Grant the `Monitoring Reader` role for your managed identity to read data from Azure Monitor. You can find more details about the roles for Azure Monitor in [Azure built-in roles for Monitor](../role-based-access-control/built-in-roles/monitor.md#monitoring-reader).
 
-    ```azurecli
-    # Get the principal ID for your managed identity
-    PRINCIPAL_ID=$(az identity show --resource-group $RESOURCE_GROUP --name $IDENTITY_NAME --query "principalId" --output tsv)
+   ```azurecli
+   # Get the principal ID for your managed identity
+   PRINCIPAL_ID=$(az identity show --resource-group $RESOURCE_GROUP --name $IDENTITY_NAME --query "principalId" --output tsv)
    
-    az role assignment create --assignee $PRINCIPAL_ID --role "Monitoring Reader" --scope /subscriptions/$SUBSCRIPTION_ID
-    ```
+   az role assignment create --assignee $PRINCIPAL_ID --role "Monitoring Reader" --scope /subscriptions/$SUBSCRIPTION_ID
+   ```
 
 ## Add a scale rule with Azure Monitor metrics
-To scale with Azure Monitor metrics, you can refer to [Azure Monitor KEDA scaler](https://keda.sh/docs/2.16/scalers/azure-monitor/) to define your Container Apps scale rule. 
+
+To scale with Azure Monitor metrics, you can refer to the [Azure Monitor Kubernetes Event-driven Autoscaling (KEDA) scaler](https://keda.sh/docs/2.16/scalers/azure-monitor/) to define your Container Apps scale rule. 
 
 Here's a list of core metadata to set up the scale rule.
 
@@ -85,11 +87,9 @@ Here's a list of core metadata to set up the scale rule.
 | metricName                         | Name of the metric to query.                                                                          |
 | metricAggregationType              | Aggregation method of the Azure Monitor metric. Options include Average, Total, Maximum.              |
 | metricFilter                       | Name of the filter to be more specific by using dimensions listed in the official documentation. (Optional) |
-| metricAggregationInterval          | Collection time of the metric in format "hh:mm:ss" (Default: "0:5:0", Optional)                       |
+| metricAggregationInterval          | Collection time of the metric in the format `hh:mm:ss` (Default: `0:5:0`, Optional)                       |
 | targetValue                        | Target value to trigger scaling actions. (This value can be a float)                                  |
 
-
-
 Add a scale rule with [Azure Monitor metrics for Azure Container Apps](./metrics.md) for your application.
 
 ### [Azure CLI](#tab/azurecli)
@@ -161,19 +161,19 @@ This command adds a scale rule to your container app with the name `scale-with-a
 > The metric `JvmGcCount` is only used as an example. You can use any metric from Azure Monitor. Before setting up the scale rule, view the metrics in the Azure portal to determine the appropriate metric, aggregation interval, and target value based on your application's requirements. Additionally, consider using the built-in [HTTP/TCP scale rules](./scale-app.md#http), which can meet most common scaling scenarios, before opting for a custom metric.
 
 ## View scaling in Azure portal (optional)
+
 Once your new revision is ready, [send requests](./tutorial-scaling.md#send-requests) to your container app to trigger auto scale with your Java metrics. 
 1. Go to the `Metrics` blade in the Azure portal for your Azure Container Apps.
 1. Add a chart, use the metric `jvm.gc.count`, with filter `Revision=<your-revision>`, aggregation using `Sum`, and split by `Replica`. You can see the `JvmGcCount` metric value for each replica in this chat.
 1. Add a chart, use the metric `jvm.gc.count`, with filter `Revision=<your-revision>` and aggregation using `Sum`. You can see the total aggregated `JvmGcCount` metric value for the revision in this chat.
 1. Add a chart, use the metric `Replica Count`, with filter `Revision=<your-revision>` and aggregation using `Max`. You can see the replica count for the revision in this chat.
 
-
 Here's a sample metric snapshot for the example scale rule.
 
 :::image type="content" source="media/java-metrics-keda/keda-auto-scale-java-gc-portal.png" alt-text="Screenshot of KEDA scale with JVM metrics." lightbox="media/java-metrics-keda/keda-auto-scale-java-gc-portal.png":::
 
 1. Initially, there's one replica (the `minReplicas`) for the app.
-1. A spike in requests causes the Java app to experience frequent JVM garbage collection (GC).
+1. A spike in requests causes the Java app to experience frequent Java Virtual Machine (JVM) garbage collection (GC).
 1. KEDA observes the aggregated metric value for `jvm.gc.count` is increased to `256`, and calculates the `desiredReplicas` value as `ceil(256/30)=9`.
 1. KEDA scales out the container app's replica count to 9.
 1. The http traffic is distributed across more replicas, reducing the average GC count.