Logic Apps - MCP Demos
We recently announced the ability to create MCP servers using Logic Apps connectors. In this post we are going to share some demo videos that will help you get started and provide you with some ideas on how you can build MCP servers to address your Agent connectivity needs. API Center + Logic Apps MCP Server Demos Getting Started - Salesforce Sales MCP Server In this video, we will leverage Azure API Center to create an MCP Server using Logic Apps connectors. Our solution will allow an end user to manage their Salesforce Contacts, Accounts and Opportunities. Building a Dataverse MCP Server In this video, we will leverage Azure API Center to create a Dataverse MCP Server using Logic Apps connectors. Our solution will allow an end user to gain insights on product returns and log an action for a quality control manager. Building a SharePoint MCP Server In this video, we will leverage Azure API Center to create a SharePoint MCP Server using Logic Apps connectors. Our solution will allow an end user to gain insights on product feedback and log new feedback on how to improve product. Calling Logic Apps MCP Server from Copilot Studio In this video, we will use API Center and Azure Logic Apps to expose an MCP Server that can be called from Copilot Studio securely. Logic Apps MCP Server Demos Getting Started - ServiceNow Incident MCP Server In this video, we will take an existing Logic App (Standard) instance and enable it as an MCP server. Our MCP server will expose tools that help users assign IT Incident tickets to ServiceNow. Resources Looking for more resources? Check out our product documentation: API Center and Logic Apps MCP server Logic Apps as an MCP serverCodeful Workflows: A New Authoring Model for Logic Apps Standard
đ This blog introduce early concepts of a pre-release functionality and is subject to change. Azure Logic Apps Standard offers you a powerful cloud orchestration engine, enabling you to build and run automated workflows that effortlessly integrate resources from various services, systems, apps, and data sources. Whether you're looking to streamline processes across a complex enterprise or simply reduce the need for extensive coding, this platform provides a solution that's both efficient and flexible. For those of you who require more control over workflow designs or want to leverage your expertise in frameworks like .NET and the Durable Tasks framework, Logic Apps Standard now introduces an exciting new feature: Codeful Workflows. With Codeful Workflows, you can define workflows using an imperative programming style, blending the flexibility of coding with the simplicity and operational strengths of Logic Apps. This means you can structure your workflows the way that makes sense to you while still tapping into the rich ecosystem of connectors and tools built into Logic Apps. What Are Codeful Workflows? 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. Built on frameworks like .NET and the Durable Tasks framework, Codeful Workflows allow you to structure workflows in code while seamlessly integrating with Logic Apps Standard rich connector ecosystem, and leverage its operational capabilities. The core elements of a Logic App workflowâtriggers, actions and connections âare translated into durable task concepts within this codeful model: Triggers are implemented as Client Functions that invoke durable orchestrations, which contain the body of the workflow, blending logic implemented by the language primitives, with connections actions for external connectivity. Connector actions are presented as Activity Functions. The Logic Apps Connector ecosystem is exposed to you via an SDK, bringing discoverability and rich support for intelisense when creating action inputs, invoking actions or reusing action outputs in later steps. The SDK vastly simplifies the execution of those connectors, by wrapping them internally on a Activity Function, so you donât need to create new activities for each connector action you want to invoke. Connections, which manages the connectivitiy between actions and end systems, remains unchanged, allowing you to setup once and share connections between multiple orchestrations and logic apps declarative workflows. Connector actions uses a reference to a connection, providing flexibility between local and cloud configurations. Using those building blocks, you can create workflows using familiar programming paradigms, while still benefiting from the easy configuration and operational feature of Logic Apps Standard. If you are an existing Logic Apps Standard customer, your codeful and visual workflows can coexist within the same application, bridging the gap between pro-code and low-code approaches. With those two execution models working hand in hand on the same application, Logic Apps Standard becomes a comprehensive orchestration tool that caters to all developer personas, from integration specialists to enterprise teams, with no cliffs on their experience. Creating Codeful Workflows Designing codeful workflows begins with creating a new Logic Apps project within Visual Studio Code, configured for .NET and the Durable Tasks framework. From triggers to actions, developers gain full flexibility to define their workflows programmatically. Implementing Triggers Triggers are the entry points of workflows, and in Codeful Workflows, they are defined as Client Functions. For example, an HTTP trigger can start a workflow when a request is received: [FunctionName("HelloTrigger")] public static async Task<HttpResponseMessage> HttpStart( [HttpTrigger(AuthorizationLevel.Anonymous, "get", "post")] HttpRequestMessage req, [DurableClient] IDurableOrchestrationClient starter, ILogger log) { var requestContent = await req.Content.ReadAsStringAsync(); var workflowInput = new HTTPHelloInput { Greeting = $"Hello from Codeful workflows. You said '{requestContent}'" }; log.LogInformation("Workflow Input = '{workflowInput}'.", JsonSerializer.Serialize(workflowInput)); string instanceId = await starter.StartNewAsync("HelloOrchestrator", workflowInput); log.LogInformation("Started orchestration with ID = '{instanceId}'.", instanceId); return await starter.WaitForCompletionOrCreateCheckStatusResponseAsync(req, instanceId); } Using Connector Actions Both Managed and Service Provider Actions are available to be used within your orchestrations. They are organized in the SDK by type making it easy to find the right connector to use. Once you identify the action to use, you can use the rich intelisense interface to generate inputs and call the action directly in your orchestration code. Deployment and Operations Deploying Logic Apps Standard that uses both codeful and codeless workflows follows the same practices already available in Logic Apps Standard. Operational insights, such as endpoint visibility and execution monitoring, are provided within the Azure Portal, ensuring parity with the functionality available for codeless workflows. This cohesive deployment model allows organizations to maximize their resources and cater to diverse development needs, whether they require quick prototyping via low-code tools or robust, scalable solutions through pro-code implementations. Codeful Workflows and Intelligent Agents You can take advantage of codeful workflows and Logic Apps Standard Agent Loop to create new intelligent applications that 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. See this demo where we share two approaches to implement agent loops â combining codeful and codeless workflows, where you can reuse existing workflows as tools, and writing agent loop actions directly with code: Looking for feedback on Codeful Workflows We are looking for early feedback on this feature. If you are interested in participating on a private preview, please use the form below to register your interest and we will contact you to share the instructions. https://aka.ms/lacodeful/privatepreview/formLogic Apps Community Day 2025
We have delayed the Speaker announcements, as we had to keep the sessions open for an extra day. Speakers will now by notified by email by September 13th, 2025. Speakers and sessions will be published by September 19th, 2025 We are bringing Logic Apps Community Day again this year, on October 30, 2025 (Pacific Time) and we want you to join us as we host a full day of learning where you will be the star! The Logic Apps Community Day is a free event driven by Microsoft, for anyone who wants to learn more about Logic Apps and how it can help to solve real life integration problems. This year, we want to learn how you have been using AI with Logic Apps, so our themes for the sessions are: Creating Intelligent Applications with Logic Apps and AI: tell us how you have been using Logic Apps features to implement your intelligent application scenarios - from Agent Loops, to Logic Apps exposed as MCP tools, to improving your intelligent application knowledge in real time - we want to see the scenarios you created! Accelerating Logic Apps Developer Velocity with AI: How are you taking advantage of Gen AI to make your developer life easier using Logic Apps? From prompts to create test data, to automated creation of maps, unit test or custom code and anything in between. Maybe you have been using prompts, instructions or chat modes to make your development life easier? We want to see it all! Registration, Speakers and Sessions Want to To make sure you are notified on the day, and want to add the event on your calendar? You can register on our Reactor event page! Check out our agenda below - it will be a day packed with information and lots of amazing topics! Speaker Session Title Session Abstract Sebastian Meyer Intelligent Enterprise Integration â Automated Order Processing with AI and SAP This session explores how modern enterprises can streamline and safeguard their business operations through intelligent system integration. At the core is an AI-powered agent loop implemented in Logic Apps that automatically receives and parses flat files containing individual purchase orders. The Agent identifies critical order quantities and routes them to a business user for manual approvalâensuring compliance with internal control policies. Only approved Orders are transmitted to the SAP system. Finally, the enriched dataâcombining raw order details and SAP referencesâis automatically sent via email to the respective business partner. The result is a seamless, transparent, and scalable process that combines human oversight with AI-driven automation. Attendees will learn: - Create AI Agent Loops with Logic Apps - Bring in a Human in the loop - Re-using existing LA Workflows as Tools - Use Connectors to communicate with external Systems - Operational Aspects Toon Vanhoutte Smart invoice processing with Logic Apps Many organizations struggle with identifying the correct internal approver for incoming purchase invoices. It's a process that often involves time-consuming manual work, especially when no purchase order reference is available. In todayâs era of generative AI, there must be a smarter way to streamline this challenge. Join me for an engaging session where I demonstrate how Microsoft Logic Apps Agent Loop can revolutionize invoice processing. Youâll see a live demo showcasing how structured data can be intelligently extracted from purchase invoices and how an AI-powered agent can reason over documented business rules to automatically determine the appropriate approver. No need for costly OCR solutionsâjust the power of Logic Apps and generative AI working together to simplify and accelerate your financial workflows. Michael Stephenson Can I unit test an agentic workflow with logic apps? In this session we will talk about the challenges of testing non deterministic workflows and look at how you might use the logic app unit test framework to be able to implement some testing strategies. Florian de Langhe Unlocking Excel Analytics: Logic Apps + Code Interpreter in Action Excel analysis has always been a challenge in Logic Apps workflows, limiting us to basic read/write operations while complex analytics required external services. This session demonstrates how the new Code Interpreter action, combined with intelligent looping patterns, unlocks powerful Python-driven analytical capabilities directly within your Logic Apps flows. Stephen W Thomas Exposing Your Logic App As An MCP Server â What, Why, and How? Have you heard all the buzz around MCP Servers, but don't really know how it can help you? This session will talk about why using MCP Servers with new and existing Logic Apps will open up new scenarios and gain maximum use across the enterprise. We will take a look at how easy it is to set this up today and expose your workflows to AI Agents. Stefano Demiliani Intelligent applications with Logic Apps and Private AI This session explores the powerful integration of the Azure Logic Apps platform with on-premises and private cloud AI solutions, enabling organizations to maintain data sovereignty while leveraging advanced AI features. You will learn practical implementation strategies and tips for creating intelligent workflows that incorporate private AI models (open LLMs hosted locally, like gpt-oss) for AI-enhanced business process automation, while respecting your organization's privacy and security requirements. Ahmed Bayoumy The âQuick Taskâ Trap and How Logic Apps agent loop Kills It A while ago i had a meeting with a new client in the cargo shipping business to map their integration landscape. Everything looked solid, most integrations had the usual needs, nothing out of the ordinary. Then they mentioned the âspecial bookingsâ that still land in an operatorâs inbox. Yes, manual bookings still occur in the enterprise world. Each one seems tiny until you multiply it across a week, a month, and a year. Those interrupts also break the operations teamâs focus. So why not build a Logic Apps agentic loop to take the ad hoc cases off peopleâs plates, while handing off the real edge cases to humans with full context? Sivaji Gullipalli Boosting Developer Productivity in Logic Apps with Generative AI In this lightning talk, I will share how Generative AI can be combined with Azure Logic Apps to accelerate integration development and simplify repetitive tasks. Drawing from real-world insurance project scenarios, I will demonstrate how AI-driven prompts can be used to generate realistic test data, assist in building maps, create unit tests, and even support custom code generation. By leveraging AI during the development lifecycle, Logic Apps developers can significantly reduce manual effort, improve accuracy, and deliver solutions faster. This session is designed to provide beginner-friendly, practical insights that attendees can immediately apply to their Logic Apps projects to enhance productivity and efficiency. Dan Probert What is a prompt - and can I automate it? In this introductory session, we look at what makes a good Gen AI prompt, and look at whether we could automate the generation of a prompt, and what that might take. This session is aimed at those devs that are new to Gen AI/LLM, and want to know more about what a prompt is, and how they might be able to simply prompt creation. Sovit Charak Agentic Document Processing with Logic Apps Standard + Document AI We will demo through logic apps: AI classification & dynamic schemas: identify doc type (contract/invoice/form) and pick the right JSON schema. Schema-aware extraction: Document AI + LLM returns exact keys; invalid outputs auto-repair via a validation loop. Agentic behaviors: tool selection & fallback OCR. Human-in-the-loop: low-confidence fields trigger a Teams Adaptive Card for approve/edit/reject. Business rules & routing. Storage & integrations: original docs to SharePoint/Blob, structured data to SQL/D365/ERP; notifications to Teams/Email. Cameron McKay Leveraging Logic Apps to build easy and effective AI Agents This session will provide an overview of Azure Logic Apps as an agent building tool that solves the problem related to organizations wanting to create agents, but not having a way to build effective agents due to disparate and segregated data sources. We will discuss Agent Loop as our tool to build agents using connectors. We will showcase demos of how to build your first agent, explore the different human in the loop capabilities that are available within agent loop and how we can use logic apps to build agents using connectors. The purpose of the session is to showcase logic apps as an agent building platform.Hybrid Logic Apps deployment on Rancher K3s Kubernetes cluster
K3s is a lightweight Kubernetes distribution, certified by the Cloud Native Computing Foundation (CNCF) and originally developed by Rancher. It is optimized for on-premises environments with limited resources, making it ideal for edge computing and lightweight hybrid scenarios. Unlike a full Kubernetes distribution, K3s reduces overhead while maintaining full Kubernetes API compatibility. This makes K3s an ideal choice for hosting Logic Apps Standard near your data sourcesâsuch as on-premises SQL Server or local file sharesâwhen you have lightweight workloads. There are 5 steps which are followed to setup the Hybrid Logic Apps including infrastructure which is illustrated in the following diagram. Most of these 5 steps are same as discussed in the Hybrid Logic Apps doc except the K3s Setup part Set up your own infrastructure for Standard logic app workflows - Azure Logic Apps | Microsoft Learn. Step 1: Prepare the K3s Cluster Docker desktop setup - In this case, the host machine is Windows 11 so decided to user Docker with WSL2 to setup the containers. Install the docker desktop using WSL2 Docker Desktop: The #1 Containerization Tool for Developers | Docker and make sure we select WSL2 Install K3s on your infrastructure and create single node cluster using k3d. #Install choco , kubectl and Helm Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1')) powershell choco install kubernetes-cli -y choco install kubernetes-helm -y choco install k3d -y # open in new powershell window powershell k3d cluster create # deleting the default load balancer Traefik as it conflicts with 80 and 443 port - we can configure the load balancer to other ports if needed kubectl delete svc traefik -n kube-system kubectl delete deployment traefik -n kube-system Next two steps are same as given Set up your own infrastructure for Standard logic app workflows - Azure Logic Apps | Microsoft Learn Step 2: Connect the Kubernetes cluster to Azure Arc Step 3: Setup the Azure Container Apps extension and environment You need to skip the core DNS setup required for Azure Local as given in Update CoreDNS Step 4: Conduct the Storage Configuration for SQL and SMB SQL Database (Runtime Store): Hybrid Logic Apps use SQL database for runtime operations and run history. In this scenario I used on-premise SQL server using SQL Authentication. I setup the SQL Server 2022 on the Windows host machine, enabled SQL server authentication and added new SQL admin user. Please follow the link for more details.. The SQL connection string can be validated using following PowerShell script $connectionString = "Server=<server IP address>;Initial Catalog=<databaseName>;Persist Security Info=False;User ID=<sqluser>;Password=<password>;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=True;Connection Timeout=30;" try { $connection = New-Object System.Data.SqlClient.SqlConnection $connection.ConnectionString = $connectionString $connection.Open() Write-Host "â Connection successful" $connection.Close() } catch { Write-Host "â Connection failed: $($_.Exception.Message)" } SMB is used as local file share on Windows host machine; it is advised to use a new user for the Windows SMB share $Username = "k3suser" $Password = ConvertTo-SecureString "<password complex>" -AsPlainText -Force $FullName = "K3s user" $Description = "Created via PowerShell" # Create the user New-LocalUser -Name $Username -Password $Password -FullName $FullName -Description $Description Add-LocalGroupMember -Group "Users" -Member $Username Once the above user is created you can use Windows hosted machine to create Artifacts folder and allow read and write access. Please follow the link for more details Step 5: Create your Logic App (Hybrid) With all prerequisites and infrastructure in place for creating Hybrid Logic Apps, the next step is to build the Logic Apps using the specified connection string and SMB share path. This can be accomplished through the Azure Portal, as outlined below. Now you can create Logic Apps workflows using the designer and execute the Logic Apps workflow.Introducing Logic Apps MCP servers (Public Preview)
Using Logic Apps (Standard) as MCP servers transforms the way organizations build and manage agents by turning connectors into modular, reusable MCP tools. This approach allows each connectorâwhether it's for data access, messaging, or workflow orchestrationâto act as a specialized capability within the MCP framework. By dynamically composing these tools into Logic Apps, developers can rapidly construct agents that are both scalable and adaptable to complex enterprise scenarios. The benefits include reduced development overhead, enhanced reusability, and a streamlined path to integrating diverse systemsâall while maintaining the flexibility and power of the Logic Apps platform. Starting today, we now support creating Logic Apps MCP Servers in the following ways: Registering Logic Apps connectors as MCP servers using Azure API Center Using this approach provides a streamlined experience when building MCP servers based upon Azure Logic Apps connectors. This new experience includes selecting a managed connector and one or more of its actions to create an MCP server and its related tools. This experience also automates the creation of Logic Apps workflows and wires up Easy Auth authentication for you in a matter of minutes. Beyond the streamlined experience that we provide, customers also benefit from any MCP server created using this experience to be registered within their API Center enterprise catalogue. For admins this means they can manage their MCP servers across the enterprise. For developers, it offers a centralized catalog where MCP servers can be discovered and quickly onboarded in Agent solutions. To get started, please refer to our product documentation or our demo videos. Enabling Logic Apps as remote MCP server For customers who have existing Logic Apps (Standard) investments or who want additional control over how their MCP tools are created we are also offering the ability to enable a Logic App as an MCP server. For a Logic App to be eligible to become an MCP server, it must have the following characteristics: One or more workflows that have an HTTP Request trigger and a corresponding HTTP Response action It is recommended that your trigger has a description and your request payload has schema that includes meaningful descriptions Your host.json file has been configured to enable MCP capabilities You have created an App registration in Microsoft Entra and have configured Easy Auth in your Logic App To get started, please refer to our product documentation or our demo videos. Feedback Both of these capabilities are now available, in public preview, worldwide. If you have any questions or feedback on these MCP capabilities, we would love to hear from you. Please fill out the following form and I will follow-up with you.Announcing 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!
đ General Availability: Enhanced Data Mapper Experience in Logic Apps (Standard)
Weâre excited to announce the General Availability (GA) of the redesigned Data Mapper UX in the Azure Logic Apps (Standard) extension for Visual Studio Code. This release marks a major milestone in our journey to modernize and streamline data transformation workflows for integration developer. What's new The new UX, previously available in public preview, is now the default experience in the Logic Apps Standard extension. This GA release reflects direct feedback from our integration developer community. Weâve resolved blockers that we heard from customers and usability issues that impacted performance and stability, including: Opening V1 maps in V2: Seamlessly open and edit existing maps you have already created with latest visual capabilities. Load schemas on Mac: Addressed schema-related crashes on macOS for a smoother experience. Function documentation updates: Improved guidance and examples for built-in collection functions that apply on repeating nodes. Stay connected We would love to hear your feedback. Please use this form link to let us know if there are any missing gaps or scenarios that are not yet coveredLogic Apps Aviators Newsletter - September 25
In this issue: Ace Aviator of the Month News from our product group Community Playbook News from our community Ace Aviator of the Month Septemberâs Ace Aviator: Kritika Singh Integration Architect & Sr. Consultant at Capgemini Norge AS What's your role and title? What are your responsibilities? I work as an Integration Architect & Sr. Consultant at Capgemini Norge AS. In my role I assist clients in addressing a wide range of integration challenges, with a particular emphasis on modernizing legacy systems, such as BizTalk, by transitioning them to cloud-native Azure iPaaS solutions. Iâm responsible for architecting secure and scalable integration landscapes, designing and developing solutions, mentoring team members, and engaging with stakeholders and cross-functional teams. I work extensively with technologies such as Azure Logic Apps, Azure Functions, API Management, Service Bus, App Service Environment(ASEv3), Virtual Networks and CI/CD pipelines using GitHub. One of my proudest achievements was successfully delivering a complex BizTalk modernization project to Azure that required deep technical expertise and strategic coordination. Can you give us some insights into your day-to-day activities and what a typical day in your role looks like? As part of a distributed team across different locations and countries, my day starts with stand-ups involving both offshore and onshore team members to review progress and assign tasks. I spend time with developers, helping them navigate technical challenges and mentoring them through dedicated sessionsâthis has helped improve delivery quality and team confidence. I collaborate closely with cross-functional teams and stakeholders to align on requirements and solution design. Throughout the day, I work on resolving issues, improving existing solutions, work on innovation ideas and managing tasks. What motivates and inspires you to be an active member of the Aviators/Microsoft community? I am deeply passionate about technologyâhaving worked with BizTalk throughout my career and, for the past 5+ years, diving into Azure iPaaS. Microsoft products evolve constantly, and that sparks my curiosity to explore, learn, and innovate every day. What truly drives me is the opportunity to give back to the community by sharing my learnings, challenges, and even failures. Itâs all about growing together and inspiring others along the way. 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? Curiosity and consistency matter more than perfection. Donât be afraid to ask questions, experiment, and fail, thatâs where the real learning happens. Also, find a community that supports you; sharing your journey, both wins and setbacks, can inspire others and help you grow faster. What has helped you grow professionally? My professional growth has been shaped by a blend of curiosity, courage, and the right opportunities. Starting with BizTalk and evolving into Azure iPaaS, Iâve embraced every challenge as a chance to learn. Whatâs made the biggest difference is having the boldness to take on responsibility, the willingness to take risks, and the drive to keep growing. Sharing my journey with the community has not only helped others but also deepened my own learning. If you had a magic wand that could create a feature in Logic Apps, what would it be and why? If I had a magic wand to enhance Logic Apps, Iâd bring in three powerful features to supercharge developer productivity and solution resilience: Seamless Version Control & Rollback Having Git-like capabilities built into Logic Appsâtrack every change, compare versions, and roll back instantly when needed. This would empower teams to experiment confidently and collaborate more effectively without fear of breaking production workflows. Effortless Disaster Recovery Setup Setting up DR should be as simple as a few clicks. A built-in, automated DR configuration for AIS would ensure business continuity, reduce downtime, and give developers peace of mindâespecially in mission-critical environments. Native JSON Mapper(Not Liquid) A visual, intuitive JSON mapping tool would simplify complex data transformations, reduce manual coding, and speed up development. This would be a game-changer for integration scenarios, especially when working with dynamic schemas and APIs. Simplified Authorization like ClaimChecks for Logic Apps Standard (Beyond EasyAuth) A more developer-friendly authorization setup that minimizes manual configurations and integrates seamlessly with identity providers. This would make securing Logic Apps faster, easier, and more consistent across environments. News from our product group Logic Apps Live August 2025 Missed Logic Apps Live in August? You can watch it here. We had a recap on Logic Apps Hybrid, our special guest Kritika Singh talking about her learnings with BizTalk Migration to AIS, and updates on Data Mapper GA and Logic Apps Standard Deployment Center. Logic Apps Community Day 2025 We are bringing Logic Apps Community Day again this year, on October 30, 2025 (Pacific Time) and we want you to join us as we host a full day of learning where you will be the star! Call for Speakers is still open until September 07, 2025 â so hurry and submit your session! General Availability: Enhanced Data Mapper Experience in Logic Apps (Standard) Weâre excited to announce the General Availability (GA) of the redesigned Data Mapper UX in the Azure Logic Apps (Standard) extension for Visual Studio Code. This release marks a major milestone in our journey to modernize and streamline data transformation workflows for integration developer. Announcing: Setup CD in Azure Logic Apps Standard with Deployment Center Looking to automate your Azure Logic Apps code deploymentsin a faster way? Deployment Center - a built-in feature in Azure Logic Apps Standard - in now available, with built-in support on your VS Code projects, making it easier to deploy Logic Apps from your source control repository. Deployment Center is designed to make deploying, updating, and managing your Logic Apps workflows simple and straightforward. Hybrid Logic Apps deployment on Rancher K3s Kubernetes cluster Explore how Hybrid Logic Apps run effortlessly on K3sâdelivering the power of Hybrid Logic Apps without the complexity and heavy infrastructure demands of a full Kubernetes cluster! News from our community What gets returned to the LLM by my Logic App Agent Loop tool? Video by Michael Stephenson Michael has been experimenting with Logic App Agent loop and, following a discussion with Kent Weare about the interaction between the workflow and the LLM, aimed to understand what data is returned to the model, since the number of tokens influences cost. He summarizes his findings from that conversation in this brief video. SOAP 1.2 Calls from Logic Apps â Fixing Unsupported Media & WS-Addressing Errors Post by Prashant Singh Struggling with SOAP 1.2 in Azure Logic Apps? Learn how to fix Unsupported Media errors, decode MTOM responses, and handle WS-Addressing headers for seamless integration in this post by Prashant. Demystifying AI Agent Loops in Logic Apps: The Future of Integration (But Not Everywhere) Post by Al Ghoniem Explore how AI Agent Loops enhance Azure Logic Apps for non-deterministic tasks like anomaly detection and IT Ops triageâwhile knowing when traditional workflows are the better fit. Can I use AI to create and deploy an Azure Logic Apps with Business Central connector? Post by Stefano Demiliani Stefano is testing the boundaries of what AI can do, so you donât have to â he ran a blind test showing that AI can deploy Azure resources wellâbut struggles with external connectors like Business Central. Learn what worked, what didnât, and why better prompts matter. How to use ChatGPT Agent Mode with Azure! Video by Stephen W. Thomas And looks like August was the month to experiment with Azure Resources. Stephen did some research too and shows you how easily ChatGPT-5 Agent Mode can auto-provision resources in Azure. This video demonstrates how to use a single prompt to build a logic app and create a resource group. Follow his video along to see how to get ChatGPT-5 agent working for you! Integration Love Story - Andrew Wilson Video by Ahmed Bayoumy and Robin Wilde In this special fast-paced episode recorded at INTEGRATE, Ahmed and Robin sit down with the brilliant Andrew, newly awarded Microsoft MVP and Logic Apps Ace Aviator, to talk about his journey, passions, and why integration is the powerhouse behind every digital experience. Tips for Migrating SAP IDoc Reception Workloads from BizTalk to Azure Logic Apps Post by Francois Malgreve Learn how to reuse BizTalk XSLTs in Azure Logic Apps! In this post by Francois, you will learn hot to configure the SAP trigger with the right IDoc format and namespace settingsâminimizing code changes and easing migration. Query Azure DevOps work items with Logic App and Managed Identity Post by Michael Stephenson Learn how to use a reusable Logic App and a user-assigned managed identity to securely query Azure DevOps work items using WIQLâideal for building scalable, secure workflows. Understand Agent Loops in Azure Logic Apps Video by Srikanth Gunnala In this video, Srikanth explore Azure Logic Apps AI Agents â also known as Agent Workflows or Agent Loops â and how theyâre redefining workflow automation with Azure OpenAI. Youâll learn what an AI agent is in Azure Logic Apps, how it works, and see a live demo of building an AI-powered, adaptive workflow. Automate Microsoft Fabric Cost Savings with Logic Apps Post by Sherry L. Robinson Learn how to pause and resume Microsoft Fabric capacity using Azure Logic Appsâcutting costs during off-hours with minimal code and seamless integration via REST API or Resource Manager, in this insightful post by Sherry. Use Graph API to send Emails in Logic Apps Post by Ĺahin Ăzdemir In this post, Ĺahin shows your hot to use Microsoft Graph API with service principals to securely send emails from Logic Apps using app registrations and access policies. This will be quite useful in cases where you canât associate the calls to a user account, which is a requirement for the Office 365 connector.Announcing: Setup CD in Azure Logic Apps Standard with Deployment Center
Introduction Looking to automate your Azure Logic Apps code deploymentsin a faster way? Deployment Center - a built-in feature in Azure Logic Apps Standard - in now available, with built-in support on your VS Code projects, making it easier to deploy Logic Apps from your source control repository. Deployment Center is designed to make deploying, updating, and managing your Logic Apps workflows simple and straightforward. The feature in a nutshell Deployment Center connects your Logic Apps to your favourite source control systemsâlike GitHub or Azure Reposâand handles code deployments automatically, giving you the following benefits: Fewer Manual Steps: Deployment Center automates your code deployment process, letting you focus on building instead of babysitting releases. Simple Setup: The user interface guides you through linking your repository and configuring deployment pipelinesâno guesswork, just results. Easy Rollbacks: Need to revert to a previous version? Deployment Center makes it painless to roll back changes if something doesnât work as expected. DevOps Friendly: Seamlessly plugs into your existing DevOps or CI/CD workflow, supporting a more unified automation strategy. How does it work There are two steps required to setup Deployment Center in Azure Logic Apps Standard: First, you need to prepare your solution to connect to Deployment Center â weâve updated the feature that generates deployment scripts in VS Code to support both Deployment Center and Azure DevOps now. This way you find all you need to generate deployments in one place. Once the Deployment Center scripts are generated and pushed to your source control, you can connect your repository to your existing Azure Logic Apps Standard application. After that, commits made on your source code will be automatically published to your Azure resource. You can find all the steps in details in the official documentation. Things you need to know There are some things you need to know before implementing Azure Deployment Center: The current Deployment Center feature implementation is based on Azure Building Services, which required SCM Basic authentication. The script generated by VS Code only cover the deployment of code and configuration adjustments. Any infrastructure related activities, like the creation of Azure Managed connections should be done as a previous step. Custom code projects are not included in the deployment.
