Merge branch 'MicrosoftDocs:main' into docs-editor/whats-new-1693324949

Author: VandhanaMehta

articles/container-apps/TOC.yml

@@ -43,7 +43,11 @@
     - name: Visual Studio Code
       href: deploy-visual-studio-code.md
   - name: Run a job
-    href: jobs-get-started-cli.md
+    items:
+    - name: Azure portal
+      href: jobs-get-started-portal.md
+    - name: Command line
+      href: jobs-get-started-cli.md
 - name: Develop and deploy
   items:
     - name: Deploy an app with containerapp up

articles/container-apps/application-lifecycle-management.md

@@ -18,6 +18,9 @@ When you deploy a container app, the first revision is automatically created. [M
 
 A container app flows through four phases: deployment, update, deactivation, and shut down.
 
+> [!NOTE]
+> [Azure Container Apps jobs](jobs.md) don't support revisions. Jobs are deployed and updated directly.
+
 ## Deployment
 
 As a container app is deployed, the first revision is automatically created.

articles/container-apps/compare-options.md

@@ -26,13 +26,13 @@ There's no perfect solution for every use case and every team. The following exp
 ## Container option comparisons
 
 ### Azure Container Apps
-Azure Container Apps enables you to build serverless microservices based on containers. Distinctive features of Container Apps include:
+Azure Container Apps enables you to build serverless microservices and jobs based on containers. Distinctive features of Container Apps include:
 
 * Optimized for running general purpose containers, especially for applications that span many microservices deployed in containers.
 * Powered by Kubernetes and open-source technologies like [Dapr](https://dapr.io/), [KEDA](https://keda.sh/), and [envoy](https://www.envoyproxy.io/).
 * 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).
-* Support of long running processes and can run [background tasks](background-processing.md).
+* Supports running on demand, scheduled, and event-driven [jobs](jobs.md).
 
 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](../aks/intro-kubernetes.md). 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 may prefer to start building container microservices with Azure Container Apps.
 

articles/container-apps/containers.md

@@ -18,15 +18,20 @@ Azure Container Apps manages the details of Kubernetes and container orchestrati
 
 Azure Container Apps supports:
 
-- Any Linux-based x86-64 (`linux/amd64`) container image
+- Any Linux-based x86-64 (`linux/amd64`) container image with no required base image
 - Containers from any public or private container registry
+- [Sidecar](#sidecar-containers) and [init](#init-containers) containers
 
-Features include:
+Container apps features include:
 
-- There's no required base container image.
 - Changes to the `template` configuration section trigger a new [container app revision](application-lifecycle-management.md).
 - If a container crashes, it automatically restarts.
 
+Jobs features include:
+
+- Job executions use the `template` configuration section to define the container image and other settings when each execution starts.
+- If a container exits with a non-zero exit code, the job execution is marked as failed. You can configure a job to retry failed executions.
+
 ## Configuration
 
 The following code is an example of the `containers` array in the [`properties.template`](azure-resource-manager-api-spec.md#propertiestemplate) section of a container app resource template.  The excerpt shows the available configuration options when setting up a container.
@@ -186,6 +191,9 @@ You can define one or more [init containers](https://kubernetes.io/docs/concepts
 
 Init containers are defined in the `initContainers` array of the container app template. The containers run in the order they are defined in the array and must complete successfully before the primary app container starts.
 
+> [!NOTE]
+> Init containers support [image pulls using managed identities](#managed-identity-with-azure-container-registry), but processes running in init containers don't have access to managed identities.
+
 ## Container registries
 
 You can deploy images hosted on private registries by providing credentials in the Container Apps configuration.

articles/container-apps/dapr-overview.md

@@ -350,6 +350,7 @@ This resource defines a Dapr component called `dapr-pubsub` via ARM.
 ### Known limitations
 
 - **Actor reminders**: Require a minReplicas of 1+ to ensure reminders is always active and fires correctly.
+- **Jobs**: Dapr isn't supported for jobs.
 
 ## Next Steps
 

articles/container-apps/environment.md

@@ -12,13 +12,13 @@ ms.custom: ignite-fall-2021, event-tier1-build-2022, build-2023
 
 # Azure Container Apps environments
 
-A Container Apps environment is a secure boundary around groups of container apps that share the same virtual network and write logs to the same logging destination.
+A Container Apps environment is a secure boundary around groups of container apps and jobs that share the same virtual network and write logs to the same logging destination.
 
 Container Apps environments are fully managed where Azure handles OS upgrades, scale operations, failover procedures, and resource balancing.
 
 :::image type="content" source="media/environments/azure-container-apps-environments.png" alt-text="Azure Container Apps environments.":::
 
-Reasons to deploy container apps to the same environment include situations when you need to:
+Reasons to deploy container apps and jobs to the same environment include situations when you need to:
 
 - Manage related services
 - Deploy different applications to the same virtual network

articles/container-apps/jobs-get-started-cli.md

@@ -1,17 +1,17 @@
 ---
-title: Create a job with Azure Container Apps (preview)
+title: Create a job with Azure Container Apps
 description: Learn to create an on-demand or scheduled job in Azure Container Apps
 services: container-apps
 author: craigshoemaker
 ms.service: container-apps
 ms.custom: build-2023, devx-track-azurecli
 ms.topic: quickstart
-ms.date: 05/08/2023
+ms.date: 08/17/2023
 ms.author: cshoe
 zone_pivot_groups: container-apps-job-types
 ---
 
-# Create a job with Azure Container Apps (preview)
+# Create a job with Azure Container Apps
 
 Azure Container Apps [jobs](jobs.md) allow you to run containerized tasks that execute for a finite duration and exit. You can trigger a job manually, schedule their execution, or trigger their execution based on events.
 

articles/container-apps/jobs-get-started-portal.md

@@ -0,0 +1,130 @@
+---
+title: Create a job with Azure Container Apps using the Azure portal
+description: Learn to create an on-demand or scheduled job in Azure Container Apps using the Azure portal
+services: container-apps
+author: craigshoemaker
+ms.service: container-apps
+ms.custom: build-2023, devx-track-azurecli
+ms.topic: quickstart
+ms.date: 08/21/2023
+ms.author: cshoe
+---
+
+# Create a job with Azure Container Apps using the Azure portal
+
+Azure Container Apps [jobs](jobs.md) allow you to run containerized tasks that execute for a finite duration and exit. You can trigger a job manually, schedule their execution, or trigger their execution based on events.
+
+Jobs are best suited to for tasks such as data processing, machine learning, or any scenario that requires on-demand processing.
+
+In this quickstart, you create a scheduled job. To learn how to create an event-driven job, see [Deploy an event-driven job with Azure Container Apps](tutorial-event-driven-jobs.md).
+
+## Prerequisites
+
+An Azure account with an active subscription is required. If you don't already have one, you can [create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F). Also, please make sure to have the Resource Provider "Microsoft.App" registered.
+
+## Setup
+
+Begin by signing in to the [Azure portal](https://portal.azure.com).
+
+## Create a container app
+
+To create your Container Apps job, start at the Azure portal home page.
+
+1. Search for **Container App Jobs** in the top search bar.
+1. Select **Container App Jobs** in the search results.
+1. Select the **Create** button.
+
+### Basics tab
+
+In the *Basics* tab, do the following actions.
+
+1. Enter the following values in the *Project details* section.
+
+    | Setting | Action |
+    |---|---|
+    | Subscription | Select your Azure subscription. |
+    | Resource group | Select **Create new** and enter **jobs-quickstart**. |
+    | Container job name |  Enter **my-job**. |
+
+#### Create an environment
+
+Next, create an environment for your container app.
+
+1. Select the appropriate region.
+
+    | Setting | Value |
+    |--|--|
+    | Region | Select **Central US**. |
+
+1. In the *Create Container Apps environment* field, select the **Create new** link.
+1. In the *Create Container Apps Environment* page, on the *Basics* tab, enter the following values:
+
+    | Setting | Value |
+    |--|--|
+    | Environment name | Enter **my-environment**. |
+    | Type | Enter **Workload Profile**. |
+    | Zone redundancy | Select **Disabled** |
+
+1. Select the **Create** button at the bottom of the *Create Container App Environment* page.
+
+### Deploy the job
+
+1. In *Job details*, select **Scheduled** for the *Trigger type*.
+
+    In the *Cron expression* field, enter `*/1 * * * *`.
+    
+    This expression starts the job every minute.
+
+1. Select the **Next: Container** button at the bottom of the page.
+
+1. In the *Container* tab, enter the following values:
+
+    | Setting | Value |
+    |--|--|
+    | Name | Enter **main-container**. |
+    | Image source | Select **Docker Hub or other registries**. |
+    | Image type | Select **Public**. |
+    | Registry login server | Enter **mcr.microsoft.com**. |
+    | Image and tag | Enter **k8se/quickstart-jobs:latest**. |
+    | Workload profile | Select **Consumption**. |
+    | CPU and memory | Select **0.25** and **0.5Gi**. |
+
+1. Select the **Review and create** button at the bottom of the page.  
+
+    As the settings in the job are verified, if no errors are found, the *Create* button is enabled.  
+
+    Any errors appear on a tab marked with a red dot. If you encounter errors, navigate to the appropriate tab and you'll find fields containing errors highlighted in red. Once all errors are fixed, select **Review and create** again.
+
+1. Select **Create**.
+
+    A page with the message *Deployment is in progress* is displayed.  Once the deployment is successfully completed, you'll see the message: *Your deployment is complete*.
+
+### Verify deployment
+
+1. Select **Go to resource** to view your new Container Apps job.
+
+2. Select the **Execution history** tab.
+
+    The *Execution history* tab displays the status of each job execution. Select the **Refresh** button to update the list. Wait up to a minute for the scheduled job execution to start. Its status changes from *Pending* to *Running* to *Succeeded*.
+
+1. Select **View logs**.
+
+    The logs show the output of the job execution. It may take a few minutes for the logs to appear.
+
+## Clean up resources
+
+If you're not going to continue to use this application, you can delete the Azure Container Apps instance and all the associated services by removing the resource group.
+
+1. Select the **jobs-quickstart** resource group from the *Overview* section.
+1. Select the **Delete resource group** button at the top of the resource group *Overview*.
+1. Enter the resource group name **jobs-quickstart** in the *Are you sure you want to delete "jobs-quickstart"* confirmation dialog.
+1. Select **Delete**.  
+    The process to delete the resource group may take a few minutes to complete.
+
+> [!TIP]
+> Having issues? Let us know on GitHub by opening an issue in the [Azure Container Apps repo](https://github.com/microsoft/azure-container-apps).
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Container Apps jobs](jobs.md)