Azure Key Vault integration: under consideration
We’re considering an Azure Key Vault source integration for developers whose clients already store service credentials in Azure. This connector is not available today. A potential implementation would need an authenticated reader accepted by the client’s Microsoft Entra tenant, permission to read selected secret values and an approved network path. No provider selection or launch date has been committed.
What could a retrieval layer add to native Azure access?
Azure already provides workload identity, access controls and secret retrieval APIs. A client running its agents inside established Azure infrastructure may be better served by native tooling. A developer working across clients with different vault products might benefit from a consistent retrieval contract and agent-attributed requests. The additional layer would need to justify its source-reader trust, administration and availability costs rather than treating cloud integration as an automatic security improvement.
Integration considerations
- 1
Azure Key Vault authenticates callers through Microsoft Entra ID. A potential connector would need a suitable application or workload identity and the client’s explicit authorization; a vault URL alone does not grant access.
- 2
The reader would need secret-value read permissions, not merely permission to view resource metadata. Scope would need to be checked against the client’s actual vault access model and selected secrets.
- 3
A managed identity belongs to its hosting context. A hosted reader cannot simply borrow a client workload’s identity; tenant trust and authentication would require a supported design.
- 4
Firewalls, private endpoints and TLS requirements are separate from API compatibility. There is no current Gazebo private-network connector or Azure authorization flow to configure.
- 5
Secret references, versions, disabled values, denied reads and source outages would need explicit handling. Revoking source access would not invalidate provider credentials previously delivered to an agent.
Workflows we’re evaluating
Client-owned Azure credentials
A possible workflow would leave selected secrets in the client’s vault while a developer uses the same agent-facing retrieval interface across clients. The client would still need to approve who can read those values and how access ends when the engagement finishes.
Agent request context alongside Azure records
A future connector could associate a named agent and approved secret reference with a retrieval decision. That would complement the client’s Azure and runtime records, not prove which downstream API operations occurred after the credential was returned.
Discuss your Azure Key Vault workflow
Tell us about your vault, agent runtime and integration needs. Please don’t send credentials or sensitive client information. No connector or launch date is promised.
Discuss your Azure Key Vault workflow