You're reading from Workflow Automation with Microsoft Power Automate Achieve digital transformation through business automation with minimal coding

Product type Hardcover

Published in Dec 2025

Publisher Packt

ISBN-13 9781836649632

Length

Edition 1st Edition

Tools

Power automative desktop

Concepts

Workflow Automation

Author (1):

Aaron Guilmette

View More author details

Table of Contents (28) Chapters

1. Workflow Automation with Microsoft Power Automate: Drive digital transformation with AI-powered automation and low-code business workflows FREE CHAPTER

2. Chapter 1: Introducing Microsoft Power Automate

3. Chapter 2: Getting Started with Power Automate

4. Chapter 3: Working with email

5. Chapter 4: Copying files

6. Chapter 5: Creating Button Flows

7. Chapter 6: Generating push notifications

8. Chapter 7: Working with shared flows

9. Chapter 8: Working with Conditions

10. Chapter 9: Understanding Expressions and Functions

11. Chapter 10: Getting Started with Approvals

12. Chapter 11: Working with Multiple Approvals

13. Chapter 12: Posting Approvals to Teams

14. Chapter 13: Using Databases

15. Chapter 14: Working with Microsoft Forms

16. Chapter 15: Posting to Slack

17. Chapter 16: Accepting User Input

18. Chapter 17: Automating Entra ID

19. Chapter 18: Introducing Robotic Process Automation

20. Chapter 19: Contributing to an Access database with RPA

21. Chapter 20: Automating webpages with RPA

22. Chapter 21: Introducing AI Models and Generative AI

23. Chapter 22: Creating a sentiment analysis flow

24. Chapter 23: Using Copilot to create and manage flows

25. Chapter 24: Using Generative AI to summarize documents

26. Chapter 25: Exporting, importing, and distributing flows

27. Chapter 26: Monitoring and troubleshooting flows

28. Chapter 27: Governance in the Power Platform

Configuring prerequisites

This approval flow will require a few components and prerequisites. You're already familiar with many of them, but we'll review the exact requirements for this flow. The next two sections will describe the requirements.

A SharePoint site

One of the main outputs of this flow is moving documents between folders on a SharePoint site, based on whether they are approved or rejected. This flow will require a SharePoint site with a document library that contains Submitted, Approved, and Rejected folders, as shown in the following screenshot:

Figure 12.1 – Creating folders in the default document library

For this example, we'll be using a SharePoint site called Purchase Order Request (connected to the team that we used in the chapter), but you can use any SharePoint site that you like.