Skip to main content
Azure Logic App - Adding comment(s) is one of the best practices.

#cloud #azure #logicapp

Hi All!

As a azure developer and/or administrator, we need to work on new and/or existing Logic App(s). If it is new, we are happy to start from the scratch.

Consider a scenario that you deployed into a team where you have 15+ logic apps in each environment like Dev, UAT and Prod. Before work on those Logic apps, we need to study the workflow (trigger and actions).

Existing Logic App UI will not tell you the action type. To know the action type, one way is that you have to go to Logic app code view which is a JSON representation of the workflow where you can find the type of all actions.

Even though we can see the type(s) from JSON as stated above, we could not know the intention or business purpose of that action.

Here we can add comments on each action which is missed most of the time. Let's see how we can add comment on each action in Logic app. So that, when others work onlogic apps, they understand it easily.

Please look into the below image.

I have trigger in logic app that when a service bus received message, this logic app starts but If we know from where and how this service bus receive message, we can talk to the concern team to discuss some more details.

So I add a comment that the service bus receives message in queue from Order shipping web application. So now, If we get any escalation or issue from customer regarding this logic app and data received at service bus, we can discuss with the order shipping web app developer / azure developer or development team.

Comments

Post a Comment

Popular posts from this blog

Azure Static Web Apps - Plan Comparison #cloud #azure Hi All! Azure Static web app is a good service when we have static web apps like javacript frameworks and libraries applictions (Ex: Angular, React, Svelte, Vue, Blazor). It also supports Python 3.10 based static web app as well as per the latest azure news. Other advantage of it is coupled with your Azure AD. so that your code can be directly pushed to azure static web app via either Azure DevOps or Github whenever code push occurs. At the time of azure static web app creation, it asks for deployment source as any one of the below. Based on the selection, it allows you to select the organization, project and repositories from the source. Azure DevOps - Azure AD connected Devops organizations will be listed out Github Other - For ex: If you want to deploy code from other organization. Below table will be helpful to choose the best pricing plan for your workload. Plan/Feature Free Standard ...
1 comment
Read more
Azure Public IP(s) are zone redundant free of cost natively - Generally Available Availability zone gives high availability to an application as well as information by forestalling the physical datacenter disappointments by involving replication of the asset in extra datacenter. Azure typically has 3 zones per region (and not all regions support zone). Thus, while setting up the environment we really want to pick the right region based on our usecase. Public IP helps to access a resource or an application publicly. Azure offers 2 types of SKU for public IP as below Basic Standard Only Standard SKU gives zone facility. Basic SKU is always non-zonal and this SKU also will be retired 09/2025. Standard public IP can be fell into any of the below category No Zone / Non-Zonal - No availability zone at all Zonal - Our services can be replicated in any one of selected zones from three zones. Zone redundant - Resource will be replicated in all 3 zones. It is opposite of...
Post a Comment
Read more
Avoid YAML Validation error in azure devops pipeline Hi All! Consider a scenario that you committed a YML CI/CD file on the repository with some syntax, indentation and/or other error(s). so that pipeline failed. After you find some errors and rectified in the repository file and committed again but pipeline still gets failed because some errors are still there. Now you afraid that even if you fixed error in all the places, what happens if pipeline failed again because your project lead or manager set up build notification mail trigger for build success and fails. you need to answer them for build fail reason. Azure devops pipelines offers YAML validation feature after altered and before committed and before run pipeline. To utilize this feature, what we do is, Instead of modifying the file from repository, Do as below Go to the specific build click "Edit Pipeline" Modify/fix errors and click "validate" as shown in the picture below ...
Post a Comment
Read more