Replace deprecated --username flag with --client-id in az login --identity commands

[Copilot]

What is being addressed

Azure CLI deprecated the --username flag when using az login --identity for managed identity authentication. The correct flag is --client-id.

How is this addressed

• Replaced username: with client-id: in all az login --identity commands across 8 Porter bundles:
  • Shared services: airlock_notifier, certs, cyclecloud
  • Workspace services: ohdsi
  • User resources: guacamole-azure-export-reviewvm, guacamole-azure-import-reviewvm, guacamole-azure-linuxvm, guacamole-azure-windowsvm
• Incremented bundle versions (PATCH level) per semantic versioning guidelines
• Updated CHANGELOG.md with issue reference (#4817)

Before:

- az:
    description: "Login to Azure"
    arguments:
      - login
    flags:
      identity:
      username: ${ bundle.credentials.azure_client_id }

After:

- az:
    description: "Login to Azure"
    arguments:
      - login
    flags:
      identity:
      client-id: ${ bundle.credentials.azure_client_id }

Note: Shell scripts using az login --service-principal --username were not changed as --username remains valid for service principal authentication.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>az cli uses depreciated --username flag when using --identity in bundles</issue_title>
<issue_description>Azure CLI needs to use az login --identity --client-id <client_id> as per https://learn.microsoft.com/en-us/cli/azure/authenticate-azure-cli-managed-identity?view=azure-cli-latest, not --username which has been deprecated.</issue_description>

<agent_instructions>Check all porter.yaml files for instances where this flag needs to be updated. The bundle versions will need updating.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes az cli uses depreciated --username flag when using --identity in bundles #4817

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

This PR updates Azure CLI authentication commands across Porter bundles to use the correct --client-id flag instead of the deprecated --username flag when authenticating with managed identities.

Changes:

• Updated az login --identity commands to use --client-id instead of deprecated --username flag in 8 Porter bundles
• Incremented bundle versions by a PATCH level following semantic versioning guidelines
• Updated CHANGELOG.md to document the bug fix

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
templates/shared_services/airlock_notifier/porter.yaml	Replaced username: with client-id: in install and upgrade actions; bumped version to 1.0.10
templates/shared_services/certs/porter.yaml	Replaced username: with client-id: in install and renew actions; bumped version to 0.7.9
templates/shared_services/cyclecloud/porter.yaml	Replaced username: with client-id: in start and stop actions; bumped version to 0.7.4
templates/workspace_services/ohdsi/porter.yaml	Replaced username: with client-id: in install and upgrade actions; bumped version to 0.3.5
templates/workspace_services/guacamole/user_resources/guacamole-azure-export-reviewvm/porter.yaml	Replaced username: with client-id: in start, stop, and reset_password actions; bumped version to 0.3.5
templates/workspace_services/guacamole/user_resources/guacamole-azure-import-reviewvm/porter.yaml	Replaced username: with client-id: in start, stop, and reset_password actions; bumped version to 0.4.4
templates/workspace_services/guacamole/user_resources/guacamole-azure-linuxvm/porter.yaml	Replaced username: with client-id: in start, stop, and reset_password actions; bumped version to 1.4.3
templates/workspace_services/guacamole/user_resources/guacamole-azure-windowsvm/porter.yaml	Replaced username: with client-id: in start, stop, and reset_password actions; bumped version to 1.4.4
CHANGELOG.md	Added entry in BUG FIXES section documenting the deprecation fix

[marrobi]

/test-extended

[github-actions]

🤖 pr-bot 🤖

⚠️ When using /test-extended on external PRs, the SHA of the checked commit must be specified

(in response to this comment from @marrobi)

[marrobi]

/test-extended e8ed9b5

[github-actions]

🤖 pr-bot 🤖

🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/21170719648 (with refid 153a815f)

(in response to this comment from @marrobi)

[github-actions]

Unit Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 8a26ebe.

♻️ This comment has been updated with latest results.

[marrobi]

/test-extended 8a26ebe

[github-actions]

🤖 pr-bot 🤖

🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/21213006566 (with refid 153a815f)

(in response to this comment from @marrobi)

[JC-wk]

LGTM

[marrobi]

/test-force-approve

Tests failing for another reason and this wasn't picked up as wasn't covered by tests.

[github-actions]

🤖 pr-bot 🤖

✅ Marking tests as complete (for commit 8a26ebe)

(in response to this comment from @marrobi)