Merge pull request #313685 from lootle1/FR42

Freshness Edit: Azure Dev Compute - Container Apps

Author: prmerger-automator[bot]

articles/container-apps/functions-overview.md

@@ -11,14 +11,16 @@ ms.author: cshoe
 
 # Azure Functions on Azure Container Apps overview
 
-Azure Functions on Azure Container Apps offers a fully managed serverless hosting environment that brings together the event-driven capabilities of Azure Functions with the robust features of Container Apps. This integration includes advanced capabilities such as Kubernetes-based orchestration, built-in autoscaling powered by KEDA (Kubernetes-based Event Driven Autoscaling), Dapr (Distributed Application Runtime) integration, GPU workload support, sidecar support, virtual network (VNet) connectivity, and revision management. 
+Azure Functions on Azure Container Apps offers a fully managed serverless hosting environment that brings together the event-driven capabilities of Azure Functions with the robust features of Container Apps. This integration includes advanced capabilities such as Kubernetes-based orchestration, built-in autoscaling powered by KEDA (Kubernetes-based Event Driven Autoscaling), Dapr (Distributed Application Runtime) integration, GPU workload support, sidecar support, virtual network (VNet) connectivity, and revision management.
 
 This approach is useful when you want your Functions to run alongside other containerized apps like microservices, APIs, or websites. Further, containerizing your function apps can help when you need custom dependencies or want to take advantage of scale-to-zero for cost savings. If you're running compute-heavy tasks like AI inference, Container Apps also supports GPU-based hosting through serverless GPU offering and Dedicated workload profiles.
 
-As an integrated feature on Azure Container Apps,  you can  deploy Azure Functions images directly onto Azure Container Apps using the `Microsoft.App` resource provider by setting `kind=functionapp` when calling `az containerapp create`. Apps created this way have access to all Azure Container Apps features. If deploying via Azure portal, you can enable the *Optimize for Functions app* option during setup. Refer to [deployment and setup](../container-apps/functions-overview.md#deployment-and-setup) section for more details.
+As an integrated feature on Azure Container Apps,  you can  deploy Azure Functions images directly onto Azure Container Apps using the `Microsoft.App` resource provider by setting `kind=functionapp` when calling `az containerapp create`. Apps created this way have access to all Azure Container Apps features. If deploying via Azure portal, you can enable the *Optimize for Functions app* option during setup. For more information, see [deployment and setup](../container-apps/functions-overview.md#deployment-and-setup) section for more details.
 
 ## Key benefits
+
 The Container Apps hosting model builds on the flexibility of containerized workloads and the event-driven nature of Azure Functions. It offers the following key advantages:
+
 - **Run Azure Functions as containers** with custom dependencies and language stacks.
 - **Scale in to zero and scale out to 1000 instances** using KEDA.
 - **[Secure networking](../container-apps/networking.md)** with full [VNet integration](../container-apps/custom-virtual-networks.md).
@@ -31,9 +33,9 @@ The following table helps you compare the features of Functions on Container App
 | Feature | Container Apps | Flex Consumption Plan |
 | --- | --- | --- |
 | Scale to zero | ✅ Yes (via KEDA) | ✅ Yes |
-| Max scale-out | 1,000 (default 10, configurable) |	1,000 |
+| Max scale-out | 1,000 (default 10, configurable) | 1,000 |
 | Always-on instances | ✅ Yes (via `minReplicas`) | ✅ Yes (via always-ready instances) |
-| VNet integration |	✅ Yes | ✅ Yes |
+| VNet integration | ✅ Yes | ✅ Yes |
 | Custom container support | ✅ Yes (bring your own image) | ❌ Limited (no bring your own container) |
 | GPU support | ✅ Yes (via serverless GPU dedicated workload profile) | ❌ No |
 | Built-in features | Container Apps feature support. For instance, KEDA, Dapr, multi-revisions, mTLS, sidecars, ingress control and more | Functions-only features |
@@ -70,13 +72,15 @@ az containerapp create \
   --kind functionapp \
   --query properties.outputs.fqdn
 ```
+
 This command returns the URL of your Functions app. Copy this URL and paste it into a web browser.
 
 In the Azure portal, select the *Optimize for Azure Functions* option during container app creation to streamline the setup.
 
 :::image type="content" source="media/functions-overview/functions-create-container-app.png" alt-text="Screenshot of the Azure portal when you create a container app pre-configured for Azure Functions.":::
 
 All standard deployment methods are supported, including:
+
 - [Azure CLI](../container-apps/functions-usage.md?pivots=azure-cli)
 - [Azure portal](../container-apps/functions-usage.md?pivots=azure-portal)
 - ARM templates / [Bicep](https://github.com/Azure/azure-functions-on-container-apps/tree/main/samples/ACAKindfunctionapp)
@@ -85,20 +89,23 @@ All standard deployment methods are supported, including:
 For detailed steps and examples, refer to the official [getting started documentation](../container-apps/functions-usage.md).
 
 ## Pricing and billing
+
 Azure Functions on Azure Container Apps follow the same pricing model as Azure Container Apps. Billing is based on the [plan type](../container-apps/plans.md) you select for your environment, which can be either Consumption or Dedicated.
-- [Consumption plan](..//container-apps/billing.md#consumption-plan): This serverless compute option bills you only for the resources your apps use while they are running.
+
+- [Consumption plan](..//container-apps/billing.md#consumption-plan): This serverless compute option bills you only for the resources your apps use while they're running.
 - [Dedicated plan](../container-apps/billing.md#consumption-dedicated): This option provides customized compute resources, billing you for the instances allocated to each workload profile.
 
 Your choice of plan determines how billing calculations are made. Different applications within an environment can use different plans.
 
 Key points to note:
+
 - No extra charges for using the Azure Functions programming model within Container Apps.
 - Durable Functions and other advanced patterns are supported and billed under the same Container Apps pricing model.
 For detailed billing mechanics and examples, refer to the [Billing in Azure Container Apps](../container-apps/billing.md) documentation.
 
 ## Event-driven scaling
 
-Azure Functions on Container Apps support all major [language runtimes available in Azure Functions](../azure-functions/supported-languages.md), including: C#, JavaScript / TypeScript (Node.js), Python, Java, PowerShell, Custom containers (bring your own image).
+Azure Functions on Container Apps support all major [language runtimes available in Azure Functions](../azure-functions/supported-languages.md), including C#, JavaScript / TypeScript (Node.js), Python, Java, PowerShell, and Custom containers (bring your own image).
 
 Azure Functions running on Azure Container Apps **automatically configure scaling rules** based on the event source, eliminating the need for manual KEDA scale rule definitions. That’s why the "Add scale rules" button on the Azure portal is disabled for Functions on Container Apps. However, you can still define minimum and maximum replica counts to establish scaling boundaries and maintain control over resource allocation.
 
@@ -111,20 +118,21 @@ The platform automatically translates your Functions trigger parameters (from `h
   - Azure Cache for Redis  
   - Azure SQL
 
-**Managed identities** are supported for triggers and bindings that allow it. They are also available for:
+**Managed identities** are supported for triggers and bindings that allow it. They're also available for:
+
 - [Default storage account](../azure-functions/functions-reference.md#connecting-to-host-storage-with-an-identity) (AzureWebJobsStorage)
 - [Azure Container Registry](../container-apps/managed-identity-image-pull.md) (ACR)
 - [Connecting to trigger event sources](../azure-functions/functions-reference.md#configure-an-identity-based-connection)
 
-For unsupported triggers, use fixed replica counts (that is, set minReplicas > 0) in Azure Functions on Azure Container Apps. For more details, refer to the [Functions developer guide](../azure-functions/functions-reference.md).
+For unsupported triggers, use fixed replica counts (that is, set minReplicas > 0) in Azure Functions on Azure Container Apps. For more information, see the [Functions developer guide](../azure-functions/functions-reference.md).
 
 ## Scaling and performance
 
 Azure Functions on Container Apps scale automatically based on events using KEDA, with no need to configure scale rules manually. You can still set min/max replicas to control scaling behavior.
 
 - **Event-driven scaling**: Automatically scales based on triggers like Event Grid, Service Bus, or HTTP.
 - **Scale to zero**: Idle apps scale-in to zero to save costs.
-- **Cold start control**: Learn about [reducing cold-start time on Azure Container Apps](../container-apps/cold-start.md). 
+- **Cold start control**: Learn about [reducing cold-start time on Azure Container Apps](../container-apps/cold-start.md).
 - **Concurrency**: Each instance can process multiple events in parallel.
 - **High scale**: Scale out to 1,000 instances per app (default is 10).
 - **GPU support**: Run compute-heavy workloads like AI inference using GPU-backed nodes.
@@ -170,14 +178,14 @@ Keep these other considerations in mind when using Azure Functions on Azure Cont
 - **Cold start latency**: When your container app scales in to zero during idle periods, the first request after inactivity experiences a cold start. Learn more about [reducing cold start times](../container-apps/cold-start.md).
 - **Application insights integration**: For robust monitoring and diagnostics, link your Functions app to Application Insights. For more information, see [App Insights integration with Functions](../azure-functions/configure-monitoring.md?tabs=v2#enable-application-insights-integration).
 - **Functions proxies**: Not supported. For API gateway scenarios, integrate with Azure API Management instead.
-- **Deployment slots**: Staging and production slots are not available. Use [blue-green deployment strategies](../container-apps/blue-green-deployment.md) for zero-downtime releases.
-- **Functions access keys**: Using the portal to generate Functions access keys is not supported. Consider using [Azure Key Vault to store keys](https://techcommunity.microsoft.com/blog/appsonazureblog/how-to-store-function-apps-function-keys-in-a-key-vault/2639181). You can also use the following options to secure HTTP endpoints in production:
-    - [Enable App Service Authentication/Authorization](../container-apps/authentication.md)
-    - [Enable ingress](../container-apps/ingress-overview.md)
-    - [Use Azure API Management (APIM) to authenticate requests](../azure-functions/security-concepts.md#use-azure-api-management-apim-to-authenticate-requests)
-    - [Deploy your function app to a virtual network](../container-apps/custom-virtual-networks.md?tabs=workload-profiles-env)
+- **Deployment slots**: Staging and production slots aren't available. Use [blue-green deployment strategies](../container-apps/blue-green-deployment.md) for zero-downtime releases.
+- **Functions access keys**: Using the portal to generate Functions access keys isn't supported. Consider using [Azure Key Vault to store keys](https://techcommunity.microsoft.com/blog/appsonazureblog/how-to-store-function-apps-function-keys-in-a-key-vault/2639181). You can also use the following options to secure HTTP endpoints in production:
+  - [Enable App Service Authentication/Authorization](../container-apps/authentication.md)
+  - [Enable ingress](../container-apps/ingress-overview.md)
+  - [Use Azure API Management (APIM) to authenticate requests](../azure-functions/security-concepts.md#use-azure-api-management-apim-to-authenticate-requests)
+  - [Deploy your function app to a virtual network](../container-apps/custom-virtual-networks.md?tabs=workload-profiles-env)
 - **Quota and resource limits**: Container Apps environments have default limits on memory, CPU, and instance counts per region. For more information, see the [environment limits](../container-apps/environment.md#limits-and-quotas) and [default quotas](../container-apps/quotas.md). If your workload requires more resources, you can [request a quota increase](../container-apps/quota-requests.md).
-- **Manual scale rule configuration**: The "Add scale rules" button on the Azure portal is disabled for Azure Functions hosted on Container Apps because scaling rules are automatically configured based on the event source. Manual KEDA rule definitions are not required in this setup.
+- **Manual scale rule configuration**: The "Add scale rules" button on the Azure portal is disabled for Azure Functions hosted on Container Apps because scaling rules are automatically configured based on the event source. Manual KEDA rule definitions aren't required in this setup.
 
 ## Submit Feedback
 
@@ -187,9 +195,9 @@ Submit an issue or a feature request to the [Azure Container Apps GitHub repo](h
 
 To continue learning and building with Azure Functions on Container Apps, explore the following resources:
 
-- [Getting started](../container-apps/functions-usage.md) – Step-by-step guide to deploying and configuring Azure Functions in Azure Container Apps.
-- [Azure Container Apps documentation](../container-apps/overview.md) – Full reference for Container Apps features including scaling, networking, Dapr, and workload profiles.
-- [Azure Container Apps pricing](https://azure.microsoft.com/pricing/details/container-apps/) – Details on consumption-based billing and Dedicated plan costs.
-- [Azure Functions hosting options](../azure-functions/functions-scale.md) – Comparison of hosting plans including Container Apps, Flex Consumption, Premium, and Dedicated.
-- [Azure Functions developer guide](../azure-functions/functions-reference.md) – Deep dive into triggers, bindings, runtime behavior, and configuration.
-  
+- [Getting started](../container-apps/functions-usage.md): Step-by-step guide to deploying and configuring Azure Functions in Azure Container Apps.
+- [Azure Container Apps documentation](../container-apps/overview.md): Full reference for Container Apps features including scaling, networking, Dapr, and workload profiles.
+- [Azure Container Apps pricing](https://azure.microsoft.com/pricing/details/container-apps/): Details on consumption-based billing and Dedicated plan costs.
+- [Azure Functions hosting options](../azure-functions/functions-scale.md): Comparison of hosting plans including Container Apps, Flex Consumption, Premium, and Dedicated.
+- [Azure Functions developer guide](../azure-functions/functions-reference.md): Deep dive into triggers, bindings, runtime behavior, and configuration.
+  

articles/container-apps/get-started.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: quickstart
-ms.date: 02/03/2025
+ms.date: 03/26/2026
 ms.author: cshoe
 ms.custom: devx-track-azurecli
 ms.devlang: azurecli
@@ -84,7 +84,7 @@ The following message is displayed when the container app is deployed:
 If you're not going to continue to use this application, run the following command to delete the resource group along with all the resources created in this quickstart.
 
 >[!CAUTION]
-> The following command deletes the specified resource group and all resources contained within it. If resources outside the scope of this quickstart exist in the specified resource group, they will also be deleted.
+> The following command deletes the specified resource group and all resources contained within it. If resources outside the scope of this quickstart exist in the specified resource group, they'll also be deleted.
 
 
 ```azurecli

articles/container-apps/index.yml

@@ -11,7 +11,7 @@ metadata:
   ms.custom: build-2023
   author: craigshoemaker
   ms.author: cshoe
-  ms.date: 04/09/2025
+  ms.date: 03/25/2026
 landingContent:
   - title: Learn and get started
     linkLists: