updates from PM review

Author: craigshoemaker

articles/container-apps/functions-overview.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic:  how-to
-ms.date: 03/31/2025
+ms.date: 04/03/2025
 ms.author: cshoe
 ---
 
@@ -15,6 +15,8 @@ Azure Functions provides integrated support for developing, deploying, and manag
 
 Container Apps hosting lets you run your functions in a fully supported and managed, container-based environment with built-in support for open-source monitoring, mTLS, Dapr, and Kubernetes Event-driven Autoscaling (KEDA).
 
+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.
+
 This article shows you how to create and deploy an Azure Functions app that runs within Azure Container Apps. You learn how to:
 
 - Set up a containerized Functions app with preconfigured auto scaling rules
@@ -23,6 +25,18 @@ This article shows you how to create and deploy an Azure Functions app that runs
 
 By running Functions in Container Apps, you benefit from automatic scaling, easy configuration, and a fully managed container environment—all without having to manage the underlying infrastructure yourself.
 
+## Scenarios
+
+Azure Functions in Container Apps provides a versatile combination of services to meet the needs of your applications. The following scenarios are representative of the types of situations where paring Azure Container Apps with Azure Functions gives you the control and scaling features you need.
+
+- **Line-of-business APIs**: Package custom libraries, packages, and APIs with Functions for line-of-business applications.
+
+- **Migration support**: Migration of on-premises legacy and/or monolith applications to cloud native microservices on containers.
+
+- **Event-driven architecture**: Supports event-driven applications for workloads already running on Azure Container Apps.
+
+- **Serverless workloads**: Serverless workload processing of videos, images, transcripts, or any other processing intensive tasks that required  GPU compute resources.
+
 ## Event-driven scaling
 
 All Functions triggers are available in your containerized Functions app. However, only the following triggers can dynamically scale (from zero instances) based on received events when running in a Container Apps environment:
@@ -39,23 +53,27 @@ All Functions triggers are available in your containerized Functions app. Howeve
 
 Azure Functions on Container Apps is designed to configure the scale parameters and rules as per the event target. You don't need to worry about configuring the KEDA scaled objects. You can still set minimum and maximum replica count when creating or modifying your function app.
 
-You can write your function code in any language stack supported by Azure Functions. You can use the same Functions triggers and bindings with event-driven scaling.
+You can write your function code in any [language stack supported](/azure/azure-functions/supported-languages?tabs=isolated-process%2Cv4&pivots=programming-language-csharp) by Azure Functions. You can use the same Functions triggers and bindings with event-driven scaling.
 
-## Scenarios
+## Managed identity authorization
 
-Azure Functions in Container Apps provides a versatile combination of services to meet the needs of your applications. The following scenarios are representative of the types of situations where paring Azure Container Apps with Azure Functions gives you the control and scaling features you need.
+To adhere to security best practices, connect to remote services using Microsoft Entra authentication and managed identity authorization.
 
-- **Line-of-business APIs**: Package custom libraries, packages, and APIs with Functions for line-of-business applications.
+Managed identities are available for the following connections:
 
-- **Migration support**: Migration of on-premises legacy and/or monolith applications to cloud native microservices on containers.
+- [Default storage account](/azure/azure-functions/functions-reference) (AzureWebJobsStorage)
+- [Azure Container Registry](/azure/azure-functions/functions-deploy-container-apps?tabs=acr): When running in Container Apps, you can use Microsoft Entra ID with managed identities for all binding extensions that support managed identities. Currently, only these binding extensions support event-driven scaling when using managed identity authentication:
+- Azure Event Hubs
+- Azure Queue Storage
+- Azure Service Bus
 
-- **Event-driven architecture**: Supports event-driven applications for workloads already running on Azure Container Apps.
+For other bindings, use fixed replicas when using managed identity authentication. For more information, see the [Functions developer guide](/azure/azure-functions/functions-reference).
 
-- **Serverless workloads**: Serverless workload processing of videos, images, transcripts, or any other processing intensive tasks that required  GPU compute resources.
+## Application logging
 
-## Making a selection
+You can monitor your containerized function app hosted in Container Apps using Azure Monitor Application Insights in the same way you do with apps hosted by Azure Functions. For more information, see [Monitor Azure Functions](/azure/azure-functions/monitor-functions).
 
-TODO: functions vs. jobs
+For bindings that support event-driven scaling, scale events are logged as `FunctionsScalerInfo` and `FunctionsScalerError` events in your Log Analytics workspace. For more information, see [Application Logging in Azure Container Apps](./logging.md).
 
 ## Next steps
 

articles/container-apps/functions-usage.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic:  how-to
-ms.date: 03/31/2025
+ms.date: 04/03/2025
 ms.author: cshoe
 zone_pivot_groups: azure-cli-or-portal
 ---
@@ -23,6 +23,8 @@ This article shows you how to create an [Azure Functions app in Azure Container
 
 ## Create a Functions app
 
+The following steps show you how to use a sample container image to create your container app. If you want to use this procedure with a custom container image, see [Create your first Azure Function on Azure Container Apps](https://github.com/Azure/azure-functions-on-container-apps/blob/main/README.md#create-your-first-azure-function-on-azure-container-apps) and [Functions in containers](/azure/azure-functions/functions-container-apps-hosting).
+
 1. Go to the Azure portal and search for **Container Apps** in the search bar.
 
 1. Select **Container Apps**.
@@ -76,9 +78,16 @@ This article shows you how to create an [Azure Functions app in Azure Container
     | Registry login server  | Enter **mcr.microsoft.com** |
     | Image and tag | Enter **azure-functions/dotnet8-quickstart-demo:1.0** |
 
-1. For *Development stack*, select **.NET**.
+1. Under *Environment variables* enter values for the following variables:
+
+    - `AzureWebJobsStorage`
+    - `APPINSIGHTS_INSTRUMENTATIONKEY` or `APPLICATIONINSIGHTS_CONNECTION_STRING`
+
+    Enter either Managed identity or connection string values for these variables. Managed Identity is recommended.
+
+    The `AzureWebJobsStorage` variable is a required Azure Storage account connection string for Azure Functions. This storage account stores function execution logs, manage triggers and bindings, and maintains state for durable functions.
 
-    This value is required since the sample container image is implemented in .NET.
+    Application Insights is a monitoring and diagnostic service that provides insights into the performance and usage of your Azure Functions. This monitoring helps you track request rates, response times, failure rates, and other metrics.
 
 1. Select **Next > Ingress** to switch to the Ingress section and enter the following values.