How does OCNORA authenticate with Azure Device Update?

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 Device Update?

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

What if the Azure Device Update operation I need is not listed?

Where Azure Device Update 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 Device Update?

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

How are Azure Device Update 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 Device Update

Microsoft AzureAPI keyConnection test available

Read Microsoft.DeviceUpdate resources — accounts (Entra ID service principal).

OCNORA ships 2 typed Azure Device Update 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 Device Update Azure Device Update API docs ↗

Before you connect Azure Device Update

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 Device Update

Operations, grouped by what they do to your data.

Read and search 2

A sample Azure Device Update workflow

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