Fail to run azd pipeline config --provider github and azd pipeline config --provider azdo

[Menghua1]

Describe the issue:
When running the azd pipeline config --provider github and azd pipeline config --provider azdo commands, the error message fails as follows:

Repro Steps:

1. Login in with command: azd auth login.
2. Run command: azd init -t todo-python-mongo-terraform -b staging.
3. Run command: azd pipeline config --provider github or azd pipeline config --provider azdo.

Environment:

• Template: todo-python-mongo-terraform, todo-nodejs-mongo-terraform, todo-java-postgresql-terraform.
• Branch: staging
• OS: Windows, Linux, Mac, Cloud Shell, DevContainer, Codespaces.
• Azd version: azd version 1.11.0-beta.1-pr.4140256 (commit b6402de) and azd version 1.11.0-beta.1-daily.4152592 (commit e2ff8ba)

Expected behavior:
azd pipeline config --provider github and azd pipeline config --provider azdo commands can be run successfully.

@jongio for notification.

[Menghua1]

@jongio This issue can also be reproduced in main. We tested the following four scenarios and they can all be reproduced:

• Template: todo-python-mongo-terraform, todo-nodejs-mongo-terraform, todo-java-postgresql-terraform.
• OS: Windows, Linux, Mac, Cloud Shell, DevContainer, Codespaces.
• Test Scenario:

1. Templates under the main branch + azd version 1.11.0-beta.1-daily.4152592 (commit e2ff8ba).
2. Templates under the main branch + azd version 1.11.0-beta.1-pr.4140256 (commit b6402de).
3. Templates under the staging branch + azd version 1.11.0-beta.1-daily.4152592 (commit e2ff8ba).
4. Templates under the staging branch + azd version 1.11.0-beta.1-pr.4140256 (commit b6402de).

[rajeshkamal5050]

@vhvb1989 do you think our internal subscriptions have policies which restrict dealing with client-credentials? but from a pipeline config feature POV we do support client-credentials?

[vhvb1989]

@rajeshkamal5050 yes, the internal policy to block client-secrets was applied some days ago. If we want to run these tests, we need to use a different Tenant/Sub w/o the policy. Or we need to move the terraform scenarios to use managed identity (see: #4343)

[rajeshkamal5050]

@vhvb1989 May be a test tenant would help here for us in testing such features which are still supported?

cc @weshaggard @danieljurek

[weshaggard]

Our new TME test tenant isn't up and running yet but once it is ready it might be worth using here.

[Menghua1]

@rajeshkamal5050 In the latest round of azd manual testing, this issue still exists.

• Template: todo-python-mongo-terraform, todo-nodejs-mongo-terraform, todo-java-postgresql-terraform.
• OS: Windows, Mac, DevContainer.
• Branch: staging
• Azd version: azd version 1.11.0-beta.1-daily.4152592 (commit e2ff8ba)

[Menghua1]

@rajeshkamal5050 and @jongio In the latest round of azd manual testing, this issue still exists.

• Template: todo-python-mongo-terraform, todo-nodejs-mongo-terraform, todo-java-postgresql-terraform.
• OS: Windows.
• Branch: staging
• Azd version: azd version 1.10.3-pr.4243081 (commit 2c05c15) and azd version 1.11.0-beta.1-daily.4244391 (commit 8fc9d80).

[Menghua1]

@rajeshkamal5050 In the latest round of azd manual testing, this issue still exists.

• Template: todo-python-mongo-terraform, todo-nodejs-mongo-terraform, todo-java-postgresql-terraform.
• OS: Windows, Mac, DevContainer.
• Branch: staging
• Azd version: azd version 1.11.0-beta.1-daily.4247716 (commit f4695c4)