updates to group connection guidance

Author: jansenbe

docs/toc.yml

@@ -1319,6 +1319,9 @@
       href: transform/modernize-branding.md
     - name: Connect to an Office 365 group
       href: transform/modernize-connect-to-office365-group.md
+        items:
+        - name: Analyze and use the scanner data
+          href: transform/modernize-connect-to-office365-group-scanner.md
   - name: Branding and site provisioning solutions
     href: solution-guidance/Branding-and-site-provisioning-solutions-for-SharePoint.md
     items:

docs/transform/media/modernize/groupifyscanner_ready_2.png

@@ -1,11 +1,11 @@
 ---
-title: Understand and process the scanner results
+title: Analyze and use the scanner data
 description: Understand and process the scanner results to help your sites be in optimal shape for connecting an Office 365 group to them.
 ms.date: 06/07/2018
 ms.prod: sharepoint
 ---
 
-# Understand and process the scanner results
+# Analyze and use the scanner data
 
 To help you understand which sites are ready to be group-connected, you can use the [SharePoint Modernization Scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization) to analyze your environment. Use this article to understand how you can use the scanner output to prepare your sites for being connected to an Office 365 group. The scanner, as of version 1.5, will generate an Excel report plus several CSV files. It's recommended to use the Excel based dashboard to review the scanner data and when needed use the CSV data for more in depth data.
 

docs/transform/modernize-connect-to-office365-group-scanner.md

@@ -87,15 +87,15 @@ During the validation script execution, the following errors can appear:
 
 Error | Description
 ---------|----------
-**[ERROR] AzureAD Naming policy : _PrefixSuffix_ does contain AD attributes that are resolved based on the user running the group-connection** | In Azure AD, you can define a [naming policy for Office 365 groups](https://support.office.com/en-us/article/office-365-groups-naming-policy-6ceca4d3-cad1-4532-9f0f-d469dfbbb552?ui=en-US&rs=en-001&ad=US). If this policy contains user Active Directory attributes, this might be an issue because bulk group-connect handles all sites using the _current_ user.
-**[ERROR] AzureAD Creation policy : _adminUPN_ is not part of group _CanCreateGroupsId_ that controls Office 365 group creation** | If [Azure AD group creation is restricted to certain accounts](https://support.office.com/en-us/article/manage-who-can-create-office-365-groups-4c46c8cb-17d0-44b5-9776-005fced8e618?ui=en-US&rs=en-001&ad=US) and the _current_ account is not among those, the Office 365 group creation fails.
-**[ERROR] _siteUrl_ : Alias [_siteAlias_] contains a space, which is not allowed** | The alias of an Office 365 group cannot contain a space.
-**[ERROR] _siteUrl_ : Classification [_siteClassification_] does not comply with available Azure AD classifications [_ClassificationListString_]** | The provided site classification is not defined as [one of the allowed site classifications for Office 365 groups](https://support.office.com/en-us/article/Manage-Office-365-Groups-with-PowerShell-aeb669aa-1770-4537-9de2-a82ac11b0540).
-**[ERROR] _siteUrl_ : Alias [_siteAlias_] is in the Azure AD blocked word list [_CustomBlockedWordsListString_]** | If a [blocked words list is set up in Azure AD](https://support.office.com/en-us/article/office-365-groups-naming-policy-6ceca4d3-cad1-4532-9f0f-d469dfbbb552?ui=en-US&rs=en-001&ad=US) and the provided Office 365 group name uses such a word, this error is generated.
-**[ERROR] _siteUrl_ : Site is already connected to a group** | A site can only be connected to a single Office 365 group, so after a site is connected, it cannot be group-connected anymore.
-**[ERROR] _siteUrl_ : Alias [_siteAlias_] is already in use** | Each Office 365 group needs a unique alias; an error is generated when the proposed alias was already used by another Office 365 group.
-**[ERROR] _siteUrl_ : Alias [_siteAlias_] was already marked as approved alias for another site in this file** | The proposed site alias was already defined for another site in earlier input lines of the bulk group-connect CSV file.
-**[ERROR] _siteUrl_ : Site does not exist or is not available (status = _site.Status_)** | The provided site URL does not represent a reachable site collection.
+**AzureAD Naming policy : _PrefixSuffix_ does contain AD attributes that are resolved based on the user running the group-connection** | In Azure AD, you can define a [naming policy for Office 365 groups](https://support.office.com/en-us/article/office-365-groups-naming-policy-6ceca4d3-cad1-4532-9f0f-d469dfbbb552?ui=en-US&rs=en-001&ad=US). If this policy contains user Active Directory attributes, this might be an issue because bulk group-connect handles all sites using the _current_ user.
+**AzureAD Creation policy : _adminUPN_ is not part of group _CanCreateGroupsId_ that controls Office 365 group creation** | If [Azure AD group creation is restricted to certain accounts](https://support.office.com/en-us/article/manage-who-can-create-office-365-groups-4c46c8cb-17d0-44b5-9776-005fced8e618?ui=en-US&rs=en-001&ad=US) and the _current_ account is not among those, the Office 365 group creation fails.
+**_siteUrl_ : Alias [_siteAlias_] contains a space, which is not allowed** | The alias of an Office 365 group cannot contain a space.
+**_siteUrl_ : Classification [_siteClassification_] does not comply with available Azure AD classifications [_ClassificationListString_]** | The provided site classification is not defined as [one of the allowed site classifications for Office 365 groups](https://support.office.com/en-us/article/Manage-Office-365-Groups-with-PowerShell-aeb669aa-1770-4537-9de2-a82ac11b0540).
+**_siteUrl_ : Alias [_siteAlias_] is in the Azure AD blocked word list [_CustomBlockedWordsListString_]** | If a [blocked words list is set up in Azure AD](https://support.office.com/en-us/article/office-365-groups-naming-policy-6ceca4d3-cad1-4532-9f0f-d469dfbbb552?ui=en-US&rs=en-001&ad=US) and the provided Office 365 group name uses such a word, this error is generated.
+**_siteUrl_ : Site is already connected to a group** | A site can only be connected to a single Office 365 group, so after a site is connected, it cannot be group-connected anymore.
+**_siteUrl_ : Alias [_siteAlias_] is already in use** | Each Office 365 group needs a unique alias; an error is generated when the proposed alias was already used by another Office 365 group.
+**_siteUrl_ : Alias [_siteAlias_] was already marked as approved alias for another site in this file** | The proposed site alias was already defined for another site in earlier input lines of the bulk group-connect CSV file.
+**_siteUrl_ : Site does not exist or is not available (status = _site.Status_)** | The provided site URL does not represent a reachable site collection.
 
 > [!NOTE]
 > Please update the `$tenantAdminUrl` variable in the following script to contain your tenant admin center URL (for example, `https://contoso-admin.sharepoint.com`).