Merge pull request #302577 from niteshj11/njACAGetStarted

Update getting started docs for ACA to include Functions

Author: prmerger-automator[bot]

articles/container-apps/compare-options.md

@@ -33,6 +33,7 @@ There's no perfect solution for every use case and every team. The following exp
 * Supports Kubernetes-style apps and microservices with features like [service discovery](connect-apps.md) and [traffic splitting](revisions.md).
 * Enables event-driven application architectures by supporting scale based on traffic and pulling from [event sources like queues](scale-app.md), including [scale to zero](scale-app.md).
 * Supports running on demand, scheduled, and event-driven [jobs](jobs.md).
+* Enables running [Azure Functions](../container-apps/functions-overview.md) for [event-driven scenarios](../azure-functions/functions-scenarios.md) using triggers, bindings and automatic scaling.
 
 Azure Container Apps doesn't provide direct access to the underlying Kubernetes APIs. If you require access to the Kubernetes APIs and control plane, you should use [Azure Kubernetes Service](/azure/aks/intro-kubernetes). However, if you would like to build Kubernetes-style applications and don't require direct access to all the native Kubernetes APIs and cluster management, Container Apps provides a fully managed experience based on best-practices. For these reasons, many teams prefer to start building container microservices with Azure Container Apps.
 

articles/container-apps/index.yml

@@ -51,6 +51,8 @@ landingContent:
             url: observability.md
           - text: Jobs
             url: jobs.md
+          - text: Azure Functions
+            url: functions-overview.md
   - title: Common tasks
     linkLists:
       - linkListType: how-to-guide
@@ -69,6 +71,8 @@ landingContent:
             url: vnet-custom.md
           - text: Quotas
             url: quotas.md
+          - text: Create a Functions app
+            url: functions-usage.md  
       - linkListType: concept
         links:
           - text: What's new in Dapr?

articles/container-apps/overview.md

@@ -49,7 +49,9 @@ With Azure Container Apps, you can:
 
 - [**Run jobs**](jobs.md) on-demand, on a schedule, or based on events.
 
-- Add [**Azure Functions**](../container-apps/functions-overview.md) and [**Azure Spring Apps**](https://aka.ms/asaonaca) to your Azure Container Apps environment.
+- [**Run Azure Functions**](../container-apps/functions-overview.md) for [event-driven scenarios](../azure-functions/functions-scenarios.md) using triggers, bindings and automatic scaling.
+
+- Add [**Azure Spring Apps**](https://aka.ms/asaonaca) to your Azure Container Apps environment.
 
 - [**Use specialized hardware**](plans.md) for access to increased compute resources.
 

articles/container-apps/quickstart-portal.md

@@ -47,6 +47,7 @@ In the *Basics* tab, do the following actions.
     | Subscription | Select your Azure subscription. |
     | Resource group | Select **Create new** and enter **my-container-apps**. |
     | Container app name |  Enter **my-container-app**. |
+    | Optimize for Azure Functions |  Leave the checkbox unchecked. Select it only if you want to [create a Functions app](../container-apps/functions-usage.md). |
     | Deployment source | Select **Container image**. |
 
 1. Enter the following values in the "Container Apps Environment" section.