When you create flows you could store data in SharePoint or in CDS and Microsoft Flow will give you easy actions to create new items. But what if you want to store data in Azure. There are quite a few different options possible. In this post I will compare the options. When you look at … Continue reading 7 options to store data in Azure with Microsoft Flow
After yesterday's post 5 reasons to use Azure LogicApps instead of Microsoft Flow you might have thought that I switched to using Azure LogicApps instead of Flow. Wrong! In this post I'm going to give 10 reasons to use Flow instead of LogicApps. Reason 1 - PowerApps integration When you use PowerApps and call flows … Continue reading 10 reasons to use Microsoft Flow instead of Azure LogicApps
Today I tried to create an Azure Logic app that creates a message in a Channel within a Microsoft Teams team. This was amazingly easy. But then the trouble started. I wanted everybody to receive an alert using the Mentions in Microsoft Teams. My team name is Triad.Microsoft.Development so @Triad.Microsoft.Development should work. Even the code … Continue reading Microsoft Teams – Azure Logic Apps – Don’t mention it!
Within my Office 365 environment I've got quite a few options when I want to develop workflows. The two options that I'm looking at in this post are Microsoft Flow and Azure Logic Apps. Both interfaces are quite similar. Looking at the trigger "When an item is created in SharePoint", the options are quite similar: … Continue reading Office 365 – Workflow options – Azure Logic Apps vs Microsoft Flow