Introduction ARM templates follow the Desired State Configuration (DSC) pattern. This means that the ARM template describes what the desired Azure infrastructure should look like. When an ARM template is applied to an Azure environment, the differences between the template and the current state are calculated and applied. The end result is an environment that conforms to the ARM template. While this is true for many of the Azure resources, it may not always be true for properties of ARM resources.
Microsoft Flow and Azure Logic Apps are based on the same platform and therefor very similar. There are, however, cases where they’re a little different. Take for example the Apply to each (Flow) action and the For each (Logic Apps) action. They’re very similar in that they execute the actions for each of the items in the array. There’s one caveat though and that is the default concurrency setting. Apply to each action
We’re living in the decade of the rise of conversational platforms like chatbots. Gartner predicts that by 2022 over 70% of modern workers use conversational platforms on a daily basis. Chatbots are around for many years, even dating back to 1966, with fluctuating interest over time. The last few years we see a big increase of excitement for chatbots with artificial intelligence (AI) becoming mainstream. The use of AI enables chatbots to better understand natural language and be able to more intelligently respond to users.