Power BI Theme Files: Enterprise Branding and Design Systems

<h2>Why Enterprise Theme Files Matter</h2>

<p>In large organizations with dozens of report developers and hundreds of published reports, visual inconsistency is a persistent problem. Without a centralized design system, each developer makes independent decisions about colors, fonts, borders, backgrounds, and formatting. The result is a portfolio of reports that look like they were built by different companies: some use the corporate blue, others use a slightly different shade; some use the approved font, others default to Segoe UI; some have dark backgrounds, others white. This inconsistency undermines the credibility of the analytics program and creates a poor user experience for stakeholders who navigate between reports.</p>

<p>Power BI theme files solve this problem at the platform level. A theme file is a JSON document that defines default visual properties for every report that uses it: data colors, background colors, fonts, text sizes, border styles, visual-specific formatting, and conditional formatting rules. When a developer applies the enterprise theme file, every visual they create automatically inherits the organization's design standards without manual formatting. This ensures brand consistency, reduces development time (developers spend less time formatting), improves accessibility (the theme can enforce accessible color contrast ratios), and creates a cohesive user experience across the entire report portfolio. Our <a href="/services/power-bi-consulting">Power BI consulting services</a> include enterprise theme development as part of every <a href="/services/power-bi-governance">Power BI governance</a> implementation.</p>

<h2>JSON Theme File Structure</h2>

<p>A Power BI theme file is a JSON document with a defined schema. The top-level structure contains metadata and formatting sections:</p>

<pre><code>{ "name": "Enterprise Corporate Theme", "dataColors": ["#0066CC", "#FF6600", "#339933", "#CC3333", "#9933CC", "#FF9900", "#006666", "#CC6699"], "background": "#FFFFFF", "foreground": "#333333", "tableAccent": "#0066CC", "maximum": "#0066CC", "center": "#FFCC00", "minimum": "#CC3333", "good": "#339933", "neutral": "#FFCC00", "bad": "#CC3333", "textClasses": { ... }, "visualStyles": { ... } }</code></pre>

<h3>Core Properties</h3>

<ul> <li><strong>name</strong>: The display name of the theme shown in the Power BI theme selector. Use a descriptive name that includes the organization and version (e.g., "Contoso Corporate Theme v2.3").</li> <li><strong>dataColors</strong>: An array of hex color values that Power BI assigns to data series in charts. The first color in the array is assigned to the first data series, the second color to the second series, and so on. Define at least 8 colors to cover most chart scenarios. These colors should be visually distinct, brand-aligned, and accessible.</li> <li><strong>background</strong>: Default page background color. Most enterprise themes use white (#FFFFFF) or a very light gray (#F5F5F5) for clean, professional appearance.</li> <li><strong>foreground</strong>: Default text color. Use dark gray (#333333) rather than pure black (#000000) for softer contrast that reduces eye strain.</li> <li><strong>tableAccent</strong>: The primary accent color used in table and matrix visuals for headers and grid lines.</li> </ul>

<h3>Semantic Colors</h3>

<p>Theme files define semantic color assignments that give meaning to colors across all visuals:</p>

<ul> <li><strong>maximum / minimum / center</strong>: Colors used in diverging color scales (heatmaps, conditional formatting). Maximum is typically the positive/high color, minimum is the negative/low color, and center is the midpoint.</li> <li><strong>good / neutral / bad</strong>: Colors used in KPI visuals and status indicators. The conventional mapping is green (#339933) for good, yellow/amber (#FFCC00) for neutral/warning, and red (#CC3333) for bad/critical. Ensure these colors maintain meaning for color-blind users by using icons or labels alongside colors.</li> </ul>

<h2>Data Colors: Building Your Palette</h2>

<p>The data color palette is the most visible element of your theme and the primary driver of brand consistency. Design your palette following these principles:</p>

<h3>Start with Brand Colors</h3>

<p>Extract 2-3 primary colors from the corporate brand guidelines. These become the first colors in the data color array, ensuring they appear most frequently in charts (the first series in any chart is the most prominent).</p>

<h3>Extend with Complementary Colors</h3>

<p>Add 5-6 complementary colors that harmonize with the brand palette and provide sufficient visual distinction between data series. Use color theory tools (Adobe Color, Coolors, or the Power BI theme generator) to create harmonious palettes. Avoid colors that are too similar to each other (e.g., two shades of blue that become indistinguishable in bar charts) or too similar to the background (e.g., light yellow on a white background).</p>

<h3>Test for Accessibility</h3>

<p>Every color in the data palette must meet minimum contrast requirements when displayed on the report background. For text elements, WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. For chart elements (bars, lines, points), ensure sufficient contrast against the chart background and against adjacent data series. Use tools like WebAIM's contrast checker or the Accessible Color Palette Builder to validate your palette.</p>

<h3>Test for Color Blindness</h3>

<p>Approximately 8% of men and 0.5% of women have some form of color vision deficiency. Test your palette using color blindness simulators (Color Oracle, Coblis, or the built-in simulator in Figma/Adobe tools). The most common issue is red-green confusion (deuteranopia/protanopia), which makes traditional red/green "bad/good" color coding ineffective for affected users. Solutions include using blue instead of green, adding patterns or icons alongside colors, and ensuring that color is never the sole means of conveying information.</p>

<h3>Example Enterprise Palette</h3>

<pre><code>"dataColors": [ "#0066CC", "#FF6600", "#339933", "#CC3333", "#9933CC", "#FF9900", "#006666", "#CC6699", "#336699", "#669900", "#993366", "#CC9933" ]</code></pre>

<h2>Font Configuration</h2>

<p>Power BI themes control typography through the <code>textClasses</code> property, which defines font families, sizes, and colors for different text categories:</p>

<pre><code>"textClasses": { "callout": { "fontSize": 28, "fontFace": "Segoe UI Semibold", "color": "#333333" }, "title": { "fontSize": 14, "fontFace": "Segoe UI Semibold", "color": "#333333" }, "header": { "fontSize": 12, "fontFace": "Segoe UI Semibold", "color": "#333333" }, "label": { "fontSize": 10, "fontFace": "Segoe UI", "color": "#666666" } }</code></pre>

<h3>Text Class Definitions</h3>

<ul> <li><strong>callout</strong>: Used for large numeric values in card visuals and KPIs. Typically the largest font size (24-32pt) in a bold or semibold weight.</li> <li><strong>title</strong>: Used for visual titles. Should be prominent but not overwhelming (12-16pt) in a semibold weight.</li> <li><strong>header</strong>: Used for column headers in tables and matrices. Slightly smaller than titles (10-14pt) in semibold weight.</li> <li><strong>label</strong>: Used for axis labels, legend labels, and data labels. The smallest text class (8-12pt) in regular weight with slightly muted color for reduced visual prominence.</li> </ul>

<h3>Font Selection Best Practices</h3>

<ul> <li><strong>Use web-safe fonts</strong>: Power BI renders reports in web browsers and the Power BI service. Fonts must be available on the rendering machine. Stick to fonts included with Windows and Microsoft 365: Segoe UI (the Power BI default and recommended choice), Arial, Calibri, Verdana, or Tahoma. Custom fonts will not render correctly in the Power BI service unless they are web-safe.</li> <li><strong>Maintain hierarchy</strong>: Use font size and weight to create clear visual hierarchy. Callout values should be significantly larger than titles, which should be larger than headers, which should be larger than labels. A clear hierarchy helps users scan reports efficiently.</li> <li><strong>Minimum font size</strong>: Never set font sizes below 8pt. Small text is difficult to read on standard monitors and impossible to read on mobile devices. For accessibility, 10pt is the recommended minimum for body text.</li> <li><strong>Consistent font family</strong>: Use the same font family across all text classes, varying only size and weight. Mixing font families (e.g., Segoe UI for titles and Arial for labels) creates visual noise without adding information.</li> </ul>

<h2>Visual Styles: Formatting Every Visual Type</h2>

<p>The <code>visualStyles</code> section is the most powerful and complex part of the theme file. It allows you to set default formatting properties for every visual type in Power BI. The structure follows a hierarchy:</p>

<pre><code>"visualStyles": { "*": { "*": { "general": [{ ... }], "background": [{ ... }], "border": [{ ... }], "title": [{ ... }] } }, "barChart": { "*": { "legend": [{ ... }], "categoryAxis": [{ ... }], "valueAxis": [{ ... }] } } }</code></pre>

<h3>Wildcard Selectors</h3>

<ul> <li><strong>\"*\" (first level)</strong>: Matches all visual types. Properties set here apply as defaults to every visual in the report.</li> <li><strong>\"*\" (second level)</strong>: Matches all sub-visual contexts. Most theme configurations use \"*\" at both levels to set universal defaults.</li> <li><strong>Specific visual type</strong> (e.g., \"barChart\", \"lineChart\", \"tableEx\", \"card\"): Override the wildcard defaults for a specific visual type.</li> </ul>

<h3>Common Visual Style Properties</h3>

<h4>Background and Border</h4>

<pre><code>"*": { "*": { "background": [{ "show": true, "color": {"solid": {"color": "#FFFFFF"}}, "transparency": 0 }], "border": [{ "show": true, "color": {"solid": {"color": "#E0E0E0"}}, "radius": 4 }], "visualHeader": [{ "show": false }] } }</code></pre>

<p>This configuration gives every visual a white background with a subtle gray border and rounded corners, and hides the visual header icons (the tooltip, filter, and focus mode icons that appear on hover). Many enterprise themes hide visual headers for a cleaner appearance and rely on toolbar-level interactions instead.</p>

<h4>Title Formatting</h4>

<pre><code>"title": [{ "show": true, "fontColor": {"solid": {"color": "#333333"}}, "fontSize": 14, "fontFamily": "Segoe UI Semibold", "alignment": "left" }]</code></pre>

<h4>Card Visual Styling</h4>

<pre><code>"card": { "*": { "labels": [{ "fontSize": 28, "fontFamily": "Segoe UI Semibold", "color": {"solid": {"color": "#0066CC"}} }], "categoryLabels": [{ "fontSize": 12, "fontFamily": "Segoe UI", "color": {"solid": {"color": "#666666"}} }] } }</code></pre>

<h4>Table and Matrix Styling</h4>

<pre><code>"tableEx": { "*": { "grid": [{ "gridVertical": false, "gridHorizontal": true, "gridHorizontalColor": {"solid": {"color": "#F0F0F0"}}, "gridHorizontalWeight": 1, "rowPadding": 4 }], "columnHeaders": [{ "fontColor": {"solid": {"color": "#FFFFFF"}}, "backColor": {"solid": {"color": "#0066CC"}}, "fontSize": 11, "fontFamily": "Segoe UI Semibold" }], "values": [{ "fontColor": {"solid": {"color": "#333333"}}, "backColor": {"solid": {"color": "#FFFFFF"}}, "fontSize": 10, "fontFamily": "Segoe UI" }], "total": [{ "fontColor": {"solid": {"color": "#333333"}}, "backColor": {"solid": {"color": "#E8E8E8"}}, "fontSize": 10, "fontFamily": "Segoe UI Semibold" }] } }</code></pre>

<p>This table configuration creates a clean, modern look: horizontal grid lines only, branded column headers with white text on the corporate blue, and alternating row colors through the row padding and background settings.</p>

<h2>Conditional Formatting in Themes</h2>

<p>While conditional formatting rules themselves are configured per-visual rather than in theme files, themes establish the color foundation that conditional formatting uses:</p>

<h3>Diverging Color Scales</h3>

<p>The <code>maximum</code>, <code>center</code>, and <code>minimum</code> theme properties define the default colors for diverging conditional formatting scales. When a user applies a color scale to a table column, Power BI uses these theme colors as defaults. Setting these consistently ensures that all color scales across all reports use the same color language.</p>

<h3>Status Colors</h3>

<p>The <code>good</code>, <code>neutral</code>, and <code>bad</code> properties define the default colors for KPI status indicators and icon sets. Standardizing these colors means that "green" always means the same shade of green across all reports, and "red" is always the same red. This consistency is critical for user comprehension when switching between reports.</p>

<h3>Custom Conditional Formatting Classes</h3>

<p>For advanced scenarios, use the theme to define custom colors that report developers reference in conditional formatting rules. Document these colors in the theme's style guide so that developers know to use, for example, \"#FFF3CD\" for warning backgrounds and \"#F8D7DA\" for error backgrounds, rather than choosing their own shades.</p>

<h2>Accessibility in Themes</h2>

<p>Enterprise themes must be accessible to users with visual impairments, including color vision deficiency and low vision. Accessibility is not optional; it is a legal requirement under Section 508 (US federal), ADA (US), and EN 301 549 (EU).</p>

<h3>Color Contrast Requirements</h3>

<p>WCAG 2.1 Level AA contrast requirements apply to Power BI reports:</p>

<ul> <li><strong>Text elements</strong>: Minimum 4.5:1 contrast ratio for normal text (below 18pt), 3:1 for large text (18pt+ or 14pt bold)</li> <li><strong>Non-text elements</strong>: Minimum 3:1 contrast ratio for chart elements (bars, lines, data points) against the chart background</li> <li><strong>Interactive elements</strong>: Minimum 3:1 contrast ratio for interactive controls (slicers, buttons) against their background</li> </ul>

<p>Validate every color combination in your theme against these ratios. Common failures include light colors on white backgrounds (light yellow, light cyan), low-contrast text (gray text on light gray background), and chart series that are indistinguishable at low contrast ratios.</p>

<h3>Color-Blind Safe Design</h3>

<ul> <li><strong>Avoid red-green reliance</strong>: Do not use red and green as the primary distinction between data categories. Instead, use blue and orange, or vary both hue and lightness so that categories remain distinguishable in grayscale.</li> <li><strong>Use patterns and shapes</strong>: Where possible, combine color with patterns (hatching, dots) or shapes (different marker shapes in scatter plots) so that color is not the sole differentiator.</li> <li><strong>Label directly</strong>: Use data labels on charts rather than relying solely on legend color matching. Direct labels eliminate the need for users to match colors between the legend and the chart.</li> </ul>

<h3>Accessibility Testing</h3>

<p>Test themes with the Power BI Accessibility Checker (available in Power BI Desktop), screen readers (Narrator, NVDA, JAWS), and color blindness simulators. Document the accessibility compliance status of the theme and include it in the theme distribution package.</p>

<h2>Built-in Theme Gallery</h2>

<p>Power BI Desktop includes a gallery of built-in themes that serve as starting points for customization:</p>

<ul> <li><strong>Default</strong>: The standard Power BI color scheme (blue-toned, Segoe UI font). Clean and professional but generic.</li> <li><strong>City park</strong>: Natural greens and earth tones. Suitable for environmental, sustainability, or outdoor-themed reports.</li> <li><strong>Classroom</strong>: Warm yellows and reds. Suitable for education or creative industry reports.</li> <li><strong>Color blind safe</strong>: Specifically designed palette that maintains distinction for users with color vision deficiency. An excellent starting point for accessible themes.</li> <li><strong>Electric</strong>: Vibrant, high-contrast colors on dark backgrounds. Eye-catching for presentations but may not suit everyday operational dashboards.</li> <li><strong>High contrast</strong>: Maximum contrast theme for users with low vision. Useful as a secondary theme that users can switch to when needed.</li> <li><strong>Sunset</strong>: Warm oranges and purples. Distinctive but may clash with corporate brand colors.</li> <li><strong>Twilight</strong>: Cool blues and purples on a dark background. Modern, visually striking, but requires careful contrast management for text readability.</li> </ul>

<p>To use a built-in theme as a starting point: apply the theme, then export it as a JSON file (View &gt; Themes &gt; Current theme &gt; Export current theme). Edit the exported JSON to replace built-in colors and fonts with your corporate standards.</p>

<h2>Creating Custom Themes</h2>

<h3>Method 1: Power BI Theme Editor (No-Code)</h3>

<p>Power BI Desktop includes a visual theme editor accessible through View &gt; Themes &gt; Customize current theme. This editor provides a graphical interface for modifying colors, text, and visual defaults. The editor is suitable for simple themes but does not expose all available theme properties. Export the result as JSON for further refinement.</p>

<h3>Method 2: Direct JSON Editing</h3>

<p>For full control, create and edit theme files directly in a text editor or IDE (VS Code is recommended for JSON editing with schema validation). Start with an exported built-in theme or a template, then modify properties according to your requirements. Validate the JSON syntax before importing to Power BI (VS Code highlights syntax errors automatically).</p>

<h3>Method 3: Theme Generator Tools</h3>

<p>Several community tools generate Power BI theme JSON files from visual inputs:</p>

<ul> <li><strong>Power BI Theme Generator</strong> (powerbi.tips): Upload your logo or enter brand colors, and the tool generates a theme JSON file with complementary data colors.</li> <li><strong>Themes.report</strong>: Visual theme builder with live preview and export to Power BI JSON format.</li> </ul>

<h3>Theme Development Workflow</h3>

<ol> <li><strong>Gather brand guidelines</strong>: Obtain the corporate style guide with primary colors, secondary colors, approved fonts, and logo usage rules.</li> <li><strong>Define the data color palette</strong>: Map brand colors to the data color array, adding complementary colors as needed. Test for accessibility and color blindness.</li> <li><strong>Configure text classes</strong>: Set font families, sizes, and colors for callout, title, header, and label text. Verify readability at all sizes.</li> <li><strong>Set visual defaults</strong>: Configure background, border, title, and specific visual type properties in the <code>visualStyles</code> section.</li> <li><strong>Test with sample reports</strong>: Apply the theme to representative reports covering different visual types (charts, tables, cards, maps, KPIs) and verify that all visuals render correctly and consistently.</li> <li><strong>Conduct accessibility review</strong>: Test contrast ratios, color blindness simulation, screen reader compatibility, and keyboard navigation.</li> <li><strong>Document the theme</strong>: Create a style guide showing the color palette with hex values, typography hierarchy, sample visual screenshots, and usage instructions.</li> <li><strong>Version and distribute</strong>: Assign a version number, publish to the distribution channel (see deployment strategies below), and communicate availability to report developers.</li> </ol>

<h2>Advanced Theme Properties</h2>

<h3>Page-Level Properties</h3>

<p>Themes can set default page-level formatting:</p>

<pre><code>"visualStyles": { "page": { "*": { "background": [{ "color": {"solid": {"color": "#F5F5F5"}}, "transparency": 0 }], "wallpaper": [{ "color": {"solid": {"color": "#EEEEEE"}} }] } } }</code></pre>

<p>The <code>background</code> property sets the page canvas color (the area where visuals are placed), while <code>wallpaper</code> sets the color of the area outside the page canvas (visible when the page is not filling the entire browser window).</p>

<h3>Slicer Styling</h3>

<p>Slicers are one of the most visible interactive elements in reports. Theme-level slicer styling ensures consistent filter UI:</p>

<pre><code>"slicer": { "*": { "general": [{ "outlineColor": {"solid": {"color": "#0066CC"}}, "outlineWeight": 1 }], "data": [{ "fontSize": 10, "fontFamily": "Segoe UI", "fontColor": {"solid": {"color": "#333333"}} }], "selection": [{ "selectAllCheckboxEnabled": true, "singleSelect": false }], "header": [{ "show": true, "fontColor": {"solid": {"color": "#333333"}}, "fontSize": 12, "fontFamily": "Segoe UI Semibold" }] } }</code></pre>

<h3>Tooltip Styling</h3>

<p>Custom tooltip pages inherit theme settings, but default tooltips can also be influenced through theme properties to maintain brand consistency in hover interactions.</p>

<h3>Button Styling</h3>

<p>Power BI buttons (navigation buttons, bookmarks, action buttons) can be styled through themes to maintain consistent interactive element appearance across reports.</p>

<h2>Theme Deployment Strategies</h2>

<p>Creating a theme is only half the challenge; ensuring consistent adoption across the organization requires a deployment strategy:</p>

<h3>Strategy 1: Shared File Location</h3>

<p>Store the theme JSON file in a shared location accessible to all report developers (SharePoint document library, OneDrive shared folder, Teams channel files, or a Git repository). Developers download and import the theme when starting new reports. This is the simplest approach but relies on developer discipline and does not automatically update existing reports when the theme changes.</p>

<h3>Strategy 2: Power BI Template Files (.pbit)</h3>

<p>Create a Power BI template file that includes the enterprise theme, standard page layouts, common slicers, and placeholder visuals. Developers start every new report from this template, ensuring consistent design from the beginning. Templates are more comprehensive than theme files alone because they include layout and structural elements in addition to formatting. Maintain templates in version control and distribute through a shared file location or internal tool catalog.</p>

<h3>Strategy 3: Organizational Theme (Fabric/Premium)</h3>

<p>In Microsoft Fabric and Power BI Premium environments, administrators can set an organizational default theme through the admin portal. When enabled, every new report created in the tenant automatically uses the organizational theme. Users can still switch themes on individual reports, but the default ensures that the corporate theme is the starting point. This is the most effective deployment strategy for ensuring adoption at scale.</p>

<h3>Strategy 4: Git Integration and CI/CD</h3>

<p>For organizations using Git integration with Power BI (available in Fabric), store theme files in the Git repository alongside report definitions. Include theme validation in the CI/CD pipeline to ensure that all reports reference the approved theme and that the theme file passes accessibility checks before deployment. This approach provides version control, change tracking, and automated quality checks for the design system.</p>

<h3>Strategy 5: Power BI REST API Deployment</h3>

<p>Use the Power BI REST API to programmatically apply themes to published reports. This enables bulk theme updates: when the theme is revised, a script can apply the new theme to all existing reports in specified workspaces. This is useful for theme migrations (updating from v1 to v2 across hundreds of reports) but requires careful testing since theme changes may affect visual layout.</p>

<h2>Maintaining Brand Consistency at Scale</h2>

<h3>Governance Framework</h3>

<p>Include theme compliance in your <a href="/services/power-bi-governance">Power BI governance</a> framework:</p>

<ul> <li><strong>Mandatory theme usage</strong>: Require all published reports to use the enterprise theme. Include theme validation in the report certification process.</li> <li><strong>Theme versioning</strong>: Maintain a version history of the theme file. Use semantic versioning (v2.1.3) so that developers know when breaking changes occur vs. minor updates.</li> <li><strong>Change management</strong>: When updating the theme, communicate changes to all developers, provide a migration guide for any breaking changes, and allow a transition period before requiring the new version.</li> <li><strong>Exception process</strong>: Define a process for requesting theme exceptions (e.g., a client-facing report that must use the client's brand colors). Exceptions should be documented and approved by the design system owner.</li> </ul>

<h3>Style Guide Documentation</h3>

<p>Publish a comprehensive style guide that accompanies the theme file:</p>

<ul> <li><strong>Color palette</strong>: All data colors and semantic colors with hex values, RGB values, and intended usage.</li> <li><strong>Typography</strong>: Font families, sizes, and weights for each text class with examples.</li> <li><strong>Visual examples</strong>: Screenshots of each visual type (bar chart, line chart, card, table, matrix, map, KPI) formatted with the theme, showing correct usage.</li> <li><strong>Layout guidelines</strong>: Recommended page layouts, visual spacing, alignment grids, and responsive design patterns.</li> <li><strong>Accessibility requirements</strong>: Minimum contrast ratios, color-blind safe practices, alt-text requirements, and tab order guidelines.</li> <li><strong>Do/Don't examples</strong>: Common formatting mistakes and their corrections.</li> </ul>

<h3>Theme Maintenance Cadence</h3>

<p>Review and update the enterprise theme on a regular cadence:</p>

<ul> <li><strong>Minor updates (monthly)</strong>: Bug fixes, additional visual type styling, performance improvements.</li> <li><strong>Major updates (quarterly or semi-annually)</strong>: New color additions, font changes, significant visual style overhauls aligned with brand guideline updates.</li> <li><strong>Breaking changes (annually or as needed)</strong>: Changes that may affect the layout of existing reports (font size changes, border changes, background color changes). Communicate well in advance and provide migration support.</li> </ul>

<h2>Complete Enterprise Theme Example</h2>

<p>Below is a production-ready theme file demonstrating the key properties discussed in this guide. Customize the colors, fonts, and properties to match your organization's brand guidelines:</p>

<pre><code>{ "name": "Enterprise Corporate Theme v1.0", "dataColors": [ "#0066CC", "#FF6600", "#339933", "#CC3333", "#9933CC", "#FF9900", "#006666", "#CC6699", "#336699", "#669900", "#993366", "#CC9933" ], "background": "#FFFFFF", "foreground": "#333333", "tableAccent": "#0066CC", "maximum": "#0066CC", "center": "#FFCC00", "minimum": "#CC3333", "good": "#339933", "neutral": "#FFCC00", "bad": "#CC3333", "textClasses": { "callout": { "fontSize": 28, "fontFace": "Segoe UI Semibold", "color": "#0066CC" }, "title": { "fontSize": 14, "fontFace": "Segoe UI Semibold", "color": "#333333" }, "header": { "fontSize": 12, "fontFace": "Segoe UI Semibold", "color": "#333333" }, "label": { "fontSize": 10, "fontFace": "Segoe UI", "color": "#666666" } } }</code></pre>

<p>This example provides the foundation. Extend it with the <code>visualStyles</code> section to configure specific visual type defaults as shown in the earlier sections of this guide.</p>

<p><a href="/contact">Contact EPC Group</a> to develop a comprehensive Power BI design system for your organization. Our <a href="/services/power-bi-consulting">Power BI consulting</a> team creates enterprise theme files, style guides, report templates, and governance frameworks that ensure brand consistency, accessibility compliance, and professional visual quality across your entire Power BI report portfolio. We help organizations move from ad-hoc report formatting to a structured design system that scales with your analytics program and integrates with <a href="/services/power-bi-governance">Power BI governance</a> and <a href="/services/microsoft-fabric">Microsoft Fabric</a> deployment workflows.</p>