Merge pull request SharePoint#5477 from a1mery/patch-2

Replace Microsoft Flow by Power Automate

Author: andrewconnell

docs/declarative-customization/site-design-overview.md

@@ -1,7 +1,7 @@
 ---
 title: SharePoint site design and site script overview
 description: Use SharePoint site scripts and site designs to provide custom configurations to apply when new sites are created.
-ms.date: 12/19/2018
+ms.date: 03/24/2020
 localization_priority: Priority
 ---
 
@@ -130,7 +130,7 @@ Available actions include:
 - Applying a theme
 - Setting a site logo
 - Adding links to quick launch or hub navigation
-- Triggering a Microsoft Flow
+- Triggering a Power Automate flow
 - Installing a deployed solution from the app catalog
 - Setting regional settings for the site
 - Adding principals (users and groups) to SharePoint roles
@@ -248,27 +248,27 @@ The **WebTemplate** parameter set to the value 64 indicates registering this sit
 
 For step-by-step information about creating a site design, see [Get started creating site designs](get-started-create-site-design.md).
 
-## PnP provisioning and customization using Microsoft Flow
+## PnP provisioning and customization using Power Automate
 
-One action provided by site scripts is the ability to trigger a Microsoft Flow. This allows you to specify any custom action that you need beyond the actions provided natively in site scripts.
+One action provided by site scripts is the ability to trigger a Power Automate flow. This allows you to specify any custom action that you need beyond the actions provided natively in site scripts.
 
-If you use the PnP provisioning engine to automate site creation, you can use a Microsoft Flow to integrate with site designs. You can maintain all your existing provisioning scripts as well as create new custom provisioning scripts by using this technique.
+If you use the PnP provisioning engine to automate site creation, you can use a Power Automate flow to integrate with site designs. You can maintain all your existing provisioning scripts as well as create new custom provisioning scripts by using this technique.
 
 <br/>
 
 ![Process of triggering a Microsoft Flow](images/process-for-triggering-a-custom-flow.png)
 
 The process works as follows:
 
-1. The script instantiates your Microsoft Flow using a URL with additional details. 
+1. The script instantiates your Power Automate flow using a URL with additional details. 
 
 2. The flow sends a message to an Azure storage queue that you have configured. 
 
 3. The message triggers a call to an Azure function that you have configured. 
 
 4. The Azure function runs your custom script, such as the PnP provisioning engine, to apply your custom configurations. 
 
-For a step-by-step tutorial about how to configure your own Microsoft Flow with PnP provisioning, see [Build a complete site design using the PnP provisioning engine](site-design-pnp-provisioning.md).
+For a step-by-step tutorial about how to configure your own Power Automate flow with PnP provisioning, see [Build a complete site design using the PnP provisioning engine](site-design-pnp-provisioning.md).
 
 ## Scoping
 

docs/declarative-customization/site-design-pnp-provisioning.md

@@ -1,7 +1,7 @@
 ---
 title: Calling the PnP provisioning engine from a site script
 description: Build a complete SharePoint site design using the PnP provisioning engine
-ms.date: 11/27/2018
+ms.date: 03/24/2020
 localization_priority: Priority
 ---
 
@@ -14,7 +14,7 @@ This article describes how to create a site design that applies a PnP provisioni
 The steps in this article use the following components:
 
 - A site design and a site script
-- Microsoft Flow
+- Power Automate
 - Azure Queue storage
 - Azure Functions
 - A SharePoint Framework (SPFx) solution
@@ -67,7 +67,7 @@ Next, trust the app, so that it has the appropriate access to your tenant:
 
 ## Create the Azure Queue storage
 
-In this section, you will use Azure Queue storage to receive messages from Microsoft Flow. Every time a message shows up in the Queue storage, an Azure function is triggered to run a PowerShell script. 
+In this section, you will use Azure Queue storage to receive messages from Power Automate. Every time a message shows up in the Queue storage, an Azure function is triggered to run a PowerShell script. 
 
 To set up the Azure Queue storage:
 
@@ -85,7 +85,7 @@ To set up the Azure Queue storage:
 
 To put a message in the queue, you need to create a flow. 
 
-1. Go to the [Microsoft Flow](https://flow.microsoft.com) site, sign in, and choose **Create from Blank** at the top of the page.
+1. Go to the [Power Automate](https://flow.microsoft.com) site, sign in, and choose **Create from Blank** at the top of the page.
 1. Choose **Search hundreds of connectors and triggers** to select your trigger.
 1. Search for **Request**, and select **Request - When a HTTP Request is received**.
 1. Enter the following JSON as your request body:
@@ -313,7 +313,7 @@ The **Add-SPOSiteDesign** cmdlet associates the site design with the team site.
 
 ## Verify the results
 
-After you created your Azure Queue storage, you created the app ID for app-only access, the Azure Function, and the site design. You then triggered the Microsoft Flow from the site design. 
+After you created your Azure Queue storage, you created the app ID for app-only access, the Azure Function, and the site design. You then triggered the Power Automate flow from the site design. 
 
 To test the results, create a new site. In your SharePoint tenant, select **SharePoint** > **Create Site** > **Team Site**. Your new site design should show up as a design option. Notice that the site design is applied after the site is created. If you configured it correctly, your flow will be triggered. You can check the run history of the flow to verify that it ran correctly. Note that the footer might not show up immediately; if you don't see it, wait a minute and reload your site to check again.