2023 Power Automate Coding Standards For Cloud Flows

2023 Power Automate Coding Standards For Cloud Flows

Welcome to the Power Automate Coding Standards For Cloud Flows.

In this guide you will find 60+ pages of coding rules, guidelines and best practices I use everyday to create Power Automate cloud flows. I have spent the last 3 years building Power Automate flows every day. Now I want to share the knowledge I’ve gained in this set of easy-to-understand, actionable examples.

Power Automate already has an official set of cloud flow coding standards released back in 2019. So why did I make my own? A few reasons:

  • I wanted an updated set of standards and guidelines for 2023 that includes all of the latest features
  • These coding standards can be continuously improved as new Power Automate features hit “general availability” in 2024, 2025, 2026 and beyond
  • Readers can leave comments on my website describing their own best practices which I can incorporate into future versions



I hope you enjoy my Power Automate Coding Standards For Cloud Flows.




Table Of Contents

  1. 🔠 Naming Conventions
  2. 📦 Variables
  3. 📝 Commenting Code
  4. 🧶 Connection References
  5. 🐞 Error-Handling
  1. Performance Optimization
  2. 📋 Flow Architecture & Design Tips



Questions?

If you have any questions about 2023 Power Automate Coding Standards For Cloud Flows please leave a message in the comments section below. You can post using your email address and are not required to create an account to join the discussion.

Subscribe
Notify of
guest

15 Comments
Oldest
Newest
Inline Feedbacks
View all comments
Francesco
Francesco
5 months ago

Hi Matthew, thank you for the great content as always.
I just want to let you know that the link in Error-Handling is pointing to the Power apps Guide
https://www.matthewdevaney.com/power-apps-coding-standards-for-canvas-apps/power-apps-standards-reviewing-canvas-apps/

Francesco
Francesco
5 months ago

Don’t worry, just a little act of service after all the help we got from your blog in our daily job.

I think that Performance optimization is wrong too, the link send me here.

https://www.matthewdevaney.com/power-apps-coding-standards-for-canvas-apps/power-apps-app-theming-guidelines/

Eric Deferm
Eric Deferm
5 months ago

Greate job Matt, tx for sharing such useful insights.

Zarko
Zarko
4 months ago

Hi Matthew and thanks for sharing your knowledge. In your guide you have a section named “Assign Connection Ownership To Service Accounts” but I miss some information there. It seems that you managed to log in as a service principal in your screen shot, but I don’t understand how. Thanks in advance.

Darren P
Darren P
4 months ago

Hi Matt,
I have implemented the error handling in flows.. Life Saver, something I wanted to point out, not sure if the json returned is different for each action, or if it changed since you put this out,but I had to edit the code for the error message.

instead of ?[‘error’]?[‘message’]
I had to do: [‘body’]?[‘error’]?[‘message’]

just wanted to pass that along

Darren P
Darren P
4 months ago

hmm mine did not have the [‘body’]

I had: [‘error’]?[‘message’]
and: [‘outputs’]?[‘error’]?[‘message’]

but I did share it out to some peers, maybe they were playing around with it… either way THANK YOU very much!!!

Roland
Roland
2 months ago

Just wanted to let you know that your suggested naming convention for actions ([action name]: [details]) doesn’t work in the new Power Automate editor. Semicolon is accepted, but colon is not.

Marcin Młynarczyk
Marcin Młynarczyk
2 months ago

Hi Matthew, thank you for this lifesaver of a guide 🙏🏻 I was wondering if you were considering posting this as a collection of Markdown files in a GitHub repository so community could help you with maintaining and expanding the guide?

Last edited 2 months ago by Marcin Młynarczyk