SharePoint Online Governance Command Center

Mature-tenant modernization · SharePoint Advanced Management · Microsoft Purview · Entra · Copilot readiness
Data: simulated v1 · Oct 24, 2026
Executive view

Governance posture of a mature SharePoint Online tenant

Baseline from a first-30-day assessment. Six headline signals tell leadership where risk, cost and Copilot exposure sit today. Click any KPI for its definition, data source, threshold and remediation path.

Copilot readiness: 3 of 9 gates
Reference scenarioMultinational manufacturer · 18 countries · tenant active 8+ years · ~9,800 sites
TeamTwo-person M365 platform team plus one governance SME; international site owners
TriggerMicrosoft 365 Copilot rollout and Purview integration on the near-term roadmap
PainAutomated site creation retired; manual requests now queue for weeks
Governance maturity LOW
0/ 5
Target 4.0 in 6 months
Below 2-owner standard HIGH
0
318 ownerless · 2,214 single-owner
Inactive 180+ days WATCH
0
31.8% of sites · 41 TB stored
Org-wide grants HIGH
0sites
EEEU / Everyone · 61 hold sensitive content
Container label coverage LOW
0%
Target ≥ 90% of active sites
Site-request backlog HIGH
0open
Median wait 13 days · SLA 2 days
0
Active sites (excl. OneDrive)
0
Teams-connected sites (incl. channels)
0
Guest accounts · 1,388 stale 90d+
0
Active "Anyone" links
0
Apps with tenant-wide Sites.* write
0
Sites under a retention policy

Maturity by governance domain — baseline vs. 90-day vs. 6-month target

Scored 1–5 against the control catalog below. Lowest today: Copilot readiness, ownership & lifecycle, permissions.

Risk concentration by site type

Count of sites carrying each risk signal. One site can carry several.

Role alignment

SharePoint Online Governance & Administration SME — requirements mapped

Every responsibility and qualification in the role brief, and the section of this command center that exercises it. Click a row to jump there.

27 / 27 items mapped
RequirementTypeWhere it shows upSection
Assess

Environment assessment — inventory, age and prioritized findings

Inventory built from PnP PowerShell, Microsoft Graph and SharePoint Advanced Management data-access-governance reports, then scored. Findings are ranked by exposure × likelihood × Copilot amplification.

2 critical · 5 high

Site inventory by type

9,846 active sites, OneDrive excluded.

Sites created per year — and where provisioning stalled

Teams adoption drove the 2020 peak. Creation falls from 2024 as automated provisioning was retired and requests moved to a manual queue.

Prioritized findings

Evidence column cites the report or script that produced it. Click a finding for the full analysis and remediation.

IDSeverityFindingEvidenceRemediationSection
Plan

Six-month modernization roadmap

Sequenced so the backlog and the highest Copilot exposure are handled first, controls are proven in simulation before enforcement, and repeatable work is documented and handed to support by month six.

Workstream timeline (weeks 1–26)

Click a workstream for scope, dependencies and exit criteria.

Govern

Governance standards — and how each one is enforced

A standard without an enforcement mechanism is a suggestion. Each row names the technical control, the evidence it produces, and the KPI that proves it is working.

12 standards
DomainStandardEnforcementEvidence · KPI

External sharing tiers — bound to sensitivity labels

The container label chosen at request time sets privacy, sharing ceiling, guest access, unmanaged-device access and default link type.

TierLabelSharing ceilingDefault linkGuestsUnmanaged devicesExtra controls
Govern

Site provisioning — clearing the backlog and restoring automation

Governed self-service: every request is classified at intake, approved by policy rather than by inbox, and provisioned the same way every time with owners, label, sharing tier, hub and retention already set.

164 requests waiting

Backlog projector

Model how fast the queue clears. Adjust intake, manual capacity and how much is automated, and when automation comes back.

Request classes & service levels

Triage of the current queue. Standard classes go fully automated; exceptions keep a human approval.

ClassQueuePathSLA

Provisioning runbook — Azure Automation (PowerShell 7.4, managed identity)

Excerpt. The provisioning identity is the one place tenant-wide write is justified; it is non-interactive, certificate-free, monitored and scoped by Conditional Access for workload identities.


        
Govern

Site lifecycle with SharePoint Advanced Management

Inventory → inactivity detection → owner attestation → access recertification → read-only → Microsoft 365 Archive → approved deletion, with retention holds checked before anything is disposed of.

3,127 sites in the inactive cohort

Inactive-site cohort — outcome funnel

Outcome of the first inactive-site policy cycle. Click a stage.

Lifecycle actions per month

Archive and deletion only begin after a full notification cycle and a retention check.

SharePoint Advanced Management policy register

Each policy is run in simulation or report mode first, then scoped, then enforced. Click a policy.

Policy / capabilityScopeActionCadenceStatus
Protect

Permissions & sharing remediation

Eight years of collaboration leave broad grants, stale links, direct user permissions and broken inheritance behind. Remediation runs in waves, highest-sensitivity first, with owners in the loop and a rollback record for every change.

0
Sites with EEEU / Everyone
0
"Anyone" links · 64% no expiry
0
External specific-people links
0
Unique-permission scopes
0
Direct user grants (no group)
0
Ownerless sites

Active sharing links by type

From the SAM sharing-links data-access-governance reports.

Remediation burn-down — weeks 1–14

Org-wide-grant sites and Anyone links, planned vs. actual.

Remediation waves

WaveTargetMethodOwner involvementGuardrail
Protect

Microsoft Purview — sensitivity labels, DLP, retention, records and audit

Labels classify containers and content; DLP acts on what labels and sensitive-information types find; retention and records keep what the business and regulators require and dispose of the rest with a reviewable trail.

Sensitivity label taxonomy

Four parent labels, few sublabels. Container settings apply to sites, Teams and Microsoft 365 groups; item settings apply to files and email.

Label coverage — baseline and plan

Containers, files labeled by users, files labeled by auto-labeling policies.

DLP matches in simulation — 30 days

SharePoint and OneDrive matches by sensitive information type, before enforcement.

DLP policy register

PolicyLocationsConditionActionMode

Retention, records & audit

ControlTypeScopeRetention & dispositionOwner
Protect

Microsoft Entra — least privilege for admins, support, automation and apps

No standing SharePoint administration. Human admins activate through PIM; automation runs as managed identities or certificate-bound apps limited to the sites they need with Sites.Selected.

17 apps with tenant-wide write

Privileged roles — standing vs. eligible

Current state vs. target after PIM rollout.

Conditional Access for SharePoint administration and content

PolicyTargetsGrant / sessionState

Applications and service principals with SharePoint access

Produced by Get-SharePointAppPermissions.ps1. Click a row for the decision record.

ApplicationPermission todayCredentialRiskTarget
Protect

Microsoft 365 Copilot & AI agent readiness

Copilot does not grant new access — it makes existing access instantly searchable and summarizable. Readiness is therefore permissions hygiene, labeling and lifecycle, gated before each licensing wave.

3 of 9 gates passed

Exposure boundary — what an average employee can reach

Sites reachable through org-wide grants and files reachable through org-wide or Anyone links, projected by week.

Licensing waves & entry criteria

WaveUsersEntry gate
Interim control: Restricted Content Discovery hides flagged sites from Copilot and org-wide search while owners remediate. Restricted SharePoint Search (100-site allow list) stays a last resort — it narrows Copilot for everyone.
Operate

Automation — PnP PowerShell, Microsoft Graph and SharePoint Online Management Shell

Inventory, permissions analysis, notifications and remediation run as scheduled, idempotent scripts with -WhatIf support and CSV evidence. Source is in the scripts folder of this repository.

ScriptPurposeModules / APIsAuth modelOutput

Code


        

Authentication models

Interactive admin
Delegated, tenant-registered Entra app (the shared PnP Management Shell app was retired Sept 2024), PIM-activated role
Scheduled jobs
Azure Automation managed identity; no secrets to rotate
Off-Azure jobs
App-only with certificate in Key Vault; never client secrets
Scoped apps
Sites.Selected with per-site read / write / owner grants
APIs
Microsoft Graph v1.0 first; SharePoint REST and CSOM where Graph has gaps (role assignments, sharing links, tenant settings)
Scale
Graph $batch, delta queries, honor Retry-After on 429/503
Operate

System KPIs and executive reporting

KPIs agreed with leadership and regional IT, each with a formula, a source of truth, a target and an owner. Power BI serves the executive view; operational reports go to site owners and the support team.

KPIFormulaSourceBaselineTargetCadenceOwner

Six-month KPI trajectory

Plan of record. Actuals replace the projection as the monthly snapshots land.

Operate

Documentation, RACI, change control and support transition

Everything built is documented as it is built. Repeatable work moves to the support team through runbooks and knowledge articles, and high-risk changes follow one protocol across time zones.

Documentation set

RACI — governance decisions across Security, Legal, Privacy, Records, Audit and the business

R responsible · A accountable · C consulted · I informed

High-risk change protocol

Subject-matter expert

Experience behind this model — Kenneth P. Barnes

Microsoft MVP (SharePoint, Project), former Microsoft Premier Consultant for Microsoft 365 and security, and 600+ SharePoint migrations. The controls on this page are the ones applied in that work.

Credentials

Engagement model: remote, hands-on SME embedded with a two-person platform team — assess, build, document, and hand over.