@Bharvi Bhut Thanks for reaching out. As you are using multiple condition so for every action you will be billed so to check one value you are using two actions so it would be 50+ actions just to check and assign the value. As there are many actions so it would be not decipherable. The workaround would be defining this condition check during the assigning the value to your variable or offload this functionality to inline code.
For example, I have defined assign the Tag variable with my custom value based on the input on my Parse_JSON action.
You can see I have used concat to combine the string and inside it I am comparing my input to some value and then it will add it to my main string variable.
concat(
if(
contains(toLower(body('Parse_JSON')?['tag'][0]),'cu1'),
'CustomValue1',
''
),
if(contains(toLower(body('Parse_JSON')?['tag'][0]),'cu2'),
'CustomValue2',
''
),
if(contains(toLower(body('Parse_JSON')?['tag'][0]),'cu3'),
'CustomValue3',
''
),
if(contains(toLower(body('Parse_JSON')?['tag'][0]),'cu4'),
'CustomValue4',
''
)
)
The above is just for reference and you need to change according to the condition that you have define and different function expression that you are leveraging. If you are choosing the above method, then in consumption logic app it would be only one action that would be billed for you. For standard logic app all the build-in conectors are free but not the azure connectors.
Hope the above and feel free to get back to me if you need any assistance.
Please accept as "Yes" if the answer is helpful so that it can help others in the community. If you need any help/clarification/concerns/follow up questions, then please click on "Add Comment" on my answer and provide more details.