One of the things I enjoy most about Microsoft Integration Services is how they constantly evolve. Teams refine features, release new capabilities, and sometimes—even more noticeably—rename things. Today’s double Friday Fact focuses on one of those small but slightly confusing name changes introduced by the Logic Apps team:
- 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. That choice made perfect sense because the field lets developers add remarks or explanations for a specific action in a workflow.
- Then came Notes – At some point, Microsoft renamed the field to match a more Office‑style look and feel, similar to Word. While the name still worked, it introduced ambiguity. Notes could mean annotations, reminders, or content unrelated to technical documentation. As a result, some developers felt the term sounded less formal.
- Now, we have Descriptions – the new—and hopefully final—name. Personally, I still prefer Comments. However, compared to Notes, Descriptions convey intent more effectively. When you describe an action, you explain its role and purpose in the workflow. That clarity feels more professional and makes collaboration easier for teams.
Descriptions let developers add comments directly to actions—also known as shapes—within a workflow. Developers perform this basic practice in every programming language, regardless of the technology they use.
This change is purely cosmetic. However, in enterprise‑grade integrations with large teams, naming conventions matter. Clear comments, notes, or descriptions embed documentation directly in the Logic App, which becomes 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.
- The configuration panel displays a new Description section for the action or trigger. You can add your comment there. Afterward, you can exit the action step by moving to another action or collapsing it.
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, you can buy (or help buy) my son a Star Wars Lego set!
