What is your primary use case for Microsoft Azure Logic Apps?

I am a monitoring engineer and primarily use Logic Apps as part of the monitoring integration project. It is leveraged for orchestrating different tasks and recognizing Azure Monitor alerts to build data pipelines.

I use the solution in my company for some of our internal projects. We have some workflows defined for which we felt Microsoft Azure Logic Apps would be the best suited because it requires an approval process. Once the approval is given, some keys are given to the users, and those are temporary keys, after which Microsoft Azure Logic Apps makes sure that after a certain period of time, maybe a few days, those keys are removed from the system.

I use the solution in my company as a part of the centralized landscape where we have it for the internal connectivity before any traffic comes in, so we use it for a safe API management gateway. Microsoft Azure Logic Apps is the main tool for API management. It is used to manage our main workflow. The reason for using the tool is that our company has not restricted itself to one tool. We have an integration board that decides based on the use cases because we have multiple technologies. Earlier, MuleSoft was used, and now we have Azure and OpenText, depending on the use case. If the use case involves file mover, then we move that piece of integration to file mover part. If there are any workflows or any processing required, any business logic is involved, and if there is any real-time stuff involved, then we go for Microsoft Azure Logic Apps. If there is a batch processing part, we go for real-time services again within Microsoft.

At our company, we validate certain configurations of the Microsoft Azure Logic Apps based on the security posture and some other factors. We check how Microsoft Azure Logic Apps are deployed and whether the configuration of the solution is appropriate as per the customer needs of our organization. At our company, we also check if Microsoft Azure Logic Apps are being configured as per the standard policies. Our organization oversees the architecture and provides consultation on whether the configuration of Microsoft Azure Logic Apps is correct and what changes or updates are needed. The use cases of Microsoft Azure Logic Apps depend upon the application design. In our company, we overview the architecture and check the functionality. Our organization checks whether the configurations and settings of the apps using Microsoft Azure Logic Apps are properly designed or not. For instance, suppose there is a Logic App that is used in one of the applications, and there is a diagnostic setting. For the aforementioned app, at our company, we need to check whether the workflow, runtime and diagnostic events are logged properly. As part of the app properties, our company often check whether a connection stream is being used and whether it's summoned by the Azure Key Vault or not.

We use Azure Logic Apps for orchestration and as a workflow engine. It's more about building and managing workflows. For instance, the tool can create a single integration that aggregates data from various sources. This capability is one advantage Azure has over solutions like MuleSoft.

Microsoft Azure Logic Apps' main use case is workflow. Depending on your needs, many available connectors allow you to configure it with different systems, whether on-premises or in the cloud. They start with a trigger and then execute steps one by one. Just as we use features in Excel, the tool can manage different tasks and handle various data formats.

We mostly work with Power Automate, but we do have some experience with Logic Apps. For example, if a user makes a request and we need to process their data, we can easily develop an Azure Logic App for that. Sometimes, we combine Power Automate and Logic Apps. For example, a user wants to view specific data and sends a request. We can easily collect that data using Azure, along with a combination of Power Automate and Logic Apps where appropriate. We use Power Automate for external interactions and have it call Logic Apps within our application.

We use the solution to integrate other systems like SAP and Salesforce for orchestration and the API. We also use it to automate business processing and balancing workflows.

Microsoft Azure Logic Apps is a fantastic suggestion, especially for those who may not have extensive coding knowledge but understand the requirements well. It provides an easy way to create an auto-response solution. For instance, if you have services running in Azure and want to generate an alert, it allows you to integrate seamlessly. You can trigger tasks based on alerts, creating multi-layered tasks with loops, conditions, and more. It will enable you to perform multiple actions.

We mainly use Azure Data Factory, Azure Synapse, Synapse Analytics, Data Lake storage, and Azure Databricks. I mainly use Microsoft Azure for services on the cloud. We're trying to create an Azure Data Transfer Layer (DTL) tool directly in the cloud environment. We usually solve complex use cases with Azure Data Factory or notebooks. So, we haven't used Logic Apps extensively. We used Logic Apps to return notifications and push them from Logic App to data lake storage. That's the kind of functionality we achieved through Logic Apps.

We use the solution for orchestration and workflow to execute all the processes manually.

It's a project management tool that primarily focuses on database integration.

We use the product for internal data transfers. It has replaced Data Factory in our organization because of the complexity of the data transfers.

We use Microsoft Azure Logic Apps for building an insurance product. We integrate multiple solutions using it.

For one of the projects that we used, this solution dealt with SharePoint and Power apps. So there, we have to do some kind of connectivity and calculations on the fly. It was related to reading a file and our heavy processing. That was one scenario. There have been a few others as well.

Azure comes into the picture when the client is already using Azure and they are migrating PeopleSoft to the Oracle XCM Cloud. They wanted to utilize the existing system, as they already have Azure as a middleware. Thus, they preferred to continue with Azure rather than adopt another platform. In this scenario, we used Azure Logic Apps to transform their requests and facilitate the interaction within their cloud journey from PeopleSoft to Oracle and vice versa. We employed Azure Logic Apps as middleware since the client was already utilizing Azure for various platforms. We used Azure Logic Apps for integration purposes, including calling REST services, short services, transferring DB calls, and handling data load into tables based on the design. Most of our clients are already using Azure, and they tend to choose it for cost considerations as they already have licensing for Azure or AWS. So we seek solutions that can be cost-effective while integrating with other SaaS services like Oracle SaaS. That's how we handle integration in such scenarios.

Logic Apps are used for integration. We use Azure Data Factory (ADA) for most cases, but in a few instances, we'll go with Logic Apps if ADA is not sufficient. The use cases are very limited. But for a few specific things, especially when we want to integrate with .NET web applications, we'll go with Azure Logic Apps.

You need to have a simple algorithm to use logic apps. We do not use the tool for complex scenarios.

Our use case of Azure Logic Apps is for the integration of data coming from different sources to the manager. We are Microsoft partners and I'm the company director.

I've got a few use cases. I have one use case where I read emails from an inbox, and then I process files in the attachments of that email. I also read from a database on-premise with an on-premise integration. I'm not sure what it's called, however, it was really easy to set up, and I could access the on-premise database in my Azure Cloud and then talk to the Logic App from my Azure web application. There's another use case where I read from a database and create a file in a file storage account.

Our company uses the solution for small use cases like transformations or doing an additional call to get extra information and enrich data.

There are two ways to use this solution. Firstly, you can connect Azure to other solutions like Jira. It automatically populates all the services. Secondly, once you are logged in, you can create your own resource group and see all these services. We have 12 teams using this solution.

We are using Microsoft Azure Logic Apps for SOC automation. It is the security operation center for automation related to security operations that we use.

We use Microsoft Azure Logic Apps to do a lot of workflows and from different areas. For example, connecting to web services, and websites, triggering based on certain conditions.

We use this solution for integration. It is deployed on cloud. We have about 50 people using this solution.

The use case depends on the situation. We primarily use this solution to schedule time-based event triggers. Sometimes, we use it for the simple starting of machines or automating the start of certain machines. It can be set up on a timer or some sort of time-based event trigger that we need to schedule, and the trigger is set up for certain logic.

We use the solution for data extraction and transformation.