One of the things I enjoy most about Microsoft Integration Services is how they constantly evolve. Features get improved, new capabilities are released, and sometimes… names change. And today’s on this double Friday Fact is all about one of those small but slightly confusing name changes that the Logic App team decided to roll out:
- The field that we used to know as Comments, then renamed to Notes, is now called Descriptions.
📝 One-Minute Brief
If you open a Logic App today and can’t find the familiar Notes or Comments, don’t worry. They’re still there, but now they’re called Descriptions. Same functionality, same place — just with a new label that better reflects their true purpose.
Yes, once again, the Logic App team has decided to revisit the terminology of this feature. Let’s do a quick trip down memory lane:
- In the beginning, we had Comments – just like in most programming languages. This made perfect sense because the purpose of the field was to allow developers to leave remarks or explanations about a specific action in the workflow.
- Then came Notes – at some point, Microsoft decided to rename them with a more Office 365-like look and feel, similar to Word. While “Notes” still worked, it introduced a bit of ambiguity. Notes could mean annotations, reminders, or even things unrelated to technical documentation. Some developers felt that “Notes” sounded less formal.
- Now, we have Descriptions – the new (and hopefully final!) name. I do not know if this aligns much better with standard documentation practices – in my opinion, I do prefer Comments. However, compared to Notes, in this case, when you describe an action, you explain its role and purpose inside the workflow. It’s more professional and easier for teams to understand.
Descriptions allow developers to apply comments inside the actions (also known as shapes) inside the workflows. This is a common and basic task that developers do in their code, independent of the language they are working with.
This is purely a cosmetic update. But if you work on enterprise-grade integrations with large teams, naming conventions matter a lot, and comments/notes/descriptions allow us to embed documentation directly in the Logic App, which is essential for:
- Knowledge sharing – other developers (or even your future self!) will thank you when trying to understand why a specific action was implemented.
- Maintenance – months or years later, these descriptions become critical breadcrumbs for debugging or enhancing the workflow.
- Collaboration – when multiple team members work on the same Logic App, clear descriptions reduce misunderstandings.
To add a note to an action step or trigger, you need to:
- Open your Logic App on the Azure Portal (of course, this can also be made inside Visual Studio) and click Edit. Or click Logic App designer inside Development Tools.
- Then, on your action or trigger, click on the 3 dots to open the option list and then choose to Add a description.
- A new description section will appear on the action or trigger configuration panel, where you can enter your comment. Once the comment is entered, you can exit the action step by moving to a new action or collapsing that action.
Friday Fact takeaway
Will this be the final name? Only time will tell. But for now, when you document your Logic Apps, remember: Comments = Notes = Descriptions.
To lazy to read? We’ve got you covered! Check out our video version of this content!
If you liked the content or found it helpful and want to help me write more content, you can buy (or help buy) my son a Star Wars Lego!
