Hi,

We have many harness projects in our org. We wish to use harness as the oidc platform to authenticate pipelines to azure managed identity resource using federated credentials. The oidc community plugin currently only supports authentication of the subject using the harness 'account_id'. In order to leverage this in a large org, we need the ability to authenticate a project pipeline to a managed identity with more than just the 'account_id' 'subject'. We need the capability for harness to present both 'account_Id' and 'project_id' to enable us to scale harness. This is currently achievable with Aws platform and Google. It would be nice for harness to provide full oidc feature parity between azure and Aws/Google.

Thanks