Azure Recovery Services
Read Microsoft.RecoveryServices resources — vaults (Entra ID service principal).
OCNORA ships 2 typed Azure Recovery Services operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Azure Recovery Services
- Authentication
- API key
- Credential
- {"tenant_id", "client_id", "client_secret"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Azure Recovery Services
Operations, grouped by what they do to your data.
Read and search 2
A sample Azure Recovery Services workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Azure Recovery Services trigger is needed.
- 2Get Resourceazure_recoveryservices.get_resourceRead one Microsoft.RecoveryServices resource by name.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Azure Recovery Services questions
- How does OCNORA authenticate with Azure Recovery Services?
- With a stored API key credential, shaped {"tenant_id", "client_id", "client_secret"}. A connection test can check it when you add it.
- What can I automate with Azure Recovery Services?
- 2 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Azure Recovery Services operation I need is not listed?
- Where Azure Recovery Services has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Azure Recovery Services?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Azure Recovery Services calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Azure Recovery Services workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.