The document discusses new features, best practices, and testing techniques for Azure Logic Apps workflows. It emphasizes improving workflow readability, security, and error handling, recommending the use of descriptive names, comments, and appropriate retry policies. It also covers managing API integrations and the importance of controlling exceptions within workflows.

1. Mastering Logic Apps Workflows: New
Features, Best Practices, and Testing
Techniques
MIUG.NL

2. Bedankt

3. Wine Lover & Star Wars fan
https: // blo g .s andro -pereira.com
P u b l i c s p e a k e r
Sandro
Pereira
Head o f Integ ration @ D evSco pe
M icro so ft A zure M V P
sand ro .pereira@ d evsco pe.net
linkedin.com / in/s androp ereira
F a t h e r
@ s a n d r o _ a s p
+351 223 751 350
www.devscope.net
@sandro_asp

4. BizTalk Server Developer Training Course
BizTalk Server
BizTalk Server Operations, Administration,
and Maintenance (OAM) Training Course
BizTalk Server
Azure Logic Apps Training Course
Azure
Azure Integration Services Training Course
Azure
Get started with Power Automate
Power Platform
Instructor
@sandro_asp

5. Foc us on P roduc t ivit y
@sandro_asp
Robust a nd e ffic ie ncy solut ions

6. what’s new…
@sandro_asp

7. vs code workspace
@sandro_asp

8. in-app function…
@sandro_asp

9. be a superhero
implement
best practices…
@sandro_asp

10. naming convention
Use descriptive names
Improves readability
Transfer knowledge
@sandro_asp

11. @sandro_asp

12. add comments…
Everyone can read the comments
Save yourself and teammates from future
frustration
Every expression should have a comment
@sandro_asp

13. @sandro_asp
?
?

14. improve security by
suppress headers
in external HTTP
calls…
@sandro_asp

15. @sandro_asp

16. This setting will limit Logic Apps to not include workflow
metadata headers in the outgoing request!
@sandro_asp

17. secure
secrets
by using
obfuscation… @sandro_asp

18. @sandro_asp
This setting secure the outputs of the
operation and references of outputs
properties!

19. @sandro_asp

20. avoid calling
external APIs
inside your workflows …
@sandro_asp

21. @sandro_asp
API Management
Internal APIs
Inbound Policies, Outbound Policies,
Security, Versioning, Routing
External APIs
Inbound Policies, Outbound Policies,
Security, Versioning, Routing
Logic App
Internal APIs Function App
External APIs
Logic App
Logic App
Logic Apps will be responsible to implement the business
logic. The authentication to APIM will use for example a
Subscription Key.
So, you don’t need to worry about usernames and
passwords anymore.
You can simplify the messages and implement REST best
practices.
APIM will be responsible to implement
authentication between the API.
Even using Authentication tokens and cache them
for the expected token duration.
Normalize the request into what is expected.

22. be carefully
calling
child workflows…
@sandro_asp

23. @sandro_asp
You may get false successfully runs

24. @sandro_asp
Option 1

25. @sandro_asp
Option 2

26. control
exceptions…
@sandro_asp

27. @sandro_asp

28. @sandro_asp

29. @sandro_asp
We can implement “try-Catch” per action
using
Run after settings

30. control APIs
retry policies
and
timeouts…
@sandro_asp

31. A retry policy applies to intermittent failures,
characterized as HTTP status codes 408, 429, and 5xx,
in addition to any connectivity exceptions. The
default is an exponential interval policy set to retry 4
times.
Specifyinterval inISO8601 format.
Examples:
• "PT20S" --parsesas"20 seconds"
• "PT15M" -- parses as "15 minutes" (where a minute is 60
seconds)
• "PT10H" -- parses as "10 hours" (where an hour is 3600
seconds)
• "P2D" -- parses as "2 days" (where a day is 24 hours or
86400seconds)
• "P2DT3H4M" --parsesas "2days, 3hoursand 4minutes"
@sandro_asp

32. contact>us
sandro.pereira@devscope.net
+351 969 185 667
https://www.linkedin.com/in/sandropereira/
@sandro_asp