Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Cloud Infrastructure / Azure / SiteRecoveryManagementClient
SiteRecoveryManagementClient logo

Microsoft Azure SiteRecoveryManagementClient

Browse all Azure APIs
52
AI ReadinessFoundational (C-)52/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth2126 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Configure replication fabrics, protect VMs, run test and planned failovers, and manage recovery plans on an Azure Recovery Services vault.

Use for: Register a Hyper-V site as a replication fabric, Create a replication policy with a 24-hour retention window, Enroll a virtual machine for replication into Azure, Run a test failover on a recovery plan

Not supported: Does not run point-in-time backups, manage individual VM disks, or provision target VM resources outside the failover flow - use for Site Recovery replication, failover, and migration only.

Jentic publishes the only available OpenAPI specification for SiteRecoveryManagementClient, keeping it validated and agent-ready. The Azure Site Recovery API exposes the replication surface of the Microsoft.RecoveryServices resource provider so agents can configure fabrics, protection containers, replication policies, recovery plans, network mappings, and individual replicated items. It supports the full disaster-recovery and migration lifecycle - protecting VMs, running planned and unplanned failovers, executing test failovers, committing migrations, and managing alerts and events on a Recovery Services vault.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the SiteRecoveryManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SiteRecoveryManagementClient, 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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-siterecoverymanagementclient" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-siterecoverymanagementclient" | 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 SiteRecoveryManagementClient API.

Register replication fabrics under a Recovery Services vault

Create protection containers and the replication policies applied to them

Discover protectable items in a fabric and enroll them for replication

Run test failovers without affecting the source workload

Execute planned and unplanned failovers as part of a recovery plan

Commit a migration once a workload has cut over to the target

Configure replication alert settings and read replication events from the vault

Use Cases

Patterns agents use SiteRecoveryManagementClient API for, with concrete tasks.

★ Disaster Recovery Drills

Resilience teams run scheduled DR drills without disrupting production. The testMigrate and testFailover endpoints spin up isolated copies of replicated workloads in the target region, give the team time to validate the runbook, and the test cleanup endpoints tear the test environment down - all driven by an agent following a runbook rather than an analyst clicking through the portal.

Call testFailover on a recoveryPlan with the target network, verify the test items come up healthy, then call testFailoverCleanup

Workload Replication Onboarding

Migration teams enroll on-premises or cross-region VMs for replication into Azure. The replicationProtectionContainers/discoverProtectableItem endpoint scans a fabric for items that can be protected, and the replicationProtectedItems endpoints enroll the chosen item into a replication policy, so an agent can onboard a fleet of VMs in a single batched flow.

Call discoverProtectableItem on the protection container, then PUT replicationProtectedItems entries enrolling each discovered VM into the chosen policy

Migration Cutover Automation

Cloud migration teams cut over workloads from on-premises VMware or AWS into Azure as part of a planned migration window. The replicationMigrationItems migrate endpoint promotes the replicated item to the target region and the testMigrate endpoint validates the cutover plan first, so an agent can drive a sequence of migrations against the calendar.

Call testMigrate on each migrationItem to validate, then on the migration window call migrate to commit each item to the target

AI Agent DR Orchestration

An agent built on Jentic drives a DR orchestration runbook end-to-end. It discovers protectable items, applies the relevant replication policy, schedules the test failover, parses replicationEvents to confirm health, and pages an analyst with a structured summary - without anyone opening the Site Recovery blade.

Search Jentic for run azure site recovery test failover, load the schemas for testFailover and replicationEvents, and execute a test failover then summarise the events back to the user

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics

List replication fabrics in a vault

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics/{fabricName}

Register a replication fabric

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics/{fabricName}/replicationProtectionContainers/{protectionContainerName}/discoverProtectableItem

Discover items in a fabric that can be protected

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics/{fabricName}/replicationProtectionContainers/{protectionContainerName}/replicationMigrationItems/{migrationItemName}/migrate

Commit a migration to the target region

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics/{fabricName}/replicationProtectionContainers/{protectionContainerName}/replicationMigrationItems/{migrationItemName}/testMigrate

Run a test migration without committing

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationEvents

List replication events for the vault

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics

List replication fabrics in a vault

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics/{fabricName}

Register a replication fabric

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics/{fabricName}/replicationProtectionContainers/{protectionContainerName}/discoverProtectableItem

Discover items in a fabric that can be protected

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics/{fabricName}/replicationProtectionContainers/{protectionContainerName}/replicationMigrationItems/{migrationItemName}/migrate

Commit a migration to the target region

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics/{fabricName}/replicationProtectionContainers/{protectionContainerName}/replicationMigrationItems/{migrationItemName}/testMigrate

Run a test migration without committing

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationEvents

List replication events for the vault

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

S

SiteRecoveryManagementClient

- Foundational (C-)
52/100
65
Foundational Compliance
56
Developer Experience & Jentic Compatibility
36
AI-Readiness & Agent Experience
76
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
65

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4
61%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

36

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
86%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

76

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1
76%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Microsoft.RecoveryServices replication surface by hand means registering an Azure AD app, running the OAuth2 token exchange, and polling the asyncOperation URLs that its predominantly long-running failover and migration operations return. Through Jentic you install once, import Site Recovery Management from the API Directory, store the Azure AD service principal credential once, and your agent calls it.

Permission scoping

Site Recovery puts the subscription, resource group, and Recovery Services vault in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/...), so a rule can pin your agent to one vault and its fabrics and protected items. You choose the operations it may call, so a failover or a migration commit are not included unless you add them.

Credential isolation

Your Azure AD service principal credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, which matters when a DR runbook runs from a chat-driven workflow.

Intent-based discovery

Agents search Jentic by intent such as 'run an Azure Site Recovery test failover' or 'enroll a VM for replication', and Jentic returns the matching Microsoft.RecoveryServices replication operation with its input schema so the agent calls the right endpoint without reading the ARM reference.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure Recovery Services Backup

→

Backup and restore on the same Recovery Services vault

Use Recovery Services Backup for point-in-time backup; use Site Recovery for replication and failover

Complementary

Recovery Services Vault Management

→

Manages the parent Recovery Services vault that hosts ASR and backup

Use Recovery Services to provision the vault before configuring Site Recovery on it

Alternative

Azure Migrate

→

Higher-level migration assessment and orchestration product built on top of Site Recovery

Use Azure Migrate for assessment-driven migrations; use Site Recovery directly for fine-grained replication control

FAQs

Specific to using SiteRecoveryManagementClient API through Jentic.

Why is there no official OpenAPI spec for SiteRecoveryManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call SiteRecoveryManagementClient 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 Site Recovery API use?

It uses Azure AD OAuth 2.0 with the implicit flow against https://login.microsoftonline.com/common/oauth2/authorize and the user_impersonation scope. When called through Jentic, your AAD service principal credentials live in your Jentic One instance and the agent receives only a short-lived bearer token scoped to the Recovery Services vault.

Can I run a test failover with this API?

Yes. POST to /.../replicationProtectionContainers/{protectionContainerName}/replicationMigrationItems/{migrationItemName}/testMigrate or the equivalent testFailover endpoint on a recovery plan. The test runs against an isolated network and the matching cleanup endpoint tears it down without affecting production.

How do I migrate a workload to Azure with this API?

Discover the protectable item via /.../discoverProtectableItem, enroll it as a replicationMigrationItem with a policy, validate with testMigrate, then POST migrate on the migrationItem to commit the cutover. Each step is async and returns an asyncOperation URL to poll.

What are the rate limits for this API?

Azure Resource Manager throttles around 12,000 reads and 1,200 writes per hour per principal at subscription scope, surfaced via x-ms-ratelimit-remaining-subscription-reads and x-ms-ratelimit-remaining-subscription-writes headers. Site Recovery operations are predominantly async with poll-based completion via asyncOperation URLs.

How do I orchestrate a DR drill through Jentic?

Search Jentic for run azure site recovery test failover, load the schemas for the testFailover and testFailoverCleanup operations on the recovery plan, and execute them in sequence around the drill window. The Jentic Python SDK ships the search, load, execute pattern after pip install jentic.

Does this API also handle backup?

No - backup lives under the related Recovery Services Backup API surface. Site Recovery handles replication and failover; backup handles point-in-time backup and restore. Both share the same Recovery Services vault as the parent resource.

GET STARTED

Start building with SiteRecoveryManagementClient API

Explore with Jentic One
View OpenAPI Document