Address review feedback on pipelines freshness update

- Update service connection type from 'Service principal (automatic)' to
  'App registration (automatic)' to match current Azure DevOps UI
- Add note about Azure Repos Git prerequisite for pipeline creation
- Add tip for Debian repository build errors with az containerapp up

Co-authored-by: Copilot <[email protected]>

Author: 2 people

articles/container-apps/azure-pipelines.md

@@ -143,7 +143,7 @@ To deploy to Container Apps, you need to create an Azure DevOps service connecti
 
 1. Select **Azure Resource Manager**, and then select **Next**.
 
-1. Select **Service principal (automatic)**, and then select **Next**.
+1. Select **App registration (automatic)**, and then select **Next**.
 
 1. Provide the following values, and then select **Save**:
 
@@ -163,6 +163,9 @@ To learn more about service connections, see [Connect to Microsoft Azure](/azure
 
 1. Select **Azure Repos Git**.
 
+    > [!NOTE]
+    > If you don't see **Azure Repos Git** as an option, make sure your source code is pushed to a Git repository in your Azure DevOps project.
+
 1. Select the repo that contains your source code (`my-container-app`).
 
 1. Select **Starter pipeline**.

includes/container-apps-github-devops-setup.md

@@ -22,6 +22,9 @@ ms.author: wujia
       --ingress external 
     ```
 
+    > [!TIP]
+    > If the build fails with a Debian repository error, make sure you're using the latest Azure CLI version and containerapp extension by running `az extension add --name containerapp --upgrade`. Alternatively, add a Dockerfile to your project for more control over the build.
+
 1. In the command output, note the name of the Azure container registry.
 
 1. Get the full resource ID of the container registry: