2026 Update: Unlock Significant Savings with Logic Apps

The landscape of enterprise integration and automation has shifted dramatically since Ben Stegink delivered his original Collab365 session in 2023. Back then, Azure Logic Apps was already a powerhouse for cost-saving automation, but the platform still heavily mirrored the citizen-developer experience of Power Automate.

Today, in March 2026, Azure Logic Apps has evolved into a tier-one Integration Platform as a Service (iPaaS). Microsoft has completely overhauled the underlying architecture, introducing single-tenant environments, advanced AI agentic workflows, and the new Flex Consumption plan.

As a senior consultant, I have prepared this exhaustive companion guide to bridge the gap between that foundational 2023 session and the realities of modern deployment. This report assumes you understand the core concepts Ben demonstrated.

My goal is to show you exactly how to execute those same six scenarios using the current 2026 toolsets, pricing models, and security best practices. We will explore the nuances of the redesigned Preview Designer, the integration of Microsoft Foundry, and the absolute necessity of transitioning to identity-based security models.

By mapping the original demonstrations to modern architectural standards, you will not only unlock the savings Ben promised but also future-proof your integration infrastructure against impending legacy retirements.

1. What's Changed Since This Session

Before diving into the technical execution, it is critical to baseline our understanding of the current Microsoft ecosystem. The tools and commercial models you relied upon in 2023 have been systematically upgraded or replaced.

Microsoft’s 2026 release wave has enforced stricter security postures, embedded generative AI into the developer experience, and fundamentally altered how cloud compute is billed. You can no longer rely on shared multitenant infrastructure for mission-critical enterprise workloads without incurring performance bottlenecks.

The table below provides a strict, factual summary of the core technological shifts. Review this carefully, as these changes dictate every architectural decision we will make in the subsequent demonstrations.

These structural changes mean that what used to be a "quick fix" in the Azure portal now requires deliberate software engineering practices. The introduction of the Standard plan brings Logic Apps out of the shadow of Power Automate and firmly into the realm of professional cloud development.

Furthermore, the July 2026 pricing updates to Microsoft 365 licensing have altered the cost-benefit analysis of user-based automation. As we proceed through the rebuilding of Ben's demos, keep these foundational shifts at the forefront of your strategy.

2. How to Build This Today

This section deconstructs the six original demonstrations from the 2023 session. For every scenario, I will first restate exactly what was built in the video.

Following that, I will provide exhaustive, step-by-step instructions for achieving the exact same business outcome using the March 2026 Azure portal and architectural standards. This is where the theoretical updates become practical implementation.

Demo 1: Creating a Basic Logic App for SharePoint List Approvals

The session showed you: Ben created a basic Consumption Logic App directly in the Azure portal designer to handle SharePoint list approvals. This was explicitly positioned as a direct, cost-saving replication of a standard Power Automate approval flow, utilizing standard Microsoft 365 connectors.

How to build that same thing today in March 2026:

The foundational concept remains the same, but the designer interface and creation methodology have been entirely modernized. You now have the option to generate the entire workflow architecture using natural language via Copilot.

First, you must navigate to the Azure portal and initiate the resource creation. Use the global search bar or follow the menu path: Azure Portal > Create a resource > Logic App.

You will immediately face a hosting decision. Under Select a hosting option, choose Consumption to create a direct, multitenant replica of the 2023 demo. Provide your subscription details, assign a resource group, and input a globally unique name for your application.

Click Review + Create, allow the validation to pass, and deploy the resource. Once the deployment succeeds, navigate to the resource overview. From your logic app's left-hand menu, under Development Tools, select Designer.

You are now looking at the 2026 Preview Designer. The most critical change to understand is that the designer now operates on a strict draft system. You are currently editing a safe draft version, not the live production workflow.

To begin the build, we will leverage the new generative AI capabilities. Locate the Copilot interface or the "Describe it to design it" prompt box. Type the following natural language command: "Trigger when a new SharePoint list item is created, then send an approval email and check the response".

The AI engine will automatically translate this description into a complete cloud flow. It will populate the designer with the correct trigger and subsequent actions, drastically reducing your manual configuration time.

Next, you must authenticate the generated SharePoint - When an item is created trigger. Select the action to open the configuration pane, which now appears at the bottom or via a consolidated toolbar, rather than a bulky side-panel. Point the trigger to your specific SharePoint site address and list name.

Now, configure the approval action. Ensure the AI has selected the Approvals - Start and wait for an approval action. Provide the necessary parameters: Approval type (e.g., Approve/Reject - First to respond), the dynamic title of the SharePoint item, and the assigned approver's email address.

The AI should have also generated a Control - Condition action immediately following the approval. Select this condition to configure its logic parameters. In the 2026 designer, you will use the dynamic content list (represented by a lightning bolt icon) to build this rule.

In the left parameter box, select the SelectedOption output from the previous approval action. Set the middle operator box to is equal to. Finally, type Approve into the right parameter box.

You now have two distinct branches: True and False. Inside the True branch, add a SharePoint - Update item action to change the list item's status to "Approved". Repeat this in the False branch, setting the status to "Rejected".

Once your logic is fully configured, you cannot simply walk away. Because you have been working in a draft state, your changes are not yet live.You must locate the vertical ellipsis menu (⋮) next to the top right toolbar and select Publish.

Only after publishing will your production workflow reflect the new SharePoint approval logic. You can easily toggle back to view the read-only published version if necessary.

Official Documentation:

Create a Consumption workflow in the Azure portal

The 2026 Logic Apps Designer Lifecycle

Workflows are now built in an isolated Draft state, often assisted by Copilot, before being committed to the live Production environment.

Demo 2: Mapping Power Automate Triggers and Actions

The session showed you: Ben demonstrated the direct parity between the two platforms by mapping common Power Automate triggers (like recurrence schedules) and actions directly to their Logic Apps equivalents. The goal was to prove that citizen developers could easily migrate their knowledge.

How to build that same thing today in March 2026: The connector ecosystem is now fully unified, boasting a shared library of over 1,400 connectors across Microsoft services, Azure infrastructure, and third-party APIs.However, the 2026 architecture introduces a critical distinction you must understand when mapping actions: the difference between Built-in and Managed operations.

When migrating a flow from Power Automate today, your first architectural decision is choosing between a Consumption plan and a Standard plan. This choice fundamentally alters how your mapped connectors will operate and bill.

Open your logic app designer and click the plus sign (+) to add a new action. You will notice the interface divides connectors into distinct tabs: Built-in and Managed. Understanding this division is the key to enterprise scalability.

Managed connectors are the exact 1:1 equivalents to the connectors you used in Power Automate. They are hosted and run using shared resources in the global Azure environment. Every time a managed connector fires, you incur a per-call micro-billing charge.

Built-in connectors, conversely, run natively on the single-tenant Azure Logic Apps runtime. They bypass the shared API infrastructure entirely. This provides significantly higher throughput, lower latency, and allows you to securely integrate with Virtual Networks (VNets).

If you are mapping a schedule-driven Power Automate trigger, such as the Recurrence trigger, you will find direct equivalents in both Consumption and Standard environments. Navigate to the Built-in tab, search for "Schedule", and select Recurrence.

Configure the interval and frequency parameters exactly as you would in Power Automate. The logic remains identical, but the underlying execution engine is vastly superior.

For event-driven architectures, map your Power Automate webhooks to the Logic Apps Request trigger. Specifically, select When an HTTP request is received. This allows you to orchestrate push-based events seamlessly.

When mapping outbound data operations, prioritize the Built-in operations whenever possible. For example, if your Power Automate flow queried a SQL database, map this to the Built-in SQL Server connector in a Standard logic app. This utilizes your dedicated compute resources and avoids standard managed connector fees.

It is crucial to note that certain Power Automate triggers do not map to Logic Apps. User-activity triggers, such as "Flow button for mobile", "For a selected row", or "Instant" UI flows, are designed exclusively for citizen developers. These have no direct equivalent in Logic Apps.

To migrate these user-driven flows, you must fundamentally redesign the architecture. You will need to replace the manual button trigger with an HTTP endpoint trigger, and have your frontend application make a secure API call to initiate the workflow.

Official Documentation:

Migrate from Power Automate to Azure Logic Apps

Demo 3: Configuring Standard Connectors

The session showed you: Ben demonstrated setting up standard connections to Microsoft 365 services, including Outlook, Teams, and OneDrive. This involved clicking the connector, opening a popup window, and authenticating with personal or service account credentials.

How to build that same thing today in March 2026:

Relying on username and password credentials for enterprise integrations is now considered a severe security anti-pattern. If you build workflows this way in 2026, they will inevitably break when mandatory organizational password rotations occur.

Today, you must configure these standard connectors using Azure Managed Identities. This approach ensures zero-trust compliance, eliminates credential management, and provides secure, seamless authentication across the Microsoft ecosystem.

Your first step is to establish the identity for your application. Navigate to your logic app resource menu in the Azure portal. Scroll down the left-hand navigation pane to find the Settings section.

Select Identity from the menu. You will see two tabs: System assigned and User assigned. For this deployment, we will use a System-assigned identity, which is tightly coupled to the lifecycle of this specific logic app.

Under the System assigned tab, toggle the Status switch to On. Click the Save button at the top of the pane. Azure will automatically provision a dedicated Microsoft Entra ID service principal for your workflow.

With the identity created, you must now grant it permission to access your target resources. This is done using Azure Role-Based Access Control (RBAC). Navigate to the resource you want the logic app to interact with—for example, a specific Azure Storage account or a SharePoint site.

Open the Access control (IAM) menu for that resource. Click Add role assignment. Select the appropriate role with the principle of least privilege in mind (e.g., "Storage Blob Data Contributor").

In the assignment wizard, under "Assign access to", select Managed identity. Search for and select the specific logic app identity you just generated. Complete the role assignment to solidify the security binding.

Now, you can safely configure the connector. Return to the Logic Apps designer under Development Tools. Add your desired Microsoft 365 or Azure action, such as the Office 365 Outlook - Send an email operation.

When the connection configuration pane appears, do not enter an email address and password. Instead, look for the authentication options dropdown menu within the connection settings.

Select Connect with Managed Identity from the dropdown list. The designer will instantly recognize the system-assigned identity you established in the previous steps.

Select your identity and click Create. The action is now securely authenticated. The workflow will use the underlying Entra ID token to communicate with the service, completely bypassing the need for embedded secrets or user credentials.

Official Documentation:

Authenticate access to Azure resources with managed identities

Demo 4: Run History Monitoring and Alerts

The session showed you: Ben walked through the basic run history pane to track execution successes and failures. He then demonstrated setting up rudimentary Azure Monitor alerts to prevent unexpected billing spikes based on simple execution counts.

How to build that same thing today in March 2026:

Cost management and operational monitoring have been deeply unified within the Azure ecosystem. Today, you do not just set passive email alerts; you configure highly granular metric tracking and automate your financial remediation using Action Groups.

To begin monitoring your operational metrics, navigate directly to your logic app's resource menu in the Azure portal.Scroll down to the Monitoring section and select Metrics.

This opens the Azure Monitor metrics explorer. Here, you can build custom charts to visualize exactly what is driving your daily costs. Click Add metric and explore the available telemetry specific to Logic Apps.

Select the Billable action executions metric to track exactly how many times your workflows are firing actions. Next, add a metric for Billing usage for storage consumption. This is critical, as saving large inputs and outputs in your run history directly impacts your storage costs.

To set a financial safety net, we must move beyond the logic app itself. Navigate to the global Azure portal search bar and type Cost Management + Billing. Open the service.

From the left-hand menu, follow the path: Cost Management > Budgets. Click the Add button to define a new spending threshold for your specific resource group or subscription. Set your desired budget limit and evaluation period.

Now, we will create the automated alert mechanism. Open the global search bar again and navigate to Azure Monitor. Select Alerts from the left-hand pane, and then select Action groups > Create.

Provide your subscription details, a resource group, and a clear name for your Action Group. Navigate to the Actions tab.This is where we define the automated response to a budget breach.

Under the Action type column, open the dropdown and select Logic App. A side pane will open, prompting you to configure the specific webhook connection.

Select your dedicated IT remediation logic app from the dropdown list. Ensure you set the Enable common alert schema toggle to Yes. This standardizes the JSON payload sent from Azure Monitor to your workflow.

Click Review + Create, then deploy the Action Group. Finally, return to your Budget configuration and attach this newly created Action Group.

When your spending exceeds the defined threshold, Azure Monitor will instantly fire your remediation logic app. This workflow can be programmed to alert finance teams via Microsoft Teams, create high-priority ServiceNow tickets, or even automatically disable non-critical logic app resources to halt runaway spending.

Official Documentation:

Plan and manage costs for Azure Logic Apps

Demo 5: Optimizing Workflows with Parallel Branches and Scopes

The session showed you: Ben demonstrated how to use parallel branches to execute independent tasks concurrently, drastically reducing overall workflow run time. He then showed how to wrap related actions into scopes to simplify error handling and lower execution bills.

How to build that same thing today in March 2026:

While the concepts of parallel execution and scoping remain vital, the 2026 Preview Designer has completely rearranged how you interact with these control flow elements. Furthermore, the modern approach to processing large datasets relies on native array debatching rather than manual branching loops.

First, open your desired workflow in the Azure portal designer. Ensure you are viewing the draft version, not the read-only published state.

To create a parallel branch, locate the two sequential actions between which you want the concurrency to occur. Hover your cursor directly over the connecting arrow connecting them.

A small plus sign (+) will appear. Click it, and select Add a parallel branch from the pop-up menu. The designer will split the flow visually.

Search for and select the specific operation you want to run in this new concurrent branch. You can continue adding actions beneath this new step to build out a complete parallel process.

Once your parallel tasks are complete, you must merge the branches back into a single execution path. This requires adding a "Join" action. Click the plus sign (+) beneath any of your parallel branches and select Add an action.

Search for a control action, such as a Compose or Condition, to serve as the joining node. Once added, select this join action to open its configuration pane.

Navigate to the Settings tab within the action pane. Locate the Run after section and open the Select actions list. You must manually select the final action from every parallel branch that feeds into this join.

The workflow will now intelligently wait for all selected branches to complete before executing the join action.

For grouping actions, you will use the Scope control. Search for and add a Scope action to your designer. In the 2026 interface, you can drag and drop existing actions directly inside the visual boundaries of the Scope block.

Scopes are essential for implementing try-catch error handling patterns. You can configure a subsequent action's "Run after" settings to only execute if the preceding Scope has a status of "Failed".

However, if you are building parallel branches simply to process a list of items quickly, you are doing it wrong. In 2026, you should utilize native trigger capabilities.

If your workflow trigger receives an array of data, select the trigger to open its settings. Locate and turn on the Split On setting.

This feature natively debatches the array at the trigger level. It automatically spins up separate, concurrent workflow instances for each individual item in the array. This completely eliminates the need for bulky "For each" loops, vastly improving processing speed and bypassing the execution billing meters associated with loop iterations.

Official Documentation:

Create parallel branches in Azure Logic Apps

Demo 6: Exporting and Importing Logic App Definitions

The session showed you: Ben demonstrated how to click the "Code View" button in the Azure portal, copy the raw JSON workflow definition, and paste it into a new logic app to facilitate team sharing and basic versioning.

How to build that same thing today in March 2026:

Manual copy-pasting of JSON definitions in the Azure portal is considered a severe operational risk and is a deprecated practice. In 2026, enterprise integration requires treating Logic Apps as proper application code. Microsoft provides dedicated, automated export tooling within Visual Studio Code to facilitate this.

Your objective is to transition from disparate, portal-managed Consumption workflows to a centralized, source-controlled Standard project.

First, you must ensure your local development environment is configured. Open Visual Studio Code and verify you have the Azure Logic Apps (Standard) extension installed (version 2.0.16 or higher is required for the export tooling).

Authenticate your Azure account within VS Code. Press the keyboard shortcut Shift + Alt + A to open the Azure window on the Activity Bar.

Look at the Workspace toolbar within the Azure pane. Locate and select the Export logic app icon. This initiates the automated extraction wizard.

The wizard will prompt you to select your target Azure subscription and the specific region where your legacy logic apps reside. Next, you will be presented with a list of your Consumption workflows.

Select the specific logic apps you wish to export. It is highly recommended to group applications that share resources, such as integration accounts or data maps, into the same export batch to maintain dependency links.

You will then reach the advanced options screen. This is a critical step. Ensure you check the box to Generate Infrastructure Template. This forces the tool to automatically generate the necessary Azure Resource Manager (ARM) templates for your target Standard logic app and all associated Azure-managed connections.

Choose a local folder directory on your machine. The export tool will now download your selected logic apps, convert their underlying syntax, and expand them into a complete Standard logic app project structure within VS Code.

Once the process completes, inspect your new project workspace. You will see individual folders for each workflow, containing their respective workflow.json files. You will also find an infrastructure folder containing the generated ARM templates.

Crucially, the export tool generates a README.md file.You must open and review this document immediately, as it outlines mandatory post-export remediation steps, such as manually reauthenticating certain connections that could not be cloned.

Your logic apps are now decoupled from the Azure portal UI. You can commit this entire folder structure directly to a Git repository, instantly enabling robust version control and team collaboration.

From here, you can deploy the project to higher environments using automated CI/CD pipelines managed by Azure DevOps or GitHub Actions.

Official Documentation:

(https://learn.microsoft.com/en-us/azure/logic-apps/export-from-consumption-to-standard-logic-app)

3. Licensing Quick Reference

Understanding the licensing requirements is critical before committing to an architectural path. The 2026 commercial models strictly separate user-driven automation platforms from enterprise system integration services.

Choosing the wrong platform can result in massive, unexpected licensing fees or severe operational bottlenecks.

The following table provides a strict, pricing-free reference of the licenses and plans required to execute the modernized approaches detailed in this report. This should be used to guide your procurement discussions.

When navigating these options, carefully evaluate your organizational scale. For small teams executing sporadic background tasks, the multitenant Consumption model remains highly effective. You only pay for the exact compute cycles you trigger.

However, if your workflows represent core business logic—handling high transaction volumes, requiring private network isolation, or demanding complex stateful operations—you must adopt the Standard plan. While the Standard plan requires a baseline investment for dedicated compute capacity, it rapidly becomes the more economical choice at scale, as you bypass the per-action micro-billing meters associated with legacy consumption models.