This article is part of the Working with Power Automate series I am writing on my experiences working with the Power Automate, which is part of the Power Platform from Microsoft. I also have a related series of articles on Power Automate with Microsoft Dynamics 365 BC.
I briefly introduced scopes in the last article of this series and thought I’d give a bit more detail on what scopes are and how they’re used.
Scopes in Power Automate are a type of action, but one which doesn’t do anything by itself.
Instead scopes are used to organise a flow, allowing you to group together related actions. As actions can be expanded and contracted, a scope allows you to control which scopes are expanded and the steps visible or not, making the view smaller when you close the scopes you’re not working on.
Scopes, like all actions, can be renamed so that they have a name which makes it clean what that action does; in terms of a scope, the scope name should clearly describe what the actions in the scope collectively do. For example, you might have a scope renamed to “Scope | Handle customer document on OneDrive”.
In addition, scopes can also be used to improve error handling (a topic I haven’t yet covered).Each action can have error handling attached to it for the result of that step, or, in the case of a scope, error handling for all the actions within the scope.
