Power Automate |
Azure Logic Apps |
| Power Automate is built on top of Azure Logic Apps | |
| It is a SaaS service for workflow automation across several different apps and SaaS services. | It is a PaaS service for workflow automation across several different apps, SaaS services, and IaaS services for enterprise integration. |
| For more of self-service and simple integration scenarios. | For complex/advanced integration scenarios |
| Targeted for Business User, Citizen Developers, Developers, IT Pros. | Targeted for Developers and IT Pros. |
| Brower based designer and mobile app UI only
|
In-browser as well as Visual Studio |
| Office 365 Service / License / Subscription | Azure Service / License / Subscription |
| Flow specific Connectors | Logic App-specific Connectors – SAP, IBM MQ, IoT, Liquid. |
| Power Automate are specific to an environment | There is no environment concept, each logic app is an independent entity. |
| Pay by run | Pay by action run and by connector run. |
| Button flow | |
| Modern Approvals https://nishantrana.me/2020/08/31/approvals-power-automate-dynamics-365/ |
|
| Flow can be extended as Logic Apps |
|
| Power Automate is supposed to be designed and tested in a non-production environment and then promoted to the production environment. The solution makes it possible with connectors requiring reconfiguration. Connection references can be considered here https://flow.microsoft.com/en-us/blog/move-flows-across-environments-without-resetting-connections/ |
Logic Apps has ALM possibilities. |
| Admin Experience through Power Platform Admin Center. | Admin experience through Azure Portal. |
Category: Power Automate
Approvals – Power Automate & Dynamics 365
app
How to – Hide Approve / Reject Button in Approval Email in Power Automate Approval Workflow
Recently we had a requirement to remove or hide the Approve and Reject buttons from the approval email as we wanted the user to manage it all from the Approval Center. The way we implemented this is by replacing the Start and wait for an approval action with Create an approval, Send email notification and…
Approval / When a file is created (properties only) – when a file is added to the folder in the SharePoint library
Recently we had a requirement to implement an approval workflow when a document is added to a SharePoint library. Below is how we can implement it. Details – Trigger – When a file is created (properties only) Specify the Site Address, Library Name, and the Folder on which the flow should run. Initialize Variable Initialize…
Assign approvals to any user in the Tenant – Power Automate
We recently implemented Approvals, and we required that any user in the tenant should be able to provide approval. For one of the users, we got the below error while testing the flow. UserNotMemberOfCdsSecurityGroup This was because we were using the Security Group to control access to Dataverse Environment. So adding the user to the…
Fixed – ‘InvalidApprovalCreateRequestAssignedToNoValidUsers’. Error Message: ‘Required field ‘assignedTo’ contained no valid users in the organization’.
We would get the below error while using Approvals in Power Automate “BadRequest. The request failed. Error code: ‘InvalidApprovalCreateRequestAssignedToNoValidUsers’. Error Message: ‘Required field ‘assignedTo’ contained no valid users in the organization’” This error occurs if we are trying to send the approval to the user which doesn’t exist in the organization or to the external users.…
Fixed – Error code: ‘UserNotMemberOfCdsSecurityGroup’. Error Message: ‘The user ‘xyz’ cannot be created in Microsoft Dataverse because the account is not a member of group ‘abc’
We would get this error within Power Automate Approval Flow if we are using Security Group to control access to Dynamics 365 Environment and are sending Approval to a user who is not a member of that security group. Below is the User within the Tenant but is not member of the My CRM Group…
Approvals in Microsoft Teams / Power Automate
Approvals App for Teams was introduced early this year. To see it in action, let us start by first adding the Approval app in Teams. Search for the app. And click on Add. The Approval app shows all the Approvals Received and Sent within teams, which can be filtered based on status. We can also…
How to – Use markdown to format approval emails – Power Automate and Dynamics 365
Let us update our previous flow, to use markdown to format the approval email. Check other posts on Approvals – https://nishantrana.me/2020/08/31/approvals-power-automate-dynamics-365/ Markdown is the lightweight mark-up language for adding formatting elements to the plain text. Refer the Markdown cheat sheet We’d update the Details property of Start and wait for an approval action. Below we…
Custom Responses in Approvals – Power Automate and Dynamics 365
Let us update our previous flow to use Approval Type – Custom Responses, using which we can define our custom response options (instead of limiting ourselves to Approve and Reject) Check other posts on Approvals – https://nishantrana.me/2020/08/31/approvals-power-automate-dynamics-365/ Here we have updated the Start and wait for an approval action’s Approval Type from Approve / Reject…
Parallel Approvals – Power Automate and Dynamics 365
Let us update our previous flow to include parallel approvals. Check other posts on Approvals – https://nishantrana.me/2020/08/31/approvals-power-automate-dynamics-365/ The difference between Approve / Reject Type – Everyone must approve and parallel approvals would be that using parallel approvals we could wait for responses for all the approvers, be it approve or reject. In case of Everyone must…
Attachments in Approval – Power Automate and Dynamics 365
Let us update our previous sequential flow, to include file attachments to notes of the case record, as part of the approval. Check other posts on Approvals – https://nishantrana.me/2020/08/31/approvals-power-automate-dynamics-365/ First, we need to add Initialize variable action and define an Array variable to store all the attachments details. Next, we will use List records action,…
How to – Use Approval/Reject Type – Everyone must approve – Power Automate and Dynamics 365
Let us update our previous flow from approval/reject type – First to respond to Everyone must approve type. Check other posts on Approvals – https://nishantrana.me/2020/08/31/approvals-power-automate-dynamics-365/ For First to respond, either Approval or rejection by any of the approver completes the request. In case of Everyone must approve, if any of the approvers rejects the request…
Manager approval – Power Automate and Dynamics 365
Continuing our previous basic approval flow, here we’d update it to send an approval request to the manager of the user. Check other posts on Approvals – https://nishantrana.me/2020/08/31/approvals-power-automate-dynamics-365/ First, we’d use the Get manager V2 action to get the user’s manager. Let us first update the profiles of the users to add their manager. Sign…
Approvals in Power Automate and Dynamics 365
Let us try implementing a basic scenario, where an agent can send a case for approval and the record is updated based on the approver’s response. Check other posts on Approvals – https://nishantrana.me/2020/08/31/approvals-power-automate-dynamics-365/ The agent here sets the Submit for Approval – custom field as Yes and saves the record for submitting it for approval.…
How to – Use markdown to format approval emails – Power Automate and Dynamics 365
Let us update our previous flow, to use markdown to format the approval email.
Check other posts on Approvals – https://nishantrana.me/2020/08/31/approvals-power-automate-dynamics-365/
Markdown is the lightweight mark-up language for adding formatting elements to the plain text.
Refer the Markdown cheat sheet
We’d update the Details property of Start and wait for an approval action.

Below we have added some sample text that uses markdown syntax.

Below is how it renders in the outlook web access OWA.

And inside the Power Automate Approval Center.

Below we have used markdown syntax for defining the table.

Inside OWA.

Inside the Power Automate approval center.

And within the Power Automate mobile app

Kindly refer to the below table that lists down inconsistencies among different clients.
https://docs.microsoft.com/en-us/power-automate/approvals-markdown-support#client-support

Also check out –
https://www.about365.nl/2020/02/27/power-automate-approvals-markdown-or-html/
https://sharepains.com/2019/07/09/using-markdown-in-microsoft-flow-approval-actions/
Hope it helps..
Custom Responses in Approvals – Power Automate and Dynamics 365
Let us update our previous flow to use Approval Type – Custom Responses, using which we can define our custom response options (instead of limiting ourselves to Approve and Reject)
Check other posts on Approvals – https://nishantrana.me/2020/08/31/approvals-power-automate-dynamics-365/
Here we have updated the Start and wait for an approval action’s Approval Type from
Approve / Reject – First to respond
to
Custom Responses – Wait for one response.

We have defined below custom responses – Accept, Reject, and Need more details.

We have updated the Condition to check for Need more details

Let us save, check, and run the flow.

The approvers are presented with the custom responses

Here among the users to who the request is assigned, the flow will complete if any of the approvers responds, it will not wait for all the approvers to respond.
Now let us update it to use Custom Responses – Wait for all
responses.

Here the flow will wait for responses from all the approvers before moving to the next action.

Lastly, if we define more than 5 responses,

Outlook and OWA have a limitation of only showing the first five responses in the actionable message as shown below.

Within the Power Automate approval center and Power Automate mobile application we do not have this limitation.
Power Automate approval centre:

Power Automate mobile application:

Hope it helps..
Parallel Approvals – Power Automate and Dynamics 365
Let us update our previous flow to include parallel approvals.
Check other posts on Approvals – https://nishantrana.me/2020/08/31/approvals-power-automate-dynamics-365/
The difference between Approve / Reject Type – Everyone must approve and parallel approvals would be that using parallel approvals we could wait for responses for all the approvers, be it approve or reject.
In case of Everyone must approve, if any of the approvers rejects, the request is considered rejected and it will not wait for other approver’s response, and for the request to be considered approved all the approver needs to approve it.
Let us add a new action Add a parallel branch after Apply to each.

Let us keep only test user 1 in the first branch and in the other branch add a Start and wait for an approval action.

We have updated both to be approval type First to respond, set Assigned to the property to test user 1 and test user 2 for the respective branches.
And also we want to evaluate the responses from both the approvers before taking further action, so we have deleted the condition action from the first branch.

Let us add a new Condition action, with 2 AND conditions, i.e. if the first user approves and the second user rejects which corresponds to the respective Start and wait for an approval action.

Here if the condition is fulfilled we update the description of the case record.

Let us save, check, and trigger the flow.

After test user 1 has approved, we can still see the flow waiting for user 2 to respond.

The flow completes successfully after the response is received from both the approvers. Here user 2 rejects the request.

As expected, we can see the description field updated as defined in the update the record action.

Hope it helps..
Attachments in Approval – Power Automate and Dynamics 365
Let us update our previous sequential flow, to include file attachments to notes of the case record, as part of the approval.
Check other posts on Approvals – https://nishantrana.me/2020/08/31/approvals-power-automate-dynamics-365/
First, we need to add Initialize variable action and define an Array variable to store all the attachments details.

Next, we will use List records action, to fetch all the notes records associated with that particular case record.

Next, we will use Apply to each action to loop through all the attachments and use it to populate our attachments array variable defined in the previous step.

Now as the last step, we’d specify the attachment array variable for the attachment field inside the Start and wait for an approval action.

Now we are ready to save and test our flow.

Here our flow is waiting for approval from the user.

The approver receives the notification and can now review the attachments before responding.


Hope it helps..

