<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Logic Apps on blog.atwork.at</title><link>https://blog.atwork.at/tags/logic-apps/</link><description>Recent content in Logic Apps on blog.atwork.at</description><generator>Hugo -- 0.153.4</generator><language>en-us</language><lastBuildDate>Tue, 07 Jan 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.atwork.at/tags/logic-apps/index.xml" rel="self" type="application/rss+xml"/><item><title>Streamlining Automation Integrating Scripts with Logic Apps</title><link>https://blog.atwork.at/post/2025/integrating-scripts-with-logic-apps/</link><pubDate>Tue, 07 Jan 2025 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2025/integrating-scripts-with-logic-apps/</guid><description>Calling scripts from an Automation Account in a Logic App is particularly useful when the tasks to be performed are too complex to implement directly in a Logic App. It is also useful when scripts need to be reused multiple times without rewriting them in each Logic App. See how to enhance your Logic Apps with Automation Account Scripts.</description></item><item><title>Azure Logic Apps Toolbox 10-Dynamic access to keys and values in a JSON object</title><link>https://blog.atwork.at/post/2024/azure-logic-apps-toolbox-10-dynamic-access-to-objects/</link><pubDate>Sat, 01 Jun 2024 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2024/azure-logic-apps-toolbox-10-dynamic-access-to-objects/</guid><description>In Azure Logic Apps, looping through objects is a common requirement. When we have prior knowledge of an objects properties, the process is straightforward. However, things get more challenging when attempting to access properties dynamically. See a method to access data in a JSON object dynamically here.</description></item><item><title>Azure Logic Apps Toolbox 9-More useful Tips</title><link>https://blog.atwork.at/post/2023/azure-logic-apps-toolbox-9-more-useful-tips/</link><pubDate>Thu, 05 Oct 2023 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2023/azure-logic-apps-toolbox-9-more-useful-tips/</guid><description>By working with Azure Logic Apps, data can be processed very quickly and conveniently. Sometimes small details are a challenge, like function names or correct syntax. This is especially true if you dont work with logic apps all the time. In addition to our existing tips here in the blog, we have some other useful functions from various scenarios that will make your work with Logic Apps easier.</description></item><item><title>Why we need the Power Platform</title><link>https://blog.atwork.at/post/2022/why-power-platform/</link><pubDate>Sun, 24 Jul 2022 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2022/why-power-platform/</guid><description>Today, a quick tip on an article about one of Microsofts fastest growing companies Helping power users to build business apps with low-code and no-code apps.</description></item><item><title>Azure Logic Apps Toolbox 8-Secure your secrets with Azure Key Vault and Managed Identity</title><link>https://blog.atwork.at/post/2022/azure-logic-apps-using-key-vault-and-managed-identity/</link><pubDate>Sun, 24 Apr 2022 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2022/azure-logic-apps-using-key-vault-and-managed-identity/</guid><description>Credentials and secrets should be stored in a secure environment and not directly in an Azure Logic App or script. Azure provides the Key Vault service, which allows to store such secrets in a secure and controllable way. See how this works here.</description></item><item><title>Azure Logic Apps Toolbox 7-Resolve issues with the SharePoint Connector</title><link>https://blog.atwork.at/post/2021/sharepoint-connector-and-azure-logic-apps/</link><pubDate>Thu, 11 Mar 2021 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2021/sharepoint-connector-and-azure-logic-apps/</guid><description>Using SharePoint Online SPO and Azure Logic Apps helps to automate processes. For a project, we have created some workflows with Azure Logic Apps that monitor changes to an SPO list or document library for approvals and other document workflows. We have found that the SPO connector does not always send all data in a reproducible manner sometimes some fields were sent and sometimes not. We struggled with this behavior and found an unexpected workaround.</description></item><item><title>Azure Logic Apps Toolbox 6-Work with items in Apply to each</title><link>https://blog.atwork.at/post/2021/apply-to-each-in-flow-and-azure-logic-apps/</link><pubDate>Sat, 06 Mar 2021 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2021/apply-to-each-in-flow-and-azure-logic-apps/</guid><description>Automation of small tasks is helpful for many recurring processes. Unless you regularly use Power Automate Flow or Azure Logic Apps, it is often not that easy to remember the correct syntax for accessing items in a loop. Here is the quick help.</description></item><item><title>Azure Logic Apps Toolbox 5-Custom JSON payloads</title><link>https://blog.atwork.at/post/2021/use-azure-logic-apps-custom-json-payloads/</link><pubDate>Thu, 14 Jan 2021 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2021/use-azure-logic-apps-custom-json-payloads/</guid><description>Did you ever have the problem of pushing different JSON payloads to a logic app and hitting errors due to JSON schema mismatches? The usual HTTP Request forces you to define the JSON Schema at the beginning. For every tiny difference in the later used properties you need to create your own Logic App even if the process is the same. I will show you an example of a single Logic App deciding at runtime which JSON schema to use for decoding the post body payload. Stay tuned!</description></item><item><title>Azure Logic Apps Toolbox 4-Working with SharePoint dropdown fields</title><link>https://blog.atwork.at/post/2020/sharepoint-dropdown-fields-in-azure-logic-apps/</link><pubDate>Fri, 18 Dec 2020 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2020/sharepoint-dropdown-fields-in-azure-logic-apps/</guid><description>Yesterday I documented in Get data from SharePoint as HTML table with Azure Logic Apps how data is retrieved from SharePoint Online with an Azure Logic app. To dig a little deeper into working with SharePoint list data, here are a few more helpful tips.</description></item><item><title>Azure Logic Apps Toolbox 3-Get data from SharePoint as HTML table</title><link>https://blog.atwork.at/post/2020/azure-logic-apps-get-data-from-sharepoint-as-html-table/</link><pubDate>Thu, 17 Dec 2020 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2020/azure-logic-apps-get-data-from-sharepoint-as-html-table/</guid><description>Sometimes its good to get data from a data source as a table and as quickly as possible in an automated way. While this can be done with multiple ways, heres a quick solution if you want to get the items from a custom list in SharePoint Online sent as a HTML table in an email with Azure Logic Apps or Power Automate.</description></item><item><title>Azure Logic Apps Toolbox 2-Send text and files multipartform-data to SharePoint Online</title><link>https://blog.atwork.at/post/2020/send-multipart-form-data-to-azure-logic-apps/</link><pubDate>Mon, 17 Feb 2020 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2020/send-multipart-form-data-to-azure-logic-apps/</guid><description>Using an Azure Logic app is often a quick fix for small computing tasks. So my scenario is as follows I want to use a form on a website to offer text fields and file upload. The submit button is intended to send the data to a Logic App. The Logic App receives the data and writes it to a SharePoint Online list and sends a notification if necessary. See the implementation here.</description></item><item><title>Azure Logic Apps Toolbox 1-Use the OData Filter for Azure SQL Databases</title><link>https://blog.atwork.at/post/2019/azure-logic-apps-with-odata-filter/</link><pubDate>Thu, 19 Sep 2019 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2019/azure-logic-apps-with-odata-filter/</guid><description>A very quick tip today When using an Azure Logic App in combination with an Azure SQL Database, filtering rows can be done like here.</description></item><item><title>Working with Microsoft Group Forms and Flow</title><link>https://blog.atwork.at/post/2019/working-with-microsoft-group-forms-and-flow/</link><pubDate>Sat, 13 Jul 2019 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2019/working-with-microsoft-group-forms-and-flow/</guid><description>Microsoft Forms is very popular because it is a very easy way to create web forms quickly. You can create surveys, quizzes and simple forms, and easily see results as they come in. This quick tutorial shows how you can use Microsoft Forms, convert it to a group form, how you can access the result file and how to add additional tasks with Microsoft Flow or Azure Logic Apps.</description></item><item><title>Having fun with IoT Flic buttons and Microsoft Flow</title><link>https://blog.atwork.at/post/2019/having-fun-with-iot-flic-buttons-and-flow/</link><pubDate>Wed, 27 Mar 2019 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2019/having-fun-with-iot-flic-buttons-and-flow/</guid><description>I just got a cute Flic button to play around with. It takes only some minutes to connect that IoT button to a connector and execute customs tasks. Well, as first step, I simply created a message in a Microsoft Teams channel. See the step-by-step instructions here.</description></item><item><title>Groups Governance Toolkit Part 4-Ownerless Groups</title><link>https://blog.atwork.at/post/2019/groups-governance-toolkit-part-4-orphaned-groups/</link><pubDate>Wed, 13 Feb 2019 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2019/groups-governance-toolkit-part-4-orphaned-groups/</guid><description>In this multi-part series we show you how to handle the Office 365 Groups and Microsoft Teams governance toolkit. The next article cover the governance part of our Groups Governance Toolkit.Imagine your company policy requires at least 2 owners per Office 365 Group or per Microsoft Team. In this part, we want to monitor all groups that are ownerless orphaned, or do not comply with our organizations policies. The IT department shall get the information of all groups and teams where there are no owners or not enough owners and the possibility to fix that. Read below how this can be accomplished.</description></item><item><title>Groups Governance Toolkit Part 3-Develop Azure Functions</title><link>https://blog.atwork.at/post/2019/office-365-groups-governance-toolkit-part-3-azure-functions/</link><pubDate>Wed, 16 Jan 2019 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2019/office-365-groups-governance-toolkit-part-3-azure-functions/</guid><description>After the introduction of the Office 365 Groups and Microsoft Teams Governance Toolkit and with the necessary requirements we are now looking into Azure Functions. In our group and team provisioning scenario, we need a little code for provisioning of an Office 365 group and a Microsoft team. Serverless computing with an Azure Function provides the optimal solution for that. Follow these steps to create the function we need for our workflow.</description></item><item><title>Groups Governance Toolkit Part 2-Provisioning requirements</title><link>https://blog.atwork.at/post/2019/office-365-groups-governance-toolkit-part-2-provisioning-requirements/</link><pubDate>Fri, 11 Jan 2019 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2019/office-365-groups-governance-toolkit-part-2-provisioning-requirements/</guid><description>In part 1 of this series we described the scenario for our Office 365 groups governance toolkit. In this part we will setup a workflow for the Office 365 and Microsoft Teams provisioning. Workflows help to follow specific processes for a successful collaboration. Offering self-services for users is a key to reduce workloads on the IT department and to allow users to cover their requirements quickly while the organizations policies are enforced during the process. A frequently asked request is how to provision a new Microsoft Team in Office 365 in a secure and monitored way. See how this can be implemented here. To allow an app to create a Microsoft group or team programmatically in a workflow, we will use the Microsoft Graph API, Azure Functions and Flow or Logic Apps. With these technologies, we can create powerful workflows to offer a self-service for users to create a team when needed, approved by the manager and being provisioned with all the necessary properties and permissions.</description></item><item><title>Groups Governance Toolkit Part 1-Overview</title><link>https://blog.atwork.at/post/2019/office-365-groups-governance-toolkit-part-1-overview/</link><pubDate>Tue, 08 Jan 2019 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2019/office-365-groups-governance-toolkit-part-1-overview/</guid><description>IT-Governance is an important topic, especially in large organizations. At Microsoft Ignite conference, we showed the Groups Governance Toolkit with a bunch of useful tools to regulate and monitor Office 365 groups and Microsoft Teams. Here, we will show the step-by-step guidance how to implement that toolkit with Microsoft 365 and Microsoft Azure. Lets start with an overview what topics we cover in this article series.</description></item></channel></rss>