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. Deployed Logic App Designer View Different than Actual Deployed Version

    I found a situation where, if I open the Logic App in the portal designer, I am seeing a very old version of it (which it seemingly would allow me to edit). However, this is not actually the real runtime version. If I go into the history and look at the latest, it reflects what I actually deployed. Additionally, when I execute the workflow and look at the workflow execution details, it is also correct. I am speculating that the potential cause of this is that 1) I first deployed the app from Visual Studio; 2) I edited the app,…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Management  ·  Flag idea as inappropriate…  ·  Admin →
  2. Simplify subnet definition in ISE Template

    The Resource Manager template for provisioning a Logic App ISE requires an array of Azure resource IDs corresponding to the four Virtual Network subnets to use for the ISE. Currently the subnets must be defined as a JSON object array in the following format:

    [
    {"id":"<resourceId>"},
    {"id":"<resourceId>"},
    {"id":"<resourceId>"},
    {"id":"<resourceId>"}
    ]

    This is a verbose format.

    It would be cleaner, and more compact if the subnet definition could accept a simple array of resource IDs (dropping the "id"). For example:
    [
    <resourceId>,
    <resourceId>,
    <resourceId>,
    <resourceId>
    ]

    One good workaround for this for now is https://github.com/Azure/azure-quickstart-templates/tree/master/201-integration-service-environment

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. Sort the list of actions in the Azure portal's Logic App run blade...

    based on the dependsOn values (not alphabetically as it is today). For actions with multiple dependent child actions, sort those alphabetically or some other way, but continue to group dependent child actions together.

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

Logic Apps

Categories

Feedback and Knowledge Base