Feature: Excel / Power BI export of the capacity dataset

Start by reviewing the existing CSV collectors and HTML dashboard entry points to understand the available schemas and datasets. Define the consolidated workbook sheets for the SKU catalogue, quota, AKS, zonal, and quota groups data, and clarify whether the optional Power BI template is in scope. Done means an opt-in, local-only export is documented while the HTML dashboard remains the default.

Alignment with toolkit principles

• This stays read-only by default — it does not mutate Azure resources, or (if a write is essential) it follows the opt-in, -WhatIf/ShouldProcess pattern of Deploy-QuotaGroups.ps1.
• It works with Reader access for analysis (writes, if any, document their elevated roles).
• It introduces no telemetry and no data leaving the user's machine.

Problem / motivation

The dashboard is HTML-only. Many customers (and capacity-planning / finance teams) live in Excel
or Power BI and want to pivot, annotate and combine the data with their own. We already emit clean
CSVs, but there is no consolidated, relationship-ready export.

Proposed solution

Add an opt-in export path (read-only, local-only):

• A consolidated multi-sheet workbook (one sheet per dataset: SKU catalogue, quota, AKS, zonal,
  quota groups) generated from the existing CSVs — no new data collection.
• Optionally a Power BI template (.pbit) wired to the CSV schemas the collectors already produce.
• Documented as a post-processing step; the HTML dashboard remains the default.

Alternatives considered

• Tell users to import the raw CSVs themselves — works, but a curated workbook/template is far more
  useful and keeps schemas in sync.

Area

Dashboard / reporting, Documentation