Skip to content

Commit df1fc58

Browse files
committed
Plugging the Microsoft 365 Assessment tool for workflow scanning
1 parent 60d4367 commit df1fc58

File tree

3 files changed

+12
-5
lines changed

3 files changed

+12
-5
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,9 @@ ms.localizationpriority: high
88

99
# SharePoint Modernization scanner reports: Workflow reports
1010

11+
> [!Note]
12+
> Assessing your workflow 2013 usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool)
13+
1114
## Excel dashboard
1215

1316
![Workflow dashboard](media/modernize/excel_workflowusage.png)

docs/transform/modernize-scanner-reports.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,9 @@ ms.localizationpriority: high
1010

1111
The output of a SharePoint Modernization Scanner run is a series of reports (CSV files and Excel dashboards). Using these outputs you can better understand what classic usage there is in your tenant, assess whether it's still relevant for you and get informed on potential remediation's needed before you can modernize. You would typically use the Microsoft Excel based dashboards to inspect the data and build up an understanding of the scan results. If you later on want to modernize sites, lists, etc you can use the CSV files as input for (PowerShell based) automation.
1212

13+
> [!Note]
14+
> Assessing your workflow 2013 usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool)
15+
1316
## Overview of the scanner output
1417

1518
The output you'll depends on the chosen scan mode. Below table lists the available scan modes:

docs/transform/modernize-scanner.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: The SharePoint modernization scanner
33
description: Gets you started with the SharePoint modernization scanner
4-
ms.date: 07/21/2020
4+
ms.date: 05/20/2022
55
ms.prod: sharepoint
66
ms.localizationpriority: high
77
---
@@ -14,14 +14,14 @@ Using the SharePoint Modernization scanner you can prepare your classic sites fo
1414
- Connecting these sites to a Microsoft 365 group
1515
- Modernizing the wiki and web part pages by creating modern site pages
1616
- Rebuilding classic publishing portals as modern publishing portals
17-
- Understanding where classic workflow is used
1817
- Understanding where InfoPath is being used
1918
- Understanding the usage of classic blog pages
2019

2120
This scanner is a key tool to use if you want to prepare for modernizing your classic sites as it will give you factual data about how easy it is to modernize your sites. Using the dashboards generated by the scanner you'll be able to drill down on the "modernization readiness" of your sites and plan the needed remediation work where needed.
2221

2322
> [!NOTE]
24-
> The SharePoint modernization scanner only is supported for running against SharePoint Online. For scanning on-premises SharePoint you can consider using the [SharePoint Migration Assessment Tool](https://docs.microsoft.com/sharepointmigration/overview-of-the-sharepoint-migration-assessment-tool) (SMAT) or the [Microsoft Consulting Services open source version of the on-premises workflow scanner](https://github.com/microsoft/SP-Server-Workflow-Scanner).
23+
> - Assessing your workflow 2013 usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool), this tool will step by step replace the still relevant features from the modernization scanner
24+
> - The SharePoint modernization scanner only is supported for running against SharePoint Online. For scanning on-premises SharePoint you can consider using the [SharePoint Migration Assessment Tool](https://docs.microsoft.com/sharepointmigration/overview-of-the-sharepoint-migration-assessment-tool) (SMAT) or the [Microsoft Consulting Services open source version of the on-premises workflow scanner](https://github.com/microsoft/SP-Server-Workflow-Scanner).
2525
>
2626
> [!IMPORTANT]
2727
> Modernization tooling and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from official Microsoft support channels.
@@ -214,12 +214,13 @@ Mode | Description
214214
`PageOnly` | Includes a scan from wiki and web part pages + includes the Microsoft 365 group connection readiness component
215215
`PublishingOnly` | Includes a classic publishing portal scan at site and web level + includes the Microsoft 365 group connection readiness component
216216
`PublishingWithPagesOnly` | Includes a classic publishing portal scan at site, web and page level + includes the Microsoft 365 group connection readiness component
217-
`WorkflowOnly` | Includes the classic workflow scan + includes the Microsoft 365 group connection readiness component
218-
`WorkflowWithDetailsOnly` | Includes the classic workflow scan with workflow migration readiness analysis + includes the Microsoft 365 group connection readiness component
219217
`InfoPathOnly` | Includes the InfoPath scan + includes the Microsoft 365 group connection readiness component
220218
`BlogOnly` | Includes the Blog scan + includes the Microsoft 365 group connection readiness component
221219
`CustomizedFormsOnly` | Includes the Customized Forms scan + includes the Microsoft 365 group connection readiness component
222220

221+
> [!Note]
222+
> Assessing your workflow 2013 usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool)
223+
223224
### Command-line parameter overview
224225

225226
```text

0 commit comments

Comments
 (0)