Skip to main content

Microsoft alignment

Kybera Impact extends Microsoft's governance and information-management services for operational scale, rather than replacing them. Two alignments matter most: Microsoft Purview for compliance content, and hub-and-spoke as the SharePoint architecture every workspace inherits.

Microsoft Purview​

Microsoft Purview remains your system of record for sensitivity labels, retention policies, adaptive scopes, and the rest of Microsoft's compliance surface. Kybera Impact makes Purview's intended outcomes operationally achievable at the scale your tenant operates at:

  • Templates apply Purview labels by default. Every workspace template specifies which retention and sensitivity labels apply. New libraries from the catalogue inherit them automatically. Compliance keeps them applied as workspaces evolve.
  • Adaptive scopes target Kybera Impact workspaces reliably. Every Kybera Impact-managed workspace carries predictable property bag values, so your Purview adaptive scopes can target workspace types accurately without enumerating sites manually.
  • Business Authority travels with the content. When the planned records-management module ships, the Business Authority metadata Kybera Impact captures at provisioning time becomes the spine for records routing.

What Kybera Impact doesn't do: content inspection, DLP, manual label application by end users. Those remain with Purview, exactly as Microsoft designed.

Hub-and-spoke architecture​

Hub-and-spoke is Microsoft's recommended SharePoint architecture for organizing related sites. Kybera Impact's workspace templates default to it from day one:

  • Every Kybera Impact workspace is associated with the right hub at provisioning time.
  • Navigation, branding, and search inherit from the hub automatically.
  • The two-track architecture (business-led spokes under business hubs, functional and records hubs as separate structures) is covered in the Adoption guidance.

Why your organization benefits​

  • One source of truth per concern. Purview owns labels. Entra owns identity. SharePoint admin owns tenant configuration. Kybera Impact reads from and writes to Microsoft's stores directly — no parallel system to keep in sync.
  • Your existing investments still count. Whatever your organization has invested in Purview, Entra, and Microsoft 365 governance, Kybera Impact builds on top of, not around.
  • Microsoft's roadmap is your roadmap. New Purview capabilities, new Microsoft 365 features — Kybera Impact uses them through the same APIs and services everyone else does.

Where this fits​

How it's built covers the Microsoft services the platform composes. Templates & the IM model covers what Kybera Impact inherits from Microsoft's information-architecture primitives.