Add support for a custom az-path

[duncan3dc]

In some of our workflows we use docker containers to ensure we've got a consistent environment. We use this action to authenticate with OIDC, but this action assumes the az CLI is running on the GitHub actions machine.

This PR allows a custom az path to be specified, so that we can authenticate inside the docker container, and then run our following az commands in there.

For example:

- name: Setup docker container
  run: |
    docker build . -t ci-image
    docker run --interactive --detach \
      --env ACTIONS_ID_TOKEN_REQUEST_URL=$ACTIONS_ID_TOKEN_REQUEST_URL \
      --env ACTIONS_ID_TOKEN_REQUEST_TOKEN=$ACTIONS_ID_TOKEN_REQUEST_TOKEN \
      --name ci ci-image

- name: Authenticate with Azure
  uses: azure/login@v2
  with:
    client-id: "${{ secrets.AZURE_CLIENT_ID }}"
    tenant-id: "${{ secrets.AZURE_TENANT_ID }}"
    subscription-id: "${{ secrets.AZURE_SUBSCRIPTION_ID }}"
    az-path: "docker exec ci az"

- name: Now we can run az inside our container
  run: docker exec ci az account show

[MoChilia]

Hi @duncan3dc, thank you for your contribution. I appreciate this feature. But I would prefer setting it as an environment variable rather than using a parameter.

@YanaXu For consistency, should we consider whether Azure PowerShell will also require a custom path?

[srceenr29y1]

vại tương lơ . Cấm mọi quyền cả admins( nguyên ; Nguyễn ...) phát hiện ban vĩnh viễn Vào Thứ 6, 6 thg 3, 2026 lúc 20:06 Mattias Vinberg ***@***.***> đã viết:

…

***@***.**** approved this pull request. — Reply to this email directly, view it on GitHub <#559 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BSDHOMFEIRD7TEDSEUP7JB34PLENRAVCNFSM6AAAAACI2RT57OVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTSMBTGYZDENZRGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>