How does OCNORA authenticate with Azure Import/Export?

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 Import/Export?

2 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Azure Import/Export operation I need is not listed?

Where Azure Import/Export 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 Import/Export?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Azure Import/Export 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.

Azure Import/Export

Microsoft AzureAPI keyConnection test available

Read Microsoft.ImportExport resources — jobs (Entra ID service principal).

OCNORA ships 2 typed Azure Import/Export 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.

Ask about Azure Import/Export Azure Import/Export API docs ↗

Before you connect Azure Import/Export

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 Import/Export

Operations, grouped by what they do to your data.

Read and search 2

A sample Azure Import/Export workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Azure Import/Export trigger is needed.
2
Get Resourceazure_importexport.get_resource
Read one Microsoft.ImportExport 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.

Operations 2