From c39ea17c45ebb611a82df7d26cde91e50961dcc0 Mon Sep 17 00:00:00 2001 From: Loreen La Penna <35536712+LoreenLa@users.noreply.github.com> Date: Mon, 8 Oct 2018 15:43:23 -0700 Subject: [PATCH] Added link to modernization scanner. --- .../publishing-sites-classic-to-modern-experience.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/SharePoint/SharePointOnline/publishing-sites-classic-to-modern-experience.md b/SharePoint/SharePointOnline/publishing-sites-classic-to-modern-experience.md index aa6ec64000..a2e35fc2ae 100644 --- a/SharePoint/SharePointOnline/publishing-sites-classic-to-modern-experience.md +++ b/SharePoint/SharePointOnline/publishing-sites-classic-to-modern-experience.md @@ -37,6 +37,8 @@ So, how you do move from publishing sites to communication sites? Here are some - [Audience targeting](#audience-targeting) +Additionally, the SharePoint Modernization scanner is a tool that you can use to find out which classic publishing features are used in your tenant or in a subset of site collections. Find this tool and more information about it in [Modernize classic publishing portals.](https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-publishing-portal) + ## Structure and navigation – use a hub site Let’s say your organization has a publishing site for Human Resources, with subsites for Benefits, Policies, Training, and Careers. It might be organized like this: