Azure Logic Apps is a powerful tool for automating workflows and integrating applications, data, and services. Before using Azure Logic Apps, it will be helpful to familiarize yourself with key terms that define how Logic Apps work. Here’s a simple breakdown to get you started:
1. Logic App
A Logic App is the Azure resource you create to build workflows. Depending on your needs, you can choose between two types:
Consumption Logic App: Supports a single workflow and runs in Azure’s global multi-tenant environment.
Standard Logic App: Supports multiple workflows, running in a single-tenant environment for more control and flexibility.
Why it matters: Choosing the right resource type impacts how your workflows are hosted, run, and billed.
2. Workflow
A Workflow is a sequence of steps or operations that accomplish a task, business process, or workload. Every workflow starts with a trigger, followed by one or more actions.
Example: Automating a process where receiving an email triggers a series of actions, like saving an attachment to a storage account.
3. Trigger
A Trigger is the starting point of any workflow. It defines the criteria or event that initiates the process.
Example Triggers: Receiving an email in your inbox. Detecting a new file in Azure Blob Storage.
4. Action
An Action is every step that follows the trigger in your workflow. Actions define what happens next, whether it’s sending a response, processing data, or connecting to a service.
Think of triggers as the “start” and actions as the “steps” that follow.
5. Built-in Connector
Built-in Connectors are operations integrated directly into the Azure Logic Apps runtime, enabling faster performance.
- Examples of built-in connectors: Recurrence trigger: Starts workflows on a schedule. Request trigger: Waits for an external call to initiate the workflow. Operations for Azure services like Blob Storage, Functions, and App Service.
Good to know: Built-in connectors usually don’t require additional connections or authentication.
6. Managed Connector
A Managed Connector is a Microsoft-hosted integration that acts as a bridge to external services like Office 365, Salesforce, or file servers.
- Examples: Start a workflow when a new email arrives in Office 365. Send data to Salesforce directly from your workflow.
Tip: Most managed connectors require you to create a connection and authenticate your credentials.
7. Integration Account
An Integration Account is a specialized Azure resource for defining and storing B2B artifacts, like trading partners, agreements, and schemas.
- Use Case: Workflows that handle Electronic Data Interchange (EDI) or Enterprise Application Integration (EAI) standards, such as X12 or AS2.
For Instance: Automating supply chain processes using predefined B2B standards like EDIFACT or RosettaNet.
Why Knowing These Terms Matters
Understanding these terms helps you design effective workflows and make better decisions when setting up Azure Logic Apps. For complex integrations, knowing the tools at your disposal ensures success. Azure Logic Apps simplifies complex processes, allowing you to focus on solving real problems while Azure handles the heavy lifting.