The challenge

A recurring status report was a PowerPoint deck assembled by hand each month: numbers copied into charts and tables, long tables trimmed to fit, and no record of which figures a circulated deck came from.

The designer owns the template, people edit the decks they download, and everything had to run inside one SharePoint site with the narrowest permission available.

What we built

  1. Control towerSection owners submit figures
  2. Data fileOne source for every number
  3. .NET engineRuns as an Azure Function
  4. PowerPoint deckCharts, KPIs and tables filled in
How it fits together: Monthly report decks generated from data

A .NET 8 engine fills named shapes in a PowerPoint template from a data file: text, KPIs, status badges, native charts and tables. It runs as an Azure Function, a serverless cloud service, behind Microsoft Entra ID sign-in, with write access to one SharePoint site only.

A SharePoint control tower runs the monthly cycle. Section owners type, paste or import their figures, and the deck is generated once everyone has submitted. Long tables continue onto additional slides instead of being cut.

A PowerPoint add-in brings a downloaded deck up to date without touching slides it did not create. Charts update both their visible values and the data behind Edit Data. There is no AI in the generation process, so every figure traces back to its data.

Outcome

Deployed to a pilot site and in use, with pilot feedback driving refinements. The engine, the control tower and the add-in are each covered by automated tests.

Have a similar challenge?

Tell us about it, and we will tell you how we would approach it.