Logic Apps
Logic Apps allow developers to design workflows that articulate intent via a trigger and series of steps, each invoking an App Service API app whilst securely taking care of authentication and best practices like durable execution.
If you have any feedback or ideas on Azure Logic Apps we’d love to hear it.
-
Deploy Logic Apps anywhere I choose
Allow customers to run Logic Apps anywhere they wish, including Azure Stack, on-premises or on the edge.
Renamed from: Bring the power of Logic apps in Azure Stack: Bring the power of Logic apps in Azure stack to automate enterprises internal complex processes and integration using easy orchestration.
324 votes -
Integration with AWS services.
Create connectors to allow integration with AWS services.
Our company is basically moving towards AWS although we still using Azure. AWS currently lacks of any decent Enterprise Integration and would be great if Logic Apps could fill that blank and actually benefit from it.108 votes -
SharePoint Online actions don't display Choice and drop-down site columns
When using the SharePoint Online actions to update SharePoint list items, the choice and drop-down site columns are not showing to update.
Can you please expose these site columns in the action so they can be updated?
26 votes -
Authentication information visible for a Logic App run
I am calling an AAD authenticated web app through one of my logic apps. I didn't face any issue while making request from logic app to the web app.
But, the authentication information that I passed to the web app from logic app gets visible when navigating to the Outputs Link on all Logic App run blade. Please see the attachment for details.I would like those sensitive information to be displayed as *sanitized*, which is the case with outputs link available on an action blade.
20 votesThanks for adding this suggestion.
-
Allow processing of SQL rows into one object/file/email
Currently a dataset from SQL can only result in an action per row ie creates a file per row, add option to iterate/loop through the dataset to create a single file/email/report
19 votes -
Paypal, Netteller PaymenGateways Connectors
It should be a great demand for Connectors for various Payment solutions
15 votes -
Validate input received in http trigger
You can define the json schema of the input in the http trigger.
It would be very convenient if it were possible to for the trigger or the logic app to validate and possibly reject invalid input. This would help make the app much more robust
14 votesThanks for supporting this feature.
-
Get updates (recent changes) from OneNote into Microsoft Flow
It would be great if changes in OneNote are accessible for Microsoft Flow! Based on a change in a Notebook or Section trigger an action in Flow like alerting via email or push notification.
13 votesThanks for your interest in this connector.
-
How can we resubmit only particular action in LogicApp?
Hi,
It would be good if we can resubmit particular action in LogicApp, obviously the actions which are dependent on resubmitted actions will also get resubmitted.
12 votesThanks for your suggestion, this is on our backlog.
-
Add detailed documentation on Dynamic CRM Connector
Need proper documentation on every functionality of the connector and clear examples for Complex requirements like associating entities, finding lookup value etc.
12 votesAgree more documentation for the Dynamics connector is needed.
-
Inline Azure Function with coding UI
I want to have the Azure Function editor/experience inline or inside the Logic Apps designer. I choose which language. You then deploy it while I'm in the designer and I can choose which RG but you keep me in the same region.
I (the user) don't need to even know that it's a Function App
10 votesGreat idea. Thanks for your suggestion.
-
Allow for Draft/Prod versions
Just like Azure Automation Runbooks, I want the ability to have a draft version (same logic app) and a production version.
When I click on "Promote" to production, you make the Prod version a copy of the Draft one.
9 votesThanks for your suggestion.
-
Versioning of Logic Apps for SxS deployments
Enable the versioning and execution of specific version of a logic app to enable SxS execution. Goal is to flight changes for different scenarios and for 'test in production' using canary tenants.
6 votesGreat idea. We have this on our backlog.
-
Database (or Cache) lookup functoids for the mapper with the EIP Tools.
The mapping tool that is currently supplied with the "Microsoft Azure Logic Apps Enterprise Integration Tools for Visual Studio 2015 2.0" doesn't have any functoids** to do code lookups (for code set or reference data translations) during transformations.
Can a functoid (or other option) please be made available to lookup values from an externally maintained data source such as a database or cache?
** Similar to what is available in the [On-prem] BizTalk mapping tool where it provides DB functoids and/or the possibility to call out to a external assemble (such as a C# helper class) which provides a lookup…
6 votesThe mapper action is planning on supporting calling custom functiods.
-
Allow for looping more than 1000 times
ForEach and Split-On functions only allow looping up to 1000 times. Please allow this limit to be increased.
4 votesIncreasing limit in phases – will start by bumping to 5000
-
template to email office tasks daily
Create a template to email office tasks daily
4 votesThere is a template today called “Get daily reminders emailed to you” in the template gallery. Your suggestion of adding more search terms to match the Recurrence trigger is a good idea.
-
Servicebus Connector - Make it easier to manage properties
Some (but not all) properties managed by the transport, known elsewhere as BrokerProperties or BrokeredMessage properties, are added into the Body.Properties object along with customer/custom properties - things like DeliveryCount, LockToken, SequenceNumber etc.
I propose that all Broker-control properties are either kept at the Body level, or given their own wrapper object.
The way it is now makes it difficult to proxy properties through logic as we cannot simply:
"Properties": "@triggerBody()['Properties']"Instead they must be set explicitly:
"Properties": {
"myProperty": "@triggerBody()?['myProperty']"
etc
}
which of course is a very fragile and inflexible approach.(Ok, the first way does work, but…
4 votes -
ARM template for LogicApp able to use dynamic connectors
Would it be possible to create new connectors using ARM template and use them to implement logic apps connections including logic app itself from ARM template, if source folder to watch is in Dropbox account, and destination is FTP.
For example: I already have a connection object in Azure apps, but only folder path to watch needs to be changed from the template as extending pre-existing connection account. Say, I have a connection source to my Dropbox account manually created to '/' folder and any future logic apps via ARM template could utilize this connection object, but the folder watch…
3 votesWe are planning on supporting service accounts to help with ARM deployment scenarios.
-
Runtime access to outputs of previous action
Currently the inputs for actions can be specified only by hard references to named actions or triggers. This severely limits the value of block structures (if-else and scope), since these structure fundamentally allow the plan of executed actions to change at runtime.
Use case 1:
Consider and if/else with an action in each branch that, say obtains data from a different location. There is no way for a subsequent action to refer to the data obtained from the if/else block.Use case 2:
Consider several actions wrapped in a scope, with a dependent "cleanup" action that is started if the…2 votesThanks – item 2 should work now (and we also have an @result() function to get the result of a scope, and item 1 should work too but both require using the workflow definition language. Marking as planned until docs get published on #2 specifically.
-
Expose the properties in the AS2 and X12/EDIFACT captured in tracking db through output
Expose or emit the data captured in the tracking DB for AS2, X12, and EDIFACT at runtime through the output of the services. This would enable an event-driven analytics model without having to introduce some type of sql polling mechanism to generate this data as events. This would include the correlation events that happen within the API Apps.
1 voteWe are planning on enabling this.
- Don't see your idea?