Microsoft Azure
Microsoft announced that the PowerShell Gallery has deprecated Transport Layer Security (TLS) versions 1.0 and 1.1 as of April 2020. This means you suddenly can’t run Install-Module anymore. You will have to run a specific Powershell command to fix the issue:
When exposing an Azure Function via API Management, the most important thing to remember is that each function has a function key that can be dynamically retrieved via function listsecrets. To make the function deployment work, you will have to add an application Setting AzureWebJobsSecretStorageType=Files to your FunctionApp.
Two important unit tests you might want to perform in your Azure project are related to maps and reusable functions. Either use the Microsoft Test Framework or XUnit for .Net Core.
For the XML fans among us. How do you validate a datetime field that can be empty? How can you use an XSLT to set a datetimefield to the inout datetime or the current datetime (when empty).
You can’t directly test against null or undefined in a Logic App, but you can try a work-around using coalesce (return string value if null).
You can get an overview of logic app runs to find out which logic apps actually failed. Via the sequence number you can lookup the message in the servicebus.
You can use Serverless360 to execute a number of tasks on a servicebus queue or topic. You can for instance edit messages and perform a manual or automated resubmit.
Managing and monitoring of iPaaS applications via the Azure Portal only is often not enough. Via the Azure Portal, we can get insights into a single logic app or servicebus, but we will not have an overview of the entire process. Serverless360 formerly actually fills the gap. It allows for monitoring at the application level as well as a consolidated monitoring view.
Larger amounts of messages quickly lead to an overload of messages. The solution is to dispense the message load by replacing Azure Event Grid messaging by Azure Service Bus messaging.
You can implement exception handling in Logic Apps via the RunAfter construct at the scope level. When you specify exception handling at the scope level, exception handling is enabled on all contained actions and and an array of failed action responses is returned. That sounds good, but there are a few snags to take into account.