Requirements

This page lists the classic pages assessment specific requirements and options.

Permission requirements

When using the classic pages module of the Microsoft 365 Assessment tool you do need to use a configured Entra application (learn more here). The classic pages assessment reads page content and web part configuration via CSOM and queries SharePoint search for page usage, so it needs read access to the assessed sites.

Authentication	Minimal
Application	Graph: Sites.Read.All SharePoint: Sites.FullControl.All
Delegated	Graph: Sites.Read.All, User.Read SharePoint: AllSites.FullControl

Note

Sites.FullControl.All is requested because reading a classic web part page's web part inventory via the LimitedWebPartManager API requires more than read-only access. If a future release can lower this requirement it will be reflected here.

Command line arguments for starting an assessment

The classic pages assessment is selected with --mode Classic and the --classicinclude Pages component. The following page-scan specific arguments are available (they are only valid together with --mode Classic):

Argument	Description
--classicinclude Pages	Include the classic page scan in a classic assessment. When --classicinclude is omitted all classic components are included.
--exportwebpartproperties	Also export each web part's properties (as JSON) into the per-web-part inventory. Off by default to keep the export compact.
--skipusageinformation	Skip collecting page usage information (recent / lifetime views and their unique users) via SharePoint search. Use this to speed up the assessment or when search-based usage is not needed.
--skipuserinformation	Skip collecting page user information (e.g. the page's Modified By).
--homepageonly	Only assess the home page of each web, rather than every classic page. Useful for a fast home-page modernization-readiness assessment.

Note

To learn more about starting an assessment checkout the Microsoft 365 Assessment tool Start documentation.