Skip to main content

Azure node

An Azure node lets you interact with Azure Resource Manager services directly from your flow. Use it to retrieve data, create or modify resources, and perform actions across Azure services. The output of one node becomes the input for the next, allowing you to define a sequence of actions and operations.

Before you begin

Azure nodes use permissions from an Azure connection. Create an Azure connection with the connection wizard, or import one from existing Cloud Connect permissions, then select that connection when you configure the node.

Find an action

When adding an Azure node to a flow, select Azure as the provider and then find an action by searching or browsing within Azure services. You can also add a template node to insert a prebuilt group of actions into your flow.

Configure an action

Selecting an action node opens a side panel where you configure its parameters, connection, and test settings:

  • Parameters: Select the service and action, then enter any parameters required by the operation. A subscription ID is required only for operations scoped to a subscription, and a resource group only for operations scoped to a resource group. For field types and how to reference values from previous nodes, see Node parameters.

  • Connection: Select an Azure connection that uses the tenant and permissions required by the action. See Use connections.

  • Test: Test the node configuration before publishing the flow. See Test nodes.

CloudFlow automatically follows paginated Azure responses and waits for supported Azure long-running operations to finish before the flow proceeds.

Require approval

If an action should be approved before its execution, select Require approval for this action on the Parameters tab.

  • Notification provider: Choose whether to notify the approver through Slack or email. For Slack, you must have a shared Slack channel with DoiT.

  • Message (optional): Add the information the approver needs to make a decision. You can reference fields from previous nodes in the message. See Configure the Message field.

  • Reject approval after certain time (optional): Set how long the action waits for approval. If the approver takes no action before the time expires, the action is automatically rejected.

Limitations

Azure nodes support Azure Resource Manager APIs. Azure data-plane APIs that require a service-specific authentication audience are not supported.

See also