https://airbytehq.slack.com/archives/C01AHCD885S/p1760419040124809 is Azure Key Vault secret has official bug? just want to confirm, if anyone faced same issue?

Based on the available documentation, Azure Key Vault is officially supported as an external secret manager in Airbyte for self-managed enterprise deployments. The documentation provides configuration examples and instructions for integrating Azure Key Vault, including the required fields such as

vaultUrl

,

tenantId

, and optional tags. There is no mention in the official documentation that Azure Key Vault is currently unsupported or that there is an official bug preventing its use. In fact, it is listed alongside AWS Secrets Manager and Google Secrets Manager as a supported option in multiple versions of the documentation, including the latest and "next" versions [Secret Management](https://docs.airbyte.com/platform/deploying-airbyte/integrations/secrets). However, there is a related open GitHub issue requesting improved support for Azure Key Vault authentication using Default Azure Credential (e.g., managed identities), which would provide more flexibility compared to the current client secret approach. This is a feature request, not a report of a general bug or lack of support [Secret Manager - Azure Keyvault - should use Default Azure Credential](https://github.com/airbytehq/airbyte/issues/60901). If you are experiencing issues with Azure Key Vault integration, it may be a specific configuration or environment problem rather than a general or officially recognized bug. If you have a specific error or problem, providing details may help the community or support team assist you further.