What can you do with the Azure Key Vault integration?

LiveContext exposes 29 operations on Azure Key Vault, covering key, secret, certificate and deleted secret. Common uses include automate operation management, enable or disable a key version and sign operation programmatically.

LiveContext

All integrations

Azure Key Vault integration

Azure Key Vault REST API for managing secrets, cryptographic keys, and certificates. Securely store and access tokens, passwords, certificates, API keys, and other secrets with hardware-backed encryption.

29 toolsOAuthAPI docs

Connect Azure Key Vault How integrations work

Common Azure Key Vault use cases

automate operation management
enable or disable a key version
sign operation programmatically
verify operation programmatically
decrypt operation programmatically
enable or disable a secret version
encrypt operation programmatically
remove a credential from Key Vault
undo an accidental secret deletion
remove a certificate from Key Vault

What you can do with Azure Key Vault

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Key, 8 operations

POSTcreate_key
Creates a new key, stores it, and returns key parameters and attributes to the client. The create key operation can be used to create any key type in Azure Key Vault.
DELETEdelete_key
Deletes a key of any type from storage in Azure Key Vault. All versions of the key are deleted. If soft-delete is enabled, the key can be recovered.
GETget_key
Gets the public part of a stored key. Returns key parameters and attributes.
PUTimport_key
Imports an externally created key and stores it in the vault. The import key operation supports importing any key type into Azure Key Vault.
GETlist_keys
Lists keys in the specified vault. Returns the key identifier and attributes for all keys in the vault.
POSTunwrap_key
Unwraps (decrypts) a symmetric key using the specified key. The UNWRAP operation is the inverse of the WRAP operation.
PATCHupdate_key
Updates the properties associated with a specified key in a given key vault. Cannot update the key material.
POSTwrap_key
Wraps (encrypts) a symmetric key using the specified key. The WRAP operation supports encryption of a symmetric key using a key encryption key.

Secret, 8 operations

POSTbackup_secret
Requests that a backup of the specified secret be downloaded to the client. All versions of the secret will be downloaded as an encrypted blob.
DELETEdelete_secret
Deletes a secret from the specified key vault. Moves the secret to the deleted state. If soft-delete is enabled, the secret can be recovered.
GETget_latest_secret
Get the latest version of a specified secret from a given key vault.
GETget_secret
Get a specified secret version from a given key vault. Returns the secret value along with its attributes.
GETlist_secrets
List secrets in a specified key vault. Returns the identifier and attributes of all secrets. Does not include secret values.
POSTrestore_secret
Restores a backed-up secret and all its versions to a vault. The vault must be the same subscription as the original vault.
PUTset_secret
Sets a secret in a specified key vault. Creates a new secret version if the secret already exists.
PATCHupdate_secret
Updates the attributes associated with a specified secret in a given key vault. Cannot update the secret value; use Set Secret instead.

Certificate, 4 operations

POSTcreate_certificate
Creates a new certificate version. If this is the first version, the certificate resource is created.
DELETEdelete_certificate
Deletes all versions of a certificate object along with its associated policy. If soft-delete is enabled, the certificate can be recovered.
GETget_certificate
Gets information about a certificate. Returns the certificate along with its policy and attributes.
GETlist_certificates
Lists the certificates in a specified key vault. Returns the identifier and attributes of all certificates.

Deleted secret, 4 operations

GETget_deleted_secret
Gets the specified deleted secret. Requires soft-delete to be enabled on the vault.
GETlist_deleted_secrets
Lists deleted secrets for the specified vault. Requires soft-delete to be enabled.
DELETEpurge_deleted_secret
Permanently deletes the specified secret. This operation is irreversible. Requires soft-delete to be enabled and the secret must be in a deleted state.
POSTrecover_deleted_secret
Recovers the deleted secret to the latest version. Requires soft-delete to be enabled. The secret must be in a deleted but recoverable state.

Operation, 4 operations

POSTdecrypt
Decrypts a single block of encrypted data. The DECRYPT operation supports decryption of a single block of encrypted data.
POSTencrypt
Encrypts an arbitrary sequence of bytes using an encryption key stored in Azure Key Vault.
POSTsign
Creates a signature from a digest using the specified key. The SIGN operation is applicable to asymmetric and symmetric keys stored in Azure Key Vault.
POSTverify
Verifies a signature using the specified key. The VERIFY operation is applicable to symmetric keys stored in Azure Key Vault.

Secret version, 1 operation

GETlist_secret_versions
List all versions of the specified secret. Returns the identifier and attributes of all secret versions.

Use Azure Key Vault from Claude Code, Cursor or Codex

Connect Azure Key Vault in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Azure Key Vault operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Azure Key Vault

Create your workspace
Sign up free. Nothing to install.
Connect Azure Key Vault once
Add your Azure Key Vault connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Azure Key Vault integration FAQ

What can you do with the Azure Key Vault integration?: LiveContext exposes 29 operations on Azure Key Vault, covering key, secret, certificate and deleted secret. Common uses include automate operation management, enable or disable a key version and sign operation programmatically.