🧩 Use Index + Direct Access to pull data across loops in Data Mapper
When working with repeating structures in Logic Apps Data Mapper, you may run into situations where two sibling loops exist under the same parent. What if you need to access data from one loop while you’re inside the other? This is where the Direct Access function, used in combination with Index, can save the day. 🧪 Scenario In this pattern, we’re focusing on the schema nodes shown below: 📸 Source & Destination Schemas (with loops highlighted) In the source schema: Under the parent node VehicleTrips, we have two sibling arrays: Vehicle → contains VehicleRegistration Trips → contains trip-specific values like VehicleID, Distance, and Duration In the destination schema: We're mapping into the repeating node Looping/Trips/Trip It expects each trip’s data along with a flattened VehicleRegistration value that combines both: The current trip’s VehicleID The corresponding vehicle’s VehicleRegistration The challenge? These two pieces of data live in two separate sibling arrays. 🧰 Try it yourself 📎 Download the sample files from GitHub Place them into the following folders in your Logic Apps Standard project: Artifacts → Source, destination and dependency schemas (.xsd) Map Definitions → .lml map file Maps → The .xslt file generated when you save the map Then right-click the .lml file and select “Open with Data Mapper” in VS Code. 🛠️ Step-by-step Breakdown ✅ Step 1: Set up the loop over Trips Start by mapping the repeating Trips array from the source to the destination's Trip node. Within the loop, we map: Distance Duration These are passed through To String functions before mapping, as the destination schema expects them as string values. As you map the child nodes, you will notice a loop automatically added on parent nodes (Trips->Trip) 📸 Mapping Distance and Duration nodes (context: we’re inside Trips loop) 🔍 Step 2: Use Index and Direct Access to bring in sibling loop values Now we want to map the VehicleRegistration node at the destination by combining two values: VehicleID (from the current trip) VehicleRegistration (from the corresponding vehicle) ➡️ Note: Before we add the Index function, delete the auto-generated loop from Trips to Trip To fetch the matching VehicleRegistration: Use the Index function to capture the current position within the Trips loop 📸 Index setup for loop tracking Use the Direct Access function to retrieve VehicleRegistration from the Vehicle array. 📘 Direct Access input breakdown The Direct Access function takes three inputs: Index – from the Index function, tells which item to access Scope – set to Vehicle, the array you're pulling from Target Node – VehicleRegistration, the value you want This setup means: “From the Vehicle array, get the VehicleRegistration at the same index as the current trip.” 📸 Direct Access setup 🔧 Step 3: Concatenate and map the result Use the Concat function to combine: VehicleID (from Trips) VehicleRegistration (from Vehicle, via Direct Access) Map the result to VehicleRegistration in the destination. 📸 Concat result to VehicleRegistration ➡️ Note: Before testing, delete the auto-generated loop from Vehicle to Trip 📸 Final map connections view ✅ Step 4: Test the output Once your map is saved, open the Test panel and paste a sample payload. You should see each Trip in the output contain: The original Distance and Duration values (as strings) A VehicleRegistration field combining the correct VehicleID and VehicleRegistration from the sibling array 📸 Sample Trip showing the combined nodes 💬 Feedback or ideas? Have feedback or want to share a mapping challenge? Open an issue on GitHubLogic Apps Aviators Newsletter - May 2025
In this issue: Ace Aviator of the Month News from our product group Community Playbook News from our community Ace Aviator of the Month May’s Ace Aviator: Calle Andersson & Cloud at Contica What's your role and title? What are your responsibilities? I’m an IT Security Expert, integration security enthusiast, and full-time breaker of bad security defaults. I'm spending my days at Contica where I serve as Head of Security – Integration & Cloud. My day job involves helping customers secure their Azure environments, focusing on Logic Apps, Function Apps, API Management, and the rest of the Azure Integration Services family. I’m also working on building managed services focused on security posture and threat detection making secure delivery of integration platforms the default, not the exception. I’m trying to make “secure by design” feel less like a personal hobby for the one paranoid person on the team, and more like something the entire delivery process just quietly gets right. Can you give us some insights into your day-to-day activities and what a typical day in your role looks like? A big part of my day revolves around helping customers design secure patterns and infrastructure in Azure. That includes everything from shaping network boundaries and authentication flows, to figuring out how to make security practical and scalable. I spend a lot of time reviewing architecture, reading documentation, and testing different configurations, always looking for ways to improve how security is built into the platform itself, not just added on top. It’s part deep technical work, part strategy, and part translating complex security concepts into something teams can actually use. I also work closely with our developers, supporting them in security related questions and helping them navigate things like identity, permissions, and secure machine-to-machine communication. There is also many meetings with different stakeholders to raise awareness, guide decisions, and provide better insight into the actual security posture of their integration platforms. What motivates and inspires you to be an active member of the Aviators/Microsoft community? I genuinely enjoy learning and mastering new skills, and writing technical blog posts or sharing insights is a great way for me to reflect on what I’ve learned, while hopefully making someone else’s day a bit easier. I’ve also met a lot of brilliant people through the community, and it’s incredibly motivating to be surrounded by others who are just as nerdy passionate about secure design in Azure as I am. 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? You don’t need to know everything, just be curious, ask thoughtful questions, and don’t be afraid to break things in a lab environment. The best learning often happens when something goes wrong, and you dig your way out. Also, just ask that stupid question you've been thinking about. What has helped you grow professionally? If I had to mention one thing, it’s consistently challenging my comfort zone and putting myself in situations that push me in the right direction, even when it feels uncomfortable or a bit scary. Growth rarely happens when things are easy and cozy. I also believe that prioritizing your health has an amazing ROI. Getting enough sleep, eating well, and staying active might not sound groundbreaking, but if you want to do extraordinary things, you need the energy and persistence to match. If you had a magic wand that could create a feature in Logic Apps, what would it be and why? This one is really hard. I have three features that i really would love to see. So if i had a magic wand, id wish for a genie that could grant me three wishes! - Private Endpoint support for Consumption: This would enable private invocations HTTP triggers and prevent unnecessary exposure. Some workflows might fit better in Consumption, but security requirements force customers to Standard. - VNET Integration support for Consumption: Same benefits as above but applies when the Logic App needs to communicate with other internal resources over the VNET. - Managed Identity support for WEBSITE_ CONTENTAZUREFILECONNECTIONSTRING in Logic App Standard: Right now, this is in many cases the only access key left that is preventing customers from fully transitioning to Managed Identity and disabling the possibility to use access keys to their Storage Accounts. I really want that magic wand! 🙂 News from our product group Logic Apps Live April 2025 Missed Logic Apps Live in April? You can watch it here. We focused on the Public Preview of Logic Apps Standrad Automated Testing Framework and on the new Logic Apps Lab initiative! You will not regret checking those out! Announcement: Azure Logic Apps (Standard) Automated Testing Public Preview We are excited to announce the public preview of the Azure Logic Apps (Standard) Automated Testing Framework! This new framework is designed to simplify and enhance the testing process for your Logic Apps workflows, ensuring that your integrations are robust, reliable, and ready for production. Hybrid deployment model for Logic Apps - Performance Analysis and Optimization recommendations This document offers an in-depth performance evaluation of Azure Logic Apps within a hybrid deployment framework. It examines, several key factors such as CPU and memory allocation and scaling mechanisms, providing valuable insights aimed at maximizing the application’s efficiency and performance. Summing it up: Aggregating repeating nodes in Logic Apps Data Mapper Logic Apps Data Mapper makes it easy to define visual, code-free transformations across structured JSON data. One pattern that's both powerful and clean: using built-in collection functions to compute summary values from arrays. This post walks through an end-to-end example: calculating a total from a list of items using just two functions — `Multiply` and `Sum`. driving efficiency, agility, and fueling business growth in the AI-powered era. Use Index + Direct Access to pull data across loops in Data Mapper When working with repeating structures in Logic Apps Data Mapper, you may run into situations where two sibling loops exist under the same parent. What if you need to access data from one loop while you’re inside the other? This is where the Direct Access function, used in combination with Index, can save the day. Beyond the Basics: Using Minimum, Maximum, and Average Functions in Logic Apps Data Mapper In this blog, we walk through real-world scenarios and provide downloadable samples so you can try it yourself and accelerate your integration workflows. Demystifying Logic App Standard workflow deployments As Logic App Standard is built on the App Services runtime, it requires a different approach to automation than the consumption tier. AI Procurement assistant using prompt templates in Standard Logic Apps Answering procurement-related questions doesn't have to be a manual process. With the new Chat Completions using Prompt Template action in Logic Apps (Standard), you can build an AI-powered assistant that understands context, reads structured data, and responds like a knowledgeable teammate. Q1’2025: Azure Integration Services Quarterly Highlights and Insights From reinventing hybrid integration to unlocking AI-powered productivity and simplifying API management across ecosystems, the first quarter of 2025 was all about making integration smarter, faster, and more accessible for everyone. Whether you're a developer modernizing legacy workflows, an IT pro securing mission-critical APIs, or a business technologist building intelligent automations, Azure Integration Services and Azure API Management are moving at the speed of innovation. Here’s what stood out this quarter and how these updates can help accelerate your next move. Unleash Innovation with a Modern Integration Platform and an API-First Strategy Join us for a two-day global virtual event where you’ll discover how to unlock the full potential of your data and APIs to drive intelligent, agile growth with Azure Integration Services and an API-first strategy (this event happened in the past, but you should have access to the on-demand videos after registering) How to get JWT token of certificate-based SPN in logic app HTTP action When working with Azure Logic Apps and needing to call an API secured with Azure AD, you might use a Service Principal Name (SPN) with certificate-based authentication to obtain a JSON Web Token (JWT). This article shows a brief guide on how to set this up and use it in an HTTP action within a Logic App Standard How to send Excel file via HTTP in Logic App Due to logic app content transfer mechanism, sending an Excel file (XLSX) in HTTP will corrupt original content format by default. This article will help you to workaround this issue by sending binary data in HTTP body instead. Using Graph API to assign roles to logic app managed identity In this article, we will use the Graph API to assign roles to logic app managed identity. Previous document are mostly use powershell, here is a simply guide with Graph API AI Gateway Enhancements: LLM policies, Real-Time API support, Content Safety, and more As AI becomes more deeply integrated into applications, managing and governing Large Language Models (LLMs) is more important than ever. Today, we’re excited to announce several major updates to AI Gateway in Azure API Management, including the general availability of LLM policies, expanded real-time API support, new integrations for semantic caching and content safety, and a streamlined UI experience to make it even easier to get started. Plus, you can now opt in to early access for the latest AI Gateway features. Let’s dive into what’s new! Enhancing AI Integrations with MCP and Azure API Management As AI Agents and assistants become increasingly central to modern applications and experiences, the need for seamless, secure integration with external tools and data sources is more critical than ever. The Model Context Protocol (MCP) is emerging as a key open standard enabling these integrations - allowing AI models to interact with APIs, Databases and other services in a consistent, scalable way. Azure API Management Your Auth Gateway For MCP Servers Azure API Management is at the forefront, ready to support the open-source Model Context Protocol (MCP). APIM provides an enterprise-ready solution that helps you securely expose your MCP servers while evolving with the latest technology. Announcing "Service updates" for Azure API management Configure service update settings to manage when you receive updates and select maintenance window Announcing open public preview of inbound private endpoint for Standard v2 tier of API Management Today, we are excited to announce the open public preview of inbound private endpoint for Azure API management Standard v2 tier. Announcing General Availability of Authoring API Management Policies with Microsoft Copilot in Azure Microsoft announced the general availability of Microsoft Copilot in Azure. The API Management team is excited to share that authoring Azure API Management policies with Microsoft Copilot in Azure is also generally available, featuring localization, responsible AI, and enhancements to availability, performance, and capabilities. Announcing the Microsoft Azure API Management + Apiboost Partnership To help organizations build scalable, tailored API portals, we are thrilled to announce our partnership with Apiboost. A leader in SaaS and On-prem API portals, Apiboost, paired with Microsoft Azure API Management, enables businesses to create powerful, fully integrated API portals. This partnership allows customers to leverage Azure's secure, scalable platform, simplifying API consumption and enhancing business value. Available on Azure Marketplace. Announcing the Microsoft Azure API Management + Pronovix Partnership We are excited to announce our partnership with Pronovix, a leader in developer portals and API documentation. Pronovix has spent nearly a decade helping enterprises worldwide build business-aligned developer portals, and together, we’re making it faster and easier for Azure API Management customers to launch and scale their own API portals. Logic Apps Aviators Community Playbook We are excited to announce the latest articles from the Logic Apps Aviators Community Playbook. Interested in contributing? We have made it easy for you to get involved. Simply fill out our call for content sign-up link with the required details and wait for our team to review your proposal. And we will contact you with more details on how to contribute. Secure Standard workflows in Azure Logic Apps with Azure API Management Author: Andrew Wilson Everything that we build requires security as a fundamental requirement. Through every stage in the software development lifecycle, starting with requirements and design to how our solutions evolve over time, we should keep a "security first" mindset so we can focus and deliberate on security's importance. In this article, Andrew outlines methods to secure Azure Logic Apps workflows using Azure API Management, focusing on Shared Access Signature (SAS) keys and Easy Auth for authentication and authorization, emphasizing best practices for security and integration. News from our community Building a Complete RAG Application in Azure with No Code Post by Dan Toomey Learn to build Retrieval-Augmented Generation (RAG), a pattern a useful pattern for building LLM-based chat applications against an easily updateable knowledge store, without the expense of re-training the LLM. The pattern provides a base for AI generated responses that are as reliable, context-bounded, and current as the data in the knowledge store (which can be as simple as a collection of documents). Debatching in Logic Apps with Performance in Mind Post by Prashant Singh When working with Azure Logic Apps, handling large arrays efficiently is critical for performance and cost control. It is almost a routine need, but many implementations either slow down over time or rack up unnecessary costs. The solution isn’t just debatching, it’s smart debatching. Let’s break it down using a realistic use case and explore different techniques to handle it effectively. Unlocking the Power of Azure Logic Apps Standard with Azure App Service Environment v3 Post by Kritika Singh In today’s fast-paced digital landscape, businesses are constantly seeking ways to streamline operations, automate workflows, and enhance productivity. Azure Logic Apps Standard, especially when deployed in an Azure App Service Environment v3 (ASEv3), offers a powerful solution for building and orchestrating workflows in a secure and scalable manner. In this blog, we will explore what Azure Logic Apps Standard is, the benefits of using it in ASEv3, and how to get started. Setting Up Azure API Management (APIM) for Logic Apps Standard Video by Stephen W Thomas Learn how to set up Azure API Management (APIM) with Logic Apps Standard to manage, secure, and expose your HTTP-based workflows as APIs. You can use Flat File Schemas in Logic Apps to parse CSV Post by Sandro Pereira There’s a clean and native way to handle csv files: Flat File Schemas. We can use them with an Integration Account inside Logic App Consumption, or they are available inside Logic App Standard by default. Learn more on this Friday Fact from Sandro! Logic App Parameters naming size limits and restrictions Post by Sandro Pereira Learn about parameter naming conventions and best practices when creating Azure Logic Apps parameters, in this Friday Fact from Sandro Pereira. Logic App Variables naming size limits and restrictions Post by Sandro Pereira And since we are talking about naming conventions and best practices – how about learn about those details when creating Azure Logic Apps variables! Another Friday Fact from Sandro Pereira. The Ultimate Azure Logic Apps Handbook: 50 Expert Tips & Best Practices [Free] released Post by Sandro Pereira That Sandro Pereira is one of most prolific authors of our community, that is no news – you just need to look a this month’s community session… But did you know that he put together and Azure Logic Apps Handbook as e-book that can be downloaded for free? Take a look at his announcement on this blog post.Transform Your Integration Strategy with Azure Integration Services
Still on Microsoft BizTalk Server or other legacy integration solutions? If you're relying on BizTalk or other legacy systems, you're already feeling the pain: rising costs, performance bottlenecks, and limited scalability. These outdated systems are holding you back, but the good news? The time to modernize is NOW and we’ve got the event that will show you how. Join us at "Unleash AI Innovation with a Modern Integration Platform and an API-First Strategy", where industry leaders like Visa, LyondellBasell, and Metcash share how they reimagined their integration landscape with Azure. This is your blueprint for moving beyond the limitations of legacy systems and unlocking innovation with a cloud-native, AI-ready approach. By attending, you’ll gain exclusive insights into how leading organizations have turned integration challenges into competitive advantages, positioning themselves for future growth with Azure. Real Stories, Real Impact Visa: Revolutionizing Operations with Azure Logic Apps Visa’s journey from BizTalk to Azure Logic Apps isn’t just a story of modernization—it’s a game-changer. By automating complex workflows and managing over 100 HR systems, Visa reduced manual intervention and slashed infrastructure costs by 95%. With Azure, Visa is now set to scale operations and leverage AI for continued growth. Discover the details of how Visa is preparing for tomorrow’s challenges today. LyondellBasell: Scaling Beyond BizTalk LyondellBasell, a global leader in chemicals, broke free from BizTalk’s limitations. Azure Integration Services empowered them with hybrid connectivity and real-time visibility, enabling them to streamline workflows and boost developer efficiency by 50%. Learn how they unlocked faster decision-making and stronger business outcomes. Brisbane City Council: From Legacy to API-First Agility Brisbane City Council, Australia’s largest local government, faced limitations with legacy integration solution. With Azure, they cut data processing times from 1 hour to under 5 minutes. The shift to an API-first approach future-proofed their strategy. Find out how this local government innovated without disruption. Metcash: Peak Retail Performance, Zero Downtime After moving to Azure Integration Services, Metcash, an Australian wholesaler, processed 8.65 million API calls in 48 hours during a major retail event without a single minute of downtime. With Azure, they achieved unrivaled resilience and scalability, all while slashing costs. See how Metcash’s transformation can serve as your blueprint for success. What You’ll Learn: How to cut costs and modernize your integration landscape Ways to scale with cloud-native solutions and AI-driven automation Strategies to secure every API with enterprise-grade governance Real-world migration paths from BizTalk and other platforms Choose Your Region and Register Now US/Canada: Reserve your seat today! Day 1: Tuesday, 29 April 2025 | 9:00 AM – 12:30 PM PDT Day 2: Wednesday, 30 April 2025 | 9:00 AM – 12:30 PM PDT Australia/New Zealand: Reserve Your Seat Today! Day 1: Wednesday, 30 April 2025 | 9:00 AM – 12:30 PM AEDT Day 2: Thursday, 1 May 2025 | 9:00 AM – 12:30 PM AEDT Europe: Reserve Your Seat Today! Day 1: Tuesday, 29 April 2025 | 9:00am – 12:30pm BST Day 2: Wednesday, 30 April 2025 | 9:00am – 12:30pm BSTSumming it up: Aggregating repeating nodes in Logic Apps Data Mapper 🧮
Logic Apps Data Mapper makes it easy to define visual, code-free transformations across structured JSON data. One pattern that's both powerful and clean: using built-in collection functions to compute summary values from arrays. This post walks through an end-to-end example: calculating a total from a list of items using just two functions — `Multiply` and `Sum`. 🧾 Scenario: Line Item Totals + Order Summary You’re working with a list of order items. For each item, you want to: Compute Total = Quantity × Price Then, compute the overall OrderTotal by summing all the individual totals 📥 Input { "orders" : [ { "Quantity" : 10, "Price" : 100 }, { "Quantity" : 20, "Price" : 200 }, { "Quantity" : 30, "Price" : 300 } ] } 📤 Output { "orders" : [ { "Quantity" : 10, "Price" : 100, "Total" : 1000 }, { "Quantity" : 20, "Price" : 200, "Total" : 4000 }, { "Quantity" : 30, "Price" : 300, "Total" : 9000 } ], "Summary": { "OrderTotal": 14000 } } 🔧 Step-by-step walkthrough 🗂️ 1. Load schemas in Data Mapper Start in the Azure Data Mapper interface and load: Source schema: contains the orders array with Quantity and Price Target schema: includes a repeating orders node and a Summary → OrderTotal field 📸 Docked schemas in the mapper 🔁 2. Recognize the repeating node The orders array shows a 🔁 icon on <ArrayItem>, marking it as a repeating node. 📸 Repeating node detection 💡 When you connect child fields like Quantity or Price, the mapper auto-applies a loop for you. No manual loop configuration needed. ➗ 3. Multiply Quantity × Price (per item) Drag in a Multiply function and connect: Input 1: Quantity Input 2: Price Now connect the output of Multiply directly to the Total node under Orders node in the destination. This runs once per order item and produces individual totals: [1000, 4000, 9000] 📸 Multiply setup ➕ 4. Aggregate All Totals Using Sum Use the same Multiply function output and pass it into a Sum function. This will combine all the individual totals into one value. Drag and connect: Input 1: multiply(Quantity, Price) Input 2: <ArrayItem> Connect the output of Sum to the destination node Summary → OrderTotal 1000 + 4000 + 9000 = 14000 📸 Sum function ✅ 5. Test the Output Run a test with your sample input by clicking on the Open test panel. Copy/paste the sample data and hit Test. The result should look like this: { "orders": [ { "Quantity": 10, "Price": 100, "Total": 1000 }, { "Quantity": 20, "Price": 200, "Total": 4000 }, { "Quantity": 30, "Price": 300, "Total": 9000 } ], "Summary": { "OrderTotal": 14000 } } 🧠 Why this pattern works 🔁 Repeating to repeating: You’re calculating Total per order 🔂 Repeating to non-repeating: You’re aggregating with Sum into a single node 🧩 No expressions needed — it’s all declarative This structure is perfect for invoices, order summaries, or reporting payloads where both detail and summary values are needed. 📘 What's coming We’re working on official docs to cover: All functions including collection (Join, Direct Access, Filter, etc.) that work on repeating nodes Behavior of functions inside loops Real-world examples like this one 💬 What should we cover next? We’re always looking to surface patterns that matter most to how you build. If there’s a transformation technique, edge case, or integration scenario you’d like to see explored next — drop a comment below and let us know. We’re listening. 🧡 Special thanks to Dave Phelps for collaborating on this scenario and helping shape the walkthrough.🔁 Public Preview Refresh: More Power to Data Mapper in Azure Logic Apps
We’re back with a Public Preview refresh for the Data Mapper in Azure Logic Apps (Standard) — bringing forward some long-standing capabilities that are now fully supported in the new UX. In our initial announcement, we introduced a redesigned experience focused on usability, error handling, and improved mapping for complex schemas. As we continue evolving the tool, we’re working to bring feature parity with the classic experience, while layering in modern enhancements along the way. With this update, several existing capabilities from the legacy Data Mapper are now available in the new preview version — so you can bring your advanced scenarios forward with confidence. 🛠️ Run XSLT Inside Your Data Map The ability to apply XSLT has long been a powerful feature in Logic Apps, and we’re excited to bring Run XSLT support into the new UX. You can now invoke reusable transformation logic from your map, including: Enterprise-grade XSLT Predefined templates or logic from your BizTalk workflows How to try it out: Create a new data map. Right-click on the MapDefintions or Maps folder and click Create new data map Store the XSLT file under Artifacts -> DataMapper/Extension -> InlineXslt. Open the data map and search for Run XSLT in the functions panel. Select the function and simply select the function you want to run from the dropdown Connect to desired destination node. In my case, the function simply adds a "Placeholder" value for the Name node at destination, alongside an "EmployeeType" node. Note that you do not need to connect any source node to the XSLT function given this is custom XSLT logic that will be applied directly at destination node. Upon testing the map, right value is generated in the destination schema 🔍 Execute XPath to Extract Targeted Values Execute XPath is now supported in the new experience, giving you control to extract specific values from nested XML structures. This function is particularly useful for: Accessing attributes and nested elements Applying logic based on the structure or content of incoming data How to try it out: Search for Execute XPath in the functions panel. Select the function and add the expression you want to extract Map it to destination node. Here is what the map will look like: The test payload correctly creates multiple Address nodes at destination based on the Address node at source. 🧩 Use Custom XML Functions Custom XML functions allow you to define and reuse logic across your map. This helps reduce duplication and supports schema-specific transformations. Now that support is available in the new UX, you can: Wrap complex logic into manageable components Handle schema-specific edge cases with ease How to try it out: Add the .xml function file under Artifacts -> DataMapper/Extension -> Functions Open the data map and under Utility category of functions, select the new function. In our case, the xml function is called Age Connect function input to Date_of_Birth node at source and output to Age node at destination. The map will look something like this Test the map and notice that the age is calculated correctly at the destination node 🌒 Dark Mode Support in VS Code The new UX now respects Dark Mode in VS Code, giving you a visually cohesive and low-contrast authoring experience — perfect for long mapping sessions. No extra steps needed — Dark Mode works automatically based on your VS Code theme settings. ⚙️ How to Enable the New Experience If you haven’t yet tried the new UX: Open your Logic Apps (Standard) project in VS Code Go to Logic Apps (Standard) extension → Settings → Data Mapper Select Version ~2 You’ll find detailed walkthroughs in the initial preview announcement blog. 💬 We’d Love Your Feedback We’re continuously evolving the Data Mapper, and your feedback is key to getting it right — especially as we bring more advanced transformation scenarios into the new experience. 👉 Submit your feedback here 🐛 Found an issue or have a specific feature request? Let us know on GitHub Issues Thanks again for being part of the journey — more updates coming soon! 🚀Announcing the BizTalk Server 2020 Cumulative Update 6
The BizTalk Server product team has released the Cumulative Update 6 for BizTalk Server 2020. The Cumulative Update 6 contains all released functional and security fixes for customer-reported issues for BizTalk Server 2020. Also, CU6 includes support for the following new Microsoft platforms: Microsoft Windows Server 2022 Microsoft SQL Server 2022 Microsoft Windows 11 BizTalk Server 2016 is currently out of support with its end of life in 2027. If you are running BizTalk 2016, or earlier versions of the product, you must upgrade to BizTalk Server 2020 CU6 or strongly consider migrating to Azure Logic Apps. Please fill this survey: https://aka.ms/biztalklogicapps. More Information about the CU6: This cumulative update includes all the product components. However, only those components that are currently installed on the system are updated. This CU6 includes fixes for the following areas: BizTalk Server Adapters Updates WCF-SAP adapter SFTP adapter BizTalk Server Administration Tools and Management APIs Lost changes to SQL Server Agent jobs You can obtain the software from the Microsoft Download Center, at https://aka.ms/BTS2020CU6. For more information about the BizTalk Server 2020 CU6, read the Microsoft Knowledgebase article posted to https://aka.ms/BTS2020CU6KB.
An Automated Tool for Collecting PSSDiag BizTalk Traces Using Event Logs
Often, users encounter intermittent event log errors from BizTalk that require further investigation using a BizTalk PSSDiag trace. However, since the timing of the next occurrence is unpredictable, troubleshooting becomes challenging. In such scenarios, a tool is needed to continuously collect PSSDiag traces until the error reoccurs, at which point the tool can automatically stop tracing and save the output. To address this need, I’ve developed a tool that automates this process based on user requirements. PSSDiag for BizTalk is a specialized diagnostic data collection tool tailored for troubleshooting BizTalk Server environments. Built as an extension of PSSDiag (Product Support Services Diagnostics), a widely used tool for diagnosing Microsoft SQL Server issues, it collects a comprehensive set of logs and diagnostic data specific to BizTalk. This includes information crucial for identifying and resolving performance, connectivity, or configuration issues. The tool runs from a console interface, and data collection can be stopped manually by pressing Ctrl+C. I have developed a console application PSSDiagCollector that launches PSSDiag to monitor the event log and automatically stops the PSSDiag collection once a specific event is detected. You can download the tool from this GitHub repository: https://github.com/huidongl/PSSDiagCollector The PSSDiagCollector.exe must be saved in the same folder as PSSDiagForBizTalk. Users can open a command prompt, navigate to the PSSDiagForBizTalk directory, and run PSSDiagCollector from there. The command can specify the Event ID, Event Source, or Event Type to capture, as well as the number of events required to stop the collection. Additionally, users can set a delay (in seconds) before stopping the trace. Detailed instructions for using the tool to collect PSSDiag BizTalk traces can be found in the repository. Run the following command to begin the collection: PSSDiagCollector.exe -eid <EventID> -c <EventCount> -p <PauseDuration> -es "<EventSource>" -lc "<LogCategory>" For example: PSSDiagCollector.exe -eid 7195 -c 3 -p 30 -es "BizTalk Server" -lc "Application" Please make sure to configure the Trace Type, Keep the last _ trace files in the Initialize.exe before running this tool to avoid the trace file being filled up.
