Authenticate Azure Repositories in Pipelines

You may try:

1. Use Git Global Config with PAT

You can configure Git globally to rewrite Azure DevOps URLs to include your PAT automatically:

git config --global url."https://<PAT>@dev.azure.com/".insteadOf "https://dev.azure.com/"

This forces Git to use your PAT whenever Julia tries to clone a repo from Azure DevOps. 

2. Use Git Credential Manager

Install and configure Git Credential Manager to securely store and inject credentials. 

3. Switch to Microsoft Entra OAuth Tokens

If you want a more secure and modern approach, you can use Microsoft Entra tokens (formerly Azure AD) with Git:

az login
az account get-access-token --resource 499b84ac-1321-427f-aa17-267ca6975798 --query "accessToken" --output tsv

Then inject the token into Git using:

git -c http.extraheader="AUTHORIZATION: bearer <accessToken>" clone https://dev.azure.com/yourOrg/yourProject/_git/yourRepo

This method is more secure than embedding PATs in URLs.

4. Use a Dedicated Service Account

Create a service account in Azure AD specifically for DevOps automation. Generate a PAT under that account and use it in your Git config. This avoids tying automation to a personal account that might expire or be deleted.