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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. BizTalk Server Conume API App Swagger Metadata

    We will see all of these great new API apps being created that support SaaS Connectivity. We do know there will be some lag before we have symmetry between Cloud and on-prem offering. We also have BizTalk migration stories to deal with.

    In the interim, why not allow BizTalk Server to consume API App Swagger meta data so that we can also plug into this connector eco-system in the mean time? Also allows existing customers to leverage existing investments during this time of transition.

    From customer perspective it allows them to pay a little to get incremental value while realizing…

    139 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  2. Read a csv file and bulk load into Azure SQL table

    I would like to read in a file from blob and add a row to a table in Azure SQL server. It would be nice to have a bulk import like bcp but also be able to add new rows as the file grows.

    126 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Connectors  ·  Flag idea as inappropriate…  ·  Admin →
  3. Logic app service bus message trigger.

    Currently logic app service message trigger should poll every 1 mins to check any message exists and every trigger cost the customers and we would like to trigger executed automatically with out polling the trigger every 1 mins whenever message received to queue/topic.

    121 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Connectors  ·  Flag idea as inappropriate…  ·  Admin →
  4. Expose Connectors Swagger definition so an External application could consume and execute the connector

    Have the ability to connect to Azure server and consume a connector.

    Essentially expose the swagger of the connector and allow for the connector to be called from an external system.

    So the external system would call some URL with the right information based on the Swagger definition.

    62 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Connectors  ·  Flag idea as inappropriate…  ·  Admin →
  5. Change the name from Azure Logic Apps to Azure Integration Apps

    I think this simple name change will add clarity to this service. All apps have "logic" in them of some sort. By changing the name to "integration", anyone looking at the service by name can place the capabilities with adapters, transformation and transport. Consider the following for context - it's integration - http://www.enterpriseintegrationpatterns.com/eaipatterns.html

    57 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Office 365 Connector Ignores .msg (email file) attachment in incoming Emails

    The bug is with the Office 365 connector when triggering on new incoming email.

    The issue is when the incoming email contains a .msg file, or Outlook item, as an attachment (read, email has an email as an attachment).

    What I am experiencing is that the connector correctly sets "Has Attachment" as True, even when the email object is the only attachment, but the "Attachments" output is empty.

    When the .msg is the only attachment the output reads as

    "Attachments":[]

    While the .msg attachment is directly ignored from the "Attachments" list if more attachments are included in the incoming mail.

    37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  7. OneDrive / OneDrive for Business Connector 'When a file is created' event not always firing

    I have a Logic App which uses the OneDrive for Business Connector.

    With the 'When a file is created' event, if I specify the root folder ('/') as the Folder property, then upload a file to the root folder, it works fine.

    If I specify any other value, it doesn't fire, and is 'Skipped' in the History tab in Azure Portal.

    The folder I'm wanting to observe is called 'Transcripts'; I have tried:
    * /Transcripts (this is what gets populated if I use the folder picker in Logic App Designer in VS2017)
    * /Transcripts/
    * Transcripts/
    * Transcripts

    This seems…

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  8. is it possible to deploy logic app to App Service Environment

    is it possible to deploy logic app to App Service Environment

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →

    Logic Apps is not part of the App Service infrastructure and cannot be deployed to an ASE. To connect across a VNET the recommended pattern is to either use the on-premises data gateway for on-prem connectors or use API Management which can span VNETs/Express Route.

  9. Workflow Foundation

    Logic Apps should support Workflow Foundation. Have a designer where you create workflows, drag api connectors and components

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Custom Retry policy for the HTTP connector

    Hi,
    Is it possible to have a fine-grained control on retry policies for the HTTP connector to distinguished the use cases related to HTTP errors.
    For example: having a different policy for HTTP 500 error and another retry policy for HTTP error 429, ...

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Connectors  ·  Flag idea as inappropriate…  ·  Admin →

    The built-in retry policy won’t retry non-retry-able errors. Since there are many scenarios where users need to interrogate the content to determine how it should retry we thought it be better to keep the retry policies simple and allow users to utilize the do-until loop for more custom retry decision logic.

  11. Issue with SQL API connector - Some of the connections are not authorized yet.

    I am copying the same issue from another person. This seems to be a new bug.

    My flows connecting to Azure SQL stopped working today as the lost the SQL connectoin I set up. Trying to set the sql connection again I get below error.

    Some of the connections are not authorized yet. If you just created a workflow from a template, please click Continue to add the authorized connections to your workflow before saving.

    I tried re-adding connection multiple times, but can't get pass this

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support for API Connections in custom API Apps

    Provide support for (re)using API Connections in custom API Apps to perform authentication with external services.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Export and Import Rules Service/Engine policies and vocabularies as XML or JSON

    Allow for publishing and remote development/management of Biztalk Rules App Service Policies and Vocabularies via Visual Studio or other source repositories.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Email alias not triggering action

    Hi,

    The initial action within my azure logic app is:

    Office 365 Outlook - When a new email arrives.

    If I put an alias into the TO: field the action is not fired.

    If I put my email address into the TO: field the action is fired.

    I've confirmed the alias is operational by sending/receiving an email.

    Regards,
    Graham

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  15. OneDrive trigger is not coordinating file contents

    In the case other than the txt file, the value is returned as the content in the form of JSON which is thought to be used internally, not the file binary.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  16. Issue with SQL API Connector

    When trying to add a SQL connection in my Logic App, I enter the connection string details but then it throws the following error:

    Please check your account info and/or permissions and try again. Details: Argument out of range
    inner exception: Index and length must refer to a location within the string.
    Parameter name: length
    clientRequestId:

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  17. Bug in Logic App connector to create automation runbook job with boolean parameters

    I have a Logic App that has an "Azure Automation - Create Job" action. This action calls a runbook to fire off some powershell commands to do some tasks to the data warehouse.

    I also have a parameter that the Powershell runbook accepts. That parameter is a Boolean value.

    The Logic App connector that calls the automation runbook has a field for parameters. This connector will pass variables to the runbook, HOWEVER, when passing Boolean values, the connector will only allow "true" and "false", but these are NOT valid values for powershell Boolean values.

    Powershell expects $True, $False, 1 or…

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  18. Can't edit a compose action in the designer - edit disappeared?

    Hi,

    The advanced edit for a compose action has disappeared from the Azure Logic Designer?

    See attached picture.

    The only workaround is to edit or peek the code.

    "Condition_-_was_a_pdf_attached": {
    "actions": {
    "For_each_2": {
    "actions": {
    "Compose": {
    "inputs": "@concat(utcnow('yyyy'), '/', utcnow('yyyyMMdd'),'/', triggerBody()?['Id'], '/', items('For_each_2')?['Name'])",
    "runAfter": {},
    "type": "Compose"

    Can the option be put back int the designer?

    Regards,
    Graham

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  19. Is there any way to trigger logic app without trigger via Workflow Management API?

    I have used the below Workflow Management API(API-Version 2015-02-01-preview) to trigger the logic app

    https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{ResourceGroupName}/providers/Microsoft.Logic/workflows/{WorkflowName}/run?api-version=2015-02-01-preview

    But after GA of logic app above API is deprecated so now new API is
    https://{endpoint}/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/workflows/{workflowName}/triggers/{triggerName}/run?api-version=2016-06-01

    But above API requires the trigger name but my logic apps doesn't contain any trigger.

    So is there any ways i can trigger logic app without trigger via Workflow Management API?

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add flow triggers for flow!

    I would like to see triggers based on flow conditions, and primarily for failed flows

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4
  • Don't see your idea?

Feedback and Knowledge Base