Merge branch 'master' of https://github.com/SharePoint/sp-dev-docs

VesaJuvonen · VesaJuvonen · commit 0d877713ce02 · 2020-07-16T16:14:36.000+03:00
diff --git a/docs/business-apps/power-automate/guidance/customize-page-approvals.md b/docs/business-apps/power-automate/guidance/customize-page-approvals.md
@@ -1,6 +1,6 @@
 ---
 title: Customize SharePoint page approvals to meet your needs
-ms.date: 05/14/2020
+ms.date: 07/12/2020
 ---
 
 # Customize SharePoint page approvals to meet your needs
@@ -11,7 +11,7 @@ However, you can add more processes, or even modify how the approval process wor
 
 To customize the default page approval flow, for a few scenarios, check out the following video:
 
-> [!VIDEO https://youtu.be/pKrHoG70FrM]
+> [!Video https://www.youtube.com/embed/pKrHoG70FrM]
 
 ## Create more than one approval flow
 
diff --git a/docs/business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md b/docs/business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md
@@ -1,6 +1,6 @@
 ---
 title: Guidance - Migrate from classic workflows to Power Automate flows in SharePoint
-ms.date: 06/30/2020
+ms.date: 07/13/2020
 ---
 
 # Guidance: Migrate from classic workflows to Power Automate flows in SharePoint
@@ -48,6 +48,19 @@ To create and author flows, users primarily use [Power Automate website](https:/
 
 To learn more about building workflows using Power Automate in SharePoint, start here: Business apps and Business process [automation in SharePoint](https://docs.microsoft.com/sharepoint/dev/business-apps/introduction-to-sharepoint-business-process-integration).
 
+## Pain points in moving between classic workflows in SharePoint and Power Automate flows
+
+Many people feel there are significant gaps between SharePoint Designer (classic) workflows and Power Automate flows, but the list is not long. Of course, there are some workarounds you should consider in your planning as you move from classic workflows to Power Automate flows.
+	
+- **30 day run limit for flows** – SharePoint Designer workflows can run endlessly, but flows have a 30 day lifespan. Getting beyond this limitation means your flow will need to call itself in a re-entrant way to restart the clock ticking.
+- **HTTP Connector** – Flow has an HTTP connector (as an action), but it is a Premium connector. If you use HTTP calls extensively, you may want to create a “service account” user with a Power Automate license and run these flows with that user account. This also will make it easier to manage the set of flows you consider "enterprise" flows.
+- **Custom permissions on list items** – While there is not a flow action to accomplish this, it is possible to do it with an HTTP call.
+- **Reusable Flows** – Using some modular thinking, you can create a master flow which a flow per list or library can call to do the heavy lifting. (In some ways this is even preferable, as you can edit a flow which is used in many locations centrally.) Alternatively, you can use flow actions to discover all of the lists or libraries which match some criteria and run the flow on them all on a timer rather than based on events.
+- **Workflow history storage** – Flows maintain a history in the context of the flow itself in the Power Automate dashboard. If you need tracking in your sites, you can have the flow log information in a list you create.
+- **Impersonation** - In SharePoint 2010 workflows, you can add an impersonation step to act as a different user. This capability is not readily available in flows.
+
+While these pain points do exist, you can see there are workarounds for each of them.
+
 ## Modern approvals with Power Automate flows
 
 Approvals are the most common workflow scenario when it comes to automating business processes in SharePoint. Transitioning to Power Automate flows, approvals can be streamlined for data in SharePoint, Dynamics 365, forms, SQL, and so on. You can create approvals in your workflow, and view sent and received requests in a unified Actions center. Power Automate approvals enable users to customize flows and create approvals for the following types:
diff --git a/docs/declarative-customization/list-form-conditional-show-hide.md b/docs/declarative-customization/list-form-conditional-show-hide.md
@@ -120,7 +120,7 @@ An example checking if the dates from [$StartDate] and [$EndDate] columns are be
 The following formula checks if the person column [$Owner] is equal to a specific user's email.
 
 ```
-=if([$Owner.email]=='chaksc@microsoft.com', 'true', 'false')
+=if([$Owner.email]=='nestorw@contoso.com', 'true', 'false')
 ```
 
 ##### Boolean (Yes/No) column
diff --git a/docs/solution-guidance/Use-remote-event-receivers-in-SharePoint.md b/docs/solution-guidance/Use-remote-event-receivers-in-SharePoint.md
@@ -10,7 +10,7 @@ Use remote event receivers to handle events in the SharePoint Add-in model. Use
 _**Applies to:** add-ins for SharePoint | SharePoint 2013 | SharePoint Online_
 
 >**Important**
->As of January 2017 SharePoint Online does support list webhooks which you can use instead of "-ed" remote event receivers. Checkout [Overview of SharePoint webhooks](https://developer.microsoft.com/office/sharepoint/docs/apis/webhooks/overview-sharepoint-webhooks) to learn more about webhooks. Also note that several webhook samples are available from the [sp-dev-samples](https://github.com/SharePoint/sp-dev-samples/tree/master/Samples) GitHub repository.
+>As of January 2017 SharePoint Online does support list webhooks which you can use instead of "-ed" remote event receivers. Checkout [Overview of SharePoint webhooks](https://docs.microsoft.com/sharepoint/dev/apis/webhooks/overview-sharepoint-webhooks) to learn more about webhooks. Also note that several webhook samples are available from the [sp-dev-samples](https://github.com/SharePoint/sp-dev-samples/tree/master/Samples) GitHub repository.
 
 The  [Core.EventReceivers](https://github.com/SharePoint/PnP/tree/master/Samples/Core.EventReceivers) sample shows how to use a provider-hosted add-in with a remote event receiver to handle the AppInstalled and AppUninstalling events. The AppInstalled and AppUninstalling events set up and remove SharePoint objects that the add-in uses when it runs. Additionally, the AppInstalled event handler adds the ItemAdded event handler to a list. Use this solution if you want to:
 
diff --git a/docs/spfx/release-1.7.1.md b/docs/spfx/release-1.7.1.md
@@ -34,7 +34,7 @@ This release is primarily a bug fix release to address few regressions and misse
 ## Changes in this release
 
 - Update title of user data property title in dynamic data
-- Add workaround for Yarn's **@types/react** resolution issue
+- Add workaround for Yarn's **\@types/react** resolution issue
 - Don't show/provision beta components in the non-beta install.
 - Update debugger **launch.json** config.
 - Add a dependency on TypeScript to meet the peer dependency requirements of **tslint-microsoft-contrib**.
diff --git a/docs/spfx/release-1.8.1.md b/docs/spfx/release-1.8.1.md
@@ -33,7 +33,7 @@ This is a _minor bump_ that fixes the issues with the Yeoman generator, projects
 
 ## Changes in this release
 
-- Fixed: Not able to set up SharePoint Server 2016 or SharePoint Server 2019 on premises using **@microsoft/sharepoint** Yeoman generator  (two issues mentioned – incorrect SupportedHosts property and incorrect reference to sp-property-pane)
+- Fixed: Not able to set up SharePoint Server 2016 or SharePoint Server 2019 on premises using **\@microsoft/sharepoint** Yeoman generator  (two issues mentioned – incorrect SupportedHosts property and incorrect reference to sp-property-pane)
   - [#3621](https://github.com/SharePoint/sp-dev-docs/issues/3621)
 - Fixed: Can't use **loadLegacyFabricCss** in SPFX 1.8
   - [#3612](https://github.com/SharePoint/sp-dev-docs/issues/3612)
diff --git a/docs/spfx/sharepoint-framework-overview.md b/docs/spfx/sharepoint-framework-overview.md
@@ -18,7 +18,7 @@ Key features of the SharePoint Framework include:
 - It runs in the context of the current user and connection in the browser. There are no iFrames for the customization (JavaScript is embedded directly to the page).
 - The controls are rendered in the normal page DOM.
 - The controls are responsive and accessible by nature.
-- It enables the developer to access the lifecycle in addition to **render**, **load**, **serialize* and **deserialize**, **configuration changes**, and more.
+- It enables the developer to access the lifecycle in addition to **render**, **load**, **serialize** and **deserialize**, **configuration changes**, and more.
 - It's framework-agnostic. You can use any JavaScript framework that you like including, but not limited to, React, Handlebars, Knockout, Angular, and Vue.js.
 - The developer toolchain is based on popular open-source client development tools such as NPM, TypeScript, Yeoman, webpack, and gulp.
 - Performance is reliable.
diff --git a/docs/spfx/toolchain/implement-ci-cd-with-azure-devops.md b/docs/spfx/toolchain/implement-ci-cd-with-azure-devops.md
@@ -12,12 +12,12 @@ Azure DevOps (Visual Studio Team Services / Team Foundation Server) consists of
 
 This article explains the steps involved in setting up your Azure DevOps environment with Continuous Integration and Continuous Deployment to automate your SharePoint Framework builds, unit tests, and deployment.
 
-## Chosing between Azure Multi-stage Pipelines (preview) and Azure DevOps builds and releases
+## Choosing between Azure Multi-stage Pipelines (preview) and Azure DevOps builds and releases
 
-There are currently two approaches available to implement continuous integration, and deployement in Azure DevOps.  
+There are currently two approaches available to implement continuous integration, and deployment in Azure DevOps.  
 Azure builds and releases is the historic one, featuring a graphical edition experience and storing the definitions in a JSON document hidden from the user.  
 Azure multi-stage Pipelines is a newer feature still in preview, is relies on pipeline definitions stored as YAML files on the repository providing transparency, version history and repeatability.  
-Both approaches are decribed for the SharePoint Framework:
+Both approaches are described for the SharePoint Framework:
 
 - Azure Build and Release (this article)
 - [Azure Multi-stage Pipelines](./implement-ci-cd-with-azure-pipelines.md)
@@ -213,7 +213,7 @@ Add a `Node tool installer` task and define `10.X` in the `Version Spec` field.
 
 ### Installing the Office 365 CLI
 
-The Office 365 Common Language Interface (CLI) is an open source project built by the OfficeDev PnP Community. In order to leverage the  CLI as part of your Release Definition, you first need to install it.  Then, you will be able to take advantage of commands available  to handle deployment. Add a `npm` task, select a `Custom` command and type `install -g @pnp/office365-cli` in the `Command and Arguments` field.
+The Office 365 Common Language Interface (CLI) is an open source project built by the OfficeDev PnP Community. In order to leverage the  CLI as part of your Release Definition, you first need to install it.  Then, you will be able to take advantage of commands available to handle deployment. Add a `npm` task, select a `Custom` command and type `install -g @pnp/office365-cli` in the `Command and Arguments` field.
 
 ![installing office 365 cli](../../images/azure-devops-spfx-14.png)
 
diff --git a/docs/spfx/toolchain/implement-ci-cd-with-azure-pipelines.md b/docs/spfx/toolchain/implement-ci-cd-with-azure-pipelines.md
@@ -1,7 +1,7 @@
 ---
 title: Implement Continuous Integration and Continuous deployment using Azure Pipelines (preview)
 description: Streamlining the build and deployment process by automating manual steps.
-ms.date: 12/19/2019
+ms.date: 07/13/2020
 ms.prod: sharepoint
 localization_priority: Priority
 ---
@@ -15,7 +15,7 @@ This article explains the steps involved in setting up your Azure Pipelines envi
 
 ## Choosing between Azure Multi-stage Pipelines (preview) and Azure DevOps builds and releases
 
-There are currently two approaches available to implement continuous integration, and deployement in Azure DevOps.  
+There are currently two approaches available to implement continuous integration, and deployment in Azure DevOps.  
 Azure builds and releases is the historic one, featuring a graphical edition experience and storing the definitions in a JSON document hidden from the user.  
 
 Azure multi-stage Pipelines is a newer feature still in preview, is relies on pipeline definitions stored as YAML files on the repository providing transparency, version history, and repeatability.  
@@ -208,7 +208,7 @@ To create the variable group, follow these steps:
 1. Under __Pipelines__ select __Library__
 1. Add a new __Variable Group__ making sure the name matches what is defined in the pipeline definition
 1. Add the following variables to the group and select __Save__
-    - o365_user_login: the user login of a SharePoint tenant administator
+    - o365_user_login: the user login of a SharePoint tenant administrator
     - o365_user_password: the user password of the account
     - o365_app_catalog_site_url: the url of the app catalog site collection
 
diff --git a/docs/toc.yml b/docs/toc.yml
@@ -125,7 +125,7 @@
     href: spfx/sharepoint-framework-overview.md
   - name: Getting started
     items:
-    - name: Set up Office 365 tenant
+    - name: Set up Microsoft 365 tenant
       href: spfx/set-up-your-developer-tenant.md
     - name: Set up development environment
       href: spfx/set-up-your-development-environment.md
@@ -430,6 +430,8 @@
       href: spfx/release-1.9.1.md
     - name: SPFx v1.8.2 - May 7, 2019
       href: spfx/release-1.8.2.md
+    - name: SPFx v1.8.1 - April 16, 2019
+      href: spfx/release-1.8.1.md
     - name: SPFx v1.8.0 - March 14, 2019
       href: spfx/release-1.8.0.md
     - name: SPFx v1.7.1 - December 18, 2018
diff --git a/docs/transform/media/modernize/scanner_consent.png b/docs/transform/media/modernize/scanner_consent.png
diff --git a/docs/transform/modernize-scanner.md b/docs/transform/modernize-scanner.md
@@ -1,7 +1,7 @@
 ---
 title: The SharePoint modernization scanner
 description: Gets you started with the SharePoint modernization scanner
-ms.date: 02/14/2020
+ms.date: 07/13/2020
 ms.prod: sharepoint
 localization_priority: Priority
 ---
@@ -32,7 +32,7 @@ Since SharePoint Online continuously evolves and more and more modern capabiliti
 
 ## Step 2: Preparing for a scan
 
-Since a typical scan needs to be able to scan all site collections, it's recommended to use an app-only principal with tenant scoped permissions for the scan. This approach will ensure the scanner always has access, if you use an account (for example, your SharePoint tenant admin account) then the scanner can only access the sites where this user also has access. You can either use an Azure AD application or a SharePoint app principal for app-only access:
+Since a typical scan needs to be able to scan all site collections, it's recommended to use an app-only principal with tenant scoped permissions for the scan. This approach will ensure the scanner always has access, if you use an account (for example, your SharePoint tenant admin account) then the scanner can only access the sites where this user also has access. You can either use an Azure AD application or a SharePoint app principal for app-only access and below links describe the manual approach to setting up things. As the recommended approach is Azure AD App-Only, you can easy the setup of your Azure AD application by using the [PnP PowerShell](https://aka.ms/pnppowershell) `Initialize-PnPPowerShellAuthentication` cmdlet. See the **Using Initialize-PnPPowerShellAuthentication to setup Azure AD App-Only** chapter for more details.
 
 - [Granting access via Azure AD App-Only (recommended)](../solution-guidance/security-apponly-azuread.md)
 - [Granting access via SharePoint App-Only](../solution-guidance/security-apponly-azureacs.md)
@@ -44,6 +44,26 @@ Since a typical scan needs to be able to scan all site collections, it's recomme
 
 Once the preparation work is done, let's continue with doing a scan.
 
+### Using Initialize-PnPPowerShellAuthentication to setup Azure AD App-Only
+
+To configure Azure AD App-Only using PnP PowerShell follow these steps:
+
+1. Install [PnP PowerShell](https://aka.ms/pnppowershell) or update it to the April 2020 or a more recent version
+2. Use the `Initialize-PnPPowerShellAuthentication` cmdet to setup an Azure AD app:
+
+```PowerShell
+Initialize-PnPPowerShellAuthentication -ApplicationName ModernizationScannerApp -Tenant contoso.onmicrosoft.com -Scopes "SPO.Sites.FullControl.All","MSGraph.Group.Read.All"  -OutPath c:\temp -CertificatePassword (ConvertTo-SecureString -String "password" -AsPlainText -Force)
+```
+
+3. You'll be asked to authenticate, ensure you authenticate with a user that is a tenant administrator
+4. The cmdlet will setup an Azure AD app and wait for 60 seconds to give Azure AD time to handle the App creation
+5. You'll be asked to consent the permissions granted to the created Azure AD application:
+   1. First you'll be asked to login again, use a tenant administrator account
+   2. Next the consent dialog is shown with the requested permissions (see screenshot below). Click **Accept**
+6. Store the returned AzureAppId, created PFX file and password somewhere safe, you'll need to use it as described in below chapter **Authenticate via Azure AD app-only**
+
+![Scanner consent](media/modernize/scanner_consent.png)
+
 ## Step 3: Launch a scan using the user interface option
 
 The easiest approach is to simply launch SharePoint.Modernization.Scanner.exe as the scanner does have a UI. Alternatively you can start a (PowerShell) command prompt and navigate to that folder so that you can use the scanner via command line. This chapter will walk you through the UI option taking a typical **full** scan. Start by launching the SharePoint.Modernization.Scanner.exe.
