update task version

Author: juliakm

articles/azure-resource-manager/bicep/deploy-github-actions.md

@@ -101,25 +101,31 @@ To create a workflow, take the following steps:
 1. Rename the workflow file if you prefer a different name other than **main.yml**. For example: **deployBicepFile.yml**.
 1. Replace the content of the yml file with the following code:
 
-    # [Service principal](#tab/userlevel)
+    # [OpenID Connect](#tab/openid)
 
     ```yml
-    name: Deploy Bicep file
     on: [push]
+    name: Azure ARM
+    permissions:
+      id-token: write
+      contents: read
     jobs:
       build-and-deploy:
         runs-on: ubuntu-latest
         steps:
 
-        - name: Checkout code
-          uses: actions/checkout@main
+          # Checkout code
+        - uses: actions/checkout@main
 
-        - name: Log into Azure
-          uses: azure/login@v1
+          # Log into Azure
+        - uses: azure/login@v2
           with:
-            creds: ${{ secrets.AZURE_CREDENTIALS }}
+            client-id: ${{ secrets.AZURE_CLIENT_ID }}
+            tenant-id: ${{ secrets.AZURE_TENANT_ID }}
+            subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
 
-        - name: Deploy Bicep file
+          # Deploy Bicep file
+        - name: deploy
           uses: azure/arm-deploy@v1
           with:
             subscriptionId: ${{ secrets.AZURE_SUBSCRIPTION }}
@@ -129,41 +135,25 @@ To create a workflow, take the following steps:
             failOnStdErr: false
     ```
 
-    Replace `mystore` with your own storage account name prefix.
-
-    > [!NOTE]
-    > You can specify a JSON format parameters file instead in the ARM Deploy action (example: `.azuredeploy.parameters.json`).
-
-    The first section of the workflow file includes:
-
-    - **name**: The name of the workflow.
-    - **on**: The name of the GitHub events that triggers the workflow. The workflow is triggered when there's a push event on the main branch.
-
-    # [OpenID Connect](#tab/openid)
+    # [Service principal](#tab/userlevel)
 
     ```yml
+    name: Deploy Bicep file
     on: [push]
-    name: Azure ARM
-    permissions:
-      id-token: write
-      contents: read
     jobs:
       build-and-deploy:
         runs-on: ubuntu-latest
         steps:
 
-          # Checkout code
-        - uses: actions/checkout@main
+        - name: Checkout code
+          uses: actions/checkout@main
 
-          # Log into Azure
-        - uses: azure/login@v1
+        - name: Log into Azure
+          uses: azure/login@v2
           with:
-            client-id: ${{ secrets.AZURE_CLIENT_ID }}
-            tenant-id: ${{ secrets.AZURE_TENANT_ID }}
-            subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
+            creds: ${{ secrets.AZURE_CREDENTIALS }}
 
-          # Deploy Bicep file
-        - name: deploy
+        - name: Deploy Bicep file
           uses: azure/arm-deploy@v1
           with:
             subscriptionId: ${{ secrets.AZURE_SUBSCRIPTION }}
@@ -173,6 +163,16 @@ To create a workflow, take the following steps:
             failOnStdErr: false
     ```
 
+    Replace `mystore` with your own storage account name prefix.
+
+    > [!NOTE]
+    > You can specify a JSON format parameters file instead in the ARM Deploy action (example: `.azuredeploy.parameters.json`).
+
+    The first section of the workflow file includes:
+
+    - **name**: The name of the workflow.
+    - **on**: The name of the GitHub events that triggers the workflow. The workflow is triggered when there's a push event on the main branch.
+
     ---