Always-on health for the Microsoft 365 intranet you actually trust.
One short page for governance leads and executive buyers landing on the Wardwell site. Who's behind it, what it watches inside the Microsoft 365 intranet, and where the platform sits today — without a sales call to walk you through it.
Questions covered
jump to oneThe mission
Wardwell watches the parts of the Microsoft 365 intranet that quietly rot while no one owns them — the broken URL references inside SharePoint pages, the stale sites nobody has refreshed since the last site redesign, the alt-text and contrast regressions a recent round of authoring introduced, and the missing SharePoint patches the Microsoft-recommended baseline surfaces week after week. The aim is the same on every one of those: a defensible, dated finding an intranet owner can act on before an audit, not after.
What Wardwell patrols — and where it stops
- Read-only Microsoft Graph scope (six permissions, never broader) — over the tenant admin's own Entra app, against their own SharePoint and Microsoft 365 estate.
- A per-tenant weekly digest plus a per-finding rolling history on ScanFinding — the audit surface an admin triages from /issues.
- Nothing about end-users: no People API reads, no contact or calendar pulls, no Teams message inspection, and never a raw file body — metadata only (path, etag, last-modified stamp, redirect picture).
What Wardwell watches
Wardwell runs an always-on scan over the customer's own Entra tenant via read-only Microsoft Graph. Every scan surfaces one row per finding it observed; the four categories below are the kinds of finding the scan walker emits, in the order a governance lead will read them.
- Broken links — SharePoint files and pages where outbound references 404 or follow redirect chains to dead targets; flagged from the per-finding rows the scan walker emits.
- Outdated pages — SharePoint pages whose LastModifiedfalls behind the customer's published SLA, observed vs. the last site-redesign cycle; surfaced via Scan lastSeenAt deltas.
- Accessibility regressions — alt-text drops, contrast regressions, missing lang attributes, and other WCAG 2.1 AA findings the scan walker surfaces; matches the WCAG 2.1 AA evidence export that ships with every plan.
- Missing patches— pages or files where known Microsoft-recommended SharePoint patch advisories apply but the customer's tenant hasn't applied them; the same posture covered by the ShieldHalf badge on /pricing.
Wardwell never reads file bodies — only metadata (path, etag, last-modified stamp, redirect-chain picture). See /compliance for the full data-residency story.
A note from the founder
Intranet owners should have the same observability a public website has had for a decade: a weekly, dated digest of what's broken, what's stale, and what regressed — without the multi-tenant application token you'd expect from a vendor scanning your tenant's content. That is the platform Wardwell is, and the platform Wardwell is becoming — and the bar is "useful enough that an intranet owner opens it on Monday morning and a compliance lead trusts it on Tuesday afternoon".
I built Wardwell because the M365 intranet is the place most knowledge actually lives, and it is the place with the fewest tools watching it. The five-minute Entra app-registration flow, the per-tenant pilot, and the weekly digest are the convincers — every customer we onboard lands on the same path, and the platform does the same job on every tenant it is pointed at.
— Andrew, founder
Status
Wardwell is onboarding a small cohort of Microsoft 365 customers ahead of general availability. The weekly digest (referenced in /pricing and /sample-report) and the per-tenant pilot cycle are how it goes live — one tenant at a time, on managed Postgres, without a procurement tax.
See a real anonymized weekly digest
See a real anonymized weekly digest.
A live SharePoint audit digest from a representative Microsoft 365 tenant — the same format a customer receives each week. Top findings, severity breakdown, and the "what to fix first" rundown.