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. 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.

    86 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 →
  2. Uploading complex schemas to integration account

    The integration account currently allows uploading one artefact at a time. This is a pain, especially when we have to upload a complex schema. Moreover, there is no provision to store dependent schemas in an order expected by the complex schema. If you are expecting enterprise integration to be done using Logic Apps, this issue needs to be addressed. The documentation on uploading complex schemas also needs to be updated.

    8 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 →
  3. 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…

    114 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 →
  4. 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 →
  5. Logic app designer platform itself should be aloud to embed in other enterprise application.

    Particular user can create or modify logic app from enterprise application and will save the changes (to trigger the save change of azure). So that user doesn't need to go to azure every time to create the logic app.

    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 →
  6. 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.

    23 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. Integration Account artefacts Versioning

    Just like Versions Tab got introduced in Logic Apps (and has proved to be extremely helpful), is there any plan to introduce Versioning in Integration Account as well – so that when any change happens in the artefact JSON it creates a new entry into a Versions Tab in Integration Account resource. It will help in not relying on VSO versions in case we have to redeploy. Also very useful in case someone from support team modifies and we want to understand what changed got made and revert to previous version from portal itself.

    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 →
  8. 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 →
  9. 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.

    12 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 →
  10. 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 →
  11. 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 →
  12. 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)

    23 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. Support for EDI files greater than 100MB - Ideally to 1GB

    The current limit on the output of B2B actions is 100MB. The ask is support outputs greater than that - Ideally to 1GB.

    10 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 →
  14. 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 →
  15. 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 →
  16. Provide a way to assign a dedicated static outbound IP to a LogicApp

    At times there is a need to add the outbound IP address of a LogicApp in some form of whitelist / Firewall rules. The current list of outbound IP address's are shared by many customer's so configuring these IP address's in the whitelist is not sage . A feature to associate a static outbound IP address to a given logic app would help in such scenarios.

    93 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 →
  17. 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.

    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 →
  18. Business Rule Engine (BRE)

    We want to have BRE which can be integrated in WebApp and will be isolated from implementation.
    For e.g.
    If Age > 40, do this
    If travel date is nearer, give some discounts and so on.

    Logic Apps does not provide this, it would be good if this can be integrated as a service with lower cost.

    231 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 →
  19. Add "EDIFACT Fallback Settings” support in “Enterprise Integration Pack” and LogicApp

    In BizTalk, there was “EDIFACT Fallback Settings” when BizTalk has not determined the agreement. Fallback Settings were not supported ever in Azure BizTalk Services.

    We need that this capability be supported in “Enterprise Integration Pack” and LogicApp

    74 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. 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.

    5 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 →
  • Don't see your idea?

Logic Apps

Categories

Feedback and Knowledge Base