The Harness UI allows configuring an Azure Key Vault secret manager connector using delegate credentials — System-assigned or User-assigned Managed Identity — without storing an Azure client secret in Harness.

The Terraform resource for the same connector currently treats client_id, tenant_id, and secret_key as required arguments. Passing null or omitting them for MSI-style configuration fails with errors such as:

Error: Missing required argument

The argument "client_id" is required, but no definition was found.

The argument "tenant_id" is required, but no definition was found.

The argument "secret_key" is required, but no definition was found.

That forces ManualConfig-style usage in Terraform, where secret_key must reference the Harness Built-in Secret Manager, which conflicts with org policies that do not allow storing connector credentials in the harness built-in secret manager.

Please update the Harness Terraform provider (and document behavior) so that harness_platform_connector_azure_key_vault match