Friday Fact: Logic App Consumption and Standard have different Action name restrictions

By setting proper names for your actions, you can quickly identify what they are intended for and what they are doing without the need to enter each action to figure it out. This provides readability and saves future time (not looking at the details and configurations inside your actions) and frustrations. However, depending on the Logic App type you are using, Logic App Standard or Logic App Consumption, you will notice that each of them has different name restrictions!

One thing they have in common… the action names must have one character and be fewer than or equal to 80 characters.

Logic App Consumption Action name restrictions

In Logic App Consumption, the action names must contain one character and be fewer than or equal to 80 characters.

But it also contains the following restrictions:

  • The action name cannot contain any control characters or any of the following symbols:
    • <
    • >
    • %
    • &
    • \
    • ?
    • /
  • The name cannot be empty. It needs at least 1 character, even if that character is a space (spaces are supported)
  • The action name must be unique inside the Logic App.

Logic App Standard Action name restrictions

In Logic App Standard, the action names must also contain one character and be fewer than or equal to 80 characters – similar to Logic App Consumption.

  • The name cannot be empty. It needs at least 1 character, even if that character is a space (spaces are supported)

But it also contains the following restrictions:

  • The action name must be unique inside a distinct workflow.

Apart from that, there are no more restrictions regarding the action name. You can use all types of characters and symbols.

Notice also that if you try to add an empty name to the action, by default, it will add the action’s default name as the action name.

To lazy to read? We’ve got you covered! Check out our video version of this content!

Hope you find this helpful! If you enjoyed the content or found it useful and wish to support our efforts to create more, you can contribute towards purchasing a Star Wars Lego for my son!

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

Leave a Reply

Your email address will not be published. Required fields are marked *

turbo360

Back to Top