docs: azdo pipeline

Author: pankajagrawal16

docs/aca/10-aca-iac-bicep/ci-cd-azdo.md

@@ -0,0 +1,91 @@
+
+# Deploy infrastructure using GitHub Actions
+
+!!! info "Module Duration"
+    30 minutes
+
+Azure Devops pipeline is another great way to automate your workflow. In this section, we will create a Azure Devops Pipeline to 
+deploy the infrastructure components of our application.
+
+The workshop repository contains a Azure Devops Pipeline yaml file that will be used to deploy the infrastructure 
+components of our application. Follow the steps below to create a devops pipeline to deploy the 
+infrastructure components of our application.
+
+### Fork the GitHub repository
+
+Start by forking the workshop repository to your GitHub account. Follow the steps below to fork the workshop:
+
+1. Navigate to the workshop repository at [:material-github: Azure/aca-dotnet-workshop](https://github.com/Azure/aca-dotnet-workshop){target=_blank}
+2. Click the **Fork** button in the top-right corner of the page.
+3. Select your GitHub account to fork the repository to.
+4. Wait for the repository to be forked.
+
+### Configure Service Connection for GitHub and Azure Subscription
+
+Before we start with creating pipeline, we need to configure service connection for GitHub and Azure Subscription. You can do this in either existing or new project.
+
+#### Create Service Connection for GitHub
+
+Provide access to the repository forked above by creating a service connection to GitHub. You create a new pipeline 
+by first selecting a GitHub repository and then a YAML file in repository at path [.ado/infra-deploy.yml](https://raw.githubusercontent.com/Azure/aca-dotnet-workshop/main/.ado/infra-deploy.yml){target=_blank}. 
+
+The repository in which the YAML file is present is called self repository. By default, this is the repository that your pipeline builds.
+
+There are three authentication types for granting Azure Pipelines access to your GitHub repositories while creating 
+a pipeline. Follow guide at [this link](https://learn.microsoft.com/en-us/azure/devops/pipelines/repos/github?view=azure-devops&tabs=yaml#access-to-github-repositories){target=_blank}
+to create service connection for GitHub.
+
+
+![AZDO GitHub Connection](../../assets/gifs/azdo-github-connection.gif)
+
+#### Create Service Connection for Azure Subscription
+
+Create new service connection to your azure subscription by following steps at [this link](https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml#create-a-service-connection){target=_blank}
+
+!!! note
+    Update the created service connection role to have **[User Access Administrator](https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles#user-access-administrator)** role. 
+    This is required for pipeline to be able to perform role assignments in the infrastructure components deployed.
+
+### Configure Variable group under Library
+
+Create a variable group named **AcaApp** under Library in your Azure Devops project. Make sure the pipeline has 
+permissions to access the created variable group under **Pipeline permissions**.
+
+This variable group will be used to store below details:
+
+```bash
+# AZURE_SUBSCRIPTION: Name of the service connection created for Azure Subscription
+AZURE_SUBSCRIPTION=<service connection name>
+
+# LOCATION: Azure region where resources will be deployed
+LOCATION=<location>
+
+# RESOURCE_GROUP: Name of the resource group which will be created and resources will be deployed
+RESOURCE_GROUP=<resource group name>
+
+# (OPTIONAL)CONTAINER_REGISTRY_NAME: Unique name of the container registry which will be created and where images will be imported
+CONTAINER_REGISTRY_NAME=<container registry name>
+```
+
+!!! note
+
+    Repository variables `CONTAINER_REGISTRY_NAME` is only needed by pipeline, if you wish the images to be deployed from private ACR.
+    
+    You may chose to skip defining this variable and the pipeline will use the [public github container registry images](https://github.com/orgs/Azure/packages?repo_name=aca-dotnet-workshop) to deploy the images.
+
+### Trigger Azure Devops Pipeline
+
+With these steps completed, you are now ready to trigger the Pipeline.
+
+!!! success
+    
+    Your Pipeline should be triggered and the infrastructure components of our application should be deployed successfully.
+
+    ![GitHub Actions Workflow](../../assets/gifs/azdo-trigger.gif)
+
+
+??? info "Want to delete the resources deployed by the pipeline?"
+    
+    Trigger the pipeline again select **checkbox** option named **Should teardown infrastructure?**.
+
+    ![GitHub Actions Workflow](../../assets/gifs/azdo-delete.gif)

docs/aca/10-aca-iac-bicep/iac-bicep.md

@@ -323,13 +323,13 @@ Next, we will prepare container images for the three container apps and update t
                 "value": "<CONTAINER_REGISTRY_NAME>"
             },
             "backendProcessorServiceImage": {
-                "value": "<CONTAINER_REGISTRY_NAME>.azurecr.io/tasksmanager/<BACKEND_API_NAME>:latest"
+                "value": "<CONTAINER_REGISTRY_NAME>.azurecr.io/tasksmanager/tasksmanager-backend-processor:latest"
             },
             "backendApiServiceImage": {
-                "value": "<CONTAINER_REGISTRY_NAME>.azurecr.io/tasksmanager/<FRONTEND_WEBAPP_NAME>:latest"
+                "value": "<CONTAINER_REGISTRY_NAME>.azurecr.io/tasksmanager/tasksmanager-backend-api:latest"
             },
             "frontendWebAppServiceImage": {
-                "value": "<CONTAINER_REGISTRY_NAME>.azurecr.io/tasksmanager/<BACKEND_SVC_NAME>:latest"
+                "value": "<CONTAINER_REGISTRY_NAME>.azurecr.io/tasksmanager/tasksmanager-frontend-webapp:latest"
             }
         }
         ```

docs/assets/gifs/azdo-delete.gif

@@ -22,6 +22,7 @@ nav:
     - aca/10-aca-iac-bicep/index.md
     - Build the Infrastructure as Code Using Bicep: aca/10-aca-iac-bicep/iac-bicep.md
     - Deploy infrastructure using GitHub Actions: aca/10-aca-iac-bicep/ci-cd-git-action.md
+    - Deploy infrastructure using Azure Devops Pipeline: aca/10-aca-iac-bicep/ci-cd-azdo.md
   - About The Authors: aca/11-about-the-authors/index.md
   - Contributing:
     - Contribution Guide: aca/12-contributing/1-contribution-guide.md