Using Logic Apps (Consumption)? Tell us what’s keeping you there
We’re inviting Logic Apps Consumption customers to share feedback on what’s influencing their decision to stay on Consumption and what might be holding them back from exploring Logic Apps Standard. Your input will help shape future improvements.Announcement: General Availability of Logic Apps Hybrid Deployment Model
We are thrilled to announce the General Availability of the Logic Apps Hybrid Deployment Model, a groundbreaking feature that offers unparalleled flexibility and control to our customers. This innovative deployment model allows you to run Logic Apps workloads on customer-managed infrastructure, providing you with the option to host your integration solutions on-premises, in a private cloud, or even in a third-party public cloud. With the Logic Apps Hybrid Deployment Model, you can tailor your integration solutions to meet your specific needs, whether it's for regulatory compliance, data privacy, or network restrictions. This model ensures that you have the freedom to choose the best environment for your workflows, while still leveraging the powerful capabilities of Azure Logic Apps. The Hybrid Deployment Model supports a semi-connected architecture, offering local processing of workflows, local storage, and local network access. This means that the data processed by the workflows remains in your local SQL Server, and you have the ability to connect to local networks. Additionally, the built-in connectors will execute in your local compute, giving you access to local data sources and higher throughput. Since we launched the public preview, we have received an overwhelmingly positive response from customers across various industries. Many customers, including those looking to migrate from BizTalk Server, have expressed interest in this offering due to its ability to co-locate integration platforms near key lines of business systems, avoiding dependencies on public internet to process transactions. Journey of the Hybrid Deployment Model Feature At the Integrate 2024 event, we announced the early access preview of the Hybrid Deployment model for Logic Apps Standard. This initial phase allowed interested parties to nominate themselves for early access and provided valuable feedback on the model's functionality and benefits. Following the private preview, we launched the public preview, which empowered our customers with additional flexibility and control. This phase allowed customers to build and deploy workflows on customer-managed infrastructure, offering the option to run Logic Apps on-premises, in a private cloud, or in a third-party public cloud. The public preview also introduced the semi-connected architecture, enabling local processing of workflows and access to local data sources. In October 2024, we refreshed the public preview and received an overwhelmingly positive response from customers across various industries. This feedback highlighted the model's ability to meet specific use cases, such as migrating from BizTalk Server and co-locating integration platforms near key lines of business systems. The public preview refresh also emphasized the model's alignment with our promise of providing customers with more options to meet their business needs. We are excited to see how our customers will leverage the Logic Apps Hybrid Deployment Model to meet their business needs and drive innovation. Thank you for your continued support and feedback. New features in the GA release: Open Telemetry support: Open telemetry is a vendor-neutral open-source Observability framework for instrumenting, generating, collecting, and exporting telemetry data. The support for Open Telemetry in Hybrid deployment model ensures the seamless logging in the semi-connected scenarios and provides the ability to choose any observability platform as a telemetry endpoint. More details here. To set up Open Telemetry capability from Azure portal, follow these steps: Open the host.json in the root directory of SMB file share path configured in your logic app. In the host.json file, at the root level, add the following telemetryMode setting with the OpenTelemetry value, for example: { "version": "2.0", "extensionBundle": { "id": "Microsoft.Azure.Functions.ExtensionBundle.Workflows", "version": "[1.*, 2.0.0)" }, "telemetryMode": "OpenTelemetry" } When you enable Open Telemetry in the host.json file, your logic app exports telemetry based on the Open Telemetry-supported app settings that you define in the environment. Add below app settings from portal by navigating to Containers-->Environment variables-->edit and deploy. App setting Description OTEL_EXPORTER_OTLP_ENDPOINT The online transaction processing (OTLP) exporter endpoint URL for where to send the telemetry data. OTEL_EXPORTER_OTLP_HEADERS (optional) A list of headers to apply to all outgoing data. Commonly used to pass authentication keys or tokens to your observability backend. If your Open Telemetry endpoint requires other Open Telemetry related settings, include these settings in the app settings too. Support for Zip deployment through VSCode: The support for Zip deployment in VSCode deployment has enhanced the deployment experience with more reliability. This feature uses Azure Entra authentication for deployment, hence the VSCode machine doesn’t require to have permissions on the SMB share and the user need not to provide SMB credentials in subsequent deployments. To use Zip deployment, follow below steps: create an app registration. In the VSCode deployment, provide Client ID, Object ID and Client secret values. If there are any concerns with creating App registration, you can continue to use SMB deployment option by choosing "Use SMBDeployment For Hybrid" in the Extensions configuration of VSCode If you would like to use zip deployment in an existing Logic App, you will need to manually add the app settings as indicated here. The Zip deployment APIs can be used in CI/CD pipelines as well for DevOps deployment. We will be publishing another blog with detailed steps on the DevOps process. Support for more regions: We are pleased to announce the expansion of our hybrid deployment support to additional regions, in response to valuable customer feedback. This enhancement aims to better meet the diverse geographic and operational requirements of your businesses. The hybrid deployment is now available in the following regions: Central US, East Asia, East US, North Central US, Southeast Asia, Sweden Central, UK South, West Europe, and West US. Logic Apps Rules Engine Support on Linux containers: In this release, we have added support for Azure Logic Apps Rules Engine to run on Linux containers which enables customers to use the Rules Engine capabilities in Hybrid Logic Apps. Improvements for Effective Scaling and Performance: We have introduced few improvements in the runtime storage and the scaling behaviour aimed at improving the performance and achieving effective scaling. Please refer to the following articles: Scaling mechanism in hybrid deployment model for Azure Logic Apps Standard | Microsoft Community Hub Hybrid deployment model for Logic Apps- Performance Analysis and Optimization recommendations | Microsoft Community Hub Diagnostic tool: To assist with troubleshooting the environment configuration issues, we have created a troubleshooting tool, which will help you review the health of all the components of the hybrid deployment and provide insights. You can find the script in our GitHub repository. Select the troubleshoot.ps1 file and copy it to a folder and run the script using PowerShell. This script should be run where you have access to kubectl. References: Create Standard logic app workflows for hybrid deployment - Azure Logic Apps | Microsoft Learn Set up your own infrastructure for Standard logic app workflows - Azure Logic Apps | Microsoft Learn Set up and view enhanced telemetry for Standard workflows - Azure Logic Apps | Microsoft LearnAnnouncing General Availability: Azure Logic Apps Standard Automated Test Framework
We’re excited to announce the General Availability (GA) of the Azure Logic Apps Standard Automated Test Framework - a major step forward in enabling developers to build, test, and maintain enterprise-grade workflows with confidence and agility. Automated testing has become a cornerstone of modern development practices, and Logic Apps Standard now offers a robust framework to help you create unit tests for both workflow definitions and workflow runs directly within Visual Studio Code. This framework empowers teams to validate logic, simulate external dependencies, and ensure workflows behave as expected—before they’re deployed to production. Since the public preview, we’ve listened to your feedback and continued to enhance the framework. With GA, we’re introducing several key improvements that make testing even more powerful and flexible. What’s New in GA Support for More Mocked Actions You can now mock a broader range of built-in and managed connector actions, making it easier to isolate your workflow logic from external systems. With this release we unlocked support to mock actions for the following actions, unavailable during public preview: Call workflow in this logic app Execute inline code (JavaScript, C#, PowerShell Call Functions (Azure functions, local functions) XML Operations (transform, parse with schema) Liquid Operations (JSON to JSON, JSON to text, XML to JSON, XML to text) Data Mapper operations This enhancement allows for more comprehensive and reliable unit tests, providing more control to your workflow tests, especially in complex integration scenarios. Access to Workflow Settings for Assertions The framework now allows you to access and assert against workflow settings, such as parameters and app setting values. This means you can validate not just the behavior of your workflow, but also the environment in which it runs—ensuring logic consistency across different environments. Inline Script Actions Support Inline Code actions are now fully supported in test scenarios. JavaScript actions are now executed as part of the test workflow execution, since they are part of workflow logic. This improvement allows you to validate the logic of those scripts at part of your workflow scenarios. We are working on bringing similar support for C# and PowerShell scripts. Learn More To get started with the Azure Logic Apps Standard Automated Test Framework, check out the following Microsoft Learn articles: Create unit tests for workflow definitions in Visual Studio Code Create unit tests for workflow runs in Visual Studio Code Logic Apps Standard Automated Test SDK. Let us know what you think and stay tuned for more enhancements coming soon!Announcing General Availability: Azure Logic Apps Standard Custom Code with .NET 8
We’re excited to announce the General Availability (GA) of Custom Code support in Azure Logic Apps Standard with .NET 8. This release marks a significant step forward in enabling developers to build more powerful, flexible, and maintainable integration workflows using familiar .NET tools and practices. With this capability, developers can now embed custom .NET 8 code directly within their Logic Apps Standard workflows. This unlocks advanced logic scenarios, promotes code reuse, and allows seamless integration with existing .NET libraries and services—making it easier than ever to build enterprise-grade solutions on Azure. What’s New in GA This GA release introduces several key enhancements that improve the development experience and expand the capabilities of custom code in Logic Apps: Bring Your Own Packages Developers can now include and manage their own NuGet packages within custom code projects without having to resolve conflicts with the dependencies used by the language worker host. The update includes the ability to load the assembly dependencies of the custom code project into a separate Assembly context allowing you to bring any NET8 compatible dependent assembly versions that your project need. There are only three exceptions to this rule: Microsoft.Extensions.Logging.Abstractions Microsoft.Extensions.DependencyInjection.Abstractions Microsoft.Azure.Functions.Extensions.Workflows.Abstractions Dependency Injection Native Support Custom code now supports native Dependency Injection (DI), enabling better separation of concerns and more testable, maintainable code. This aligns with modern .NET development patterns and simplifies service management within your custom logic. To enable Dependency Injection, developers will need to provide a StartupConfiguration class, defining the list of dependencies: public class StartupConfiguration : IConfigureStartup { /// <summary> /// Configures services for the Azure Functions application. /// </summary> /// <param name="services">The service collection to configure.</param> public void Configure(IServiceCollection services) { // Register the routing service with dependency injection services.AddSingleton<IRoutingService, OrderRoutingService>(); services.AddSingleton<IDiscountService, DiscountService>(); } } You will also need to initialize those register those services during your custom code class constructor: public class MySampleFunction { private readonly ILogger<MySampleFunction> logger; private readonly IRoutingService routingService; private readonly IDiscountService discountService; public MySampleFunction(ILoggerFactory loggerFactory, IRoutingService routingService, IDiscountService discountService) { this.logger = loggerFactory.CreateLogger<MySampleFunction>(); this.routingService = routingService; this.discountService = discountService; } // your function logic here } Improved Authoring Experience The development experience has been significantly enhanced with improved tooling and templates. Whether you're using Visual Studio or Visual Studio Code, you’ll benefit from streamlined scaffolding, local debugging, and deployment workflows that make building and managing custom code faster and more intuitive. The following user experience improvements were added: Local functions metadata are kept between VS Code sessions, so you don't receive validation errors when editing workflows that depend on the local functions. Projects are also built when designer starts, so you don't have to manually update references. New context menu gestures, allowing you to create new local functions or build your functions project directly from the explorer area Unified debugging experience, making it easer for you to debug. We have now a single task for debugging custom code and logic apps, which makes starting a new debug session as easy as pressing F5. Learn More To get started with custom code in Azure Logic Apps Standard, visit the official Microsoft Learn documentation: Create and run custom code in Azure Logic Apps Standard You can also find example code for Dependency injection wsilveiranz/CustomCode-Dependency-InjectionConfigure SQL Storage for Standard Logic Apps
Logic Apps uses Azure Storage by default to hold workflows, states and runtime data. However, now in preview, you can use SQL storage instead of Azure Storage for your logic apps workflow related transactions. Note that Azure Storage is still required and SQL is only an alternative for workflow transactions. Why Use SQL Storage? Benefit Description Portability SQL runs on VMs, PaaS, and containers—ideal for hybrid and multi-cloud setups. Control Fine-tune throughput and performance; predictable pricing based on usage. Reuse Assets Leverage SSMS, CLI, SDKs, and Azure Hybrid Benefits. Compliance Enterprise-grade backup, restore, failover, and redundancy options. When to Use SQL Storage Scenario Recommended Storage Need control over performance SQL On-premises workflows (Azure Arc) SQL Predictable cost modeling SQL Prefer SQL ecosystem SQL Reuse existing SQL environments SQL General-purpose or default use cases Azure Storage Configuration via Azure Portal Prerequisites: Azure Subscription Azure SQL Server and Database SQL Setup: Navigate to Security > Networking > Public Access > Exceptions. Enable “Allow Azure services…” in SQL Server settings. Ensure “Support only Microsoft Entra authentication” is unchecked. Note: this can be done during SQL server creation from the Networking tab. Logic App Setup: Create a new Logic App (Standard). In the Storage tab, select SQL from the dropdown. Add your SQL connection string (replace {yourpassword} as needed). Verification Tip: After deployment, check the environment variable Workflows.Sql.ConnectionString to confirm the SQL DB name is reflected. Known Issues & Fixes Issue Fix Could not find a part of the path 'C:\home\site\wwwroot' Re-enable SQL authentication and verify path settings. SQL login error due to AAD-only authentication Disable AAD-only mode and enable SQL authentication. Final Thoughts SQL as a storage provider for Logic Apps opens up new possibilities for hybrid deployments, performance tuning, and cost predictability. While still in preview, it’s a promising option for teams already invested in the SQL ecosystem. If you are already using this as an alternative or think this would be useful, let us know in the comments below. Resources https://learn.microsoft.com/en-us/azure/logic-apps/set-up-sql-db-storage-single-tenant-standard-workflows Pricing - Logic Apps | Microsoft AzureExtending Logic Apps App Insight integration with Azure Workbooks
With the improvements we made in Logic Apps integration with App insight, we streamlined how various types of Logic Apps associated events get emitted and ingested into Application Insights. This change also improved how they get mapped to existing application insight concepts such as requests, dependencies, and exceptions. Azure workbooks provides a flexible canvas for data analysis and the creation of rich visual reports within azure portal. Azure workbooks also replace Azure monitoring solutions which we had been using with Consumption Logic Apps to build visual dashboards on top of Log Analytics data from consumption Logic Apps. In this blog post we are going to show how we can use Azure workbooks together with recent improvements to application insight integration to build similar rich and interactive dashboards for standard Logic Apps.Recent Logic Apps Failures with Defender ATP Steps – "TimeGenerated" No Longer Recognized
Hi everyone, I’ve recently encountered an issue with Logic Apps failing on Defender ATP steps. Requests containing the TimeGenerated parameter no longer work—the column seems to be unrecognized. My code hasn’t changed at all, and the same queries run successfully in Defender 365’s Advanced Hunting. For example, this basic KQL query: DeviceLogonEvents | where TimeGenerated >= ago(30d) | where LogonType != "Local" | where DeviceName !contains ".fr" | where DeviceName !contains "shared-" | where DeviceName !contains "gdc-" | where DeviceName !contains "mon-" | distinct DeviceName Now throws the error: Failed to resolve column or scalar expression named 'TimeGenerated'. Fix semantic errors in your query. Removing TimeGenerated makes the query work again, but this isn’t a viable solution. Notably, the identical query still functions in Defender 365’s Advanced Hunting UI. This issue started affecting a Logic App that runs weekly—it worked on May 11th but failed on May 18th. Questions: Has there been a recent schema change or deprecation of TimeGenerated in Defender ATP's KQL for Logic Apps? Is there an alternative column or syntax we should use now? Are others experiencing this? Any insights or workarounds would be greatly appreciated!Logic Apps Aviators Newsletter - June 25
In this issue: Ace Aviator of the Month News from our product group News from our community Ace Aviator of the Month April’s Ace Aviator: Andrew Wilson What's your role and title? What are your responsibilities? I am the Chief Consultancy Officer at Black Marble, a multi-award-winning software company with a big focus on the Microsoft stack. I work with a talented team of consultants to help our customers get the most out of Azure. My role is all about enabling organisations to modernise, integrate, and optimise their systems, always with an eye on DevOps best practices. I’m involved across most of the software development lifecycle, but my focus tends to lean toward consultations, gathering requirements, and architecting solutions that solve real-world problems. I work across a range of areas including application modernisation, BizTalk to Azure Integration Services (AIS) migrations, system integrations, and cloud optimisation. Over time, I've developed a strong focus on Azure, especially around AIS. In short, I help bridge the gap between technical possibilities and business needs, making sure the solutions we design are both practical and future-ready. Can you give us some insights into your day-to-day activities and what a typical day in your role looks like? No two days are quite the same which keeps things interesting! I usually kick things off with a quick plan for the day (and a bit of reshuffling for the week ahead) to make sure we’re focused on what matters most for both customers and the team. My time is a mix of customer-facing work, sales conversations with new prospects, and supporting existing clients, whether that’s through solution design, quick fixes, or hands-on consultancy. I’m often reviewing or writing proposals and architectures, and jumping in to support the team on delivery when needed. There’s always some active learning in the mix too, reading, experimenting, or spinning up quick ideas to explore better ways of doing things. We don’t work in silos at Black Marble, so I’ll often jump in where I can add value, whether or not I’m directly on the project. It’s a real team effort, and that collaboration is a big part of what makes the role so rewarding. What motivates and inspires you to be an active member of the Aviators/Microsoft community? I’ve always enjoyed the challenge of bringing systems and applications together, there’s something really satisfying about seeing everything click into place and knowing it’s driving real business value What makes the Aviators and wider Microsoft community special is that everyone shares that same excitement. It’s a group of people who genuinely care about solving problems, pushing technology forward, and learning from one another. Being part of that kind of community is motivating in itself, we’re all collaborating, sharing ideas, and helping shape a better, more connected future. It’s hard not to be inspired when you’re surrounded by people who are just as passionate about the work as you are. Looking back, what advice do you wish you had been given earlier that you'd now share with those looking to get into STEM/technology? Stay curious, always ask “why,” and don’t be afraid to get things wrong, because you will, and that’s how you learn. Some of the best breakthroughs come after a few missteps (and maybe a bit of head-scratching). It’s easy to look around and feel like others have it all figured out, don’t let that discourage you. Everyone’s journey is different, and what looks effortless on the outside often has a lot of trial and error behind it. One of the best things about STEM is its diversity, there are so many different roles, paths, and people in this space. Whether you’re hands-on with code, designing systems, or solving data challenges, there’s a place for you. It’s not a one-size-fits-all, and that’s what makes it exciting. Most importantly, share what you learn. Even if something’s been “done,” your take on it might be exactly what someone else needs to see to help them get started. And yes, imposter syndrome is real, but don’t let it silence you. You belong here just as much as anyone else. What has helped you grow professionally? A big part of my growth has come from simply committing to continuous learning, whether that’s diving into new tech, attending conferences like Integrate, or being part of user groups where ideas (and challenges) get shared openly. I’ve also learned to say yes to opportunities, even when they’ve felt a bit daunting at first. Pushing through the unknown, especially with the support of a great team and community, has led to some of my most rewarding experiences. And finally, I try to approach everything with the mindset that I’m someone others can count on. That sense of responsibility has helped me stay focused, accountable, and constantly improving. If you had a magic wand that could create a feature in Logic Apps, what would it be and why? Wow, what an exciting question! If I had a magic wand, the first thing I’d add is having the option to throw exceptions that can be caught by try-catch scope blocks, this would bring much-needed clarity and flexibility to error handling. It’s a feature that would really help build more resilient and maintainable solutions. Then, the ability to break or continue loops, sometimes you need that fine-tuned control to keep your workflows running smoothly without extra workarounds. And lastly, full GA support for unit and integration testing, because testing is the backbone of reliable software, and having that baked in would save so much time and stress down the line. News from our product group Logic Apps Live May 2025 Missed Logic Apps Live in May? You can watch it here. We focused on the Logic Apps big announcements from Microsoft Build 2025. There are a lot of great things to check! Announcing agent loop: Build AI Agents in Azure Logic Apps The era of intelligent business processes has arrived! Today, we are excited to announce agent loop, a groundbreaking new capability in Azure Logic Apps to build AI agents into your enterprise workflows. With agent loop, you can embed advanced AI decision-making directly into your processes – enabling your apps and automation to not just follow predefined steps, but to reason, adapt, and act autonomously towards goals. Agent Loop Demos We announced the public preview of agent loop at Build 2025. Agent Loop is a new feature in Logic Apps to build AI Agents for use cases that span across industry domains and patterns. In this article, share with you use cases implemented in Logic Apps using agent loop and other features. Announcement: Azure Logic Apps Document Indexer in Azure Cosmos DB We’re excited to announce the public preview of Azure Logic Apps as a document indexer for Azure Cosmos DB!00 With this release, you can now use Logic Apps connectors and templates to ingest documents directly into Cosmos DB’s vector store—powering AI workloads like Retrieval-Augmented Generation (RAG) with ease. Announcement: Logic Apps connectors in Azure AI Search for Integrated Vectorization We’re excited to announce that Azure Logic Apps connectors are now supported within AI Search as data sources for ingestion into Azure AI Search vector stores. This unlocks the ability to ingest unstructured documents from a variety of systems—including SharePoint, Amazon S3, Dropbox and many more —into your vector index using a low-code experience. Announcement: Power your Agents in Azure AI Foundry Agent Service with Azure Logic Apps We’re excited to announce the Public Preview of two major integrations that bring the power of Azure Logic Apps to AI Agents in Foundry – Logic Apps as Tools and AI Agent Service Connector. Learn more on our announcement post! Codeful Workflows: A New Authoring Model for Logic Apps Standard Codeful Workflows expand the authoring and execution models of a Logic Apps Standard, offering developers the ability to implement, test and run workflows using an imperative programming model both locally and in the cloud. Announcing the General Availability of the Azure Logic Apps Rules Engine we are announcing the General Availability of our Azure Logic Apps Rules Engine. A deterministic rules engine runtime based on the RETE algorithm that allows in-memory execution, prioritization, and reevaluation of business rules in Azure Logic Apps. Integration Environment Update – Unified experience to create and manage alerts We’re excited to announce the next milestone in our journey to simplify monitoring across Azure Integration Services. As a follow-up to our earlier preview release on unified monitoring and dashboards, we’re now making it easier than ever to configure alerts for your integration applications. Automate Invoice data extraction with Logic Apps and Document Intelligence This blog post demonstrates how you can use Azure Logic Apps, the new Analyze Document Details action, and Azure OpenAI to automatically convert invoice images into structured data and store them in Azure Cosmos DB. Log Ingestion to Azure Log Analytics Workspace with Logic App Standard Discover how to send logs to Azure Log Analytics Workspace using Logic App Standard for VNet integration. Learn about shared key authentication and HTTP action configuration for seamless log ingestion. Generating Webhook Action Callback URL with Primary or secondary Access Key Learn how to manage Webhook action callback URLs in Azure Logic Apps when regenerating access keys. Discover how to use the accessKeyType property to ensure seamless workflow execution and maintain security. Announcing the Public Preview of the Applications feature in Azure API management Discover the new Applications feature in Azure API Management, enabling OAuth-based access to APIs and products. Streamline secure API access with built-in OAuth 2.0 application-based authorization. GA: Inbound private endpoint for Standard v2 tier of Azure API Management Today, we are excited to announce the general availability of inbound private endpoint for Azure API management Standard v2 tier. Securely connect clients in your private network to the API Management gateway using Azure Private Link. Announcing the open Public Preview of the Premium v2 tier of Azure API Management Announcing the public preview of Azure API Management Premium v2 tier. Experience superior capacity, highest entity limits, and unlimited calls with enhanced security and networking flexibility. Announcing Federated Logging in Azure API Management Announcing federated logging in Azure API Management. Gain centralized monitoring for platform teams and autonomy for API teams, streamlining API management with robust security and operational visibility. Introducing Workspace Gateway Metrics and Autoscale in Azure API Management Introducing workspace gateway metrics and autoscale in Azure API Management. Efficiently monitor and scale your gateway infrastructure with real-time insights and automated scaling for enhanced reliability and cost efficiency. Introducing Model Logging, Import from AI Foundry, and extended model support in AI Gateway Introducing workspace gateway metrics and autoscale in Azure API Management. Efficiently monitor and scale your gateway infrastructure with real-time insights and automated scaling for enhanced reliability and cost efficiency. Expose REST APIs as MCP servers with Azure API Management and API Center (now in preview) Discover how to expose REST APIs as MCP servers with Azure API Management and API Center, now in preview. Enhance AI integration with secure, observable, and scalable API operations. Now in Public Preview: System events for data-plane in API Management gateway Announcing the public preview of new data-plane system events in Azure Event Grid for the Azure API Management managed gateway. Gain near-real-time visibility into critical operations, automate responses, and prevent disruptions. News from our community Agentic AI – A Potential Black Swan Moment in System Integration Video by Ahmed Bayoumy Discover how Agentic Logic Apps are revolutionizing system integration with AI-driven workflows. Learn how this innovative approach transforms business processes by understanding goals, deciding actions, and using predefined tools for smart orchestration. Microsoft Build: Behind the Scenes with Agent Loop Workflow A New Phase in AI Evolution Video by Ahmed Bayoumy Explore how Agent Loop brings “human in the loop” control to enterprise workflows, on this video by Ahmed, sharing insights directly from Microsoft Build 2025, in a chat with Kent Weare and Divya Swarnkar. Microsoft Build 2025: Azure Logic Apps is Now Your AI Agent Superpower! Post by Sagar Sharma Discover how Azure Logic Apps is transforming AI agent development with new capabilities unveiled at Microsoft Build 2025. Learn about Agent Loop, AI Foundry integration, Document Indexer, and more for intelligent, adaptive workflows. Everyone is talking about AI Agents — Here’s how to actually build one that works Post by Mateusz Partyka Learn how to build effective AI agents with practical strategies and insights. Discover tips on choosing the right tech stack, prototyping fast, managing model costs, and prompt engineering for optimal results. Agent Loop | Azure Logic Apps Just Got Smarter Post by Andrew Wilson Discover Agent Loop in Azure Logic Apps – now in preview - a revolutionary AI-powered integration feature. Enhance workflows with advanced decision-making, context retention, and adaptive actions for smarter automation. Step-by-Step Guide to Azure Logic Apps Agent Loop Post by Stephen W. Thomas Dive into the step-by-step guide for creating AI Agents with Azure Logic Apps Agent Loop – now in preview. Learn to leverage 1300+ connectors, set up OpenAI models, and build intelligent workflows with no-code integration. You can also follow Stephen’s video tutorial Confessions of a Control Freak: How I Learned to Love Low Code (with Logic Apps) Post by Peter Mugisha Discover how a self-confessed control freak learned to embrace low-code development with Azure Logic Apps. From skepticism to advocacy, explore the journey of efficient integration and streamlined workflows. Logic Apps Standard vs. Large Files: Common Hurdles and How to Beat Them Post by Şahin Özdemir Learn how to overcome common hurdles when handling large files in Logic Apps Standard. Discover strategies for scaling, offloading memory-intensive operations, and optimizing performance for efficient integration. There is a new-new Data Mapper for Logic App Standard Post by Sandro Pereira Discover the new Data Mapper for Logic App Standard, now in public preview. Enjoy a modern BizTalk-style mapper with code-first, schema-aware experience, supporting XSLT 3.0, XSD, and JSON schemas for efficient data mapping! A Friday Fact from Sandro Pereira. The name of When a HTTP request is received trigger affects the workflow URL Post by Sandro Pereira Discover how the name of the "When a HTTP request is received" trigger affects the workflow URL in Azure Logic Apps. Learn best practices to avoid integration issues and ensure consistent endpoint paths. Changing APIM Operations Doesn’t Update their PathTemplate Post by Luis Rigueira Learn how to handle PathTemplate issues in Azure Logic Apps Standard when switching APIM operations. Ensure correct endpoint paths to avoid misleading results and streamline your workflow. It is a Friday Fact, brought to you by Luis Rigueira!Announcing the General Availability of the Azure Logic Apps Rules Engine
This week we announced our agent loop, a groundbreaking new capability in Azure Logic Apps to build AI agents into your enterprise workflows. With agent loop, you can embed advanced AI decision-making directly into your processes – enabling your apps and automation to not just follow predefined steps, but to reason, adapt, and act autonomously towards goals. Now, we are announcing the General Availability of our Azure Logic Apps Rules Engine. A deterministic rules engine runtime based on the RETE algorithm that allows in-memory execution, prioritization, and reevaluation of business rules in Azure Logic Apps. The Azure Logic Apps Rules Engine is a decision management inference engine in Azure Logic Apps, which provides the capability for customers to build Standard workflows in Azure Logic Apps and integrate readable, declarative, and semantically rich rules that operate on multiple data sources. The native data sources available today for the Rules Engine are XML and .NET objects. These data sources are called "facts" and are used to construct rules from small building blocks of business logic or "rulesets". To create rules, you need the Rules Composer. It can be downloaded from the download center. The Rules Engine can also interact with the data exchanged by all the connectors available for Standard logic app resources. This design pattern promotes code reuse, design simplicity, and business logic modularity. Our Rules engine uses a VSCode experience to create Logic Apps projects with Rules engine support. For more information on how to create projects with Rules Engine, visit here. Now. What can I do with it? In a world of AI that essentially follows a probabilistic approach, rules engines are vital because they provide consistency, clarity, and compliance across different business goals. When you use rules with a workflow in Azure Logic Apps, you can define the logic, constraints, and policies that govern how to process, validate, and exchange data across systems, while you avoid AI hallucinations. Rules also help you make sure that applications follow the regulations and standards of their respective industries and markets. By using a rules engine, you can manage and update your workflow's business logic independently from the code and without having to alter your workflow. This approach helps you reduce the complexity and maintenance costs of your applications and increase their agility and scalability. From a technical perspective, the Azure Logic Apps rules engine allows you to do forward chaining or forward reasoning, in other words to do a re-evaluation of rules triggered by changes in the facts because of a rule’s execution. This is one of those scenarios where rules engine is unique; instead of writing complex code or creating complex “state-machine” workflows, the logic apps rules engine conducts this task with an instruction called “Update”. Getting started In the example below, I will show how to use the Logic Apps rules engine to ground an AI workflow loop. For this to scenario, I am adding a Rules Engine workflow, to an existing agent loop workflow, and use it to correct rates and provide a “cross-sell” recommendation. First, I need to deploy the workflow from VSCode to Azure. As the rules engine currently only supports XML and .NET Framework objects, I create an XSD schema (using Copilot if you don’t have an existing one) and use it with a “Compose XML with schema” action to create the XML fact that is needed. To obtain the returned data, I am using the “Parse XML with schema” action as well. After the logic app was deployed, I added it as a tool in the Logic Apps agent workflow loop, with a Call workflow in this logic app. I then pass the values that I need for parameters for the Rules engine to work. And I leave the rules engine return values empty. Then I updated my system prompt to indicate how I want the Rules engine to be used. The agent loop will find the right tool for the right job. Once the system prompt has been updated, I proceed to run the workflow with a payload. I have highlighted in red in the Agent chat, the guardrails imposed by the Rules Engine. Those rules have been used to make sure that the AI responses fall within the internal compliance and cross-sell company criteria. Some of the business rules can have different priorities and might require re-calculation for accuracy. The Logic Apps Rules Engine takes care of it without coding or adding complex business logic through additional workflows. Further adjustments to the rules using the Rules Composer will ground the agent’s results even more. What else can I do with it? You can use a Rules Engine in any context. In fact, decision management that falls under Intelligent business processes automation is growing in customers who want to provide flexibility, governance and compliance with their cloud workloads. Another well-known scenario is for BizTalk Migrations to Azure Logic Apps. For customers who have implemented the BizTalk BRE for decision management, content redirection, SWIFT or .NET framework. Demo Please watch the following short demo of this sample. Contact Us Have feedback or questions about the Rules Engine? We’d love to hear from you. Reply directly to this blog post or reach out to us through this form. Your input helps shape the future of Logic Apps and the rules engine.
