Scanner doc updates

Author: jansenbe

docs/transform/media/modernize/excel_blogusage.png

@@ -1,7 +1,7 @@
 ---
 title: The SharePoint modernization scanner reports for the blog scanner mode
 description: Explains the blog output created by the modernization scanner
-ms.date: 10/23/2019
+ms.date: 11/27/2019
 ms.prod: sharepoint
 localization_priority: Priority
 ---
@@ -21,6 +21,7 @@ Column | Description
 **Site Collection Url** | Url of the scanned site collection.
 **SiteUrl** | Url of the scanned web.
 **Web Relative Url** | Relative Url of the scanned web.
+**Blog Type** | Is this a classic blog or Delve blog (requires scanner 2.7+).
 **Web Template** | Used web template (should all be BLOG#0).
 **Language** | Language used to create the blog site.
 **Blog Page Count** | Number of blog posts in this site.
@@ -38,6 +39,7 @@ Filter | Takeaway
 ---------|----------
 **No filter** | Lists all the blog sites found in your tenant.
 **Blog Page Count > 10 AND Change Year = this year** | A good filter to identify the actively used blog sites in your tenant. These sites are good candidates for modernization.
+**Blog Type = "Delve blogs"** | As Delve blogs are retired it's good to understand where they are used in your tenant. (requires scanner 2.7+)
 
 ## Understanding the ModernizationBlogPageScanResults.csv file
 
@@ -48,6 +50,7 @@ Column | Description
 **Site Collection Url** | Url of the scanned site collection.
 **SiteUrl** | Url of the scanned web.
 **Web Relative Url** | Relative Url of the scanned web.
+**Blog Type** | Is this a classic blog page or Delve blog page (requires scanner 2.7+).
 **Page Title** | Title of this blog post.
 **Modified At** | Last modified date of this blog post.
 **Modified By** | This blog post was last modified by.

docs/transform/media/modernize/excel_groupconnection.png

@@ -1,7 +1,7 @@
 ---
 title: The SharePoint modernization scanner reports for the Office 365 group connect scanner mode
 description: Explains the Office 365 group connect output created by the modernization scanner
-ms.date: 10/23/2019
+ms.date: 11/27/2019
 ms.prod: sharepoint
 localization_priority: Priority
 ---
@@ -31,6 +31,7 @@ Column | Description
 **ModernUIWarnings** | This is a collection of warnings indicating either some modern UI component was turned off or incompatible features/customizations have been detected. Possible values are `ModernPageFeatureDisabled` (modern pages are disabled for this site), `ModernListsBlockedAtSiteLevel` (modern UI for lists has been purposely been blocked at site collection level), `ModernListsBlockedAtWebLevel` (modern UI for lists has been purposely been blocked at web collection level), `MasterPageUsed` (a custom master page has been used), `AlternateCSSUsed` (alternate CSS was defined), `UserCustomActionUsed` (incompatible user custom actions have been found) and `PublishingFeatureEnabled` (publishing features are enabled).
 **WebTemplate** | The web template used by the site.
 **Office365GroupId** | If this site is already connected to an Office 365 group is shows the id if that group.
+**HasTeamsTeam** | Is there a Teams team created for the Office 365 Group connected to this site collection (as of version 2.7)
 **MasterPage** | Was a custom master page used?
 **AlternateCSS** | Was alternate CSS defined?
 **UserCustomActions** | Are there incompatible user custom actions used?
@@ -72,6 +73,7 @@ Filter | Takeaway
 **ReadyForGroupify = TRUE** | Will give you all the site collections that can be "Office 365 group connected". There might still be warnings to check, but we did not find any blocking issues
 **ReadyForGroupify = FALSE AND Office365GroupId = ""** | Will give you all the sites which do not yet have an Office 365 group connected and which can't be "Office 365 group connected"
 **ReadyForGroupify = TRUE AND GroupMode = PUBLIC** | Will give you all the site collections that can be "Office 365 group connected" and for which we'll default to a public group (based on the presence of the `everyone` or `everyone except external users` in the site members or site owners
+**HasTeamsTeam = FALSE AND WebTemplate = GROUP#0** | Modern group connected team sites that do not yet have a Teams team created for their Office 365 group (as of version 2.7)
 
 ## Understanding the ModernizationWebScanResults.csv file ##
 

docs/transform/modernize-scanner-reports-blogs.md

@@ -1,7 +1,7 @@
 ---
 title: The SharePoint modernization scanner
 description: Gets you started with the SharePoint modernization scanner
-ms.date: 11/19/2019
+ms.date: 11/27/2019
 ms.prod: sharepoint
 localization_priority: Priority
 ---
@@ -38,7 +38,9 @@ Since a typical scan needs to be able to scan all site collections it's recommen
 - [Granting access via SharePoint App-Only](../solution-guidance/security-apponly-azureacs.md)
 
 > [!IMPORTANT]
-> If you're choosing for Azure AD app-only, then above mentioned instructions grant the Azure AD app the **Sites.FullControl.All** permission, which is needed if you want to run all scan components. If you're not interested in workflow scanning you can also use **Sites.Read.All** as a permission as of version 2.6 of the SharePoint Modernization Scanner.
+> If you're choosing for Azure AD app-only, then above mentioned instructions grant the Azure AD app the **Sites.FullControl.All** permission, which is needed if you want to run **all** scan components.
+> If you're not interested in workflow scanning you can also use **Sites.Read.All** as a permission (as of version 2.6).
+> If you want to report on site collections that have a Teams team linked then you also need to add the **Group.Read.All** permission (as of version 2.7).
 
 Once the preparation work is done, let's continue with doing a scan.
 
@@ -61,6 +63,9 @@ If you've [setup access via Azure AD App-Only](../solution-guidance/security-app
 - **Certificate file**: the certificate that you granted app-only access to the Azure AD app, this needs to be presented as a password protected PFX file
 - **Password for the PFX file**: the password used to secure the previously provided PFX file
 
+> [!NOTE]
+> You can also opt to install the certificate on your computer and refence it via the -w command line parameters. To reference the certificate you would use this value for the -w parameter "My|CurrentUser|1FG498B468AV3895E7659C8A6F098FB701C8CDB1". You can use My/Root and CurrentUser/LocalMachine to identify the store. The last argument is the certificate thumbprint. This option is available as of the 2.7 release.
+
 > [!IMPORTANT]
 > The default instructions mentioned to grant the Azure AD app the **Sites.FullControl.All** permission which is needed if you want to run all scan components. If you're not interested in workflow scanning you can also use **Sites.Read.All** as a permission as of version 2.6 of the SharePoint Modernization Scanner.
 
@@ -180,7 +185,7 @@ Mode | Description
 ### Command line parameter overview
 
 ```Console
-SharePoint PnP Modernization scanner 2.6.0.0
+SharePoint PnP Modernization scanner 2.7.0.0
 Copyright (C) 2019 SharePoint PnP
 ==========================================================
 
@@ -287,5 +292,9 @@ https://contoso-admin.contoso.com -u [email protected] -p pwd
 
   -e, --separator                          (Default: ,) Separator used in output CSV files (e.g. ";")
 
+  -w, --storedcertificate                  (Default: ) Path to stored certificate in the form of
+                                           StoreName|StoreLocation|Thumbprint. E.g.
+                                           My|LocalMachine|3FG496B468BE3828E2359A8A6F092FB701C8CDB1
+
   --help                                   Display this help screen.
 ```