How microsoft/powerbi-desktop-samples works
Project type and purpose
• This is not a traditional codebase but a “resource monorepo” for Microsoft Power BI. It bundles:
• Sample PBIX reports (Monthly Desktop Blog Samples, Sample Reports, service samples)
• JSON Schema definitions (Report Theme JSON Schema, item-schemas)
• A Performance Analyzer export tool
• DAX backups
• Contribution guidelines and telemetry settings
• Its purpose is to provide reference implementations, schema definitions, and tooling for Power BI developers and report authors.
File structure
• Top‐level modules:
• Monthly Desktop Blog Samples – PBIX files organized by month/year
• Sample Reports – curated PBIX demos for various domains
• new-power-bi-service-samples & powerbi-service-samples – additional PBIX/PBIT and Excel templates for Power BI Service
• Report Theme JSON Schema – JSON Schema files (v2.114–v2.142) + images for theming reports
• item-schemas – machine-readable definitions for Power BI artifacts (common config, dataset, report)
• DAX – backup DB (.bak) and PBIX for Adventure Works DW
• Performance Analyzer – PBIX report, schema, and documentation
• Root files for licensing, README, telemetry info, security policy, CLA integration
• No runtime services—this is a static content repo with schema artifacts and sample files.
README
• Describes contribution workflow (GitHub CLA-bot)
• Instructs disabling telemetry in Power BI Desktop
• Summarizes location and purpose of each sample folder
a. Main components:
• GitHub Repository (monorepo)
• Module directories (Samples, Schemas, Tools)
• Developer Machine
• Power BI Desktop application
• JSON Schema Validator (built into Power BI or external editor)
• Microsoft Telemetry Service
• GitHub CLA-bot
b. Relationships & data flow:
– Developer clones repo from GitHub -> local disk
– Developer opens PBIX in Power BI Desktop
– Power BI Desktop loads schemas from “Report Theme JSON Schema” & “item-schemas” when validating theme files or model definitions
– If enabled, Power BI Desktop sends usage data to Microsoft Telemetry Service
– Developer submits PR -> GitHub CLA-bot checks for CLA -> merges into repo
c. Architectural patterns & principles:
– Monorepo grouping by functional area (samples vs. schemas vs. tools)
– Separation of concerns: sample data, tooling, schema definitions
– Declarative artifacts (JSON Schemas) consumed by clients
– Static content delivery—no in-repo backend services
d. Key technologies/frameworks:
– Power BI Desktop (.pbix/.pbit files)
– JSON Schema (json-schema.org)
– Git/GitHub (CLA-bot integration)
– Telemetry via Power BI usage settings
Elements
• Clear labels on each module/directory grouping
• Git clone (GitHub Repo → Developer Machine)
• File access (Developer Machine → Power BI Desktop)
• Schema validation (Power BI Desktop ↔ JSON Schemas on disk)
• Telemetry (Power BI Desktop → Telemetry Service)
• PR workflow (Developer → GitHub Repo → CLA-bot → Repo)
• Blue for on-disk/static content
• Orange for user interactions
• Green for external SaaS/services
• Gray for automation scripts/bots