Skip to content

Insights

The Insights area of IMPACT 365 covers reporting, governance KPIs, and Teams activity—with planned extension to Teams archiving and disposal.

Teams activity reporting

IMPACT 365 can pull Teams activity data from Microsoft Graph (e.g. active users, channels, meetings) for a chosen period and store the results in a SharePoint list on the portal. This supports:

  • Understanding how Teams are used across the tenant.
  • Feeding activity metrics into reports or dashboards.
  • Historical snapshots when the operation is run on a schedule (e.g. weekly).

The operation is triggered via the workflow engine with the appropriate Resource and Operation; the payload can specify the reporting period (e.g. last 7, 30, 90, or 180 days).

SharePoint site usage

Site usage reporting fetches SharePoint site usage from Microsoft Graph and updates the provisioned-workspaces list with metrics such as:

  • Last activity date.
  • File counts, page views, storage.

This keeps your central list of workspaces in sync with usage so you can report on adoption and identify inactive sites. The operation is typically run on a schedule (e.g. weekly).

Workspace audit and KPIs

A workspace audit scans provisioned workspaces and computes governance KPIs for each site. Results are written to audit lists (summary, per-library, per-user) and the provisioned-workspaces list is updated with last audit date and status.

What the audit measures (high-level)

  • Permission health — Balance of owners vs members and prevalence of unique permissions.
  • Enterprise adoption — Use of IMPACT-managed (enterprise) libraries vs ad-hoc libraries.
  • Schema governance — Whether content types in enterprise libraries are still aligned with template (no unauthorized drift).
  • Activity and risk — Usage levels, concentration of content, and other risk indicators.

Each workspace gets a governance score and status (e.g. Green/Yellow/Red) plus findings that explain what to look at. The audit does not change site content; it only measures and records.

How it’s run

The audit is triggered via the workflow engine. It can be scheduled (e.g. weekly) or run on demand. Optional payload parameters can control batch size and how many consecutive failures stop the run.

Planned: Teams archiving and disposal

IMPACT 365 is planned to support Teams archiving and Teams disposal as part of the Insights/governance module. These will allow:

  • Archiving inactive or closed Teams in a controlled way.
  • Disposing of Teams and associated content according to policy and retention.

When these capabilities are released, they will be exposed as workflow operations (Resource/Operation) so they can be triggered from Power Automate or other processes. Documentation will be updated at that time.

What you can trigger via the workflow

  • Teams activity report — Resource/Operation for team activity report; payload can include period (D7, D30, D90, D180).
  • Site usage sync — Resource/Operation for site usage report; payload can include period.
  • Workspace audit — Resource/Operation for audit run; optional payload for batch size and failure limits.

See Adapter Registry for exact Resource and Operation values.

Next: Compliance — Workspace and repository compliance.