Apr 5
Friday Fact: Workflow and Trigger expressions can help monitor your Logic Apps.
Indeed, simplicity often proves to be the most effective approach This holds true, particularly in the context of using the workflow expression alongside the
Apr 4
Logic App Best Practices, Tips, and Tricks: #42 How to convert JSON into XML inside Logic Apps
Welcome again to another Logic Apps Best Practices, Tips, and Tricks In my previous blog posts, I discussed a basic trick for developers that was to
Apr 3
Logic App Best Practices, Tips, and Tricks: #41 How to convert XML into JSON inside Logic Apps
Welcome again to another Logic Apps Best Practices, Tips, and Tricks In my previous blog posts, I discussed one good trick for administrators Today we
Mar 25
Logic App Consumption deployment: The secret of KeyVault parameter cannot be retrieved. Http stat...
Recently, a client asked me for help rectifying some existing logic apps in their environment because their resource had left the company Not only to rectify
Mar 22
Friday Fact: Existing Logic Apps with Service Bus trigger using peek lock cannot be changed from ...
Azure Service Bus stands out in cloud-based messaging services as a reliable and scalable solution that facilitates asynchronous communication between
Mar 15
PowerShell script to identify all SQL V1 actions and triggers inside Logic Apps Consumption
A few days ago, Luis Rigueira created a Kusto query to identify all Logic Apps Consumptions that use SQL V1 actions and triggers that will soon be deprecated
Mar 15
Friday (funny) Fact: There is no size limit for the Logic App parameter name
In Azure Logic Apps, you can abstract values that might change in workflows across development, test, and production environments by defining parameters
Mar 14
Logic Apps Consumption SQL Connector version 1 Actions/Triggers will be deprecated!
Microsoft has announced that Version 1 Actions/Triggers of the SQL Connector for Logic Apps will be deprecated by the end of March 2024 In response, we have
Mar 8
Friday Fact: Logic Apps don’t interpret escaped characters as plain text, even inside a str...
In the realm of Logic Apps, the treatment of escaped characters differs from handling plain text Let's look into a scenario were understanding special
Mar 1
Friday Fact: When a HTTP Request is Received trigger can accept more http methods other than POST
Diving into Logic Apps, it's a common oversight to assume that only POST requests can be use when using the "When a HTTP request is received" trigger However,
