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. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  2. Liquid JSON Transform action allow include tags

    At present the liquid template "include" tag is not supported. Any attempt to use it gives the response:

    "Liquid error: Error - This liquid context does not allow includes"

    Allow the use of the "include" tag for liquid maps.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support Multiple ISA Envelope in on File

    Azure X12 Decode will not support multiple ISA Envelopes sent in one file. BizTalk 2010 can do it: https://docs.microsoft.com/en-us/biztalk/core/enabling-the-receiving-of-multiple-interchanges-in-a-single-message.

    We need to have this function work in Azure.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support ExtensionObjects (external assemblies) when using XML Transform

    For performing the more complex transformations, it would be great to be able to add an external assembly dll to the "Transform XML" action (or to the Map artifact itself in the Integration account), and be able to use it inside the XSLT maps. Like ExtensionObjects in BizTalk. Today we use a workaround that performs the transformation inside an Azure Function or API App, but it would be better design-wise to be able to use ExtensionObjects in the action itself. It would also make migrations from BizTalk to Logic Apps easier.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  5. Increase maximum LogicApp Message size

    I routinely deal with messages >100Mbs in size. In BizTalk this is not a problem, but in Logicapps we are having various problems with connectors, etc. where such messages are not accepted. We are trying to migrate existing solutions to Logic Apps and this size limit is severely impairing our ability to do so. I would suspect other might have the same problem.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  6. SharePoint Online "New site created" trigger

    When a new site is created in SharePoint Online the sites permissions are automatically set to public, so that anyone in the organization can add themselves. We want to know when a new site is created so that our Admins can begin monitoring it, and also we want to programatically change the site permissions to private and send out notifications.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add the ability to throw an Exception.

    You should be able to fail a Logic App on purpose. This way you can build enterprise integration patterns to check responses of other systems and let the Logic App fail if necessary.

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  8. SOAP header support for Logic App Custom Connector

    Some WS need a custom <soap:header>. We need the possibility to define custom soap headers in Logic App Custom Connector.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  9. Resolve EDI Agreement without Qualifiers

    The ReceiverQualifier and SenderQualifier are optional in some EDI files, but to create a Partner is necesary to select a Qualifier value and there isn't the option to select something similar to "<NotValued>" as in BizTalk.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  10. Handle Base64 Encoding

    This: "body": "@base64toBinary(triggerBody()['fileContent'])" Is just ugly. I am picking up an EDI doc from a file system, decoding the doc, and then I want to pass the resulting file to the file system... why do I have to do this? Should be simpler.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  11. Power BI Dataset refresh events

    We want to trigger a Logic App on the successes or failures of Power BI dataset refreshes.
    This cannot be accomplished when a data-driven alert is triggered.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  12. Export ARM template for Integration Account

    Attempting to export a resource group containing a Logic App and Integration Account will fail with:

    Export template operation completed with errors. Some resources were not exported. Please see details for more information. (Code: ExportTemplateCompletedWithErrors)
    •The schema of resource type 'Microsoft.Logic/integrationAccounts' is not available. Resources of this type will not be exported to the template. (Code: ResourceTypeSchemaNotFound, Target: Microsoft.Logic/integrationAccounts)

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  13. Display Integration Account Certificate thumbprint on Portal

    It would be very helpful if thumbprint was shown on the portal. It helps build trust between two parties because they are always sure of what version of certificate they have.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  14. Metrics for Logic App Integration account

    Supply the Integration account metrics to the users the same way we are able to get for logic apps.

    This metrics would be really helpful to create the azure monitoring alerts , so that the devops/DRI team can be able to get notified quickly that the logs to take an action.

    FYI, Logic metrics:

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow triggers from Keyvault so you can use approval flow for secure key access

    Allow us to create triggers and flows for approval process for accessing restricted secrets and certs

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  16. WDL Intellisense in LogicApps

    During last week i saw that Logic apps designer had intellisense for WDL functions. But for past few days it is not working in Logic Apps designer.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  17. HL7 Support in Logic Apps

    t will be very helpful if you add HL7 accelerator to Logic Apps similar to BizTalk. This is a gap where we are not able to propose Logic Apps for our client.

    56 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  18. Make a FHIR-specific parser, to parse HL7 FHIR in an intelligent and user friendly manner

    Make a parser that can take FHIR-based content (which is JSON or XML based format) and parse this in a quick and user friendly manner, for example by using FHIRPATH. FHIR is a bit tricky to parse since it uses arrays extensively. (FHIR = HL7 v4)

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  19. Support multiple Control Version Number (ISA12) per agreement

    There are partners that use different control versions across the messages. The GS segment can be defined per schema, but ISA12 is unique per agreement.

    We are forced to create multiple agreements to set different version of ISA12, although the rest of the agreement stays the same.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise Integration  ·  Flag idea as inappropriate…  ·  Admin →
  20. Specific for X12 Connectors - Agreements.

    Current scenario : Only a single Control Version Number(ISA12) is supported for an X12 agreement. For example, If the control version number is set to "00401", then this agreement wont work for X12 messages for version number "00501". Current solution is to create a new agreement to resolve your version number issue.

    What can be done ? : Sticking to the above mentioned example, Agreement can have capability of registering more than one versions such that all the required schema (version separated) can be registered on the same agreement rather creating individual agreements for specific version numbers.

    Example : X12…

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

Logic Apps

Categories

Feedback and Knowledge Base