Cloud / Storage / CI-CD · 45 pre-built actions
Azure integration with Nexus
Start governed work from Azure storage and event streams. Azure estates produce files, messages and directory events that should start real work. Nexus turns them into governed runs with rules, approval and a complete record.
Pre-built actions
What you can automate
45 pre-built Azure actions, grouped by what they work on.
45
PRE-BUILT ACTIONS
- 01Azure Blob Storage appears in the Nexus actions library and is also a trigger source.
- 02Trigger sources include Azure Event Hub, Azure Service Bus and Azure Active Directory.
Workflow
How it fits into a Nexus workflow
Azure Blob Storage, Azure Event Hub, Azure Service Bus and Azure Active Directory are listed trigger sources. Each can start a run with the event as input.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Use the HTTP Request node against Azure APIs for operations outside the pre-built action groups.
02
Use Rules + Code for parsing, validation and routing.
03
Require approval for actions that policy marks as consequential.
Examples
Workflow examples
Invoice intake from Blob Storage
A new file in Azure Blob Storage starts reconciliation against SAP and a SQL source.
Message-driven processing
Service Bus or Event Hub messages start validated runs with an execution record per item.
Directory event follow-up
An Azure Active Directory event starts a review or coordination workflow.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Multi-system workflows
Use cases that include Azure
AWS S3 or Azure Blob Storage, SAP, MSSQL or Oracle
Invoice intake and reconciliation with object storage, SAP and SQL
A file lands in object storage, SAP and a reconciliation database are checked, Rules + Code matches the result and exceptions go to a named reviewer.
ServiceNow, Okta, Microsoft 365 / Calendar
Governed employee access changes with ServiceNow, Okta and Microsoft 365
A ServiceNow request carries the context, an approver authorises the change, the identity step runs and the outcome returns to the ticket.
Industry use cases
Processes that use Azure
FAQ
Azure connector questions
- Which Azure sources can start a workflow?
- Azure Blob Storage, Event Hub, Service Bus and Azure Active Directory are listed trigger sources.
- Is Azure Blob Storage also an action?
- Yes. It appears in the actions library as well as the trigger list.
- Does this page list every Azure action?
- No. Nexus includes 45 Azure actions across Form Recognizer, Blob Storage, Virtual Machines and Azure Active Directory.
Related reading
Continue from here
- AWS connector
Equivalent storage and event sources on AWS.
- Microsoft 365 connector
Calendar actions and Teams triggers.
- Deployment
Where Nexus runs relative to your cloud estate.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Azure fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.