What it decides

Rule
SPO-MODERN-001
Applies to
sharepoint · site
Default severity
low
Basis
documented-guidance

On what authority

Microsoft states that "turning on the classic publishing feature for a modern communication site is not supported", and publishes a guide for moving from publishing sites to communication sites. It does not remove the feature or require anybody to stop using it, and an organisation with a working publishing portal may reasonably keep it. The second source is where the feature identifiers come from. They are quoted rather than remembered: `PublishingSite` is F6924D36-2FA8-4F0B-B16D-06B7250180FA at site scope and `PublishingWeb` is 94C94CA6-B32F-4DA9-A9E3-1F3D343D7ECB at web scope.

What it needs to decide

  • web.web_feature_ids

Without these facts the rule answers unknown, which is not a pass and is not a failure: it is the rule saying the evidence could not settle the question.

Where the evidence comes from

  • modernity: how one site is built: template, branding, publishing · live-validated

What a pass does not establish

A site that never had the publishing feature can still be entirely classic: classic pages, classic web parts, and a custom master page all exist without it. This rule reads one feature identifier and says nothing about how the site is actually built.

  • Only the web-scoped feature is read. The site-collection feature `PublishingSite` is collected as evidence and not evaluated here, because a site collection with it enabled and this web without it is a different situation that deserves its own rule rather than a footnote.
  • A feature identifier is not a measure of dependence. A publishing site with two pages and one with two thousand fail this rule identically.

Source

The rule as the Engine holds it, at the revision this page was generated from: 1.0.0b6@b4bf9c325233.

Generated from capability-manifest/1.0.0 at1.0.0b6@b4bf9c325233, contract1.0.0b6. Every fact on this page is the Engine's; this site publishes it and does not maintain it.