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

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

Logic App Consumption name restrictions

The name of Logic App Consumption must be fewer than or equal to 80 characters.

But it also contains the following restrictions:

  • The name can only contain letters, numbers, and ‘-‘, ‘(‘, ‘)’, ‘_’ or ‘.’.
  • The Logic App name must be unique within a Resource Group.
  • You can use both lowercase and uppercase letters.
  • The name can finish with any valid character, including ‘-‘ or ‘_’.

Logic App Standard name restrictions

The name of your Logic App Standard resource must be fewer than or equal to 43 characters.

But it also contains the following restrictions:

  • The names only allow alphanumeric characters and hyphens.
  • The Logic App name must be unique within a subscription.
  • You can use both lowercase and uppercase letters.
  • The name cannot start or end in a hyphen.

However, workflow names have different rules!

  • Both Stateful and Stateless workflow names must be fewer than or equal to 255 characters!
  • The name must be unique within a Logic App Standard.
  • The name can only contain letters, numbers (0-9), dashes (“-“), and underscores (“_”).
  • You can use both lowercase and uppercase letters.
  • Workflow names must start with a letter and finish with a letter or number.
  • Workflow names cannot have two symbols (“-“) or (“_”) together.

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