Friday Fact: Logic App Parameters naming size limits and restrictions

In the past, we had a similar Friday Fact: Friday (funny) Fact: There is no size limit for the Logic App parameter name. But on that, we didn’t go through all the scenarios, something we will address now here today.

In Azure Logic Apps, you can abstract values that might change in workflows across development, test, and production environments by defining parameters. A Logic App parameter stores values that can be reused throughout a Logic App workflow. These parameters allow for a more flexible and maintainable configuration of logic apps, making it easier to update values without changing the actual workflow’s logic.

However, when working with Logic App parameters, Logic App Standard and Logic App Consumption have different name sizes and restrictions that you need to be aware of!

Logic App Consumption Parameters Naming Restrictions

Inside Logic App Consumption, parameters are probably the only Logic App “component” that doesn’t have almost any type of limitations regarding the name. It can:

• Use any type of characters, including control characters, dots, and spaces.
• And it doesn’t have any size limitation.

The only two limitations that exist are:

• The parameter names must contain one character.
  • That character can be whatever character you want.
    • A single space is allowed!
    • You can create a variable call ‘ ‘ (space) and another call ‘ ‘ (two spaces)
    • You can use a heart if you want! ♥
      • We never know when we will need to create a romantic business process!

• The parameter name must be unique within the Logic App Consumption

Logic App Standard Parameters Naming Restrictions

In Logic App Standard, the parameters are way more restricted, and they have very restricted rules:

• Inside Logic App Standard, the parameter names must contain one character and be fewer than or equal to 80 characters. But also
• The name can only be a letter, digit, or the following symbols:
  • –
  • .
  • (
  • )
  • _
• The parameter name must be unique within the workflow.
• They are also Case insensitive.

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!