Microsoft Azure RecoveryServicesClient

Name: RecoveryServicesClient API
Brand: Recovery Services Client
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageBackup Recoveryoauth22 EndpointsREST

Install Jentic One Beta

Connect the RecoveryServicesClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RecoveryServicesClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with RecoveryServicesClient API.

Upload an X.509 certificate to a Recovery Services vault for backup or replication agents

Rotate the vault certificate by uploading a new one with a unique name

Remove a registered workload identity from a Recovery Services vault

GET STARTED

Start building with RecoveryServicesClient API

Explore with Jentic

View OpenAPI Document

For Agents

Upload or rotate the vault certificate on an Azure Recovery Services vault and unregister a workload identity that should no longer access the vault.

Use for: Upload a new X.509 certificate to a Recovery Services vault, Rotate the vault certificate on an Azure backup vault, Remove a registered identity that is no longer used, Provision the certificate backup agents need to register

Not supported: Does not configure soft delete, manage backup policies, or trigger restores - use for vault certificate upload and registered-identity removal only.

Use Cases

Patterns agents use RecoveryServicesClient API for, with concrete tasks.

★ Backup agent enrolment

On-premises and Azure VM backup agents register against a Recovery Services vault using a certificate the platform team has uploaded. The API accepts the public certificate in PEM format under a chosen certificate name so the resulting vault credentials can be downloaded and installed on the agent host.

Upload PEM certificate 'mab-host-prod.pem' to vault 'rsv-prod' under certificate name 'mab-host-prod'

Certificate rotation

Vault certificates expire and need to be rotated before agents fail to authenticate. The PUT endpoint accepts a new certificate under a fresh name; once agents have re-registered with the new credential, the old certificate can be retired.

Upload a new certificate 'mab-host-prod-2026' to vault 'rsv-prod' ahead of the existing certificate's expiry

Decommission a registered host

When a backup-protected host is decommissioned, its registered identity should be removed from the vault so it cannot continue to interact with backup workflows. The DELETE on registeredIdentities/{identityName} removes the identity in a single call.

Delete the registered identity named 'host-old-finance' from vault 'rsv-prod' as part of the host decommissioning runbook

Agent-driven credential lifecycle

An AI agent maintaining backup hygiene watches certificate expiry dates and registered identity inventories, uploads renewed certificates ahead of expiry, and removes decommissioned hosts on a schedule. Jentic isolates the AAD client secret so the agent only sees scoped bearer tokens.

List vaults in subscription X with vault certificates expiring in 30 days and upload a renewed certificate to each

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for recoveryservicesclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/certificates/{certificateName}

Upload or rotate a vault certificate

DELETE

/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/registeredIdentities/{identityName}

Remove a registered identity from the vault

PUT

/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/certificates/{certificateName}

Upload or rotate a vault certificate

DELETE

/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/registeredIdentities/{identityName}

Remove a registered identity from the vault

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Azure AD OAuth 2.0 credential is stored once, encrypted, by your own Jentic One instance and a scoped bearer token is injected at execution time. The client secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'upload a recovery services vault certificate' or 'remove a registered identity from a vault', and Jentic returns the matching operation with its input schema so the agent supplies the vault name, certificate name, and PEM body without browsing the reference docs.

Time to first call

FAQs

Specific to using RecoveryServicesClient API through Jentic.

Why is there no official OpenAPI spec for RecoveryServicesClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call RecoveryServicesClient via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Recovery Services Vault Certificates API use?

The API runs through Azure Resource Manager and uses OAuth 2.0 bearer tokens issued by Azure Active Directory under the azure_auth scheme with the user_impersonation scope. Through Jentic, the AAD client secret is held in the encrypted vault and a short-lived access token is supplied at execute time so the secret never appears in the agent's context.

Can I rotate a vault certificate without downtime?

Yes. PUT .../vaults/{vaultName}/certificates/{certificateName} accepts a new certificate under a fresh name. Agents continue to authenticate with the old certificate while you re-register them against the new one, then the old certificate can be retired.

What are the rate limits for the Recovery Services Vault API?

Azure Resource Manager applies subscription-level read and write throttles (around 12,000 reads per hour and 1,200 writes per hour per region per subscription) and returns 429 with a Retry-After header when exceeded. Certificate uploads are typically infrequent so this rarely applies.

How do I upload a vault certificate through Jentic?

Search Jentic for 'upload recovery services vault certificate', load the schema for PUT .../vaults/{vaultName}/certificates/{certificateName}, then execute with subscriptionId, resourceGroupName, vaultName, certificateName, and a body containing the PEM certificate value. The pip install jentic Python SDK uses the async search, load, execute pattern.

Is the Recovery Services Vault Certificates API free?

There is no per-call charge for the management API itself; certificate and identity operations are part of the Recovery Services vault and are not separately metered. You pay for the vault and the storage consumed by backup data.

Can I limit what my agent is allowed to do with the Recovery Services Client API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and the subscription, resource group, vault name, and certificate or identity name all travel in the URL path, so a rule can pin the agent to a single Recovery Services vault. You choose the operations it may call, so you can allow it to upload or rotate a vault certificate while excluding the destructive delete of a registered identity unless you add that operation. The Azure AD credential is stored once and injected as a scoped bearer token at execution time, so the client secret never enters the agent's context.