Merge pull request #249118 from anthonychu/20230823-jobs-billing

[Container Apps] Update billing to include jobs

Author: prmerger-automator[bot]

articles/container-apps/billing.md

@@ -6,7 +6,7 @@ author: craigshoemaker
 ms.service: container-apps
 ms.custom: event-tier1-build-2022
 ms.topic: conceptual
-ms.date: 06/19/2023
+ms.date: 08/23/2023
 ms.author: cshoe
 ---
 
@@ -22,7 +22,7 @@ Billing in Azure Container Apps is based on your [plan type](plans.md).
 - Your plan selection determines billing calculations.
 - Different applications in an environment can use different plans.
 
-For more information, see [Azure Container Apps Pricing](https://azure.microsoft.com/pricing/details/container-apps/).
+This article describes how to calculate the cost of running your container app. For pricing details in your account's currency, see [Azure Container Apps Pricing](https://azure.microsoft.com/pricing/details/container-apps/).
 
 ## Consumption plan
 
@@ -37,15 +37,14 @@ The following resources are free during each calendar month, per subscription:
 - The first 360,000 GiB-seconds
 - The first 2 million HTTP requests
 
-This article describes how to calculate the cost of running your container app. For pricing details in your account's currency, see [Azure Container Apps Pricing](https://azure.microsoft.com/pricing/details/container-apps/).
-
+Free usage doesn't appear on your bill. You'll only be charged when your resource usage exceeds the monthly free grants.
 
 > [!NOTE]
 > If you use Container Apps with [your own virtual network](networking.md#managed-resources) or your apps utilize other Azure resources, additional charges may apply.
 
 ### Resource consumption charges
 
-Azure Container Apps runs replicas of your application based on the [scaling rules and replica count limits](scale-app.md) you configure for each revision. You're charged for the amount of resources allocated to each replica while it's running.
+Azure Container Apps runs replicas of your application based on the [scaling rules and replica count limits](scale-app.md) you configure for each revision. [Azure Container Apps jobs](jobs.md) run replicas when job executions are triggered. You're charged for the amount of resources allocated to each replica while it's running.
 
 There are 2 meters for resource consumption:
 
@@ -54,15 +53,17 @@ There are 2 meters for resource consumption:
 
 The first 180,000 vCPU-seconds and 360,000 GiB-seconds in each subscription per calendar month are free.
 
+#### Container apps
+
 The rate you pay for resource consumption depends on the state of your container app's revisions and replicas. By default, replicas are charged at an *active* rate. However, in certain conditions, a replica can enter an *idle* state. While in an *idle* state, resources are billed at a reduced rate.
 
-#### No replicas are running
+##### No replicas are running
 
 When a revision is scaled to zero replicas, no resource consumption charges are incurred.
 
-#### Minimum number of replicas are running
+##### Minimum number of replicas are running
 
-Idle usage charges may apply when a revision is running under a specific set of circumstances. To be eligible for idle charges, a revision must be:
+Idle usage charges may apply when a container app's revision is running under a specific set of circumstances. To be eligible for idle charges, a revision must be:
 
 - Configured with a [minimum replica count](scale-app.md) greater than zero
 - Scaled to the minimum replica count
@@ -77,24 +78,30 @@ Usage charges are calculated individually for each replica. A replica is conside
 
 When a replica is idle, resource consumption charges are calculated at the reduced idle rates. When a replica isn't idle, the active rates apply.
 
-#### More than the minimum number of replicas are running
+##### More than the minimum number of replicas are running
 
 When a revision is scaled above the [minimum replica count](scale-app.md), all of its running replicas are charged for resource consumption at the active rate.
 
+#### Jobs
+
+In the Consumption plan, resources consumed by Azure Container Apps jobs are charged the active rate. Idle charges don't apply to jobs because executions stop consuming resources once the job completes.
+
 ### Request charges
 
 In addition to resource consumption, Azure Container Apps also charges based on the number of HTTP requests received by your container app. Only requests that come from outside a Container Apps environment are billable.
 
 - The first 2 million requests in each subscription per calendar month are free.
 - [Health probe](./health-probes.md) requests aren't billable.
 
+Request charges don't apply to Azure Container Apps jobs because they don't support ingress.
+
 <a id="consumption-dedicated"></a>
 
 ## Dedicated plan
 
 You're billed based on workload profile instances, not by individual applications.
 
-Billing for apps running in the Dedicated plan is based on workload profile instances, not by individual applications. The charges are as follows:
+Billing for apps and jobs running in the Dedicated plan is based on workload profile instances, not by individual applications. The charges are as follows:
 
 | Fixed management costs | Variable costs |
 |---|---|